HELP!!! Can't log into windows

[lordtyranus]

System Rig:
Athlon XP 2500+ @ 2.2 ghz
1 GB Generic 2700 DDR
Biostar NCVND Pro motherboard
Geforce 6800 GT

The system has been the same for 2 years (except the video card) with no issues.

Yesterday my computer inexplicably crashed. Upon restarting, I found that it would get a blue screen error upon logging into windows. I went into bios and reset defaults, after which I was able to log into windows successfully. However, any overclocking over the 1.8 ghz stock resulted in a blue screen error again.

It worked fine for a day or so, after which it froze. I restarted, but again I got the blue screen error as windows was starting up. It says "cannot log into windows, domain error 0xx0x0000000" or something to that effect. I have tried resetting the bios again to no effect.

I can successfully log into safe mode, which I used to get a couple needed files for homework. I am going to see if I can burn a CD now to get the rest of my files.

Can anyone tell me what is happening?

 

[chocoruacal]

The overclocking adds too many variables to say with any certainty. Your best bet, IMO, is to set the CPU and RAM to SPD/stock. Then run Memtest86 overnight. If you're lucky, Memtest will spit out errors and you can replace the RAM. If Memtest86 doesn't error, you're left reinstalling teh OS or swapping out parts. Could be a bad PS, hard drive, or CPU causing data corruption with your OS install. Are you running XP? Check Event View and see if anything useful is reported there (fat chance though).

 

[SaturnX]

Like mentioned above, by OC'ing the system, you throw in a lot of uncertainty with what could potentially be wrong. My first instinct is to check RAM, and if all that checks out, I'd bet to say it's data corruption on the HDD caused by the OC'ing... heh I've had that happen before.

--Mark

 

[lordtyranus]

Originally posted by: chocoruacal
The overclocking adds too many variables to say with any certainty. Your best bet, IMO, is to set the CPU and RAM to SPD/stock. Then run Memtest86 overnight. If you're lucky, Memtest will spit out errors and you can replace the RAM. If Memtest86 doesn't error, you're left reinstalling teh OS or swapping out parts. Could be a bad PS, hard drive, or CPU causing data corruption with your OS install. Are you running XP? Check Event View and see if anything useful is reported there (fat chance though).

Well, right now it is at stock speeds. After the first crash, I reset to stop speeds.

 

[lordtyranus]

Update: I ran prime95 in safe mode for 3 hrs. No crashes. Don't think CPU or RAM is the problem.