Reboot loop
in [Windows XP]
|
Prev: The Registry Cannot load the hive (file)
Next: Defrag
From: Peter on 22 Feb 2010 09:20 "Jose" <jose_ease(a)yahoo.com> wrote in message news:e215a0b4-448d-4dad-a87f-ff3d2ec33384(a)q21g2000yqm.googlegroups.com... On Feb 21, 10:21 pm, "Daave" <da...(a)example.com> wrote: > Jose wrote: > > 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? > > Rather than respond to your hypotheticals, I trust that Menno is > intelligent enough to figure it out on his own and that furthermore, if > he has questions, he will certainly be able to ask them. Okay - I recreate what I believe to be the problem with the OP computer again and booted on my Knoppix CD. What have I learned? That you have a know-it-all attitude and that you should stop it with your trolling!
From: Daave on 22 Feb 2010 11:05 Menno Hershberger wrote: > "Daave" <daave(a)example.com> wrote in news:#8WbZ42sKHA.4752 > @TK2MSFTNGP04.phx.gbl: > >> Jose wrote: >>> 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? >> >> Rather than respond to your hypotheticals, I trust that Menno is >> intelligent enough to figure it out on his own and that furthermore, >> if he has questions, he will certainly be able to ask them. > > It turns out that the Microsoft update *was* the culprit. On > examining the cloned drive, I noticed that a local security program > called "SecureIT" was installed on the computer. There was a known > vulnerability between that update and SecureIT. It amounts to > renaming or deleting a file named "scfltr.sys" in the > windows\system32\drivers folder. That fixed it. Thanks to everyone > that replied. Excellent. Thanks for the update. I was leaning toward a hardware issue (I believe Anna was, too); apparently the hardware is fine. :-) KB977165 seems to be having problems with legit programs (like SecureIT) as well as with the W32/Alureon-variants of malware. For good measue, I would still vigorously scan for malware. Good luck. P.S., You might be interested in the following: http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/73cea559-ebbd-4274-96bc-e292b69f2fd1
From: Jose on 23 Feb 2010 09:34
On Feb 22, 8:47 am, Menno Hershberger <mhers...(a)nosuchplace.net> wrote: > "Daave" <da...(a)example.com> wrote in news:#8WbZ42sKHA.4752 > @TK2MSFTNGP04.phx.gbl: > > > > > > > Jose wrote: > >> 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? > > > Rather than respond to your hypotheticals, I trust that Menno is > > intelligent enough to figure it out on his own and that furthermore, if > > he has questions, he will certainly be able to ask them. > > It turns out that the Microsoft update *was* the culprit. On examining the > cloned drive, I noticed that a local security program called "SecureIT" was > installed on the computer. There was a known vulnerability between that > update and SecureIT. It amounts to renaming or deleting a file named > "scfltr.sys" in the windows\system32\drivers folder. That fixed it. Thanks > to everyone that replied. > > -- > --- Long live Fat32! --- Good job. I see some new information in another place on the KB977165 that says it may cause the BSOD (that we know about already) and now read that it may hang on mup.sys in Safe Mode as another symptom. I only knew about the BSOD and how to fix that, I did not know about the symptom of it hanging in Safe Mode on mup.sys, but it is another good clue. |