Driver disabled write cache error Asus a7v333 and

[Vin]

... seagate baracuda ata 133 7200rpm 2mb ide HDD.

Hi

Started getting the following error in the event log, (Windows XP Pro) -

The driver disabled the write cache on device \Device\Harddisk1\DR1

The Event ID is 34.

Machine is grinding to a halt, excessive paging, and even lost sight of my CD ROM on many an occasion, then get lots of errors in the event log.
I say lost sight, can see it, but cannot see any data on the CD.

Any ideas please?

Rig is asus a7v333, xp2100+, Rad 9700 Pro, SB Audigy, 1gb DDR 333, lite-on 32x12x40 CD-RW, 40gb Seagate Bara.

Makes gaming impossible and even web browsing can become tedious. Everything is.

uninstalled all and any crap, disk clean up'd, defrag'd etc etc.....


This was error I got when couldnt use CD at all -
The device, \Device\Ide\IdePort1, did not respond within the timeout period.

Event id 9



Thanks

Vin




NVidia "The way it is meant to be played"

ATI "The way it is actually played"

<P ID="edit"><FONT SIZE=-1><EM>Edited by vin on 10/01/03 10:01 AM.</EM></FONT></P>

 

[ChipDeath]

There are a few things it might be. it could be a heat or power issue. What are your temperatures & voltages? (you can use something like motherboard monitor 5, or look in the BIOS to see)

---
<font color=red>The preceding text is assembled from information stored in an unreliable organic storage medium. As such it may be innacurate, incomplete, or completely wrong</font color=red>

 

[Vin]

Temps are all ok, CPU 40c idle, MAX 45c under heavy gaming load. Ambient case temp 29c.

Voltages all fine and stable.

Machine has been SOLID stability wise since build approx 1 year ago, maybe 15 months thinking about it.

This is a new issue. Odd one too, could be motherboard I reckon!?!



NVidia "The way it is meant to be played"

ATI "The way it is actually played"

 

[ChipDeath]

try underclocking the system to 100Mhz FSB. granted you'll then only be running @1300Mhz (instead of 1733), but you might find it's stable. (I don't necessarily mean this as a permanent solution, just for troubleshooting)..

I only suggest this because I myself have an A7V333 mobo, which was also fine for something like 8 months, but then suddenly started crashing for no good reason. After fiddling with it for ages, I found it was stable @ 100Mhz FSB (1250Mhz CPU))

Having tried virtually everything (new power supplies, different RAM, CPU cooling, etc), and having noticed that the CPU Vcore is fluctuating by about +/- .15V, I could only conclude that the Voltage regulators on the board have gone a bit haywire, and it's overvolting the northbridge, so the chipset itself is overheating (even at 100FSB my mobo temp is generally higher than my CPU one).

I managed to find a compromise @112FSB, but any further pushes the PCI bus out of spec, and as this is now only my secondary PC (second player in LAN games) I can't be bothered to sort it out, as it's happy enough now.

Maybe you have a similar problem?

---
<font color=red>The preceding text is assembled from information stored in an unreliable organic storage medium. As such it may be innacurate, incomplete, or completely wrong</font color=red>