DRIVER_CORRUPTED_MMPOOL

Code: 0xd0 (208)

As HRESULT:As NTSTATUS:

Parameters

ParameterDescription
1Memory referenced
2IRQL at time of reference
3

0: Read

1: Write

4Address that referenced memory

Description

The DRIVER_CORRUPTED_MMPOOL bug check has a value of 0x000000D0. This indicates that the system attempted to access invalid memory at a process IRQL that was too high.

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Cause

The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. The ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.

In most cases, this bug check results if a driver corrupts a large allocation (PAGE_SIZE or larger). Smaller allocations result in bug check 0xC5 (DRIVER_CORRUPTED_EXPOOL).

Resolution

If you have recently installed any new software, check to see if it is properly installed. Check for updated drivers on the manufacturer's website.

To debug this error, use the special pool option of Driver Verifier. If this fails to reveal the driver that caused the error, use the Global Flags utility to enable the special pool by pool tag.

For information about the special pool, consult the Driver Verifier section of the Windows Driver Kit.

An alternate method is to open the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management registry key. In this key, create or edit the ProtectNonPagedPool value, and set it equal to DWORD 1. Then reboot. Then the system will unmap all freed nonpaged pool. This will prevent drivers from corrupting the pool. (This does not protect the pool from DMA hardware, however.)

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

ModuleCodeFound inDescription
EventCreate.exe0xd078.11011%1
KernelBase.dll0xd078.1The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.
dsreg.dll0xd011Failed to get NGC transport key name . Falling back to software.
kernel32.dll0xd078.11011The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified.
nslookup.exe0xd078.11011*** ls: error receiving zone transfer:
webservices.dll0xd078.11011There was an error listening on the TCP socket.
6 entries