BSOD on wake from sleep, BCcode 19 - Bad Pool Header

[Maytangerines]

This has been happening to me for awhile now. When my computer wakes from sleep, it will work perfectly fine for a little while until it seemingly randomly BSODs for no reason. This never happens if I don't put it into sleep.

Here are the parameters:
BCCode: 19
BCP1: 0000000000000020
BCP2: FFFFF8A011B63330
BCP3: FFFFF8A011B63410
BCP4: 00000000050E0211

I've attached my SF diagnostic tool report to this post as well.

Thank you

 

[HarriePateman]

Welcome to SevenForums, Please fill in your system specs

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="Blue"]BugCheck 19[/COLOR], {20, fffff8a011b63330, fffff8a011b63410, 50e0211}

GetPointerFromAddress: unable to read from fffff800032f9100
GetUlongFromAddress: unable to read from fffff800032f91c0
Probably caused by : [COLOR="Red"]fltmgr.sys ( fltmgr!DoFreeContextMemory+6b )[/COLOR]

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

:ar: BCCode: 19 0x00000019

That could be drivers although antivirus/antispyware/security programs and other hardware
are also probable causes. Updating the major drivers and BIOS would be the best plan of
attack. If needed also try uninstalling your antivirus/security as a test.

Please Fill out your system specs and i will be able to help you further.

 

[Maytangerines]

Thanks for the help thus far! I've filled out my system specs, I apologize about that. [:

 

[HarriePateman]

Okay brilliant, lets start troubleshooting.

Firstly i would like to check if all your drivers are okay:

:ar: Enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

 

[Maytangerines]

I followed those instructions and got hit by an instant BSOD when trying to start windows. Something about IO management and the code was a 0xc9

EDIT: I've attached the associated minidump

 

[HarriePateman]

Okay so that tells us that a driver is failing.

Please can you upload the DMP File.

 

[Maytangerines]

I just uploaded the file in my last post, I apologize for the delay in doing so.

 

[HarriePateman]

No worries

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23b, fffff880050d4ae0, fffff9800bebee10, 0}

*** WARNING: Unable to verify timestamp for [COLOR="red"]chdrvr03.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]chdrvr03.sys[/COLOR]
Probably caused by : chdrvr03.sys ( chdrvr03+2ae0 )

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

Okay so the driver that failed:

chdrvr03.sys :ar: CH Products joysticks (and other flight-sim related controllers)

Downloads and Community CH Products, Sales Network

 

[Maytangerines]

Wow! I am seriously impressed with your skills. I'll try updating the drivers for the joystick and rerun the verifier. [:

 

[HarriePateman]

Wow! I am seriously impressed with your skills. I'll try updating the drivers for the joystick and rerun the verifier. [:

Thank you Brilliant let me know how it goes

 

[Maytangerines]

Unfortunately, updating the driver didn't resolve the issue. However, I did try running the verifier without any CH drivers selected and, though I didn't get a BSOD, when it tried to start Windows the screen went black and the computer rebooted.

I've attached both dumps. 6988 is the black screen dump, 6318 is the BSOD dump.