Event ID 34. 'The driver disabled the write cache on device \Device\Harddisk0\DR0.' HELP!!!
Steve Taylor
crshes the cd drive is still powered and monitor etc. i run XP Pro.
i have disabled the write cache on the hard disk properties and it still
crashes. ultr DMA is enabled aswell.
the only idea i can come up with is that the power supply could, for some
reason, not be supply enough power to the computer meaning that write
caching is disabled. any ideas????
in the mean time i'm gona replace the power supply.
oh my PC is an Athlon 1500XP with 256mb ram
Gary
Welcome to the club. Many, many users have had this error to occur. It
seems to occur with different hardware, XP, W2K, VIA drivers or not,.
I had built 5 systems using Epox 8KHA+ mobo, ATI video,
Maxtor/IBM/Seagate ATA-133's, no sound card or Soundblaster, Kingston
memory. In addition to getting the warning message (driver disabled
write cache), I would get corrupted system/registry files every now
and then.
I seem to have solved the corruption problem by formatted the disk
using FAT32 instead of NTFS, and disabling write caching. However, I
still get the warning message. I don't know why, since the write cache
is turned off. Go figure.
Karan Mehra [MS]
"Gary" <gg...@bellsouth.net> wrote in message
Unfortunately, the IDE spec does not provide for a method to query the drive's write cache setting. So, every boot, the IDE driver attempts to turn it ON. If that succeeds, write caching is available on the drive and if not, the drive does not support write caching
Now the DISK driver will then turn it OFF if the user said so [ via the Policies Tab under Device Manager ]
To sum :- Please ignore that event ... its harmless
:)
karan
--
This posting is provided "AS IS" with no warranties, and confers no rights
Steve Taylor
for some it is harmless. but for me it creates corrupt registry files and
errors all over the hard disk. it also creates errors in running services
which mean MORE errors linked with pservices such as DCOM COM+ ISS, and
on.....!
my PC hasn't crashed for 4 days, but it is slowly currupting everythin and
will crash soon enough.i get check disk when i start my PC, every time. and
NO this is not scheduled.
this is problem deriving from 2000 pro.and supposidly a VIA problem. for
some it is. but VIA updates have done nothing.
"Karan Mehra [MS]" <kar...@nospam.microsoft.com> wrote in message
news:uSEtF#O7BHA.2464@tkmsftngp05...
Karan Mehra [MS]
| for some it is harmless. but for me it creates corrupt registry files and
| errors all over the hard disk. it also creates errors in running services
| which mean MORE errors linked with pservices such as DCOM COM+ ISS, and
| on.....!
| my PC hasn't crashed for 4 days, but it is slowly currupting everythin and
| will crash soon enough.i get check disk when i start my PC, every time. and
| NO this is not scheduled.
| this is problem deriving from 2000 pro.and supposidly a VIA problem. for
| some it is. but VIA updates have done nothing.
|
Steve:
That event is _simply_ informing you that the system turned OFF write-caching. If you like, open up the Disk Policies Tab [ via Device Manager ] and turn write-caching back ON and you won't see it ever again
veronica taylor
on. however, my machine ran for quite a while before i started having COM+
problems.
i'm not that well versed in hardware, but disabling write caching should
make a computer MORE stable than less, right? in the case of an unexpected
shutdown, one doesn' t lose information sitting in the cache that an
application believes it has written to the disk. am i wrong?
"Karan Mehra [MS]" <kar...@nospam.microsoft.com> wrote in message
news:#ajH#$a7BHA.1628@tkmsftngp02...
Karan Mehra [MS]
"veronica taylor" <dark...@bestweb.net> wrote in message
|
| i'm having the same write cache deal - even tho in policies i have it turned
| on. however, my machine ran for quite a while before i started having COM+
| problems.
|
| i'm not that well versed in hardware, but disabling write caching should
| make a computer MORE stable than less, right? in the case of an unexpected
| shutdown, one doesn' t lose information sitting in the cache that an
| application believes it has written to the disk. am i wrong?
You are absolutely right. Turning OFF the write-cache is very much recommended on IDE drives when using NTFS. The unfortunate side-effect of this is that on every boot, you will see an event in the system log stating that we did this for you. This event is benign and may be safely ignored
On the other hand, the other events that you find in there [ COM+, etc ] do need to be investigated ... and might give us a clue as to what could be going wrong
Gary
That is correct. Disabling the caches does prevent data loss in case
of power failure.
Also, Karan, what you say doesn't make a lot of sense. The error
spoken about is "The driver has disabled the write cache...." If the
driver can or cannot turn on/off the caching (as you say it can't),
why would it say it turned it off. You contradict yourself. you said
the driver can't communicate with the drive on caching properties. I
believe that, but why would it then say it turned off the caching when
I elect to have it left on?
"veronica taylor" <dark...@bestweb.net> wrote in message news:<ezz8wL07BHA.2496@tkmsftngp05>...
Karan Mehra [MS]
| spoken about is "The driver has disabled the write cache...." If the
| driver can or cannot turn on/off the caching (as you say it can't),
| why would it say it turned it off. You contradict yourself. you said
| the driver can't communicate with the drive on caching properties. I
| believe that, but why would it then say it turned off the caching when
| I elect to have it left on?
|
Gary:
On IDE disks, there is no way to _query_ the current write-caching state. In other words, the spec allows us to turn write-caching ON or OFF but no way to ask the device whether it is currently ON or OFF
So by default we turn it ON... and then we apply your chosen setting. So, if you elected to have write-caching ON, we wouldn't do anything and you wouldn't see that event. On the other hand, if you chose to have it OFF, we would turn it OFF and notify you that we did via that event
Hope this clears it up...