For some reason, the computer I built a couple of years back has taken to doing an odd reboot loop. It had been working fine, but now when I turn it on it POSTs as normal, starts to load Windows (7 Home Premium 64bit), but when it gets to the point where it would normally show the login screen it jumps to chkdsk. It goes through the tests, often saying it's fixing things, then restarts. After restarting, it does the same thing again, ad nauseum. When it starts chkdsk is says 'press any key to skip/cancel', but pressing a key on the keyboard does nothing. I've tried using the install disc to do a repair, but it doesn't make any difference. I've run the samsung HDD test tools from the ultimate boot cd which have come back with no errors. I've also run memtest from a flash drive and left it running for over 100 hours. In that whole time it did give two errors, but I don't think that's responsible for causing the constant reboot loop. The worst I ever used to get was an occasional BSOD/reboot. Any ideas? It's driving me spare. I'd rather not have to, but the only option after this is to boot a linux livecd and backup anything super-essential to an external HDD. Thanks in advance.
Any updates go on recently? I've seen it do that loop after a couple of dodgy windows updates before. If you can get in to safe mode try the following http://www.sevenforums.com/tutorials/56685-check-disk-reset.html
Nope, no joy If I boot into safe mode, it takes as long as it would do to get to desktop/login, then immediately reboots without warning. I noticed that when safe mode was loading, I got some graphical corruption across the top of the screen. This led me to think that maybe it was a problem with my gpu (GTX460), so I unplugged it, reset the bios and loaded into safe mode with the onboard gfx instead. Exactly the same thing happens, and I get the same corruption/artefacts at the top. Any more ideas anyone?
Did you run memtest on each stick? or while all the DIMMS were in? If you have errors on the RAM then yes this could be the cause. Isolate the offending module and remove it then try booting the machine.