• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 22676
  • Last Modified:

Win XP Stuck in Continuous reboot cycle

The title says it; here my analysis so far:

I installed SP2 within the week before I shut it down and it did started this behavior. (The PC runs almost round the clock) Basically it boots up everythings normal it gets the the windows XP screen with the little progress bar then it shows the cursor. This is the buggy part. I press the OSD and no resolution is shown or set. The cursor is the only thing shown and works, but a few seconds later it reboots. Once in a while ill get an error talking about Not enough virtual memory or qouta. <-something similar to that and again reboot.


Drink was spilled on the USB keyboard.

After thorough wash and air dry, i plugged keyboard back in and keyboard still did not work, though the caplock lights came on.

Popped open the key matrix and found charred wires all over it.

Got a new keyboard plugged it in, and worked just fine but still cant get to the login screen.

Ive tried chkdsk and used recovery console as well as used XPs Repair setup.

Compaq restore doesnt boot.

I followed MS procedure for deleting Pagefile.sys but still get same reboots.

I beleive SP2 could be the problem but unfortuantanly i couldnot find the  $ntservicepackuninstall$ in the root directory, using recovery console and folllowing MS directions. I never fully had SP2 on the system but i beleive the install was completed but the system needed a restart which i denied. I did find a lot of the ntuninstall folders but most seem to be XP hotfixes.
0
tim102096
Asked:
tim102096
  • 13
  • 8
  • 4
  • +1
1 Solution
 
SheharyaarSaahilCommented:
Hello tim =)

Can you boot the system in safemode ??
When you did the repair install... which CD you used ??
Have you read here yet ??

How to use the Automatic Recovery feature to recover your computer or your Tablet PC if the Windows XP Service Pack 2 Setup program is not completed successfully
http://support.microsoft.com/default.aspx?scid=kb;en-us;875355&Product=winxp
0
 
tim102096Author Commented:
No i cannot boot into safe mode or DOS. Not of the F8 options work. I used to XP setup disk to get recovery console and the repair setup.
0
 
