HDD, 317 Write Errors appear overnight

Over the past few weeks I've had fluctuating 01 Raw Read Error Rates. I have a fluctuating "Current" of 185-200, and a "Data" of anywhere from 0-50.

The "Data" value drops 29 to 19, increases 19 to 29, and so on within 1 minute intervals when doing a HDD intensive operation (such as burning a DVD then verifying it bit-by-bit). 1 unit drops and increases are common when doing nothing with the drive.

I don't even know how the "Data" value can fluctuate, since I'd assume it counts the # of errors it has experienced but apparently the value can decrease.

Despite the read errors, my Write Error data value stayed at 1 (and has been 1 ever since I bought it).

Recently, after 36 hours of running Window's Memory Diagnostic utility (the most comprehensive scan + no cache + extended memory map), I look back and see a radical jump of my "Write Error Rate" data value from 1 to 317.

Thinking it was the app or the fact that I had DOS open for so long with zero HDD activity, I let Memory Diagnostic run a few more hours, came back, and write error still at 317.

I hadn't even accessed Windows or even WRITTEN to the disk within the time it took the Write Error count to jump from 1 to 317. How can this be possible??

 

once a HD starts getting errors it just gets worst, You need to go to the web site of the manufacturer of your HD and DL their free diag tools, you probably will need a floppy and drive....they may have an iso you can burn to a cd.

 

First high priority - Backup your data files to CD, DVD, or external drive.
Second, go to manufactures site for your hard drive and download their Diagnostic Software for your model drive.

 

I just ran Windows Memory Diagnostic overnight for 8 hours, and when I booted up, the Write Error count grew 122--now it's 439.

How does this make sense: I am getting write errors, when the Memory Diagnostic doesn't touch my disk?

There surely must be some element of some drives in general, that causes it to spew out write errors after long hours of sitting idle or in DOS.

The fact is, I have no idea. But the events of using Windows Memory Diagnostic (my 1st use of it ever) then immediately after getting 317 write errors (on a drive that previously stayed at 1 write error for 2.5 years), then reproducing this same occurrence, it is very likely these 2 events are linked.

Has anyone themselves run Windows Memory Diagnostic overnight? I'd be particularly interested in hearing if you noticed write errors afterwards.

I'll test this on another PC in the meantime.

 

it could be something else , like bad ram or possibly the processor is overheating

 

The memory diagnostic passed all of the tests I put it through.

I suppose having the processor cache turned off could cause overheating, as test lengths increased about 10x--but the fan is working and I don't overclock.

Despite several restarts and lots of writing to the disk, my write error value hasn't increased by 1.

It's definitely something that is happening during the diagnostic, or the program itself.

Has anyone even used this app before? Or had their processor cache turned off?