Sign in with
Sign up | Sign in
Your question

HDD keeps failing to retrieve data for long periods of time

Last response: in Storage
August 26, 2013 3:19:50 PM

Having issues with my PC. The HDD keeps dropping about every 30-5 minutes for periods of up to 4 minutes causing programs to stop or crash.

It is not the HDD as the first HDD I installed windows 7 64 bit home premium to did the same, it's also not the OS, I tried older versions of windows I had spare and the issue persisted.

I have also done a disc and memcheck and received "Working" as well as changed most of my BIOS settings to try and make it work but to no avail.
The GPU is working although not fully updated (The driver for games, the rest is the newest), I have internet connection too. I also "removed myself from the home network" as an attempt to fix as recommended on other sites. I also stopped "AMD Cool N Quiet" as also recommended by someone. Have also replaced sata cables and no luck.

It seems to either be one of two things, a sata control/driver error or a conflicting driver, yet all drivers (And bios) are updated as well as every windows update for windows 7 home premium 64 bit. However I am not sure.

The following pictures show the latency issues I am experiencing. []

Image 1: Resource monitor showing HDD drop

Image 2: Latency test tool 10 seconds in

Image 3: Driver list with errors showing

Image 4: Latency test tool 30 seconds in (Same as 2 but with more alarming values)

I am convinced it is a driver error/conflict however I am unsure of how to fix it, I have been trying for almost 13 hours of problem searching/ruling out problems and it is frustrating as Ii am running out of leads.

Any ideas? It's not a bad drive, I reinstalled it into a new PC and installed windows perfectly... :( 

The PSU is 500w corsair, but the CPU and GPU are not even on load so I doubt it would be that... unless the 12v rail is dodgy...? I didn't see the voltage fluctuate much so I doubt it.

I did a test using a test, hell if I know the name of it anymore, the PC is currently reinstalling on a new HDD, but that can be stopped and the old fully updated one can be rebooted for more tests.

Any help in diagnosing the issue would be helpful, thanks!

Computer name PC-2
OS version Windows 7 Service Pack 1, 6.1, build 7601 (x64)
CPU AuthenticAMD AMD FX(tm)-6300 Six-Core Processor
Logical processors 6
Processor groups 1
RAM 8093 MB total
Motherboard M5a97 E 2.0

Reported CPU speed 3511.0 MHz
Measured CPU speed 1828.0 MHz (approx.)

Note reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs) 4134.361651
Average measured interrupt to process latency (µs) 7.068445

Highest measured interrupt to DPC latency (µs) 3777.463516
Average measured interrupt to DPC latency (µs) 3.22190

The SMI, IPI and CPU stalls value represents the highest measured interval that a CPU did not respond while having its maskable interrupts disabled.

Highest measured SMI or CPU stall (µs) 11.663338

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs) 599372.714042
Driver with highest ISR routine execution time hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

Highest reported total ISR routine time (%) 0.043855
Driver with highest ISR total time hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

Total time spent in ISRs (%) 0.077935

ISR count (execution time 250 µs) 602883
ISR count (execution time 250-500 µs) 0
ISR count (execution time 500-999 µs) 1
ISR count (execution time 1000-1999 µs) 62
ISR count (execution time 2000-3999 µs) 0
ISR count (execution time =4000 µs) 0

DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs) 11352.889490
Driver with highest DPC routine execution time storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Highest reported total DPC routine time (%) 0.117429
Driver with highest DPC total execution time USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Total time spent in DPCs (%) 0.264981

DPC count (execution time 250 µs) 2004345
DPC count (execution time 250-500 µs) 0
DPC count (execution time 500-999 µs) 142
DPC count (execution time 1000-1999 µs) 8
DPC count (execution time 2000-3999 µs) 68
DPC count (execution time =4000 µs) 0

Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count svchost.exe

Total number of hard pagefaults 913
Hard pagefault count of hardest hit process 504
Highest hard pagefault resolution time (µs) 87483255.441185
Total time spent in hard pagefaults (%) 14.673457
Number of processes hit 16

Best solution

a c 748 G Storage
August 26, 2013 5:27:19 PM

You haven't mention if you've done virus scans or tested the hard drive for errors or surface scan. Usually the first two thing I think of when I see a drive with no output but high utilization its either a hidden virus or the drive is attempting to recover from a bad sector.