BSOD when going out of sleep

[Daniol71]

I just did a fresh install of Windows 7 on my Asus K70IJ. Everything works as it should (even hibernation) except for sleep mode. The laptop will go to sleep and come out of sleep without any problems. But upon login in the "Welcome" page will keep loading for 1-2 minutes and then I will get the BSOD for about half a second and then the laptop reboots and asks me if I want to start normally or in safe mode etc.

I have installed all the drivers available for the laptop from the Asus support page. None had any effect on the problem except for the Intel Matrix Storage Manager. After installing that, the laptop would come out of sleep and go almost straight into BSOD. I would see the blue screen for about 2 seconds and then I would be back to choosing Safe mode etc.

My BIOS is on the latest version available. I reset it to factory defaults but it didn't fix the problem.
I even made another fresh install of Windows 7 but it still didn't help. I applied all the Windows Updates available.

I hope one of you can help me, especially since I haven't been able to pinpoint the source of the problem yet.

NOTE: I installed Win7 on a completely new Kingston SSD. Previously the laptop was running Win8 on another drive. I don't know if that could be the source of the problem.

 

[Thedoctor44]

Follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[Daniol71]

Hi, sorry about that, here's the zip

 

[Thedoctor44]

There are no dump files, check in these directories.

C:/Windows/minidump

C:/Windows/memory.dmp

Small Memory Dumps or Minidumps can be copied to the desktop, zipped up then uploaded directly here.

Kernel Memory Dumps on the other hand are too large to upload directly here.

you must upload the new dump file to a file sharing website like OneDrive.
The new dump file will be located in C:/Windows/memory.dmp.

 

[Daniol71]

Yeah it said something like "can't find specified path" when I ran DM Log Collector. I'll try to upload them manually.

 

[Daniol71]

Alright, I'm having a problem, I figured I had to make Windows create these memory dumps, so I followed the instruction for kernel memory dump from here http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html however, I still can't find memory.dmp

 

[Thedoctor44]

So there are no dump files under both directories?

I'm struggling to understand the exact problem.

 

[Daniol71]

Yep, no dump files at all, even after I followed the instructions to make Windows create them.

 

[Thedoctor44]

You might need to wait for another BSOD.

You can try this but it's a bit a gamble whether or not it will work.

Enable driver verifier but only enable the options: Standard settings and IRP logging step 3.
Don't enable Force Pending I/O Requests

Enable Driver Verifier to monitor the drivers.
Driver Verifier -Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

We use Driver Verifier as it puts a stress on the drivers, and so it makes the unstable drivers crash. This should flag the driver responsible in the dump file.
It

Driver Verifier will make the system laggy, this is normal so don't worry.

Before enabling DV, make sure that you have earlier System restore points made in your computer.

If there are no points, make a System Restore Point Manually

Post back the results.

 

[Daniol71]

Well, the problem isn't making the BSOD appear. I can pretty much do it on demand since it happens EVERY SINGLE TIME I wake the device from sleep. However, as I said, it only appears for less than half a second. Maybe not enough time for the system to make a dump?

I'll run driver verifier and report back with the results, thanks for your help

 

[Thedoctor44]

follow the instruction before on how to change the dump files, but just untick the automatic restart option.

 

[Daniol71]

Great, that made the BSOD stay on. It still doesn't seem to create a memory dump however. By the way, the technical detail is: STOP 0x000000F4 (and then a lot of numbers in brackets. Driver Verify didn't do anything btw.

I'll get back to you when I have more details. Hope this helps so far.

 

[Thedoctor44]

The technical detail means nothing with 0xF4.
I need the dump files.
Without them I can't do much, it can be hardware related but due to the nature of the crash (only when waking up) it looks driver related.

Display drivers can cause these problems.
I'm on my mobile so I can't look at your other files.
You could try updating it if you haven't already.

 

[Daniol71]

I'll try updating the display drivers, but I think they're on the latest version. I'm really annoyed that Windows can't seem to create the dump files. How long am I supposed to leave it in BSOD for it to save the dump data?

 

[Golden]

Are you using CCleaner or other cleaning/optimising tools? They have a nasty habit of deleting .dmp files.

 

[Daniol71]

No, I used to run that on Win8, but this is a fresh install of Win7 and I haven't installed anything on it except for all the Windows Updates needed (and Chrome, but the problems were already there before Chrome).

When I get BSOD it says "Collecting data for crash dump..." and "Initializing disk for crash dump..." at the bottom, but it's as if it never manages to write anything to the disk.

 

[Daniol71]

Is there a command I can type in terminal to make my laptop sleep in Safe Mode? That way I could see if it's related to third party drivers.

 

[Golden]

How long are you waiting between the BSOD happening and cold booting the computer? Did you set it to create a minidump or kernel dump?

Driver Verifier is the only way I know to trap the offending driver....I suggest trying that again.

 

[Daniol71]

I've tried both minidump and kernel dump. After BSOD appears I wait between 5-10 minutes before pressing the power button to turn off the laptop.

I've tried driver verifier and it did nothing, but I guess that I need to run it longer maybe?

 

[Golden]

Run Driver Verifier for a minimum of 24hrs, or until the next BSOD. Whilst running DV, continue using the computer as normal.