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

teven0855 · 03 Jul 2016

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

**axe0** · 03 Jul 2016

I would like it.

teven0855 · 03 Jul 2016

Attached.

**axe0** · 03 Jul 2016

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 · 04 Jul 2016

5.01 results attached. No errors over 8 passes.

**axe0** · 04 Jul 2016

teven0855 said:

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 · 04 Jul 2016

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** · 04 Jul 2016

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 · 04 Jul 2016

see attached pictures

**axe0** · 05 Jul 2016

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.