windows vista - Why does my computer reboot by itself

  • Nir

    My computer sometimes reboots when I'm not near it, usually sometime at night or early morning.

    It happens ay completely random times, not every day, not the same day of month or day of week and not at the same time of day - sometimes it happens in consecutive days sometimes it doesn't happen for over a week.

    It never happens when the computer is in use, usually it happens in the middle of the night but it can happen during the day if I'm away from the computer, I've never seen a message saying the computer will automatically reboot (except after windows update - and that's not the case here)

    The system is running Windows Vista Ultimate, this computer is at my home - it's not a part of a domain and there is no domain controller on the local network.

    I believe Windows Update is not involved because after the reboot available updates are not installed, windows update is set up to download all update but not automatically install them.

    I've used the event log to try and find the problem, I've found when the computer rebooted but there was nothing in the system or application logs right before the reboot (actually, there was nothing but standard notifications that happen all the time for hours before the reboot).

    There is no special hardware in this computer, there is a lot of software installed most of the time MS Office 2007, Visual Studio 2008 & 2010, iTunes, IE and FireFox are running (as well as a lot of small utilities), any software that has auto-update is up to date (including Windows itself and all the programs listed above).

    (the "small utilities" running right now, based on the notification tray icons, are: dropbox, tortoiseHG, JungleDisk Simply Backup, MS security essentials, USB safely remove, "Control Center 3" and "Status monitor" from the brother MFC-250C printer software, Crushplan and Windows Clipping)

    The computer's power cable is connected to a surge suppressor, the same model of surge suppressor as the rest of the electronics in the house, I have not seen any evidence of power interruption in any other device. the weather as been very "good" this winter (almost no rain or strong wind) and power has been stable.

    This is very annoying since I sometimes leave things running overnight, does anyone have any idea how to find what causes those reboots?


    Except for those reboots the computer is stable, there are no blue screens or anything like that.

    Sleep and hibernate are disabled (there were problems with resuming from sleep - but I don't really care because that's wouldn't work with running things overnight anyway).

    The overnight jobs are not intensive, and the reboots also happen when the computer is idle

  • Answers
  • nctrnl

    Is your computer by any chance set to hibernate after x minutes/hours of inactivity? Perhaps the hibernation fails and makes your computer reboot instead?

    If that's the case, the power settings should be easy to find in the control panel. There could also be some pre-installed 3rd party programs that handles power settings.

    Something else you could try is upgrading your BIOS and drivers. I know some people recommend not fiddling with the BIOS at all, but there is often (if not always) a switch on the motherboard to set the BIOS to factory defaults in a worst case scenario.

  • wizlog

    Do you also have issues sometimes at bootup or an occasional freeze or unstable situation (bluescreen)?

    I would then recommend checking the memory and cleaning the memory's contacts.

    BTW, Memory is RAM in this case. Don't touch the contacts with your fingers.

  • Nir

    The problem was a bad graphics card or a bad graphics driver.

    Found out when one time the computer blue-screened and rebooted in front of me, I have no idea why the blue-screen details weren't in the event log.

    I have since discovers the GPU fan malfunctioned so it may be related to GPU overheating - or it could be just a bad driver installation.

  • Related Question

    How to diagnose a spontaneous reboot?
  • Spectralist

    My computer reboots, seemingly completely at random, about once every week to two weeks but has occasionally gone months. It just goes from running fine to the POST with no error messages or anything and doesn't seem to be due to heat or usage as it's happened a couple of times when the computer has booted just a few moments ago and is idling. It's been happening for as long as I've had this computer, almost two years. It's happened in both Vista and Windows7.

    I strongly suspect it's a hardware problem. But due to the rareish and random nature of the crashes my normal strategy of just removing hardware until the problem stops isn't really practical. My guess would be Power Supply, Ram, or Motherboard. But I just don't know how to test an issue this random and want to figure out how to confirm which it is before I go replacing things. So is there some software or hardware that can be used to test these sorts of errors? I did run memtest86 for about 8 hours without finding any issues. And the power supply is more than capable of running my system.

  • Related Answers
  • Zsub

    It certainly seems like a hardware issue.

    The first course of action would be to test your ram. Memtest86+ is a widely used diagnostics tool for RAM. I suggest you leave it running overnight or longer and see if it reports any errors.

    If your RAM seems to be alright, you can try running a CPU burn-in tester to see if your processor is alright, if it doesn't produce strange faults.

    If that doesn't produce any errors you could try to replace your BIOS battery. I have seen examples in which an empty BIOS battery somehow made a system instable. It's also a cheap solution.

    My last guess would be the PSU. Replace it with any decent and recent model and test RAM and CPU again.

    A note: if you test RAM, leave as much hardware out as possible.

  • 8088

    I won't repeat the guides others have written - you should start by disabling automatic restarts and doing a memory test (forget this though as you already have).

    AFter this, Take a look at Bluescreenview, this utility will allow you to see any bluescreens that have appeared in the past and hopefully allow you to track down the fault.

    As for the fault itself, the number one cause in older machines is Blown Capacitors, I have attached my little guide:

    Blown capacitors -

    Blown capacitors can be the cause of many "random" problems which appear to be completly unrelated, very annoying and hard to diagnose.

    alt text

    The top should be almost flat (with slight indents out embossed sections depending on specification... look at the middle one) but you do not want to see any big bumps such as the first one or any leakage as the last one.

    Hope this helps.


    Turn off automatic restart (the instructions are similar for Vista and 7) and see if the computer is BSOD'ing and get the stop codes. You can also look into the event log under "System" and check for critical errors.

    Otherwise, "acquire" a copy of PC Doctor and run some extended diagnostics.

  • Mick

    I don't know about windows-7 and Vista, but on XP you can look at the event viewer to give you some clues. On XP you right click on "My Computer" and select "Manage", then click "Event Viewer", then double click "system". This will show all sorts of events that were happening on your PC just before the crash, including ones labelled "Error".

  • Mokubai

    The problem is that this can be tied to almost any piece of old hardware going into a slightly odd failure state. The hardware could be 99% perfect but it's that 1% that gets you.

    I've had a similar problem with my machine of 5 years now and only managed to kill the random reboots about a year ago. I had two particular modes of failure. First one is that windows would appear to hang and then the machine would reboot and the main hard drive would not appear on the BIOS POST screen so that got replaced and got rid of that problem. The second issue was exactly what you are describing, a completely random reboot out of nowhere which I only killed on a hunch that the oldest piece of hardware in my machine was an 8 year old CD-writer that had migrated from an old machine. After removing these two parts my machine has behaved quite well.

    Don't just be looking at the mobo, suspect the hard drives and other peripherals too, HDDs can make your computer "pause" or appear to temporarily go dead on a bad block and then windows may reboot as a result. In my case the drive failed to appear after reboot but yours could be able to recover during the reboot. If this is the case then an error log would show nothing as it cannot be written to as the hard drive is missing.

  • Noblejoker

    Just to add to the good advice of others above I will add my 2 cents. In my experience the first candidates to check for random reboots and hardware problems are your power supply and cpu cooler. If you have multiple drives & devices and a power supply that is getting on a bit then that would be my first guess for causing the reboot. The other alternative culprit can be heat. If the system is overheating then it may be restarting itself - heat should be easy enough to monitor.

    Overall - sounds like a good excuse to update to me - buy a new one!

  • Rick Genz

    this may seam strange but it is the problem more times than not... check your fans... the bios will typically shut down or reboot if it senses a fan failure, typically a failure is nothing more than the fan not spinning at a minimum fan speed. for about 5-10 dollars the fan can be replaced, or if you have compressed air, clean it up in there. another option is to check bios and set the minimum speed lower or disable the protective mode all together (not recommended). often times a PWM fan may actually shut down for a bit if temperatures are o.k. when it shuts down it may cause this issue.. the settings in the bios can actually contradict each other and cause these issues. but more than liley you have a old fan that is slowing down, enough that the bios sees it as a potential danger causing the reboot.