Solved Random BSOD, need help identifying driver

[TheTrueWingman]

I was getting constant BSODs back in March (MEMORY_MANAGEMENT, paging errors, etc), and eventually identified the problem as a faulty stick of RAM. I got it replaced and thought the problem would be solved.

Since I installed the new RAM modules (I wasn't using my PC during the RMA process, because I didn't have a temporary replacement), I have been getting BSODs (IRQL_NOT_LESS_OR_EQUAL, DRIVER_CORRUPTED_XPOOL) that are likely due to driver issues, but they always point to ntoskrnl. It's probably obvious from my dump files, but the error almost always occurs at the stack address: ntoskrnl.exe+72a40. A few days ago, I did an error check on my C: drive, although I'm not entirely sure of the results, because I started it before I went to bed and it had rebooted to my desktop by the time I got up. In the log files, there should be a break in the crashes between 4/20 and today, the days after the disk check, when the BSODs stopped (until today).

The most recent crash (BAD_POOL_HEADER) happened during my first attempt at creating this account was caused by win32k.sys.

 

[Arc]

4 BSODs within 5 hours with 4 different bugchecks and 4 different probable causes.

I would prefer to test the RAM before doing anything else.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
___________________________________________________

BugCheck 19, {3, fffff880029601c0, fffff880009601c0, fffff880259601c0}

Probably caused by : win32k.sys ( win32k!DrvEnumDisplayDevices+290 )

Followup: MachineOwner
---------

BugCheck A, {fffff8800d9fc718, 2, 1, fffff800036c2a68}

Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSendToExecutionQueue+788 )

Followup: MachineOwner
---------

BugCheck C5, {180000000e0, 2, 0, fffff800037abaab}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )

Followup: Pool_corruption
---------

BugCheck 24, {1904fb, fffff8800d6e9fe8, fffff8800d6e9840, fffff800036a3801}

Probably caused by : memory_corruption ( nt!MmMapViewInSystemCache+71 )

Followup: MachineOwner
---------

 

[TheTrueWingman]

Alright, I was hoping that wouldn't be the most likely issue. Luckily, I still have my memtest drive from the last set.

 

[TheTrueWingman]

Yep, that was the problem, failed near the end of the 2nd pass. Looks like I'm doing another RMA.

Thanks for the help.

 

[Arc]

Yep, that was the problem, failed near the end of the 2nd pass. Looks like I'm doing another RMA.

Thanks for the help.

Another?

 

[TheTrueWingman]

Yep, that was the problem, failed near the end of the 2nd pass. Looks like I'm doing another RMA.

Thanks for the help.

Another?

Yep, the RAM I was using currently is the new set after I sent back the original set in March. That's why I had assumed it wasn't faulty RAM.

After my previous post, I took out one stick and did 4 full passes with just one. I didn't get any errors with that one, so I'm just leaving the other one out for the time being. Luckily, it has a lifetime warranty, so I'm only out the cost of shipping. Still a huge pain, of course.

And, before you ask, I did already test for a faulty connector on the MB. The working ones work on both slots, and the failing ones fail on both slots.

 

[Arc]

And, before you ask, I did already test for a faulty connector on the MB. The working ones work on both slots, and the failing ones fail on both slots.

Pure bad luck, mate! Hope this time you will get some good RAMs.