File system corrupted

[Banzai042]

Ok, here's the situation: last night i set my computer to hibernate instead of shutting it down, when i came back this morning my network connection suddenly stopped working, so i rebooted, only to have very weird behaviors during the boot process (taking faaaaaar longer than normal to load everything in windows), no network usability, and an inability to install any new drivers from CDs (to try and get network operational again). Suspecting a hard drive problem because the comp recently said that it couldn't save data to specefic sectors during a recent shutdown i downloaded the segate HDD utility (i have 2 120 gig gen 7 drives) and ran it. According to the utility all of my partitions have corrupted file systems, all 3 have errors in the index, and the 2 that have programs installed on them have errors in the metadata. Is there any way for me to fix this, or am i limited to a reinstall?

 

[LiLithTecH]

Are you Overclocking?

If not, I would suspect the RAM as the culprit.

 

[dclive]

Originally posted by: Banzai042
Ok, here's the situation: last night i set my computer to hibernate instead of shutting it down, when i came back this morning my network connection suddenly stopped working, so i rebooted, only to have very weird behaviors during the boot process (taking faaaaaar longer than normal to load everything in windows), no network usability, and an inability to install any new drivers from CDs (to try and get network operational again). Suspecting a hard drive problem because the comp recently said that it couldn't save data to specefic sectors during a recent shutdown i downloaded the segate HDD utility (i have 2 120 gig gen 7 drives) and ran it. According to the utility all of my partitions have corrupted file systems, all 3 have errors in the index, and the 2 that have programs installed on them have errors in the metadata. Is there any way for me to fix this, or am i limited to a reinstall?

Just boot into the OS and run chkdsk -f a few times; reboot when prompted.
Or boot into the recovery console and run chkdsk -p from there.