BSOD Usually on Wake From Sleep

Brucex64 · 28 Mar 2015

Ever since I built my new computer (with all new parts) and installed Windows 7 Pro I've been getting random BSODs from time to time, and they tend to happen when I push the sleep button on my keyboard to come out of sleep mode. When it does this, it never wakes up. I'll hear the CPU & drive spin up but the screen will stay black for a couple seconds, then it will simply shut down and turn off. I'll have to hit the power button to start again and it'll always start, leaving a windows message saying windows has recovered from an unexpected shutdown. Another time it happened just after I came out of sleep and got back into Windows. The first thing I did was open my browser (firefox) and then I got the BSOD. I'd say it took less than 30 seconds after waking when I got the BSOD. A few times I can come out of sleep and get into some work but it'll go BSOD on me within minutes. And the error code is usually different most times!

It never happens while the computer is up, or if I'm working on something. It also never happens if I shut down all programs prior to entering sleep mode. So, I don't know if its hardware or windows related. It does not happen EVERY time I put it into sleep but frequently. All my dump files are in the zip file.

I have done a memory test using memtest and it passed ok. BIOS is updated, and I've taken all the GeForce video card driver updates. I don't know what else to try so I'm looking for some help.

Arc · 31 Mar 2015

Hi Brucex64.

There are various multiple BSODs with various probable causes.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, 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

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

*** Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs. And without doing it, Driver Verifier will not go updo desktop.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus.
Apply > OK
Accept then restart.

Brucex64 · 01 Apr 2015

I followed the instructions for DV and when it rebooted, I got BSODs right away before going into windows. It would not boot up. so I booted into safe mode, disabled DV, then booted back into win7 and created a new zip file from DM log collector which should have the new dump info.

Arc · 01 Apr 2015

Gigabyte Easy Saver - mobo power utility driver.

Code:

BugCheck C4, {f6, 328, fffffa800c455b30, fffff880095bc879}

*** WARNING: Unable to verify timestamp for gdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for gdrv.sys
Probably caused by : gdrv.sys ( gdrv+1879 )

Followup: MachineOwner
---------

You should not have installed it at the first place. Dont install anything other than the drivers from the driver CD bundled with the motherboard. Those gigabyte craps may ruin a windows install beyond repair.

I'd recommend you to Clean Up Factory Bloatware, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

Brucex64 · 02 Apr 2015

I'm going to kill some of my startup programs. Do you think it would work to also uninstall the Gigabyte Application Center, which has the mono apps?

Arc · 02 Apr 2015

Brucex64 said:

I'm going to kill some of my startup programs.

Why some? Disable all other than the antivirus. None is required there.

Brucex64 said:

Do you think it would work to also uninstall the Gigabyte Application Center, which has the mono apps?

That's an obvious.

Brucex64 · 02 Apr 2015

Well, I've got a few that I think should stay - for example, Crashplan Tray (I use the Crashplan cloud backup which is always running in the background); Colorvision Startup (colorvision.exe) - I used a Spider to color profile my monitor so don't I need that to run? It tells me the profile is loaded into the video card when I boot up. I'm not sure what else it does though. I use Roboform for password management, so that starts & always runs; Google Drive Sync - at times I do pull items from my Google Drive so having it sync would be helpful. There's intellitype pro & Setpoint - don't those have the settings for the kbd & mouse?

Safepstbackup is another startup item I use for backing up Outlook. And Rainmeter - I have that application on my desktop for monitoring my system so it starts up at boot time.

Arc · 02 Apr 2015

Rainmeter may stay there.

All the others you may have access anytime form start > all programs.

Brucex64 · 04 Apr 2015

Well, today I got another BSOD upon wake. This time, the bug check code & string is 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA

Do you think this is a RAM issue? I tried to run memtest again but it takes a VERY long time it only made 3 passes in 4 hours; I could leave it on again tomorrow when I go to work to see if I can get 8 passes. After 3 passes there were no errors however.

Golden · 04 Apr 2015

Brucex64 said:

if I can get 8 passes. After 3 passes there were no errors however.

As Arc explained, you must run a minimum of 8 consecutive passes - any less is a waste of time.