Reboot loop
in [Windows XP]
|
Prev: The Registry Cannot load the hive (file)
Next: Defrag
From: "db" databaseben at hotmail dot on 21 Feb 2010 13:02 one of the processes of booting is loading the registry. the registry may have crashed. what you might try is to restore the default registry that was created when the windows was setup on the machine. then if you can boot with a basic registry hive, you can then replace it with a registry hive that is a bit more current via the desktop. -- db���`�...�><)))�> DatabaseBen, Retired Professional - Systems Analyst - Database Developer - Accountancy - Veteran of the Armed Forces - Microsoft Partner - @hotmail.com ~~~~~~~~~~"share the nirvana" - dbZen > > "Menno Hershberger" <mhersh22(a)nosuchplace.net> wrote in message news:Xns9D25EFFC9BD1Cbutter(a)wefb973cbe498... > 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! ---
From: Jose on 21 Feb 2010 13:07 On Feb 21, 9:18 am, Menno Hershberger <mhers...(a)nosuchplace.net> wrote: > And how do I go about doing that when I can't even get booted up? > > captain977 <captain...(a)discussions.microsoft.com> wrote innews: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! --- It's not mup.sys, its' what comes after mup.sys... I know what it is for me, but that may not be the same for you. When you boot through the boot menu, choose: Disable automatic restart on system failure Then you can see the BSOD (if you have one) Here are some BSOD blue screen of death examples showing information you need to provide: http://www.codinghorror.com/blog/images/Windows_XP_BSOD.png http://techrepublic.com.com/i/tr/downloads/images/bsod_a.jpg Send the information pointed to with the red arrows (3-4 lines total). Skip the boring text unless it looks important to you. We know what a BSOD looks like, we need to know the other information that is specific to your BSOD. Unplug everything except the keyboard, no mouse, network, especially no USB devices, etc. You only need the KB to boot and choose a boot option. It could be the KB, so if you have another KB, swap it. You need to see if it boots with everything external unplugged then isoalate a suspicious peripheral. Boot into the Recovery Console and run chkdsk on your drive(s). From the RC prompt, run for example: chkdsk c: /r Let chkdsk finish and correct any problems it might find. It may take a long time to complete or appear to be 'stuck'. Be patient. If the HDD light is still flashing, it is doing something. Keep an eye on the percentage amount to be sure it is still making progress. Go ahead and run a RAM test - here are some instructions: Run a test of your RAM with memtest86+ (I know it is boring and will cost you a CD). Memtest86+ is a more up to date version of the old memtest program and they are not the same. The memtest86+ will not run under Windows, so you will need to download the ISO file and create a bootable CD, boot on that and then run the memtest86+ program. If even a single error is reported that is a failure and should make you suspicious of your RAM. If you have multiple sticks of RAM you may need to run the test on them one at a time and change them out to isolate the failure to a particular single stick. Always keep at least the first bank of RAM occupied so the test will find something to do and there is enough to boot your system. Sometimes, reseating the RAM in the slots will relieve the error but a failure is still cause for suspicion. The file and instructions are here: http://www.memtest.org/ If someone says to run memtest86, you can say that you know memtest86+ supercedes memtest86 and here's why: http://en.wikipedia.org/wiki/Memtest86
From: Jose on 21 Feb 2010 13:08 On Feb 21, 10:46 am, "Daave" <da...(a)example.com> wrote: > 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. I would like to try this. How do I boot off a live Linux CD if I don't have one and how long is a while? If it runs for a while, how will that help me fix Windows (what do I do next).
From: Daave on 21 Feb 2010 14:03 Jose wrote: > On Feb 21, 10:46 am, "Daave" <da...(a)example.com> wrote: >> 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. > > I would like to try this. Why would you like to try this? Do you have a similar situation? I proposed leaving the Windows environment to the OP as a method to determine if this is a Windows problem or a hardware problem. > How do I boot off a live Linux CD if I don't have one Think about what you just stated. Obviously, if you don't have a live Linux CD, it is impossible to boot off of a live Linux CD! I am sure you already know this, and it is puzzling why you would ask such a question. Pehaps there is sarcasm embedded in your question; I don't know. If you are being sarcastic, I'm not sure why you would choose to do so. At any rate, if you truly want to boot off a live Linux CD (like Knoppix or Ubuntu) and currently don't have one, you obviously need to obtain one. Perhaps your question is "How do I obtain one?" If so, you may borrow or purchase one or use a working PC to make your own. If you still need guidance, I am sure you know how to use Google, correct? > and how long is a while? How long do I think a while should be? Don't you think it would be logical that this would depend on how long it takes for the OP's PC running under Windows to start acting up? If it does this within one minute consistently and if he can run for a significantly longer amount of time (perhaps one hour) under Linux with no issues, it would imply the hardware is not at fault. If the PC behaves the same exact way with regard to the rebooting issue under Linux, this surely would point to a hardware problem, don't you agree? > If it runs for a while, how will that help me fix Windows (what do I > do next). That question makes no sense considering the context. We do not yet know that Windows needs to be "fixed." Assuming that there is a hardware problem and nothing wrong with Windows, why would you want to fix Windows? If you have seen convincing evidence I may have missed that the reason for the rebooting is most likely due to Windows, please share it with the rest of us. My personal take is that if there is a possibility hardware is to blame, that is what should be addressed first. Otherwise, troubleshooting Windows or even taking the time to perform a Repair Install or a Clean Install could wind up wasting a lot of time.
From: Jose on 21 Feb 2010 18:45
On Feb 21, 2:03 pm, "Daave" <da...(a)example.com> wrote: > Jose wrote: > > On Feb 21, 10:46 am, "Daave" <da...(a)example.com> wrote: > >> 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. > > > I would like to try this. > > Why would you like to try this? Do you have a similar situation? I > proposed leaving the Windows environment to the OP as a method to > determine if this is a Windows problem or a hardware problem. > > > How do I boot off a live Linux CD if I don't have one > > Think about what you just stated. Obviously, if you don't have a live > Linux CD, it is impossible to boot off of a live Linux CD! I am sure you > already know this, and it is puzzling why you would ask such a question. > Pehaps there is sarcasm embedded in your question; I don't know. If you > are being sarcastic, I'm not sure why you would choose to do so. > > At any rate, if you truly want to boot off a live Linux CD (like Knoppix > or Ubuntu) and currently don't have one, you obviously need to obtain > one. > > Perhaps your question is "How do I obtain one?" If so, you may borrow or > purchase one or use a working PC to make your own. If you still need > guidance, I am sure you know how to use Google, correct? > > > and how long is a while? > > How long do I think a while should be? Don't you think it would be > logical that this would depend on how long it takes for the OP's PC > running under Windows to start acting up? If it does this within one > minute consistently and if he can run for a significantly longer amount > of time (perhaps one hour) under Linux with no issues, it would imply > the hardware is not at fault. If the PC behaves the same exact way with > regard to the rebooting issue under Linux, this surely would point to a > hardware problem, don't you agree? > > > If it runs for a while, how will that help me fix Windows (what do I > > do next). > > That question makes no sense considering the context. We do not yet know > that Windows needs to be "fixed." Assuming that there is a hardware > problem and nothing wrong with Windows, why would you want to fix > Windows? > > If you have seen convincing evidence I may have missed that the reason > for the rebooting is most likely due to Windows, please share it with > the rest of us. > > My personal take is that if there is a possibility hardware is to blame, > that is what should be addressed first. Otherwise, troubleshooting > Windows or even taking the time to perform a Repair Install or a Clean > Install could wind up wasting a lot of time. You through out the suggestion to the OP, so if I was the OP what would I do with your advice and how would I follow it? I don't have a live Linux CD, and don't know anybody that does, so can I make one, how do I do that and what do I do when I boot using it? Why don't you post a link where I can download what you think is the best for the situation? I have a Ubuntu CD so do I just boot on that and let it sit there a while and then try Windows again or do I do something? It wants to install on my system, is that what I need to do or do I just boot and sit? What do you mean "let it run for a while and then try iIndows again?" What will booting on a live Linux CD do? I have a Knoppix CD too - do I boot and sit or do I try to do something and what do you recommend I do? The OPs PC won't boot, it tries and powers off and hangs on mup.sys in Safe Mode. Do you recommend downloading a live Linux CD from some unspecified place, booting the system on that and letting it sit for a while? Is that a good test, what gets tested if it just sits for a while (perhaps an hour) or is there something to do? How could it behave exactly the same - it hangs on mup.sys, should we look for that when booting the live Linux CD? I induced a BSOD booting in Normal mode and the Safe Mode mup.sys failure on a system here (I know what comes next). I downloaded Ubuntu and Knoppix and made bootable CDs that for each and they seem to boot just fine but my Ubuntu want's to install - should I let it?. I don't know if I downloaded the right stuff - I just picked one of the Google results. I booted each, let each sit for a hour and still have the same problem - Windows won't boot. I often read "boot on a Knoppix or Ubuntu CD..." when people have problems, so I did. That's all the instructions I usually see. It never says what to do next - unless you are copying file to do a complete reinstall. How do I fix my Windows system? You said boot on a live Linux CD (I did) and run the PC for a while. What do I run? Can I run chkdsk? Can I run a memory test? Now what do I do? I'm following the advice (I think), but don't know what to do next to fix Windows. If yo uare going to ask someone to make a CD, at least post a link to what they are supposed to download. It's like saying "run a RAM test", well, how do I do that if my system will not boot? Where do I get this RAM test? Then db says the registry might have crashed and to try the default registry and then use a registry hive that is a bit more current. How will instructions like that help the OP? How do I do that on my system that will not boot? Try? Might? Maybe? I need things to do, not things to try. |