Device Driver Has Corrupted The Executive Memory Pool
Andrea Falconieri S Mp3 more. If you receive an error message which reads: Windows error 'Device Driver has corrupted the executive memory pool., it basically means that there is a corruption with a driver somewhere on your system. This issue can occur when an attempt to touch invalid memory at a process IRQL that is too high occurs. This is almost always caused by drivers that have corrupted the system pool. The number one cause for this problem is overwriting the end of a memory buffer; this overwrites the pool header for the NEXT block of memory.
If you receive an error message which reads: Windows error 'Device Driver has corrupted the executive memory pool., it basically means that there is a corruption with. Nokia Pc Suit. Server reboots or blue screening I am. 0x8046cda6 A device driver has corrupted the executive memory. Has corrupted the executive memory pool.
Try figuring out the driver that is suspect and running it with driver verifier enabled – that will catch the corruption at the time it occurs rather than later when the system touches the next block. To resolve this issue, run the Driver Verifier tool against any new (or suspect) drivers, and if that does not locate the problem, use gflags to turn on the Special Pool feature. Windows kernel-mode graphics drivers (such as printer and display driver DLLs) are restricted from calling the pool entry point directly. Rather, pool allocations are performed indirectly using graphics device driver interface (DDI) callbacks to Win32k.sys. For example, EngAllocMem is the callback that a graphics driver calls to explicitly allocate pool memory. Also, other specialized callbacks such as EngCreatePalette and EngCreateBitmap return pool memory. To provide the same sort of automated testing for the graphics drivers, support for some of the Driver Verifier functions is incorporated into Win32k.sys.