Solved BSOD upon wake from sleep (0x7A, 0xF4)

[teven0855]

Hey all,

Recently I've run into a problem where, upon resuming from sleep, I receive a blue screen. It usually appears after entering my login information and hitting enter. Other times, I will proceed to the desktop before the crash appears. Turning off the computer and back on does not result in this blue screen.

These blue screens are either 0x7A (KERNEL_DATA_INPAGE_ERROR) or 0xF4 (CRITICAL_OBJECT_TERMINATION; with a parameter of 0x3 - process). Furthermore, the minidump step never completes - it hangs on "initializing disk..."

My research on this site and other sites has lead me to try the following ideas before posting here myself:

• Backup of files, imaged hard drive
• chkdsk /f /r
• sfc /scannow
• SeaTools Basic Tests
• MemTest
• Removing programs from startup
• S.M.A.R.T disk test
• CrystalDiskInfo

All of these do not return any issues with the hard drive or RAM.

I have attached the "DM log collector" results as a .zip file. Any help would be greatly appreciated.

 

[axe0]

Please provide more details of the tests:

• upload the chkdsk log :ar: http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html ,
• post a screenshot/photo of SeaTools of the long generic test,
• what memory test did you run, for how long/how many passes?
• what are the details of the smart disk test?

 

[teven0855]

Please provide more details of the tests:

• upload the chkdsk log :ar: http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html ,
• post a screenshot/photo of SeaTools of the long generic test,
• what memory test did you run, for how long/how many passes?
• what are the details of the smart disk test?

• chkdsk results attached in chkdskresults.txt
• final results of SeaTools long generic attached
• I ran MemTest86 for 4 runs. Furthermore, the memory is quite new. I replaced it after this problem started to occur (not related, the timing worked)
• See attached wmic output and CrystalDiskInfo output

 

[axe0]

New memory does not mean it is not at fault and the performed test is not per our recommendation, but for now we can leave the memory for what it is

I would need to see a BSOD dump, or at least a photo of the BSOD screen, because I need to know what value parameter 2 from the 0x7A is to get a better indication of possible causes.

 

[teven0855]

I would need to see a BSOD dump, or at least a photo of the BSOD screen, because I need to know what value parameter 2 from the 0x7A is to get a better indication of possible causes.

I have attached a picture of the BSOD.

New memory does not mean it is not at fault and the performed test is not per our recommendation, but for now we can leave the memory for what it is

I just started up MemTest86 to do 8 passes instead of 4!

 

[axe0]

The parameter indicates a I/O error, I'll wait for the memtest result for a next suggestion

You do run MemTest86+ I hope.

 

[teven0855]

The parameter indicates a I/O error, I'll wait for the memtest result for a next suggestion

You do run MemTest86+ I hope.

Yes, I ran MemTest86+! I ran it for over 11 passes, no errors.

 

[axe0]

Please fill in your system specs

Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.
How to fill in your system specs:

 

[teven0855]

Please fill in your system specs

System Specs have been filled in via the System Info tool.

 

[axe0]

Yes, I ran MemTest86+! I ran it for over 11 passes, no errors.

Normally a picture of the result is requested, but for now it is not required.

Could you please open your laptop and check if the cable connecting the hard drive is properly connected, or let someone more experienced do it.

 

[teven0855]

Yes, the cable is seated properly. I do have a picture of the MemTest86+ result if you would like.

 

[axe0]

I would like it.

 

[teven0855]

Attached.

 

[axe0]

Please run the updated version 5.01

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Forums

   Note

MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

[teven0855]

5.01 results attached. No errors over 8 passes.

 

[axe0]

Yes, the cable is seated properly. I do have a picture of the MemTest86+ result if you would like.

How did you check it? Did you reconnect it or only check if it was properly connected?

 

[teven0855]

I disconnected the hard drive and plugged it into another computer to eliminate the possibility of error on the hard drive connection or hard drive itself. I plugged another hard drive into the laptop's cable to eliminate the possibility of error with the cable. Both worked fine. Then I reconnected the hard drive that I have issues with and it works fine until sleep mode is activated.

 

[axe0]

Alright, I would like to go hunt for bad drivers but first I would like to make sure the system files are fine

Diagnostics Test

 System File Check

Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow says "Windows Resource Protection found corrupt files but was unable to fix some of them" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

Make a photo of the result and post it.

 

[teven0855]

see attached pictures

 

[axe0]

Lets see if we can force a BSOD dump now

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.