Bug Check 0x1A: MEMORY_MANAGEMENT
The MEMORY_MANAGEMENT bug check has a value of 0x0000001A. This indicates that a severe memory management error occurred.
MEMORY_MANAGEMENT Parameters
The following parameters are displayed on the blue screen. Parameter 1 is the only parameter of interest; this identifies the exact violation.
| Parameter 1 | Cause of Error |
|---|---|
|
0x1 |
The fork clone block reference count is corrupt. (This only occurs on checked builds of Windows.) |
|
0x31 |
The image relocation fix-up table or code stream has been corrupted. This is probably a hardware error. |
|
0x403 |
The page table and PFNs are out of sync . This is probably a hardware error, especially if parameters 3 & 4 differ by only a single bit. |
|
0x411 |
A page table entry (PTE) has been corrupted. Parameter 2 is the address of the PTE. |
|
0x777 |
The caller is unlocking a system cache address that is not currently locked. (This address was either never mapped or is being unlocked twice.) |
|
0x778 |
The system is using the very last system cache view address, instead of preserving it. |
|
0x780 0x781 |
The PTEs mapping the argument system cache view have been corrupted. |
|
0x1000 |
A caller of MmGetSystemAddressForMdl* tried to map a fully-cached physical page as non-cached. This action would cause a conflicting hardware translation buffer entry, and so it was refused by the operating system. Since the caller specified "bug check on failure" in the requesting MDL, the system had no choice but to issue a bug check in this instance. |
|
0x1010 |
The caller is unlocking a pageable section that is not currently locked. (This section was either never locked or is being unlocked twice.) |
|
0x1233 |
A driver tried to map a physical memory page that was not locked. This is illegal because the contents or attributes of the page can change at any time. This is a bug in the code that made the mapping call. Parameter 2 is the page frame number of the physical page that the driver attempted to map. |
|
0x1234 |
The caller is trying lock a nonexistent pageable section. |
|
0x1235 |
The caller is trying to protect an MDL with an invalid mapping. |
|
0x3451 |
The PTEs of a kernel thread stack that has been swapped out are corrupted. |
|
0x5003 |
The working set free list is corrupt. This is probably a hardware error. |
|
0x5100 |
The allocation bitmap is corrupt. The memory manager is about to overwrite a virtual address that was already in use. |
|
0x8884 |
(Windows 7only). Two pages on the standby list that were supposed to have identical page priority values do not, in fact, have identical page priority values. The differing values are captured in parameter 4. |
|
0x8888 0x8889 |
Internal memory management structures are corrupted. |
|
0x888A |
Internal memory management structures (likely the PTE or PFN) are corrupted. |
|
0x41283 |
The working set index encoded in the PTE is corrupted. |
|
0x41284 |
A PTE or the working set list is corrupted. |
|
0x41286 |
The caller is trying to free an invalid pool address. |
|
0x41785 |
The working set list is corrupted. |
|
0x41287 |
An illegal page fault occurred while holding working set synchronization. Parameter 2 contains the referenced virtual address. |
|
0x41790 |
A page table page has been corrupted. On a 64 bit version of Windows, parameter 2 contains the address of the PFN for the corrupted page table page. On a 32 bit version of Windows, parameter 2 contains a pointer to the number of used PTEs, and parameter 3 contains the number of used PTEs. |
|
0x41792 |
A corrupted PTE has been detected. Parameter 2 contains the address of the PTE. Parameters 3/4 contain the low/high parts of the PTE. |
|
0x61940 |
A PDE has been unexpectedly invalidated. |
|
0x61946 |
The MDL being created is flawed. This almost always means the driver calling MmProbeAndLockPages is at fault. Typically the driver is attempting to create a Write MDL when it is being asked to process a paging Read. |
|
0x03030303 |
The boot loader is broken. (This value applies only to Intel Itanium machines.) |
|
Other |
An unknown memory management error occurred. |
