Previously working STANDBY now crashes everytime invoked..

By generatorlabs ·
I am at my wits end with a problem on my desktop PC. This PC has been functioning for a very long time flawlessly. I would routinely send the PC into standby and later return from standby with no issues. I don't know what happened but it does not work anymore. When I press the sleep button on my computer it closes the desktop and then says "preparing for Standby" and just sits there forever. So I am seeking a bit more knowledge on what happens behind the scenes when Standby is invoked.

1) Is there a tool I can use to monitor exactly what process is not shutting down?
2) Is there a log that is used as well?
3) I have pretty much shut down all processes looking for the culprit using Sysinternals Process Explorer. There is no hardware other than a video card in the AGP slot. The sound is outboard via firewire. I have disabled it in my troubleshooting.
4) I have scoured the internet for similar problems and have done the recommended procedures at the microsoft website regarding "Standby crashes".

At this point I know a full re-install will remedy this. However I think I gain more if I fix it and learn from it. I just need the tools or the guidance to point me in the right direction. Any suggestions truly appreciated.


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

A couple of checks

by Jacky Howe In reply to Previously working STANDB ...

You will need to check the Bios Power settings and look for settings like this and make sure that it is enabled.
S3 Suspend to RAM (Sleep)
Common BIOS entry Keys
F1 <br>
F2 <br>
DEL <br>
ESC <br>
F10 <br>
You will know when to press this key when you see a message similar to the below example as the computer is booting. Some older computers may also display a flashing block to indicate when to press the F1 or F2 keys. Some newer computers may not display it at all so see the tip below.
Press <F2> to enter BIOS setup
Tip: Hold a Key down, this will cause a stuck key error, which may allow you to enter the BIOS setup remember to save the settings if you have made any changes.
Log on to the computer as an administrator.
Check the Event Logs for errors and the <b>Event ID</b> which can be used to track down the problem. The Error is in the right hand pane. To get the information double click on the Error and when it opens click on the Icon that is under the Up/Down arrows and it will be copied to the Clipboard and can be pasted into Notepad.
Click Start and right click on <b>My Computer</b> and click <b>Manage</b>
Click on the <b>+ sign</b> next to Event Viewer to expand it.
Left click on <b>Application</b> to highlight it.
Left click on <b>System</b> to highlight it.
<b>Here is an Example</b>
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event I 10005
Date: 1/06/2008
Time: 7:56:52 AM
User: AMBO\Rob
Computer: AMBO
Product: Microsoft Network Monitor 3.1 -- The installer was unable to configure automatic updates. Visit http://update.microsoft.com to get updates for Microsoft Network Monitor and other Microsoft products.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0000: 7b 42 44 46 38 32 30 46 {BDF820F<br>
0008: 33 2d 37 39 41 36 2d 34 3-79A6-4<br>
0010: 41 43 46 2d 42 39 31 30 ACF-B910<br>
0018: 2d 34 33 42 32 36 42 42 -43B26BB<br>
0020: 38 39 34 43 43 7d 894CC} <br>
Have you updated all of your Device Drivers especially the Video and Chipset.
Have you recently installed new software or hardware that may have caused the problem.
I would try sfc /scannow and see if that fixes it.
How to perform an in-place upgrade, or reinstallation of XP.
1: Right click My Computer, select properties<br>
2: Click the Hardware Tab and press Device Manager button<br>
3: Expand the universal Serial Bus Controllers<br>
4: Double click on the USB Root Hub<br>
5: Select the Power Management Tab and check the "allow the computer to turn off the device to Save Power<br>
If you have more than one USB Root Hub, then you should apply the steps to each one of them. That's it, Reboot<br>
As you can see there are a couple of options available before you have to reinsall. Other peers may know of something else to try but I am hoping that it will be picked up in the event logs.
<i>Keep us informed as to your progress if you require further assistance.</i>
<i>If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as <b>Helpful</b> so that others may benefit from the outcome.

Collapse -

Thanks for the feedback

by generatorlabs In reply to A couple of checks

I did check the MOBO settings prior to this post. The firmware is at the most recent revision and the settings are correct. I however did not check to see the if the chipset has a new level out. Also I will try the other things you suggested as soon as I get home this evening! Thanks...

Collapse -

Have you checked the hard drive?

by 1bn0 In reply to Previously working STANDB ...

Scan the disk for errors.

You say "This PC has been functioning for a very long time flawlessly."

The three things you can count on in life are "Death, Taxes and Hard Drive Failure"

I believe your hard drive may be showing its age.

Collapse -

Hardrive error?

by generatorlabs In reply to Have you checked the hard ...

I did check the hard drives. However I think the likelihood of a failure there, while not impossible, is low. I am running a hardware level RAID and it has not reported any inconsistencies. Outside of running chkdsk and the built in RAID verifier I do not know if I should check anything else with that subsystem. Thanks for the advice though.

Collapse -

Possibly a temp file that is the culprit..

Run a cleaner on your computer such as ccleaner:
You can then try spybot:
With these two they might cure your issue.

Please post back if you have any more problems or questions.
If this information is useful, please mark as helpful. Thanks.

Related Discussions

Related Forums