Overclock.net › Forums › Components › Hard Drives & Storage › HDD ,Controler or Chipset Error ?
New Posts  All Forums:Forum Nav:

HDD ,Controler or Chipset Error ?

post #1 of 2
Thread Starter 
First problem was slowdown in general on everything longer boot into windows random crashes in Google .

Next prob it failed to load the nvidia on board video drivers got stuck on a light blue screen w/circle of death would not load windows normal or safe mode also would not run start up repair from safe mode either. Made a startup repair CD on my other computer went into bios set Cd as 1'st drive booted this comp from that
after several times running startup repair from CD it started working normally . chkdsk f /r found corrupted volume C and some file in google I think and replaced those files .
it found 4kb in bad sectors and marked them .

About 3wks later same thing would not load windows ran startup repair CD got it working chkdsk f /r found 1180 KB in bad sectors it added 2 bad clusters and corrected the volume bitmap. it's been holding steady at that.for 3 days no errors in event viewer then 7 errors in event viewer today . chkdsk only no /f /r today does not report any more bad clusters or sectors since last chkdsk f /r
I wonder if these are logical read errors or bad physical sectors as in a failing drive or maybe a bad /failing HDD controller or motherboard chipset

Comp is working fine for now no bad files found today sfc /scannow finds nothing either . Of course the smart drive fails the HP test (otherwise windows would not see errors as the smart drive would take care of them first. ) also it fails Seatools smart test and will not go to extended test but it passed both short and long Western digital lifeguard drive tests .and windows chkdsk /f /r

Avast, Malwarebytes and MSE come up clean . defrag works also drive is only about 30% full . system works good back up to speed and all now.

What is interesting it works fine now but every 3 days I get about 7 disc errors in a row in event viewer along with 7 nvstor64 errors . I updated MB chipset drivers HDD firmware
and video drivers.I'm thinking an HDD controller error or MB chipset error?

Thinking about zeroing the drive and a clean format install . But then again if the bad sectors do not increase maybe it is just trying to read a corrupt file but then again chkdsk should point the hdd away from the ones already re allocated and it should not have read errors so maybe it is the drive or controller no noises though .

Computer is a readymade HP s5302f Win 7X64 HP SP1 slimline with an Athlon II X 2 240 4 GB ram 750GB Seagate 7200RPM sata III barracuda hdd,and dvdr+rw , Nvidia 6150se on board video HP , motherboard is an HP pegatron narra 6 motherboard Nvidia MCP61 chipset , 6.01 bios and an add on Asus DGX PCIE sound card w stock P/supply I'll post the logs below in case any one would like to hazard a guess all software and windows updates/hotfixes are current drive is only 30% full

winevent logs

Disk error,

Log Name: System
Source: Disk
Date: 5/18/2013 8:25:32 AM
Event ID: 7
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxx -PC
Description:
The device, \Device\Harddisk0\DR0, has a bad block.
Event Xml:

7
2
0
0x80000000000000

125734633
System
XXXX -PC


\Device\Harddisk0\DR0
030080000100000000000000070004C0000100009C0000C0000000000000000000B06A4C630000007D60550000000000FFFFFFFF000000005800008402000000EE200A1242072000000000003C0000000020790480FAFFFF80BD8D0380FAFFFF00000000000000004035070A80FAFFFF00000000000000005835A63100000000280031A6355800000800000000000000F00003000000000B00000000000000000000000000000000


nvstor64 error ,

Log Name: System
Source: Microsoft-Windows-UserPnp
Date: 5/17/2013 3:19:13 PM
Event ID: 20003
Task Category: (7005)
Level: Information
Keywords:
User: SYSTEM
Computer: xxxxx-PC


Description:
Driver Management has concluded the process to add Service umbus for Device Instance ID UMB\UMB\1&841921D&0&IPBUSENUMROOT with the following status: 0.
Event Xml:

20003
0
4
7005
0
0x8000000000000000

125734527


System
xxxx -PC

umbus
system32\DRIVERS\umbus.sys
UMB\UMB\1&841921D&0&IPBUSENUMROOT
true
true
0
y>

Last chkdsk /f /r

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 5/15/2013 2:02:21 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer:xxxx -PC
Description:

Checking file system on C:
The type of the file system is NTFS.
Volume label is HP.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
487424 file records processed. File verification completed.
1969 large file records processed. 0 bad file records processed. 0 EA records processed. 77 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
574638 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
487424 file SDs/SIDs processed. Cleaning up 12 unused index entries from index $SII of file 0x9.
Cleaning up 12 unused index entries from index $SDH of file 0x9.
Cleaning up 12 unused security descriptors.
Security descriptor verification completed.
43608 data files processed. CHKDSK is verifying Usn Journal...
37513136 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x5d6128c000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x5d6128c000 for 0x1000 bytes.
Windows replaced bad clusters in file 480920
of name \SYSTEM~1\{BBDD1~1.
487408 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
131220640 free clusters processed. Free space verification is complete.
Adding 2 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

720993279 KB total disk space.
195248468 KB in 431931 files.
245184 KB in 43609 indexes.
1168 KB in bad sectors.
615903 KB in use by the system.
65536 KB occupied by the log file.
524882556 KB available on disk.

4096 bytes in each allocation unit.
180248319 total allocation units on disk.
131220639 allocation units available on disk.

Internal Info:
00 70 07 00 9f 41 07 00 8b 04 0d 00 00 00 00 00 .p...A..........
29 91 01 00 4d 00 00 00 00 00 00 00 00 00 00 00 )...M...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:

