Need Troubleshooting Help with i7 Rig

[Jeff_C]

I've just had a crash with my i7 rig and could really use some help sorting it out. I'm running Windows XP Pro and the last PTLE 8.0.3cs release before 8.0.4 became official.

When I powered the PC up, BIOS startup screens looked normal. I got the windows logo, then the screen went black and never displayed the user login screen. When I restarted, my USB keyboard wasn't working, so I couldn't go to the BIOS setup or hit F8 for Safe Mode.

When I plugged in a PS/2 connector keyboard, Safe mode worked normally. No hardware errors in device manager. Restart and I get stuck again on the black screen before the login screen.

I got back to safe mode and deleted my vid card drivers and the computer runs fine with windows standard VGA drivers. If I reinstall either the latest ATI drivers or an old one, my lockup returns. Now I've gotten a "registry is full, nothing more can be written" message.

I'm running cnet's favorite free registry repair/cleaner now. What's next?

Here's the hardware list:
Gigabyte GA-EX58-UD3R (V 1.0) Motherboard
Intel i7-920 CPU
Noctua NH-U12P SE1366 CPU Cooler
6GB OCZ3P1333LV6GK (3 x 2GB kit) Memory
HIS H465PS512P Silent (Fanless) Video Card
Western Digital WD10EADS OS Hard Disk (1TB, 32MB cache, 7200RPM)
Seagate ST3120813AS Audio Hard Disk (500GB, 32MB cache, 7200RPM)
Samsung SH-S223Q DVD Burner
Nexus RX8500 Power Supply

[Keybeeetsss]

Get to ur Cmd prompt in safe mode or with the Disk & type FIXMBR & then after that runs, type FIXBOOT & see if that gets u up...

[Jeff_C]

Originally Posted by Keybeeetsss

Get to ur Cmd prompt in safe mode or with the Disk & type FIXMBR & then after that runs, type FIXBOOT & see if that gets u up...

Thanks, Keybeeetsss! I'll give it a shot & report back.

[Hotcrazyfruit]

Try using different driver versions. Try the one on the CD that came with your graphics card, also try the latest one on ATI's website.

[sunburst79]

Google the "registry has exceded is maximum amount and no data can be written" message. I had this about a year ago and as I recall it was related to the Intel storage driver.

Out of curiosity whty did you delete the video drivers?

Registry cleaners may not do you any good in this situation. Some times you need to run Regedit, roll up your sleeve and delete stray entrys by hand.

[Jeff_C]

Originally Posted by sunburst79

Google the "registry has exceded is maximum amount and no data can be written" message. I had this about a year ago and as I recall it was related to the Intel storage driver.

I didn't see the Intel storage driver issue when searching, but it looks like a corrupt swap file is a likely candidate. I'm running chkdsk now, then I'll zero out the swap file, reboot, then let it recreate the swap file.

Originally Posted by sunburst79

Out of curiosity whty did you delete the video drivers?

After it worked in safe mode, I wondered if the computer was actually waiting for me to sign in but couldn't display the logon screen. It is still the case that the PC works as long as I use the generic windows video drivers.

Originally Posted by sunburst79

Registry cleaners may not do you any good in this situation. Some times you need to run Regedit, roll up your sleeve and delete stray entrys by hand.

That seems to be true. It keeps finding the same empty keys over & over again. Maybe it will get better after the page file is cleared.

[Jeff_C]

Originally Posted by Keybeeetsss

Get to ur Cmd prompt in safe mode or with the Disk & type FIXMBR & then after that runs, type FIXBOOT & see if that gets u up...

I haven't tried this yet, Key. Microsoft's knowledge base says this will help if you are locking up before the windows logo appears. I'm locking up after the logo appears but before the logon screen.

There were also a couple of references to people losing their partition data when using fixboot. That scares me.

I'm keeping it in the back of my mind...

[Keybeeetsss]

OH; well no, u shouldn't do so if ur locking up afterwards; jus do as SB suggested & google that error; it also happened to me once; its a simple fix but I couldn't begin to remember what it was...

[Jeff_C]

It looks like clearing the swap file solved the problem. Here are the steps I took:

1. Run error checking on my OS disk (required a reboot). No errors found.
2. Turned off swap file & rebooted.
3. Defrag OS Disk.
4. Turn swap file back on & reboot.
5. Install latest ATI video drivers & reboot.
6. Everything seems to be working normally.

Thanks for the tip sunburst79. It sent me down the right path.

I do appreciate the way many of you folks (Keybeeetsss & many others) jump in to help folks so often. Y'all make the DUC a useful and cool place.

[Keybeeetsss]

Good deal Jeff