Repeated BSODs, 0x000000C2, BAD_POOL_CALLER. No idea what is causing this and Google isn't helping.

avalonbright

Distinguished
Nov 3, 2011
12
0
18,510
So I used to be getting those 0x000000C5 BSODs and absolutely no idea what's causing them. The past two days though now the code is 0x000000C2 with "BAD_POOL_CALLER." This seems to be related to trying to allocate memory that's either already in use or doesn't exist, and I have no idea WHY it's doing this.

Adding to how infuriated I am to keep coming back from AFK to this, my system STILL is not making any minidumps. Out of all the BSODs I've had it has made a single arbitrary minidump that has not helped me even remotely. Now I'm stuck with this error, an error that seems to suggest numerous bad things, and I'm stuck fumbling around in the dark.

I've run numerous hard drive scans to no avail, nothing wrong. Last night I did a full six-pass run of memtest86 because RAM issues were coming up with 0x000000C2, and still nothing. 0 errors. I'm at my complete wits' end here and I'm losing my mind being unable to figure out what on earth is going on.

As for the minidump issue, the closest causes I'm finding are "None of your recent crashes have been written to file or even recognized by Windows. There are a number of reasons that this might happen: Hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems." Yet I've run system file checker (multiple times), chkdsk (twice), HDDScan (twice), memtest (1 pass then 6 passes), and literally every single thing comes up clean. I'm pulling my hair out.

The only thing I haven't done yet is followed the following steps of uninstalling Intel RST:
5b. Change the IDE configuration for the Serial ATA Controller from 'RAID' to 'IDE'.

5c. Save changes and exit the system BIOS setup.

But I don't think that'd be an issue with this. I'm not in a RAID setup in the first place, and I've never used RST in my life.

And no, I don't have TrendMicro, weird antivirus software, or anything else but MSE, so those Google results aren't helping either. Someone please say they have some kind of idea as to what is going on with this thing... I'm almost tempted to just nuke and pave but I'm afraid it's a hardware issue still even though both hdd and ram keep coming up clean...
 

avalonbright

Distinguished
Nov 3, 2011
12
0
18,510
Would that matter if zero errors came up? I'd imagine that's only a problem if you have memtest errors and something came up since it needs narrowed down. But 0? Wouldn't that imply neither sticks nor slots are bad?

I mean you'd think I'd be willing to try anything at this point but our house is set up in such a way that repeatedly unplugging everything, dragging the case to another room entirely, opening it up, swapping RAM around, closing it up, bringing it back in to the other room, plugging it all back in, and running memtest for who knows how long, well... Ugh. That and I'm on 4x 2GB, so I'd need to do ALL OF THAT for every single stick in every single slot...
 
It's your call. Just so you know, testing all the modules at once doesn't always work right. You can get zero errors even if there's a bad module. I don't know why or how, but I've seen it. It's more accurate to test the modules individually.

Checking the SATA setting can help. However, it shouldn't matter what it is set to so long as it is kept on the same setting that Windows is installed with. I'd like to say that it can't hurt to change it if that's what the instructions say, but I can't make a guarantee on that. I just leave mine set to AHCI most of the time.
 

avalonbright

Distinguished
Nov 3, 2011
12
0
18,510
Well, unfortunately I did what Intel said to do and tried setting things back to IDE. ...And then I got an instant blue screen that informed the Boot Disk could not be found. Lovely. I set it back to RAID and it system restored, at least. But apparently even following Intel's instructions on getting rid of their RST business ... don't work.