Hooked up a monitor and blew the OS system out. Why?
Last night, hooked up a brand new monitor and turned the pc back on - only to find that the system 32 file was corrupt (?) and needed to repair the file (?). Basically, I am in the process of complete OS install. This sucks.
This system was rebuilt two months ago:
x2 4800
Asus 8n vm mobo
2 hard drives
9800 gt
audigy 2 zs
floppy drive
Wave Master case
xp pro
Samsung 22 monitor
Thanks for the reply. I had to move my post to the correct area. I've got several forum users that suggest it might be memory modules that are possibly corrupt or going bad.
If you check out the survey I'm thinking about taking on this pc, I'd have to put you vote for C and D.
C)Scream some really bad profanities (Especially trying to figure out what MS is trying to say about fixing a corrupted registry!)
D)Have patience with it and pray that the Lord will forgive me for my profanity (see C).
Problem found. It was a hard drive going out. Grrrr. This explains why last month the OS got blown out for no clear reason.... and why I could not install RAID 0 when trying to reinstall the OS.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.