Fatal Error Messages 0x0140 and 0x0240

Last reviewed: July 22, 1997
Article ID: Q12244

3.00 3.10 WINDOWS kbprg

The information in this article applies to:

Microsoft Windows Software Development Kit (SDK) for Windows versions 3.0 and 3.1

The FatalExit messages "Local heap is busy" (0x0140) and "Critical section problems" (0x0240) indicate internal errors in Windows's memory management routines; 0x0140 indicates an incorrect attempt to enter or leave a critical section in the local memory manager; 0x0240 indicates that the total number of free handles doesn't match up.

These errors shouldn't occur unless something gets destroyed; this is usually an indication that an application is destroying memory by writing to an area where it shouldn't.

Additional reference words: 3.00 3.10 rip dgroup
KBCategory: kbprg
KBSubcategory: KrMm
Keywords : kb16bitonly

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.