BSOD after waking up the machine from sleep state

ommbeu · 14 Apr 2014

Hi everybody!

I'm new here and please excuse me in advance if I post a message the wrong way.

A friend of mine has an almost new desktop PC on which he has installed Windows 7 Ultimate x64 SP1.
From time to time he gets the BSOD after waking the machine from sleep state or the machine only restarts (while waking up) and the message appears the the system was not cleanly shut down. A few times in the middle of working (web browsing, using word processor...) the computer also get BSOD and restarted itself. The machine was never overclocked.

The system is fully updated and we have tried to change some of the configuration parameters of Power options. Most exactly we have changed the setting "Allow hybrid sleep" from ON to OFF but we haven't noticed any improvements.

We have updated the BIOS of MB to the last version, but we have no luck.
We have also run some other test for hardware testing:
-memtest 86+ for RAM: run over night about 10 times with no errors
-HD test with DataLife Diagnostics from WD: no errors
-run checkdisk (chkdsk): no errors
-run Stress test with prime95: the TEMP increased from about 30 0C to over 72 0C in about 5 minutes - then we have stopped the test because we were afraid to overheat the CPU. Even though the system was stable. Maybe this is the cause of our problem?

Moreover I have cloned the system partition, formatted the partition and done a fresh install of Windows 8.1 Pro (first installed win 8 and then upgraded to 8.1 Update 1). No other software were installed except MS Office 2010. After three days the system while it was waking up from sleep state restarted itself (no BSOD) and in the Event viewer we found a similar critical message of kernel-power event than in win 7. So I have restored back to win 7 and the problems continue.

I have also tried to enable the driver verifier now in win 7. After that I have only noticed that the system started up a bit slowly and also every program that I started it started a bit slowly - no other visible problems.

Today I have run the DM Log Collector and attached the results.

System specifications:
MB: Gigabyte GA B85-HD3, rev 1.0 with latest BIOS - F6
CPU: Intel i5 4440
RAM: 8GB
HD: 1T WD
GRAPHIC: nVidia GeForce GT 640 + Intel HD 4600

I have no idea where to look for problems so I hope that somebody could help us.
Best regards.

Arc · 17 Apr 2014

Hi ommbeu.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

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.
_________________________________

Code:

BugCheck C1, {fffff98020790ec0, fffff98020790147, b7c140, 23}

Probably caused by : memory_corruption ( nt!MiCheckSpecialPoolSlop+9a )

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

Code:

BugCheck A, {fffffb80071fe0e8, 2, 1, fffff80002f04fc4}

Probably caused by : memory_corruption ( nt!MiComputeFlushRange+2cc )

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

ommbeu · 17 Apr 2014

Hi!

First of all thank you for your response!

Today I have done the memtest86+ again with no errors (see attached picture).

Now I have enabled driver verifier. In the configuration settings I have enabled the option "Automatically select all drivers installed on this computer"(see attached pictures) instead "Select drivers names from list". The computer starts normally, but as I wrote in the first post everything works a bit slowly (no crashes until now).

I have done both those test already before with no errors (as I wrote in my first post). When one time the driver verifier was enabled (for 3 days), the computer (while it was waking up from sleep state) only restarted with no BSOD. Unfortunately I can't provide any information of that event because at that point I have formatted the system and installed Win 8.1 for a few days to see if it is more stable (but the problem was similar in Win 8.1 - the second day the system restarted while it was waking up from sleep state).

I really don't know what to think about, but for me it is very strange that both Win 7 & 8.1 suffer the same problem. I'm more in favor of hardware problem that software problem, but I can't prove it.

The only bad thing that I can prove is the temperature of CPU after 5min of stress test with Prime95 (see attached picture) where it reaches 73 0C - at that point I stopped the stress test.

I will wait for the next crash with DV enabled and I will post the DM Log Collector info again.
Thank you for your help.

Best regards.

Arc · 17 Apr 2014

Driver verifier makes the computer laggish on purpose. Still work on it ... try to perform the most crash prone tasks to reproduce the BSODs.

ommbeu · 24 Apr 2014

Hi!

After a week of DV enabled the computer has not crashed. I have tried all the possible scenarious to reproduce the BSOD but it didn't happen. I do not know what to think about?

Now I have disabled DV and I will return the PC to my friend to see what will happen. If BSODs will start to appear I will post new DM Log Collector data here.

For now thank you for your time and help.

Arc · 24 Apr 2014

Its OK, let us know the situation. :)

ommbeu · 30 Apr 2014

Hi!

Here we go again. After returning the PC to my friend the PC crashed again in about a week. The DV was disabled and we have changed the setting "Allow hybrid sleep" from ON to OFF and changed the power profile so that the computer goes into hibernation instead to sleep. The computer crashed after it was coming out from hibernation (see attached screenshot picture of the error message).

I have also attached the results of DM Log Collector after the crash (again the DV was disabled).
Hope someone get's an idea what is going on?

Best regards

Arc · 30 Apr 2014

Hi ommbeu.

Though no crash dump is there in the zip, but the screenshot says it all.

Hibernate etc are for portable computers (laptops, notebooks, netbooks) those run on stored power; so aggressive power conservation policy is needed there, to secure the battery charge for long. This philosophy is not completely applicable for a desktop PC. But the OS have the option.

Disable hibernate. Hibernate - Enable or Disable
Only display timeout settings are enough for desktops. You will not loss anything by doing it. But, the issue will not occur anymore.

ommbeu · 01 May 2014

Hi!

Thanks for a quick reply. I partially agree with you - I agree that the option to hibernate or sleep was mainly developed for portable devices. But it should also apply for desktop PCs. I have seen a lot of "modern" desktop PCs (with Win 7 & 8) that have power profiles with enabled hibernation or sleep by manufacturer. And a lot of people like this, because when they come back (they turn on the PC after it has gone to hibernation/sleep) they found their workplace as it was left before - sleep state is especially practical (and let's say "safe") if you have UPS.

I will tell my friend to disable the hibernation and see if crashes still occurs. I will post again here if the system will crash (and hopefully get BSOD).
Thanks again for your time.

Best regards