BSOD every time coming back to computer after several hours

Kilo413 · 15 Sep 2012

Hello all,

I recently performed a clean install of windows 7 home premium (64) on my Asus G74SX laptop. I have been plagued by BSOD issues that seem to appear every time I'm away from my computer for more than a few hours. Whenever my computer shows the "resuming windows" screen, it inevitably ends up in BSOD. It is not limited just to that though. If not enough time has elapsed for the computer to go into hibernation mode, and it's only been untouched long enough to lock automatically, it still BSODs. (when I come back, I see that it's on the enter password screen and it freezes shortly after I move the mouse).

When I click check for solutions, there is no response. It just closes the window and nothing happens.

I tried installing my drivers slowly over a few days.. one at a time. It all seemed to be going well, and if I changed something to start making the BSODs happen, I'm not sure what it was. I can't pinpoint the cause to any one issue, so if I need to reinstall windows I'm fine with that.

Thanks for your time and help.

koolkat77 · 15 Sep 2012

Welcome

Your dumps do not provide any probable cause.

The dump does not provide any information so lets enable driver verifier to rule out buggy drivers.

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Driver Verifier - Enable and Disable

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Capt.Jack Sparrow said:

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Kilo413 · 15 Sep 2012

I followed the instructions for enabling verifier, but how can I tell if it's running? After restarting my PC, I can see no noticable difference in its performance. Also, you said it might take 24h for verifier to do it's thing.. isn't it possible that my computer will crash on it's own(not because of verifier) the next time I leave my computer? I'm concerned that I won't be at my computer long enough for a verifier-induced crash since it crashes on it's own every time I leave.

koolkat77 · 15 Sep 2012

If you have done everything on the tutorial it should be running now.
You need to keep it for 36 hours

Kilo413 · 16 Sep 2012

BSOD upon returning to my computer this morning. I moved the mouse and my enter password screen popped up and froze about 1 second later. About 10 seconds later the screen went black and then turned off, about 10 seconds later the blue screen popped up. Here's the dump info, I'm not sure if it's going to provide any more information. I'll keep verifier running in the meantime

Kilo413 · 17 Sep 2012

Here's the latest crash log

koolkat77 · 17 Sep 2012

Your dump shows NFTS file system error that are causing some effects on the hard drive

Suggestions:

-Reseat the sata and power.
-Run chkdsk /f/r, following the option two of the tutorial Disk Check
-Seatool for dos: SeaTools | Seagate download
-Burn it in a blank cd. boot from the CD, click on "Accept", wait for it
to finish detecting the drives, then in the upper left corner select
"Basic Tests", then select "Long Test" and let it run.

Let us know the results

Kilo413 · 17 Sep 2012

Do you know which hard drive it is? I have two HDs, a 160GB Solid state drive and a 750GB traditional disk drive. Would the error be coming from the drive that the OS is installed on?(The SSD)?

koolkat77 · 17 Sep 2012

Kilo413 said:

Do you know which hard drive it is? I have two HDs, a 160GB Solid state drive and a 750GB traditional disk drive. Would the error be coming from the drive that the OS is installed on?(The SSD)?

It should be the hard drive where windows is installed.
You should also check for a firmware update for your SSD.

Kilo413 · 17 Sep 2012

I ran chkdsk, I walked away from the computer and when I came back it had restarted... so I'm not sure what the results were.

I tried running the Seatool DOS, it refused to find any of my hard drives. I let it sit for 10 minutes but nothing popped up. I tried restarting and nothing popped up the 2nd time either.

I opened up my laptop and re-seated the SSD.

I'm in the process of finding new firmware for it now.