Wierd computer issue...
-
Every now and then I come in to work, wake up my computer, and discover at some point during the night, it rebooted. It's not a huge issue, I save frequently, but it's annoying when I'm working on something that involves multiple applications that each take a few minutes to start up. So I was digging around in the event log, and discovered about every 5 days, for the past month, my computer has an unexpected shutdown just before 6:02 AM (specifically, all in the range of 6:01:42 AM to 6:01:56 AM). No one else seems to be having this issue. :doh: EDIT: Digging around in the BIOS I found my PC was set to boot everyday at 6 am automatically, could be related so I turned that off...won't know for sure for around another 4 days.
-
None of the replies (so far) have suggested this, but it could be network 'magic packets' that are able to wake your machine (WOL) to do admin/maintenance. My first guess was BIOS RTC. Now that you've disabled that, it's just a case of wait and see. :)
dusty_dex wrote:
None of the replies (so far) have suggested this, but it could be network 'magic packets' that are able to wake your machine (WOL) to do admin/maintenance.
Those are enabled, and they seem to wake the machine every couple hours regularly. But I don't think you can cause a forced power off via software short of a BSOD.
-
dusty_dex wrote:
None of the replies (so far) have suggested this, but it could be network 'magic packets' that are able to wake your machine (WOL) to do admin/maintenance.
Those are enabled, and they seem to wake the machine every couple hours regularly. But I don't think you can cause a forced power off via software short of a BSOD.
-
What does the Event Log say exactly? Windows scripts can power-down/reboot remote machines *if* the policy is in place to allow that.
Level: Critical Source: Kernel-Power Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. (Also, reviewing the logs, "SleepInProgess" is true for all of them, this implies the computer was still asleep when these happened.)
-
Level: Critical Source: Kernel-Power Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. (Also, reviewing the logs, "SleepInProgess" is true for all of them, this implies the computer was still asleep when these happened.)
lewax00 wrote:
this implies the computer was still asleep when these happened
Maybe the computer is having bad dreams, causing it to crash. :)
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
-
lewax00 wrote:
this implies the computer was still asleep when these happened
Maybe the computer is having bad dreams, causing it to crash. :)
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
-
-
lewax00 wrote:
Do computers dream of downloaded sheep?
That's scary...What would the computer do to those poor sheep. :rolleyes:
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
OriginalSin?
-
OriginalSin?
-
OriginalSin?
Good one. :laugh:
BDF The internet makes dumb people dumber and clever people cleverer. -- PaulowniaK
-
It's not Windows Update, it's listed as an unexpected power loss (the log event that is added when the plug is pulled, the power button is held down, etc.). Scheduled defrag is plausible. And it is way too consistent in timing to believe it's a human.
Unexpected power loss? Back in the day we had a very similar issue with a machine which was being used as a print server. Turned out the cleaning lady would unplug it to plug in her vacuum cleaner!
MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Do you have cleaners in your office? They might be unplugging your computer to plug in the vacuum.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Should have read this before posting above :-O
MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
OriginalSin?
[Original sin] That's when you purposely spill hot hamburger juice on your keyboard, have to dissasemble it in order to find out that the plastic under the keys has melted the trace borders, and now, after rifling the state of Michigan for another plastic switch you find there's no suitable replacement to get it to work again so you don't even bother to put the whole thing back together. [/Original sin]
-
Unexpected power loss? Back in the day we had a very similar issue with a machine which was being used as a print server. Turned out the cleaning lady would unplug it to plug in her vacuum cleaner!
MVVM # - I did it My Way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
It's not Windows Update, it's listed as an unexpected power loss (the log event that is added when the plug is pulled, the power button is held down, etc.). Scheduled defrag is plausible. And it is way too consistent in timing to believe it's a human.
-
Level: Critical Source: Kernel-Power Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. (Also, reviewing the logs, "SleepInProgess" is true for all of them, this implies the computer was still asleep when these happened.)
-
lewax00 wrote:
And it is way too consistent in timing to believe it's a human.
It is quite possible on windows for networks admins to schedule stuff - at an exact time.
