Reboot loop
in [Windows XP]
|
Prev: The Registry Cannot load the hive (file)
Next: Defrag
From: Menno Hershberger on 21 Feb 2010 09:13 Jose <jose_ease(a)yahoo.com> wrote in news:054740f3-4ad2-407e-b2da-74386158bc8a(a)k41g2000yqm.googlegroups.com: > On Feb 21, 12:35�am, Menno Hershberger <mhers...(a)nosuchplace.net> > wrote: >> I have an older Systemax here with XP Home Edition (SP3) that keeps >> rebooting itself whether or not in Normal or Safe Mode. I have the >> restore CD and can get in to the Recovery Console OK. I ran chkdsk, >> fixboot, and fixmbr. Those didn't fix it. So I cloned the drive just >> for good luck and then tried to do a repair install. The install went >> as far as examining the disk, copying files, and then rebooted... >> only to go back into the reboot loop. >> These people use their computer every day and keep their updates up >> to date so I'm guessing it is NOT related to the MS update that >> created havoc here a couple or three weeks ago. >> I can always (and probably will) wipe it out and start anew since I >> have all the data saved on another drive. But I'd rather not if I can >> get out of it since it would require reinstall of a lot of programs >> that they likely don't have in installation CDs for. >> Does anyone have any ideas how I might get this fixed from the >> Recovery Console? Or any other way, as far as that goes... :-) >> >> -- >> � � � � � � � � � � --- Long live Fat32! --- > > What is your definition of reboot? In normal mode, it gets as far as the XP logo screen, then powers off. In Safe Mode, it powers off shortly after "mup.sys" appears. > > Do you get to logon and then see a message "Saving your settings..." > and can't get out of that mode? NO > > That is not a reboot, so first we need to know for sure what is > happening, then fix it. > > If you had the 02/09/2010 update issue, your system would not boot at > all and you would have a Blue Screen of Death (BSOD), so if you don't > see that, you do not have that problem. No BSOD > What is a restore CD? Is that a genuine bootable XP installation CD > or some kind of recovery CD that came with the system? They are not > the same. It is genuine bootable installation CD. I used it to get into the Recovery Console and to do the attempted repair install. -- --- Long live Fat32! ---
From: Menno Hershberger on 21 Feb 2010 09:16 nass <nass(a)discussions.microsoft.com> wrote in news:0E33C17B-4A45-4B95-8132-C1386394E875(a)microsoft.com: > > > "Menno Hershberger" wrote: > >> I have an older Systemax here with XP Home Edition (SP3) that keeps >> rebooting itself whether or not in Normal or Safe Mode. I have the >> restore CD and can get in to the Recovery Console OK. I ran chkdsk, >> fixboot, and fixmbr. Those didn't fix it. So I cloned the drive just >> for good luck and then tried to do a repair install. The install went >> as far as examining the disk, copying files, and then rebooted... >> only to go back into the reboot loop. >> These people use their computer every day and keep their updates up >> to date so I'm guessing it is NOT related to the MS update that >> created havoc here a couple or three weeks ago. >> I can always (and probably will) wipe it out and start anew since I >> have all the data saved on another drive. But I'd rather not if I can >> get out of it since it would require reinstall of a lot of programs >> that they likely don't have in installation CDs for. >> Does anyone have any ideas how I might get this fixed from the >> Recovery Console? Or any other way, as far as that goes... :-) >> >> -- >> --- Long live Fat32! --- >> . > > > Did you check for Hardware defectiveness? Like RAM, Heat Issue..etc Yes. Ran memtest. Heat sink is clean, fans are running. It reboots before it has a chance to get warm. > > Also did you test to see if the backed up data will be accessed easy > without problem before wiping out the HDD? Yep. Cloned the drive, put it in another computer and can access everything on that drive. -- --- Long live Fat32! ---
From: Menno Hershberger on 21 Feb 2010 09:18 And how do I go about doing that when I can't even get booted up? captain977 <captain977(a)discussions.microsoft.com> wrote in news:A735D018-9E45-4C4C-BECA-B39D494C83C4(a)microsoft.com: > try reinstalling your drivers or updating them,had the same thing > happen on my machine.Recovery will put the same old drivers back in. > > "Menno Hershberger" wrote: > >> I have an older Systemax here with XP Home Edition (SP3) that keeps >> rebooting itself whether or not in Normal or Safe Mode. I have the >> restore CD and can get in to the Recovery Console OK. I ran chkdsk, >> fixboot, and fixmbr. Those didn't fix it. So I cloned the drive just >> for good luck and then tried to do a repair install. The install went >> as far as examining the disk, copying files, and then rebooted... >> only to go back into the reboot loop. >> These people use their computer every day and keep their updates up >> to date so I'm guessing it is NOT related to the MS update that >> created havoc here a couple or three weeks ago. >> I can always (and probably will) wipe it out and start anew since I >> have all the data saved on another drive. But I'd rather not if I can >> get out of it since it would require reinstall of a lot of programs >> that they likely don't have in installation CDs for. >> Does anyone have any ideas how I might get this fixed from the >> Recovery Console? Or any other way, as far as that goes... :-) >> >> -- >> --- Long live Fat32! --- >> . >> > -- --- Long live Fat32! ---
From: Daave on 21 Feb 2010 10:46 Menno Hershberger wrote: > I have an older Systemax here with XP Home Edition (SP3) that keeps > rebooting itself whether or not in Normal or Safe Mode. I have the > restore CD and can get in to the Recovery Console OK. I ran chkdsk, > fixboot, and fixmbr. Those didn't fix it. So I cloned the drive just > for good luck and then tried to do a repair install. The install went > as far as examining the disk, copying files, and then rebooted... > only to go back into the reboot loop. > These people use their computer every day and keep their updates up > to date so I'm guessing it is NOT related to the MS update that > created havoc here a couple or three weeks ago. > I can always (and probably will) wipe it out and start anew since I > have all the data saved on another drive. But I'd rather not if I can > get out of it since it would require reinstall of a lot of programs > that they likely don't have in installation CDs for. > Does anyone have any ideas how I might get this fixed from the > Recovery Console? Or any other way, as far as that goes... :-) In order to determine whether or not this is a hardware-related problem, boot off a live Linux CD and run the PC for a while to see if the rebooting behavior occurs.
From: Anna on 21 Feb 2010 10:58
>> "Menno Hershberger" wrote: >>> I have an older Systemax here with XP Home Edition (SP3) that keeps >>> rebooting itself whether or not in Normal or Safe Mode. I have the >>> restore CD and can get in to the Recovery Console OK. I ran chkdsk, >>> fixboot, and fixmbr. Those didn't fix it. So I cloned the drive just >>> for good luck and then tried to do a repair install. The install went >>> as far as examining the disk, copying files, and then rebooted... >>> only to go back into the reboot loop. >>> These people use their computer every day and keep their updates up >>> to date so I'm guessing it is NOT related to the MS update that >>> created havoc here a couple or three weeks ago. >>> I can always (and probably will) wipe it out and start anew since I >>> have all the data saved on another drive. But I'd rather not if I can >>> get out of it since it would require reinstall of a lot of programs >>> that they likely don't have in installation CDs for. >>> Does anyone have any ideas how I might get this fixed from the >>> Recovery Console? Or any other way, as far as that goes... :-) > nass <nass(a)discussions.microsoft.com> wrote in > news:0E33C17B-4A45-4B95-8132-C1386394E875(a)microsoft.com: >> Did you check for Hardware defectiveness? Like RAM, Heat Issue..etc > Yes. Ran memtest. Heat sink is clean, fans are running. It reboots before > it has a chance to get warm. >> >> Also did you test to see if the backed up data will be accessed easy >> without problem before wiping out the HDD? "Menno Hershberger" <mhersh22(a)nosuchplace.net> wrote in message news:Xns9D26542877922butter(a)wefb973cbe498... > Yep. Cloned the drive, put it in another computer and can access > everything > on that drive. (Menno adds...) In normal mode, it gets as far as the XP logo screen, then powers off. In Safe Mode, it powers off shortly after "mup.sys" appears. It is genuine bootable installation CD. I used it to get into the Recovery Console and to do the attempted repair install. Menno: From the sound of your description of the problem it sounds like this may be a problem involving one or more components although that's not definitive by any means. First of all it would be appropriate (assuming you haven't already done this) to check out the HDD with the diagnostic utility generally freely available from the disk's manufacturer. While it doesn't sound like this is the root cause of the problem it's conceivable you're simply dealing with a defective HDD. Assuming the disk checks out OK, (and further assuming this is a desktop PC) it probably would be wise to perform some basic diagnostic processes. After shutting down your machine, remove (disconnect) all peripheral devices from the machine including your hard drive(s), optical drive(s), sound card, etc. Disconnect all storage devices, printers, and any other devices connected to the machine. So that all you'll be working with is your motherboard, processor, heat sink, RAM, video card, and power supply. Better yet, should your motherboard be equipped with onboard video/graphics capability, disconnect your video card from the system. Just make sure your BIOS setting (should there be this setting) reflects that onboard graphics/video is enabled. In any event ensure that as best you can determine all the components are properly seated & connected. Reconnect your A/C cord and power on the system. What happens? Presumably you get a "normal" screen display, i.e., no error messages or strange notations of any kind, right? Can you access your BIOS without any difficulty at this point and review the CMOS settings? Can you check the hardware monitor in the BIOS to determine that all temps are within normal range? Keep monitoring the temps while the system is running for a reasonable length of time to determine whether there's any overheating problem. Assuming all is well at this point leave the system powered on for the next hour or so, continually checking to see if anything untoward shows up, particularly temperature-wise. Using your reset button, try powering down & up a few times to determine if there are any problems there. Should all appear well at this point this is an indication that there's nothing wrong with the basic components of your system. While it's not absolutely definitive that this is so, it's a very strong indication that something else is amiss - possibly involving an operating system corruption of some sort. If it is a hardware problem as it appears to be, the only definitive way to determine the defective component is through substitution on a component-by-component basis which of course is obviously a problem for most end-users. It doesn't sound like a motherboard problem but it's possible. While I would lean toward a possible defective power supply it could be something else. I'm sure you've checked all your data/power cable connections to determine they're properly connected, right? Anna |