tim102096Author Commented:
O yeah that link you gave, thats the one i used for the SP2 uninstall from recovery console but i couldnt find the $ntservicepackuninstall$ folder or whatever it is :(
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
SheharyaarSaahilCommented:
Using Recovery Console and Doing a Repair Install are two different things.... see here >> http://www.webtree.ca/windowsxp/repair_xp.htm

Seems like you have tried using Recovery Console... but not yet tried the Repair install.... and im afradi that you cannot try it as Compaq Restore CDs dont give the Option of Non-Destructive Install! =\

Try this, use of the CDs listed below.... by using such CD you can boot with them and can enter in the OS to do some operations,,,,, so try to check that if you can enter into the system and if can use Add Remove Programs to remove SP2 or atleast use the System Restore to the date when system was working fine!!

Bart's PE Builder CD:
http://www.nu2.nu/pebuilder/

EBCD - Emergency Boot CD
http://ebcd.pcministry.com/

Knoppix - Linux Based CD
http://www.knoppix.org/
0
 
huntersvcsCommented:
Sounds like you might have fried the PS/2 Port - or - your keyboard is still acting up.  Try (1) another keyboard; and if that doesn't work (2) get a replacement PCI PS/2 card and try a different keyboard over that.
0
 
EladlaCommented:
what keyboard did you get?
It might sound stupid, but I have seen this mistake a million times.
If it`s an MS one, then remember to turn on the "F Lock" key before trying to press F8 in order to go into safe mode.

If this works, when in safe mode, I would check out the eveny viewer.
0
 
tim102096Author Commented:
Ok first, i have done repair install and recovery console (Windows CD in...Press R go through the stuff) I beleive the PS/2 port is working fine because i have a new keboard working fine on the same port the old one was on. I have gotten it to boot safe mode and dos but none of this fully boots, it freezes or if trying to boot into windows safe mode or not reboots. The keyboard i got is a wireless....ill check the name...but it works fine.
0
 
huntersvcsCommented:
Can you now get into the BIOS?  If so, check to make sure that PS/2 is activated.  Sometimes, if the BIOS can't find the keyboard (even just once) it could be trying to access something else (i.e. DIN, USB, whatever).  You can also check to see if HALT ON ALL ERRORS is set and change it to HALT ON ALL BUT KEYBOARD.
0
 
SheharyaarSaahilCommented:
>> Ok first, i have done repair install and recovery console (Windows CD in...Press R go through the stuff)
nooo..... for repair install. you have to boot with the cd. then have to press "Enter" to start a fresh windows installation.... then it will examine your system and will tell that an existing Operating System is found..... do you want to repair it, at THIS stage you have to press "R" to perform a repair!!

pressing R on the very first screen will take you to the Recovery Console which cannot do any repair! =\
0
 
EladlaCommented:
From my experience on cases like this one, it almost never finds the currentlly installed OS and will ask you to install windows fresh, if it does that, then sorry, but you will not have meny options.
0
 
tim102096Author Commented:
...ok....i didnt go into specific procedures but yes i have been through the repair i atleast know that much about what im doing ;) (Recovery console is similar to DOS, windows repair is similar to 16 bit color programs). When i did the repair before i did the recovery console, it went fine copied everything fine but i did get an error on GETIMUS entry points...not found...MSDART.dll was the error one, but if i understand correctly this deals with SQL and is not essential for Boot, supposedly windows also names this wrong as MSDART.dll instead of MSDART32.dll, i clicked through about 30 error messages wit hthe same dll call from different things and everything went through.  When i first booted with the new keyboard and ran the repair, it had a problem with hidusb.sys, and then with another .sys file but it disappeared the second time arround on repair. Before the repair the cursor would not show at all. It would get to the windows load screen then after a few reboot. After the repairs it made it to the cursor and 32 bit color (Read original comments).
0
 
tim102096Author Commented:
pressing R on the very first screen will take you to the Recovery Console which cannot do any repair! =\

Yes you can ;) Just that its a little more advanced and requires you know exactly what the problem is and what your doing. Unfortunantly the problem may be bigger so recovery console problaby isnt the most efficent way.
Bart's PE Builder CD:
http://www.nu2.nu/pebuilder/

EBCD - Emergency Boot CD
http://ebcd.pcministry.com/

Knoppix - Linux Based CD
http://www.knoppix.org/
About that ^ would prefer not having to buy anything, because im extremely low budget :(.
I fear that i will have to wait untill income taxes get a new computer and put this harddrive as a slave. :( Ive got stuff in this harddrive i can probably never get back, and is very valuable. Sigh i wish i could offer one of you points but so far most of it is all that ive tried. I maay split them thanks for the help. Any more suggestions are welcome :(

Qoute:
Can you now get into the BIOS?  If so, check to make sure that PS/2 is activated.  Sometimes, if the BIOS can't find the keyboard (even just once) it could be trying to access something else (i.e. DIN, USB, whatever).  You can also check to see if HALT ON ALL ERRORS is set and change it to HALT ON ALL BUT KEYBOARD.

Do not quite understand, i know the ports are activated and keyboard and mouse both work fine. As far as halt on all errors hmmm...where would that be....Ive beens into the boot options, when i press F9 at bootup and seived through everything in their and made sure all was good, but didnt find that. sorry if that is bios setup im not good with names of programs, dealing with the bios, etc. But some of you dont seem to understand, my new USB KEYBOARD works just fine in recovery console and everything i have access to =)
0
 
SheharyaarSaahilCommented:
>> About that ^ would prefer not having to buy anything, because im extremely low budget :(.
Bart's PE is free! :)
0
 
huntersvcsCommented:
OK, if it works in the console (and evidently in DOS since you can get into the BIOS) then most likely BIOS is not the issue.  Does the BIOS include an entry for USB-Keyboard support?  Even if it works in DOS (Console), the info it provides to the OS may be flaky.

You mentioned above that during repair you did have a temporary problem with hidusb.sys - Human Input Device USB?!

It could very well be that the kbdclass.sys is damaged/corrupted.  Go into the console under Windows\System32\Drivers and rename it kbdclass.old.  When you reboot the restore function should set you up with a fresh copy.

The continuous rebooting is probably being caused by the system itself when it encounters a non-repairable error (like 32-bit drivers).  If I remember right you can turn this off.  What you then get, instead of a reboot, should be the popular BOD (Blue Screen of Death).  This screen, however, can most likely tell you where the problem lies - it's usually one of the last entries in the table.  I had this once on an NT Workstation - I renamed the problem file and then could boot in an repair.
0
 
tim102096Author Commented:
Thankyou hunter this advice seems very true to my situation.
(I know Barts PE free now but i have limited access to CD burners right now :( )
I will try the advice tonight. The hidusb.sys keep in mind only came up during the inital attempts at repair, it actually stopped setup from starting. Apparently it fixed though because after that setup booted fine.

Qoute:
It could very well be that the kbdclass.sys is damaged/corrupted.  Go into the console under Windows\System32\Drivers and rename it kbdclass.old.  When you reboot the restore function should set you up with a fresh copy.

The continuous rebooting is probably being caused by the system itself when it encounters a non-repairable error (like 32-bit drivers).  If I remember right you can turn this off.  What you then get, instead of a reboot, should be the popular BOD (Blue Screen of Death).  This screen, however, can most likely tell you where the problem lies - it's usually one of the last entries in the table.  I had this once on an NT Workstation - I renamed the problem file and then could boot in an repair.

Excellent advice. I will try it tonight.

Does the BIOS include an entry for USB-Keyboard support?  Even if it works in DOS (Console), the info it provides to the OS may be flaky.

This could be it to, I am using a usb keyboard without the drivers installed off the CD. so far in what works the keyboard is fine though and it does have an entry for USB Keyboard support. I have gotten the BOD once or twice but it was rare. I am not sure their is a option to turn off the nonrepairable error errors, ill look again. (Compaq Pesario....looking it up....)
0
 
huntersvcsCommented:
Hi Tim,

Just did some additional checking on my workshop PC.

It appears that SP2 updated several USB drivers and left one or two old ones alone.  Here are the ones that come to mind:

usbd.sys
usbhub.sys
usbport.sys
usbuhci.sys
usbehci.sys

These are located, of course, under C:\Windows\System32\Drivers

All should be present, and with the exception of the USBD.SYS, all should have the same date.  I renamed each of these .OLD and Windows automatically regenerated a fresh copy.  You might also try this (if the above doesn't help), making sure that (a) no other USB devices are connected (initially) and (b) try switching to a different USB Port for your keyboard.
0
 
tim102096Author Commented:
Yeah the previous stuff didnt work, though if it changes much windows scandisk did run, ill try the new stuff tonight, hunter thanks for so much good advice.
0
 
tim102096Author Commented:
Nothing works...I found that if i push F8 now though that the advanced startup utility will show with like 10 more options than it used to....Debugging Mode....Domain REsotre something....etc. However none of it is of much help. I booted command prompt in safe mode however winodws actually ended up booting,  however before windows boots a list of .sys files i nthe DRIVERS folder shows up. If i rename on of these like mup.sys at the end. Everythings the same but the .sys file does not show. Could i be missing one? As i said before the message Not enough paging qouta or virtual memory or soemthing has to have something to do with it. I get that message all the time. By the way windows doesnt replace the renamed DLLs unless i do a repair (doesnt boot far enough).
0
 
huntersvcsCommented:
Hi Tim,
I don't believe I recommended renaming DLLs - only SYS files under Drivers.  Renaming the DLLs (as you found out) causes nothing but problems!  Since you can now (I believe) boot into Safe Mode, start there.  Go into the equipment manager and check all USB devices (keyboard, mouse, cam, etc.) to see if there are multiple entries.  If so, delete them (but ONLY the USB devices, hubs, etc.).  Windows will restore the ones needed on reboot.  I don't know if you can adjust the virtual memory in Safe Mode - never tried to!  But you should be able to deactivate the REBOOT command on system failure.  The error message may give you more info.  You could also see if you are able to go back to a previous RESTORE POINT - sometime before all the troubles started.

Let me know if anything helps!
0
 
tim102096Author Commented:
I meant sys files :) didnt rename any dlls, and no i still cant get to anything good in windows, it still reboots after the message even in safe mode :S. Sigh. Hunter if i get this working you deserve more than 500 points thats for shore thanks for all the research and aid so far.
0
 
huntersvcsCommented:
What happens if you try booting without the keyboard?
0
 
tim102096Author Commented:
Sorry for the late reply, nothing different happens :(.
0
 
tim102096Author Commented:
Ill grant you points though. This problem is evidently pretty deep.
0
 
huntersvcsCommented:
Sorry I couldn't help more.  I still think it's a driver conflict issue.  Thanks for the points.

Just a thought:  did you try (back at the beginning) resetting the BIOS default options?
0
 
tim102096Author Commented:
Ill give it a go.
0
 
tim102096Author Commented:
Nope still didnt do anything.
0
 
huntersvcsCommented:
If you've more than one memory slot filled (i.e. 2x 256MB) try removing one - if that doesn't help try the other one instead.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 13
  • 8
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now