Well, everytime I start my computer the past 2 days, it says that my C:\Windows\system32\system file is corrupted or missing. I think the file is a devisce driver. Anyway, I have to boot from my Windows XP CD and it repairs it. But it does it all over again the next time I fire up my computer. Anyone else have a similar problem that might know how to fix this?
-
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
Windows XP PRO blem.
- Thread starter Joker76
- Start date
- Joined
- Sep 2, 2001
- Location
- Elkhart, Indiana
that happens when you oc to high....
- Joined
- Sep 24, 2001
- Location
- Currently Nowhere
The theory should be easy enough to test. Just back down your speed to default and reboot. The problem will either show up (and it's NOT the O/C) or go away (the O/C IS the problem).
Otherwise, you might have a bad sector on your HD to which the driver keeps getting written. Though XP should detect bad sectors automatically (and then mark it as such), you may want to try a disk integrity utility to see if there are any problems.
Otherwise, you might have a bad sector on your HD to which the driver keeps getting written. Though XP should detect bad sectors automatically (and then mark it as such), you may want to try a disk integrity utility to see if there are any problems.
- Joined
- Feb 2, 2002
- Location
- St. Louis, Missouri
I get this problem whe i put in my other sticks of ram. so im stuck at 128
- Joined
- Feb 2, 2002
- Location
- St. Louis, Missouri
It's still the same FSB, and it didn't work at the default speeds. They only worked at 100mhz.
