Why the hell does my PC keep hibernating? :(
-
A real head-scratcher, this one. I have a Dell Precision 530, twin 1.7Ghz Xeon server running XP, at home. The server runs headless, and I access it via TS from my laptop (or remotely from work). It's used as a torrent server, and also as a music server for streaming choons to my Soundbridge. It's been running fine since I set it up a couple of months ago. To save a bit of power, and because it's noisy as hell and keeps me awake at night, I have it set up with an AT job to hibernate it at 22:30 each evening, and the BIOS wakes it up again at 8am each day. Again, that's been working just fine for the last 8 weeks. However, last week, it suddenly started shutting down for no apparent reason. It seems to start up, works for 3-4 minutes, and then hibernates, after which it's inaccessible (remotely) until I physically power it up again (not practical when I'm in the office ). Question is, why?!?! I've checked the event log sometimes the last thing in the event log seems to be a message saying ".NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Completed all work. Shutting down.", which implies that this service is completing and causing the machine to shutdown or reboot. However, after some investigation it seems that the 'Shutting Down' comment refers to the CLR optimisation process, not the PC itself, so this may be a red herring. (see here: http://discussion.autodesk.com/thread.jspa?threadID=521502). I've tried uninstalling the .Net Framework v3 to see if it's that which is causing the problem, but no joy. I've also played with the power-saving settings, to see if they'd got corrupt, but again, not change (I have them set to 'Never' hibernate). I installed AVG last night, no viruses or other crap which might be causing it. The PC seems to stay alive when I'm connected to it, but shuts down a few minutes after I disconnect. I ran the AVG full scan, which took about half an hour, and at some point after that did the machine hibernate, so it's like it's doing it when the machine is idle. I have no idea why it's behaving like this, but it's driving me nuts - and is particularly irritating as I'm currently trying to initial-seed a 23GB torrent at the moment, which isn't going to happen if the machine's only up for 4 minutes at a time. If I disable hibernation, the machine stays awake and it's not a problem. So, any other ideas?
________________________ http://www.webreaper.net
-
A real head-scratcher, this one. I have a Dell Precision 530, twin 1.7Ghz Xeon server running XP, at home. The server runs headless, and I access it via TS from my laptop (or remotely from work). It's used as a torrent server, and also as a music server for streaming choons to my Soundbridge. It's been running fine since I set it up a couple of months ago. To save a bit of power, and because it's noisy as hell and keeps me awake at night, I have it set up with an AT job to hibernate it at 22:30 each evening, and the BIOS wakes it up again at 8am each day. Again, that's been working just fine for the last 8 weeks. However, last week, it suddenly started shutting down for no apparent reason. It seems to start up, works for 3-4 minutes, and then hibernates, after which it's inaccessible (remotely) until I physically power it up again (not practical when I'm in the office ). Question is, why?!?! I've checked the event log sometimes the last thing in the event log seems to be a message saying ".NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Completed all work. Shutting down.", which implies that this service is completing and causing the machine to shutdown or reboot. However, after some investigation it seems that the 'Shutting Down' comment refers to the CLR optimisation process, not the PC itself, so this may be a red herring. (see here: http://discussion.autodesk.com/thread.jspa?threadID=521502). I've tried uninstalling the .Net Framework v3 to see if it's that which is causing the problem, but no joy. I've also played with the power-saving settings, to see if they'd got corrupt, but again, not change (I have them set to 'Never' hibernate). I installed AVG last night, no viruses or other crap which might be causing it. The PC seems to stay alive when I'm connected to it, but shuts down a few minutes after I disconnect. I ran the AVG full scan, which took about half an hour, and at some point after that did the machine hibernate, so it's like it's doing it when the machine is idle. I have no idea why it's behaving like this, but it's driving me nuts - and is particularly irritating as I'm currently trying to initial-seed a 23GB torrent at the moment, which isn't going to happen if the machine's only up for 4 minutes at a time. If I disable hibernation, the machine stays awake and it's not a problem. So, any other ideas?
________________________ http://www.webreaper.net
The machine is a TS, right? Is it even possible to change PowerSaving settings like that? I find it hard to believe that someone logged in to a TS session would be able to change the effective hibernation settings. If I was you, I would try logging in on the machine's console as Administrator, then checking the PowerSaving settings again. Maybe the hibernation is active there. If it is not, and that is a stab in the dark, try changing to installation mode and changing the settings again. Additionally, one of my old computers actually had BIOS Power Saving options (which only worked with Windows). Even if PowerSaving was disabled in Windows, the machine would still switch to Stand By if the BIOS decided the machine had been inactive for too long. Sorry for the late reply.
Cheers, Sebastian -- "If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
-
The machine is a TS, right? Is it even possible to change PowerSaving settings like that? I find it hard to believe that someone logged in to a TS session would be able to change the effective hibernation settings. If I was you, I would try logging in on the machine's console as Administrator, then checking the PowerSaving settings again. Maybe the hibernation is active there. If it is not, and that is a stab in the dark, try changing to installation mode and changing the settings again. Additionally, one of my old computers actually had BIOS Power Saving options (which only worked with Windows). Even if PowerSaving was disabled in Windows, the machine would still switch to Stand By if the BIOS decided the machine had been inactive for too long. Sorry for the late reply.
Cheers, Sebastian -- "If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton
The machine is just a standard XP pro box. I use TS to access it via my laptop so I don't have to have a screen attached to it. Nobody other than myself accesses the box, so it's something that couldn't get changed by somebody else. I see where you're coming from with the comment re: the Bios - the only weird thing is that it only hibernates the box, and it wasn't happening 2 weeks ago!
________________________ http://www.webreaper.net
-
The machine is just a standard XP pro box. I use TS to access it via my laptop so I don't have to have a screen attached to it. Nobody other than myself accesses the box, so it's something that couldn't get changed by somebody else. I see where you're coming from with the comment re: the Bios - the only weird thing is that it only hibernates the box, and it wasn't happening 2 weeks ago!
________________________ http://www.webreaper.net
Oh. I totally missed the "XP Pro" part and concentrated on the mention of "TS". Sorry about that. With a XP Pro box and the Remote Desktop Client, everything SHOULD work as if you were logged in locally. Do you have any programs that offer their own "power saving settings"? I remember seeing software offering to "hibernate, after all downloads are complete" or similar mumbo-jumbo. That is pretty much all I can think of right now, sorry. Hope it helps.
Cheers, Sebastian -- "If it was two men, the non-driver would have challenged the driver to simply crash through the gates. The macho image thing, you know." - Marc Clifton