1001
0
4
0
0
0x80000000000000

84027


Application
xxxx-PC

Checking file system on C:
The type of the file system is NTFS.
Volume label is HP.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 5)...
487424 file records processed. File verification completed.
1969 large file records processed. 0 bad file records processed. 0 EA records processed. 77 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)...
574638 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)...
487424 file SDs/SIDs processed. Cleaning up 12 unused index entries from index $SII of file 0x9.
Cleaning up 12 unused index entries from index $SDH of file 0x9.
Cleaning up 12 unused security descriptors.
Security descriptor verification completed.
43608 data files processed. CHKDSK is verifying Usn Journal...
37513136 USN bytes processed. Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x5d6128c000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0x5d6128c000 for 0x1000 bytes.
Windows replaced bad clusters in file 480920
of name \SYSTEM~1\{BBDD1~1.
487408 files processed. File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
131220640 free clusters processed. Free space verification is complete.
Adding 2 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

720993279 KB total disk space.
195248468 KB in 431931 files.
245184 KB in 43609 indexes.
1168 KB in bad sectors.
615903 KB in use by the system.
65536 KB occupied by the log file.
524882556 KB available on disk.

4096 bytes in each allocation unit.
180248319 total allocation units on disk.
131220639 allocation units available on disk.

Internal Info:
00 70 07 00 9f 41 07 00 8b 04 0d 00 00 00 00 00 .p...A..........
29 91 01 00 4d 00 00 00 00 00 00 00 00 00 00 00 )...M...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Edited by preferreduser - 5/18/13 at 11:11pm
post #2 of 2
You need to reduce the amount of time you use this drive. It would be best to have no use at all.

Best for you to do is to us software (that can boot from CD so no need for windows) to migrate your drives entire contents to another drive in a one to one read.

Specialized software that is made for recovering data may be the better thing to use that just using a clone program but cloning may be fine as long as all the current locations of data are readable.

By loading windows automatically even if you do no work files are being moved around and accessed and can cause things that are not corrupt to be corrupt or corrupt things to be read and then cause an error.



After you have backed up all of your data you can feel free to completely wipe the old drive and then run some extensive tests on it using something like seatools.exe I would run the heaviest full drive write and read tests. This requires previous info to be wiped so you can not do it till you back your data up.



I am no pro but I have done this many times and one thing I can say for sure... if you value this data you stop in your tracks and do this correctly. You may only get one shot.
Edited by givmedew - 5/18/13 at 11:27pm
Silence
(20 items)
 
Secondary Rig
(9 items)
 
 
CPUMotherboardGraphicsGraphics
Intel i7-5820k  ASRock x99 extreme 4 AMD R9 290X AMD R9 290X 
RAMHard DriveCoolingCooling
ballistix ddr4 dual channel Samsung 850 EVO 500GB DT 5noz CPU Waterblock XSPC Razor Full Cover GPU Block 
CoolingCoolingCoolingCooling
XSPC Razor Full Cover GPU Block 4x120 Black Ice Xtreme GTX480 Swiftech MCP655 Danger Den Monsoon Pump/Reservoir 
CoolingOSMonitorKeyboard
Corsair Link Fan Controller Windows 8.1 Nixeus 2560x1440 Logitech G15 
PowerMouseMouse PadAudio
Kingwin PF-850 Ttesports Level10M Razer Vespula Sennheiser HD590 
CPUMotherboardGraphicsRAM
Intel i5-2500k gigabyte z68xp-ud4 Gigabyte GTX 970 G1 Gaming DDR3 1600 4x2GB 
Hard DriveCoolingOSMonitor
Western Digital Velociraptor 300GB w/ Intel RST... Corsair H100 Windows 8.1 1920x1200 HP 
Power
PC P+C 1000w 
  hide details  
Reply
Silence
(20 items)
 
Secondary Rig
(9 items)
 
 
CPUMotherboardGraphicsGraphics
Intel i7-5820k  ASRock x99 extreme 4 AMD R9 290X AMD R9 290X 
RAMHard DriveCoolingCooling
ballistix ddr4 dual channel Samsung 850 EVO 500GB DT 5noz CPU Waterblock XSPC Razor Full Cover GPU Block 
CoolingCoolingCoolingCooling
XSPC Razor Full Cover GPU Block 4x120 Black Ice Xtreme GTX480 Swiftech MCP655 Danger Den Monsoon Pump/Reservoir 
CoolingOSMonitorKeyboard
Corsair Link Fan Controller Windows 8.1 Nixeus 2560x1440 Logitech G15 
PowerMouseMouse PadAudio
Kingwin PF-850 Ttesports Level10M Razer Vespula Sennheiser HD590 
CPUMotherboardGraphicsRAM
Intel i5-2500k gigabyte z68xp-ud4 Gigabyte GTX 970 G1 Gaming DDR3 1600 4x2GB 
Hard DriveCoolingOSMonitor
Western Digital Velociraptor 300GB w/ Intel RST... Corsair H100 Windows 8.1 1920x1200 HP 
Power
PC P+C 1000w 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Hard Drives & Storage
Overclock.net › Forums › Components › Hard Drives & Storage › HDD ,Controler or Chipset Error ?