Win7 x64 Resume from Sleep results in STOP 0x19 Error

After waking my 64-bit Windows 7 PC from sleep mode, after a few seconds it changes to a BSOD with a STOP 0x19 error. I had read that this could have been caused by iolo System Mechanic Pro (not System Mechanic) being installed. After throughly removing this application, I restarted, then tried to Sleep then Wake the PC and the BSOD occurred. Not a huge issue, but it prevents me from being somewhat green by not running my 1 kW system 24 x 7 x 365. Any ideas as to what causes the STOP error?
 

Question Info


Last updated March 15, 2018 Views 1,444 Applies to:
Answer
Answer

Bugcheck 0x19 is BAD_POOL_HEADER - this indicates memory corruption is occurring, and could be caused by a bad/incompatible driver, or faulty hardware such as RAM.  

Are the bugcheck codes always the same? For memory corruption such as this, turn on verifier as described below and upload a dump when you have a bugcheck, after enabling verifier.

General guidance for dealing with bluescreens follows:

 

Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

Also consider running SFC /SCANNOW.

It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings->Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog.

Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

Wait for a bugcheck to occur after enabling verifier as described, and then upload it to you SkyDrive and provide a link.

If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules.

Other common suggestions include ensuring drivers are up to date (including video drivers), as well as ensuring that you're using the latest BIOS.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.