Corrupted Registry

[DeathByGrogg]

Allright guys. Windows 7 is robbing me off my damn holiday.

Every single time i install it, after some time (Windows updates? Dunno) it won't start, instead booting into it's incredibly unusable startup repair utility to inform me that it can't do anything, and that i have a Corrupted Registry. This happens EVERY SINGLE TIME i install, and frankly it's getting a bit annoying.

What could be causing this?

Specs:

GeForce FX 5700
SoundBlaster Audigy 2
P4 3Ghz
Gig O' Ram
Brand spanking new 1 TB-HDD

 

[sup3rsprt]

so, it runs fine as long as you don't install updates or drivers?

 

[DeathByGrogg]

Scratch that. I just tried reinstalling and turning off automatic updates. No go.

This time, i even refrained from installing the GeForce drivers. Just installed the standard Realtek AC'97 Drivers (removed the SoundBlaster).

 

[fseal]

My two bets would be Memory problem (could be chipset driver related) or Hard Drive Driver issue.

Unfortuantely if the default drivers are not good enough to be stable to the point that you can install real motherboard/storage drivers, it's going to make it tougher.

But you might try switching to IDE mode in the bios (no AHCI). Definately removing any over clocking if you have any. Heck maybe even a full BIOS reset is in order.

It may also be that your install disk is corrupt, didyou burn it yourself? Or is is a factory disk?

Might try a new DL/Burn at a slow speed, then "check" the disk after the burn (burning siftware option susualy).

You could also try removing some ram, if you have 4 gig, remove 2 gig and try installing with that. THen update the motherboad drivers and reinstall the second two gig after you are sure it is stable on 2.

 

[sup3rsprt]

Just installed the standard Realtek AC'97 Drivers (removed the SoundBlaster).

the problem happens before or after installing drivers?

registry errors could point to a problem with hardware such as memory or hard disk (edit - a conclusion which fseal just beat me to)

 

[DeathByGrogg]

The disk is burned by myself, after an .iso acquired from the Microsoft Academic Alliance. I burned it at slow speed, and verified it, 100% correct. The problems arise after a few reebots, sometimes a few days, sometimes an hour. I suppose it might have to do with driver related issues, but i'll follow your advice and use some different hardware.