Disk Read error - tried all i can think of

ArcAneTSGK

ArcAneTSGK

ArcAneTSGK

Associate
Joined
3 Jan 2008
Posts
374
Location
Manchester
Hello

i have a problem with my PC, i keep get disc read error about 70% of the time i boot my PC, and sometimes i get system freezes meaning i have to reboot my PC again. The only way i can seem to get the HDD to load the first time i boot is running the bios and exiting it...

But this still doesn't eliminate the random freezes i get. Sometimes it will run perfectly fine, other times it will bum out when i go into localdisk, try to run a game, or just applications loading at start up can cause the PC to stop responding.

I have done FIXMBR in the recovery console, i have re-installed windows, the only thing i have left to do is check the SATA cables in my PC.

Does anyone know anything else i can try before i declare my HDD dead and have to buy a new?
 
I had a succesful boot, downloaded WD diagnostic tool for my HDD, about 5 seconds into the diagnostic, the system re-booted. Ever since then everything freezes when i get to the desktop. When i get back home i will attempt to chkdsk, or re-install windows again. If all else fails, i guess i will be without a PC for a few months.

I swapped the sata cables, made no difference. System is unresponsive after boot, still get disk read errors.

Checked power cables no issue there, checked bios, should be no issue there either.
 
Now when i boot, my avast antivirus does not work, 2USB ports have stopped working at the back of the mobo. I think perhaps the motherboard is faulty.

Maybe i should RMA it?

I cant find dead sectors because the moment i try i crash...

no diagnostic tools are working, I also get the "computer beep" noise from inside the machine, rather than sounds through my speakers when say, backspace on MSN when there is no text there as an example...

A friend may be able to lend a spare HDD and i will then be able to decipher what the problem is.

Any more help/coments here are welcome
 
The diagnostic of the drive came back clean, so it has to be the motherboard.

It would explain the bios settings randomly changing now and then (Before this main issue), and the slow startups i guess.

I doubt i would be able to play games and access the internet and access partition if the HDD was corrupt or bad, and there appear to be no bad sectors.

Both quick test and extended test got the green tick and "Passed"

Memtest will test the motherboard?

@Chemical, all my attempts to fix mbr etc were done in the Recovery console, booted from WinXP disc.

@baten PSU is in my spec, the TX 650Watt Corsair

I checked the volts they are fine, also if the PSU was so bad i doubt my PC would run games when i get a succesful boot. today i have had 2 succesful boots out of arround 20, and this second succesful boot i have been able to do the diagnostic. Anyway, my motherboard makes annoying beeping noises, and i recon when i reboot again im going to get another disk error. Shame i can't leave it on 24/7.
Another problem is my Anti Virus stopped working too after the crash caused by running the diagnostic the first time round. The diagnostic is the one from Western Digitals website, for my specific HDD.

So a quick conclusion:
Problems:
2 USB ports out of action on back of motherboard when in Windows - Seem to be fine on boot up to access bios
Bios settings sometimes alter themselves (Ie change boot priority)
Beeping noise from inside the machine instead of the default "Your doing something wrong" noise or w/e you want to call it, that is meant to come through external speakers.
Random succesful boots - allowing me to play games browse the net etc...

What i have tried/done:
Re-Install of WinXP
FIXMBR
Chkdsk
WD Diagnostic tools (Quick and Extended passed on the HD)
Swapping sata ports
Tinkering with bios settings
Checked voltages (Normal volts)
Checked temperatures (Normal temps)
Stocked my overclocked hardware
made sure everything is connected properly in the case (All connected/no loose wires/parts)

So it seems to be the motherboard.

Unless anyone else can indicate why it could possibly be the HDD.
 
Last edited:
Ok i have more info i got from my system log
(This error x15)
The driver detected a controller error on \Device\Harddisk0\D.
EventID: 11
Source: Disk
(This next error x2)
A parity error was detected on \Device\Ide\IdePort0.
EventID: 5
Source: atapi

Here shows my AV stop working
The avast! Antivirus service hung on starting.
EventID: 7022
Source: Service Control Manager

(Another error x MANY)
An error was detected on device \Device\Harddisk0\D during a paging operation.
EventID: 51
Source: Disk

Scrolled down my event log and found even more disk errors warnings and atapi thing...

i would say there was a combine error of like 50 of each... there are 860 events in the log. (Mostly information, followed by these errors)
 
You must log in or register to reply here.
Back
Top Bottom