Computer won't get past bootscreen, just reboots

Static EMP

Member
Oct 26, 2004
104
0
0
Today, my computer started only making it to the bootscreen, where it would load for a while and then just reboot again. My computer was working fine before this. The last thing I did before this was uninstall a couple of programs (iMesh and WinCVS to be specific, but that shouldnt matter). It asked me to reboot so I did. I've tried safe mode, safe mode w/command prompt, debug mode, and last known good config, but the problem persists. Is there anything I can do to fix this? I can't use my computer at all now!

Thanks!
 

imported_tomcat1

Junior Member
Sep 15, 2005
23
0
0
I had a similar problem that caused me to purchase new hardware, MB, HD Memory ect and it turned out to be a intermittent short in my reset switch on my case. After months of rebooting and frustration and money I disconnected the switch from my NEW motherboard and that fixed it.
 

ZoomStop

Senior member
Oct 10, 2005
841
0
76
Static - Windows is doing the 'ol Reboot on Crash routine that can be so annoying. The only problem is it is a major PITA to change it when your system is already broken.

So what your going to want to do is either:
1. Take the hard drive out of your PC and install it as a slave in another PC. Then get a good registry editing program and change the key below.
2. Get a PE disc like BartPE or MiniPE and boot into the PE off the disc and change the key below.

Browse to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
and change the AutoReboot key from 1 to 0.

Once you do all that you'll be able to see the STOP code that is being generated and using that we should be able to find out what the problem is :)

PS - if anyone knows of an easier way to regedit I'd love to hear it. I am pretty sure regedit is useable from the command prompt but I have never tried to edit keys from DOS or the recovery console.
 

montag451

Diamond Member
Dec 17, 2004
4,587
0
0
I think you can only use Regedit for the registry in use.

There MAY be some third party yoots that MIGHT allow you to do this.
That would be a good idea if there was.
Will post back if I find sommat.
 

FlyingPenguin

Golden Member
Nov 1, 2000
1,793
0
0
Could have been caused by a variety of things including a corrupt registry, spyware, bad uninstall of an app.

The quick fix is to perform a manual registry restore which will allow you to boot into safe mode. From there you can use System Restore to go back to a restore point prior to the problem occuring.

Instructions for a manual registry restore here: http://support.microsoft.com/kb/307545

After restoring I would recommend a thorough spyware cleaning. Please follow my detailed instructions here: http://theflyingpenguin.com/spyware-removal.shtml

Then perform a FULL virus scan in SAFE MODE.

Hope this helps...
 

Static EMP

Member
Oct 26, 2004
104
0
0
This is the STOP code:

c000021a {Fatal system error}
The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000135 (0x00000000 0x00000000). The system has been shut down.


If any of you know what this means, and how I can fix it, that would be great! Thanks!
 

DAPUNISHER

Super Moderator CPU Forum Mod and Elite Member
Super Moderator
Aug 22, 2001
30,807
28,355
146
FP already gave you the fix for it, see for yourself. Before you do that you can try a more generic and less involved fix, if you find the MSKB resolution rather involved. Boot from the XP CD, hit R for the recovery console, then type chkdsk /r. When its done, type fixboot, then reboot and see if you can get to desktop. If it doesn't make it the more involved registry restore is the ticket.