Windows XP Home in rebooting loop
Results 1 to 9 of 9

Thread: Windows XP Home in rebooting loop

  1. #1
    Registered User
    Join Date
    Feb 2001
    Posts
    765

    Windows XP Home in rebooting loop

    Hello -

    I have an HP Pavilion with WinXP Home. It is in a rebooting loop. It will not start in any mode without restarting. I have tried 2x repair installs, but it still does the same thing.

    Any suggestions?
    "It is very dark here. You are likely to be eaten by a grue."

  2. #2
    Registered User BOB IROC's Avatar
    Join Date
    Jun 2003
    Location
    Lockport, IL
    Posts
    1,158
    If you hit F8 to get to the Safemode options screen is one of the options "disable automatic restart on system failure" If so maybe it will get to an error screen that will help us.

    This could also be caused by spyware/viruses or hardware problems such as bad memory or hard drive.

    Sometimes HPs have built in diagnostics you can run and thats were I would start. Test your hadware and if all passes you may have no choice but to do a complete system reformat/restore.
    At the source of every error which is blamed on the computer, you will find at least two human errors, including the error of blaming it on the computer.
    http://www.facebook.com/BlueLightningTechnicalServices

  3. #3
    Registered User
    Join Date
    Feb 2001
    Posts
    765
    That option is not there in the boot up options list. The whole reason I tried a repair install was that the entire desktop had disappeared. All that was on it was the background. The only thing I could do was Ctrl-Alt-Del to try to do anything. After the repair install is when this started.
    "It is very dark here. You are likely to be eaten by a grue."

  4. #4
    Registered User BOB IROC's Avatar
    Join Date
    Jun 2003
    Location
    Lockport, IL
    Posts
    1,158
    Sounds like you got some Windows Corruption going on that may be related to Spyware or malware. I hope you have your essential data backed up because in case such as this I would recommend doing a complete system restore/reformat.
    At the source of every error which is blamed on the computer, you will find at least two human errors, including the error of blaming it on the computer.
    http://www.facebook.com/BlueLightningTechnicalServices

  5. #5
    Registered User Ferrit's Avatar
    Join Date
    Apr 2001
    Location
    Vancouver Island The Real Canada
    Posts
    4,952
    Were you able to get to the desktop the first time after these repair installs?
    Gigabyte 990FXA-UD3
    AMD FX 8350 4ghz OCTO-Core
    Windows 8.1 PRO 64
    Adata 256 gig SSD
    Kingston HyperX 1600 16 Gigs
    Sapphire R9 280 2gig
    Enermax Liberty Modular 620
    www.northernaurora.net
    http://www.northernaurora.net/page/chat.html

  6. #6
    Registered User slgrieb's Avatar
    Join Date
    Feb 2003
    Posts
    4,103
    I'm curious to see jakk's response to Ferrit's post, but I'd speculate that doing a full restore (one that reformats the hard drive) is the only practical way to get the computer running again. I see this so often, and after the fact, it's hard to say if the problem was malware related, caused by ill behaved software, or whatever. But I'm pretty certain that even after a single failed repair installation. Windows is completely fried. If the culprit were bad memory or the like, the repair would have been likely to generate errors.

  7. #7
    Registered User Ferrit's Avatar
    Join Date
    Apr 2001
    Location
    Vancouver Island The Real Canada
    Posts
    4,952
    I was wondering because I have seen this out of a few odd manufacture ati based video cards. Changeing the video card fixed the issue
    Gigabyte 990FXA-UD3
    AMD FX 8350 4ghz OCTO-Core
    Windows 8.1 PRO 64
    Adata 256 gig SSD
    Kingston HyperX 1600 16 Gigs
    Sapphire R9 280 2gig
    Enermax Liberty Modular 620
    www.northernaurora.net
    http://www.northernaurora.net/page/chat.html

  8. #8
    Registered User
    Join Date
    Feb 2001
    Posts
    765
    No, the desktop didn't show up. That is curious that you mentioned the vid card. It stalls out and reboots on a agp related file - I will post which one.

    Maybe something there....The video is onboard. Not sure which one. Will post that also...
    "It is very dark here. You are likely to be eaten by a grue."

  9. #9
    Registered User slgrieb's Avatar
    Join Date
    Feb 2003
    Posts
    4,103
    jakkwb, the startup screen displays the last driver successfully loaded, so a hangup after that means that the next driver in the sequence crapped out. Admittedly, this makes troubleshooting boot issues harder than it needs to be, but sometimes a search may provide a clue.

    Edit: Ferrit got me to thinking that problems with chipset drivers can also be a source of crashes. Still, I'm going with the "Nuke It" recommendation. Even if you don't have a current backup, you have a good chance of recovering your data without major expense, but let's worry about that if the time comes.
    Last edited by slgrieb; May 31st, 2007 at 09:34 PM. Reason: Second thoughts

Similar Threads

  1. OS NEWS: Windows XP Service Pack 3 Not Coming
    By TechZ in forum Tech News
    Replies: 0
    Last Post: April 9th, 2007, 12:59 PM
  2. OS NEWS: Microsoft confirms Windows XP SP3
    By TechZ in forum Tech News
    Replies: 0
    Last Post: October 7th, 2005, 05:25 AM
  3. who stole device manager?
    By ringo2143z in forum Windows XP
    Replies: 25
    Last Post: November 2nd, 2004, 01:28 AM
  4. Replies: 2
    Last Post: October 1st, 2004, 04:18 PM
  5. A7M266 and Windows XP Home
    By VCTech in forum BIOS/Motherboard Drivers
    Replies: 2
    Last Post: November 21st, 2001, 08:10 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •