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:
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...
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...