computer starts rebooting on its own, every two weeks to the day
I have an XP sp3 machine that will start randomly rebooting on its own every 2 weeks to the day. I do a rollback and it works fine again for 2 weeks...
What I have already tried:
I did memtest, flashed the mb bios, chkdsk on the hd, updated all device drivers, changed AV programs from symantec to microsoft security essentials, used spybot and several AV to check the machine for virus/spyware, All microsoft updates and current on the computer, and the machine does not give me a BSOD when it does this. This is just a desktop and not a server and it gets rebooted often so probably not a memory leak issue. TOTALLY baffled by this.
What is so incredibly strange is that his happens exactly 2 weeks after I rollback the machine to an earlier date, (doesn't matter when I roll it back to prior to the problem.)
Any suggestions would be appreciated.
What I have already tried:
I did memtest, flashed the mb bios, chkdsk on the hd, updated all device drivers, changed AV programs from symantec to microsoft security essentials, used spybot and several AV to check the machine for virus/spyware, All microsoft updates and current on the computer, and the machine does not give me a BSOD when it does this. This is just a desktop and not a server and it gets rebooted often so probably not a memory leak issue. TOTALLY baffled by this.
What is so incredibly strange is that his happens exactly 2 weeks after I rollback the machine to an earlier date, (doesn't matter when I roll it back to prior to the problem.)
Any suggestions would be appreciated.
MarkieS
Any scheduled tasks intefering?
Strange, indeed.
First question is: Are there any messages in the System Event log?
First question is: Are there any messages in the System Event log?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check the harddisk it could be the problem
Clarification please. When you say it starts randomly rebooting two weeks to the day do you mean that it reboots for no apparent reason at random intervals AFTER the two weeks is up and that prior to the two weeks elapsing it runs fine and does not reboot. Or it reboots every two weeks?
If you do not do a system restore, what happens after two weeks?
If you do not do a system restore, what happens after two weeks?
It could also be a faulty psu
http://www.lockergnome.com/it/2005/03/02/learn-how-to-diagnose-power-supply-problems/
http://www.lockergnome.com/it/2005/03/02/learn-how-to-diagnose-power-supply-problems/
ASKER
The only error in the event log was ati2mtg (I2c return failed,) but these do not correspond with the reboots.
The machine works fine for exactly 2 weeks...then starts randomly rebooting at random intervals...I restore the machine and it runs fine for exactly 2 weeks...then starts randomly rebooting at random intervals.
I have already done a chkdsk
There are no scheduled events.
The machine works fine for exactly 2 weeks...then starts randomly rebooting at random intervals...I restore the machine and it runs fine for exactly 2 weeks...then starts randomly rebooting at random intervals.
I have already done a chkdsk
There are no scheduled events.
what about the psu??
Definitely do a restore, then disable system restore, then follow the instructions in my post above. If you have any malware of a virus hiding in the system restore, this should help get rid of it.
Curious problem. Are Windows updates scheduled to occur at a regular interval, say two weeks?
ASKER
Windows updates are daily, not on two week intervals, so doubtful there.
I restored the machine to 2/1, updated patches, turned off system restore, and running a malware scan now.
Seems unlikely to be psu because this happens every 2 weeks exactly, (this is the 3rd time it has happens and each time on Friday exactly 2 weeks after last occurance.)
I restored the machine to 2/1, updated patches, turned off system restore, and running a malware scan now.
Seems unlikely to be psu because this happens every 2 weeks exactly, (this is the 3rd time it has happens and each time on Friday exactly 2 weeks after last occurance.)
So the rebootings occur on Friday and are not dependent on the day you do the restore?
For example if you do a restore on say Sunday then the rebooting will occur on the Friday 2 weeks after the last occurrence.
For example if you do a restore on say Sunday then the rebooting will occur on the Friday 2 weeks after the last occurrence.
ASKER
I don't know that one, because I need this machine I restore it the day it happens...which as always been Friday
Then try restoring it again in the next few days and see whether the problem occurs on a Friday or two weeks after you've restored it.
Looking to see if rebooting is dependent on a Friday or two weeks after restoration.
Looking to see if rebooting is dependent on a Friday or two weeks after restoration.
ASKER
will do
check the bios - in the boot priority options - disable all but disk drive
could be it receives something over lan
could be it receives something over lan
Couple of additional suggestions:
1. Check the Regional Settings and ensure they are English US and the time zone, etc are correct.
2. Have you tried replacing the CMOS battery?
1. Check the Regional Settings and ensure they are English US and the time zone, etc are correct.
2. Have you tried replacing the CMOS battery?
ASKER
Since this happens on every other Friday exactly I did a preemptive rollback today (Wednesday,) since it was due to start doing the rebooting thing again this Friday. I will continue to monitor it.
I removed everything from the boot options except the hard drive as per suggested above and I the time settings are correct.
I did not replace the cmos battery and I will continue to test if anything seems to be working here. It takes 2 weeks for the problem to manifest making testing this somewhat time consuming.
Thanks
I removed everything from the boot options except the hard drive as per suggested above and I the time settings are correct.
I did not replace the cmos battery and I will continue to test if anything seems to be working here. It takes 2 weeks for the problem to manifest making testing this somewhat time consuming.
Thanks
did you turn off system restore and run a scan?
remember, without doing that, your restore could essentially be reinfecting yourself.
ASKER
Yes, sorry I forgot to mention last. The Friday before last I did turn off system restore and do a full scan but nothing was found. I then patched the box back up to current. Reinstalled the AV software and made a restore point then and that point is what I just restored back to today.
ok great.
let's hope Harry Potter does not invade your pc..
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I did a preemptive rollback on Wednesday of this week, (as this problem was due to manifest today (Friday) morning.) At 11:15 the machine starting random reboots....
Checked event logs, no errors prior to this.
This machine is joined to a domain and is effected by some GPO's, (no computer-specific policies,) and none of the other users in that OU are effected.
I am trying Dial A Fix nowl I also figured in 2 weeks I would fire up Wireshark and sniff the traffic in and out of that machine on Friday and see if I can find anything. Still baffled and of course I can wipe the machine and start over but I'm looking for an actual fix first because I want to know what the heck is causing it for future reference.)
Checked event logs, no errors prior to this.
This machine is joined to a domain and is effected by some GPO's, (no computer-specific policies,) and none of the other users in that OU are effected.
I am trying Dial A Fix nowl I also figured in 2 weeks I would fire up Wireshark and sniff the traffic in and out of that machine on Friday and see if I can find anything. Still baffled and of course I can wipe the machine and start over but I'm looking for an actual fix first because I want to know what the heck is causing it for future reference.)
I would be very curious to see what would occur if you swapped the HDD out; joined it to the domain, etc and let it run.
Biggest thing is trying to isolate if it's Hardware or Software [i.e. - Potential Hack, etc] related as I would suspect hardware would be easier on your nerves then the latter.
Keep us updated.
Biggest thing is trying to isolate if it's Hardware or Software [i.e. - Potential Hack, etc] related as I would suspect hardware would be easier on your nerves then the latter.
Keep us updated.
One more thing I'd suggest as well if possible:
Isolate the machine from your domain/network environment [i.e. - pull the cord out] and let it sit.
Isolate the machine from your domain/network environment [i.e. - pull the cord out] and let it sit.
I'm curious as to if he was ever able to resolve it. If he didn't all suggestions are technically valid but in my opinion no points should be awarded simply because we have no further direction from the OP as to what he ultimately did or at least steered him/her in the right direction.
As long as it got fixed, great. Would just be nice to know what the problem was.