- Joined
- Jul 10, 2010
- Messages
- 1
- Reaction score
- 0
I have a "custom" built PC with:
Windows 7 Ultimate (64-bit)
Q6600 Quad Processor
4 GB DDR2 Ram
750 GB Hitachi HDD (SATA)
Nvidia 9800 Graphics card
1000watt Power supply (Black Widow)
MOBO - Don't know without looking
Air Cooled Antec case
Anyway, I had some power issues in my house and my computer was turned off abruptly at random times due to power loss. After it happening for like the 6th time, the computer freezes on the Windows (Flag) start up screen.
I used "Eurosoft: PC Check" to check my hardware and it turns out I had a read test failure on the HDD. Well this can easily be fixed by a CHKDSK fix to repair bad sectors of the HDD. However, my PC would not even boot into safe mode to run the command prompt CHKDSK.
So, in order to repair the HDD, I set it up as a static on my other ASUS built PC:
Windows 7 Home Premium (64-bit)
Intel i7 Core (8 core) Precessor
9 GB DDR3
Hitachi 7200rpm 1TB HDD
Nvidia GTX 480
1000watt Power Supply (Black Widow)
Asus MOBO
Air Cooled
and used the GeekSquad tool MRI 5.0.1 to run a CMD prompt. Typed in CHKDSK D:/r/f (D is the drive's static name) and select run. It wasn't able to dismount it and told me to run it at next start up. And so I selected "yes" and rebooted. Right off the bat in phase 1 it said it was deleting bad or corrupted sectors I believe and then continued a few minutes later into scrolling "Correcting errors in the volume Bitmap." However, I've had it running for about 33hours and it's still scrolling "Correcting errors in the volume Bitmap."
I've read the corruptions typically take a while to repair and so I've waited it out, as it IS a 750gb HDD. However, I feel it's a bit excessive and I don't know if I should interrupt it or not.
So, the question is (give me a real answer, not a copy and paste), should I stop it and rerun one? If so, what if it does it again? Or should I stop it and attempt to boot it. I fear that if it has already deleted some sectors and it hasn't repaired them yet, that booting it might actually cause MOAR (lol the geek in me) damage to the HDD.
Any Ideas?
Thanks.
Windows 7 Ultimate (64-bit)
Q6600 Quad Processor
4 GB DDR2 Ram
750 GB Hitachi HDD (SATA)
Nvidia 9800 Graphics card
1000watt Power supply (Black Widow)
MOBO - Don't know without looking
Air Cooled Antec case
Anyway, I had some power issues in my house and my computer was turned off abruptly at random times due to power loss. After it happening for like the 6th time, the computer freezes on the Windows (Flag) start up screen.
I used "Eurosoft: PC Check" to check my hardware and it turns out I had a read test failure on the HDD. Well this can easily be fixed by a CHKDSK fix to repair bad sectors of the HDD. However, my PC would not even boot into safe mode to run the command prompt CHKDSK.
So, in order to repair the HDD, I set it up as a static on my other ASUS built PC:
Windows 7 Home Premium (64-bit)
Intel i7 Core (8 core) Precessor
9 GB DDR3
Hitachi 7200rpm 1TB HDD
Nvidia GTX 480
1000watt Power Supply (Black Widow)
Asus MOBO
Air Cooled
and used the GeekSquad tool MRI 5.0.1 to run a CMD prompt. Typed in CHKDSK D:/r/f (D is the drive's static name) and select run. It wasn't able to dismount it and told me to run it at next start up. And so I selected "yes" and rebooted. Right off the bat in phase 1 it said it was deleting bad or corrupted sectors I believe and then continued a few minutes later into scrolling "Correcting errors in the volume Bitmap." However, I've had it running for about 33hours and it's still scrolling "Correcting errors in the volume Bitmap."
I've read the corruptions typically take a while to repair and so I've waited it out, as it IS a 750gb HDD. However, I feel it's a bit excessive and I don't know if I should interrupt it or not.
So, the question is (give me a real answer, not a copy and paste), should I stop it and rerun one? If so, what if it does it again? Or should I stop it and attempt to boot it. I fear that if it has already deleted some sectors and it hasn't repaired them yet, that booting it might actually cause MOAR (lol the geek in me) damage to the HDD.
Any Ideas?
Thanks.