The STOP 0xC2 error (BAD_POOL_CALLER) fault can occur on Windows XP, Windows Vista, Windows Server 2003, Windows 7, Windows Server 2008, and Windows Server 2008 R2 and in almost all cases it indicates you have bad memory. I get tons of feedback that it’s very useful. This is by far the most popular hit on my website even 5+ years later. I didn’t notice it last night but Microsoft has a memory test utility (on a bootable CD-ROM image no less) at. Hopefully this will help others with STOP 0xC3 errors: it could be a memory failure.
This box doesn’t really need 1.5GB of memory so if I get new memory for it, it will be to replace the existing good DIMMs (“Spectek“ brand) with a different high-quality brand just to be safe. I put the 2 DIMMs that tested OK in the system and rebooted into W2K3. So I took that DIMM out and tried the next one. I powered down the system, removed all 3 DIMMs (512MB each), and plugged one in, restarted the system and Memtest started. Within minutes I had burned a bootable CD with Memtest86 3.1a on it, booted the CD in the system, and saw mucho memory errors fly across the screen!
So a quick Google Bing search for “memory tester” came up with Memtest86.
#Blue screen memory management faulty ram software
I haven’t touched the software on this system for weeks, so I strongly suspected some sort of memory failure.
#Blue screen memory management faulty ram how to
In fact, this KB Article shows how to debug the memory dump file to determine the faulty driver.īooting the system into safemode resulted in a memory write fault in explorer.exe. Rebooting the computer caused a chkdsk and then the system came up…and promptly blue screened again.Īccording to this doc page on, the 0x07 parameter indicates “Attempt to free a memory pool that was already freed.” Further Google Bing searches indicated that this type of error is usually due to a faulty device driver. However any modern version of Microsoft Windows including Windows XP, Windows Vista, Windows 7, and Windows 8 can experience this problem. In my case, the computer was running Windows Server 2003.
The good news is RAM is relatively inexpensive and very easy to replace. You can easily test the memory in your computer with the built-in memory tester built into Windows. In almost all cases the STOP 0xC2, BAD_BOOL_CALLER blue-screen indicates failed or failing RAM (random access memory) in your computer. See the details below, but the summary is: This post describes what happened and how you can figure out if this is why you are getting this error. I discovered the reason was some memory chips had failed. My computer bluescreened with a STOP 0xC2, BAD_POOL_CALLER fault.