CHKDSK Failure?

wushudragon84

New member
Local time
4:24 PM
Messages
3
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.
 

My Computer

OS
Windows 7
CPU
Intel Quad Q6600
Memory
4 GB DDR2
Graphics Card(s)
NVidia 9800
Hard Drives
Hitachi 750gb
Case
Antec
Cooling
Air Cooled
I would be hesitant to stop a chkdsk run if it is making corrections to the bitmap. Doing so could corrupt the drive to the point of it not booting.

However, since the drive isnt bootable anyway, stop it. Grab all the data off of it then try a repair install once the drive is reinstalled, but be prepared to perhaps do a clean install if that doesnt work.

Also, I would invest in a battery backup since you have electrical issues at your house to help protect these computers. )

You can also try to launch command prompt from a Windows 7 disc and issue the commands:
BootRec.exe /fixmbr
BootRec.exe /fixboot
 

My Computer

Computer Manufacturer/Model Number
ATX Custom Build 2012
OS
Windows 7 Enterprise x64 SP1
CPU
Intel Core i3-2100 @ 3.10GHz
Motherboard
Intel DH67CL desktop ATX
Memory
10 GB DDR3
Graphics Card(s)
Asus EAH5450 series (Radeon)
Monitor(s) Displays
Samsung SyncMaster 226BW, Samsung Syncmaster P2450H
Screen Resolution
226BW: 1680 x 1050 & P2450H: 1920 x 1080
Hard Drives
Western Digital 320 GB sata (boot), Samsung 640 GB sata, Seagate 2 TB sata (data)
PSU
Cooler Master Extreme Power Plus 500W
Case
Thermaltake V3 Black Edition
Cooling
stock cooling with added intake fan
Keyboard
HP Wireless Elite Keyboard Wireless Keyboard
Mouse
Microsoft Touch
Internet Speed
Comcast Cable business class <=18Mb {averages 12Mb}
Other Info
Optical drives: LG SuperMulti Blue, HP DVD 1260T
Other: Kensington Bluetooth Receiver
Network: Buffalo Wireless N USB, DLink N router/DLink Ethernet Switch/DLink Xtreme N wireless bridge
Printer: HP Photosmart Plus, HP Officejet Pro 8600 Plus
PCs: HP dv6-3040us (7 x64 SP1), HP DM4-2165dx (7 x64 SP1), HP Pavilion zv6130us (7 x86), Apple Macbook Air (Lion)
************

My Computer

OS
ME/XP/Vista/Win7
(This is in reply to Merkat)

Thanks for the suggestion, but I can't afford to base my actions off "what if's"--if you will. I need a more definitive answer as to whether it's been too long, probably stuck, or what ever is the case.

Any idea? What would cause it to go on for 33 hours?
 

My Computer

OS
Windows 7
CPU
Intel Quad Q6600
Memory
4 GB DDR2
Graphics Card(s)
NVidia 9800
Hard Drives
Hitachi 750gb
Case
Antec
Cooling
Air Cooled
Why would you use V/X/R? V would simply display clean up messages, X would dismount (something worth doing) and R would locate bad sectors. Shouldn't there also be an F?
 

My Computer

OS
Windows 7
CPU
Intel Quad Q6600
Memory
4 GB DDR2
Graphics Card(s)
NVidia 9800
Hard Drives
Hitachi 750gb
Case
Antec
Cooling
Air Cooled
Back
Top