BSOD Can't Return to Desktop from Sleep

sbuxman · 13 Feb 2015

Tuesday, FEB 10, pressed the ESC key to bring my system out of sleep and was greeted with the BSOD, "Windows was shut down to prevent further damage." Was told to restart IF the BSOD screen was a first-timer, which it was. Restarted with no errors until reaching the desktop where I was greeted with the error message, "windows has recovered from a serious error...details of the problem are listed below."

Attached is the zip file requested in the opening notes of this forum, and below is a link to a Microsoft MVP's findings about the issue based on the codes in the "details of the problem are listed below" message found on the screen per the above paragraph. This link was provided by the Dell tech who attempted to resolve the issue, but his "fix" (NOT the MVP's) is questionable because this morning the sound of my system trying to unsuccessfully come out of sleep was enough to wake me...the system would just continue to make the sound heard as it begins to come out of sleep, but it could not do so this morning. Heard instead was the recycling sound of each new attempt, unsuccessful, in a loop. And the only way to turn off the computer was to pull the plug from the tower, which I did. After several minutes, I attempted to boot by plugging the power cord back into the back of the tower, but only a grey screen became visible and boot stopped. Holding down the on/off key until the system again shut down, waiting, then restarting a second time finally gave me the desktop.

It was time to upload the attached .zip and start a new thread as instructed in the Forum Rules here.

Thank you!

sbuxman

https://social.technet.microsoft.com/Forums/windowsserver/en-US/4649ac0c-e599-4be7-89bc-c3e672c9cde2/random-bsods-involving-intelppmsys

Arc · 13 Feb 2015

There is a stray crash dump which is almost silent about the probable cause. A stop 0x7E is very wide in its scope. For a branded desktop of almost 4 years, the bugcheck is critical.

First let us see some basic info about your computer before we start troubleshooting.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU installed there.

After having these two information, we may frame our troubleshooting plan.
_______________________________________________

Code:

BugCheck 1000007E, {ffffffffc0000096, fffff8800486714c, fffff880033773e8, fffff88003376c40}

Probably caused by : intelppm.sys ( intelppm!SetPerformanceEnergyBiasPolicy+8 )

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

sbuxman · 13 Feb 2015

The computer is not hot...I'm not aware of any difference in temp and I feel confident that I would as the tower is very close to me and I've experienced a hot case before when there was a problem (not my system).

Speccy snapshot of my system specs:

Page missing

Installed PSU is genuine Dell 460 watts.

PSU Wattage Calculator

jpeg of wattage summary attached (mistakenly identified as "temperature"

sbuxman · 13 Feb 2015

Speccy Summary, one more time...

Arc · 14 Feb 2015

The primary things are seeming to be right. Now we may take some basic hardware tests.

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.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us.

Stress test the CPU.

Hardware - Stress Test With Prime95

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Let us know the results. Also make it sure that you have all (taking the optional one out of the scope) windows updates installed; and post any further BSOD.