A Device Driver Has Corrupted The Executive Memory Pool
Came home today to find my Northpoint DSL shutoff (thanks, Ameritech mad ) and my Win2k Server machine blue-screened with this: STOP: 0x000000c5 (0xc0472684, 0x00000002, 0x000000000, 0x8046712F). A device driver has corrupted the executive memory pool. Address 8046712F base. A common error encountered by Microsoft Windows users when trying to read or write from a drive, disk, or portable media device is the I/O device error.
The DRIVER_CORRUPTED_EXPOOL bug check has a value of 0x000000C5. This indicates that the system attempted to access invalid memory at a process IRQL that was too high. Important Information If You Have Received a STOP Code If you have received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer.
If you purchased Windows separately from your computer, Microsoft provides support. To find contact information for Microsoft or your computer manufacturer,. David Robertson Driver Manager.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article. The following actions might prevent an error like this from happening again: • Download and install updates and device drivers for your computer from Windows Update. • Scan your computer for computer viruses. • Check your hard disk for errors. DRIVER_CORRUPTED_EXPOOL Parameters The following parameters are displayed on the blue screen.
Parameter Description 1 Memory referenced 2 IRQL at time of reference 3 0: Read 1: Write 4 Address that referenced memory 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 small allocation (less than PAGE_SIZE). Larger allocations result in (DRIVER_CORRUPTED_MMPOOL). 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. Bug_Check: C5 0x000000C5 Memory - find Memory Diagnostics tool at top of list - Right Click - RUN AS ADMIN follow the instructions Windows Vista: How to Scan / Test your RAM or Memory with Windows Vista Memory Diagnostic Tool How to Run the Memory Diagnostics Tool in Windows 7 Test Your Computer’s Memory Using Windows Vista Memory Diagnostic Tool Hope this helps.
Hi everyone, We have a Windows 2000 Server with ISA Server on it. National Priority Programs Afghanistan Language here. Primarily it is a proxy server but it is also a domain contoller. In the last week it has blue screen of death'd on me 5 times. It starts to do a memory dump and give the error address as 8046B4B5 at base 80400000 - ntoskrnl.exe. I am wondering if it is a problem with one of the memory sticks, a while ago someone told me of a website where you can put in you bsod error message and get a more meaningful translation.
Does anyone have an idea of what might be wrong or know the address of this website? Any help greatly appreciated. Nothing in event viewer sheds light?!?! RE: Blue screen of death (IS/IT--Management) 9 Oct 03 05:40. Hi sorry for the delay, the error was 0x000000c5 (0x00008400, 0x00000002, 0x00000000, 0x8046b4b5) and it said 'The device driver has corrupted the executive memory pool check to make sure any new hardware or software is installed properly, check windows 2000 updates, run driver verifier, try enabling special pool.'
We haven't added any hardware of software for at least 9 months and the machine is fully service packed up. I ran windows driver verifer and it crashed completley. I have restarted in safe mode and disabled driver verifier, don't know how long the machine will work for?? Does this code mean anything to anyone, thankyou Lindsay.