Fatal Error Messages 0x0140 and 0x0240 (12244)
The information in this article applies to:
- Microsoft Windows Software Development Kit (SDK) 3.0
- Microsoft Windows Software Development Kit (SDK) 3.1
This article was previously published under Q12244 SUMMARY
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.
| Modification Type: | Major | Last Reviewed: | 3/15/2004 |
|---|
| Keywords: | kb16bitonly KB12244 |
|---|
|