... write cache enabled. Data corruption may occur ?

[David H. Lipman]

It's a warning only. If the PC looses power than the cache might not get flushed to disk
thus causing data corruption.

This is true with any hard disk with a cache or a caching controller. Good caching
controllers have their own battery just in case of a power disruption. Hard disks don't
provide this however.

To enable or disable it would be a hard disk manufacturers DOS or Win32 utility or third
party product. For example, Adaptec has a utility to enable or disable the cache on SCSI
hard disks.

Dave



| I've been seeing this warning frequently in my System Event log... always
| about 8 times in a row during the course of about a minute shortly after
| startup....
|
| I've had such a sordid history regarding HDD longevity, that any hiccup
| makes me nervous.
|
| + Can someone tell me what the below warning is intended to tell me?
|
| + Which exactly is "\Device\Harddisk1\DR1" ... I presume it refers to the
| Master HDD on first IDE channel? (WD400bb - standard 2 mb cache), and not
| necessarily any particular volume such as my C:, which is the first primary
| volume on that HDD.
|
| + Why wouldn't I want "write cache enabled"? (...or why disable it? and
| How?... a BIOS option?)
|
| + What "Data Corruption" could this be causing... ?
|
| I chkdsk and defrag frequently, especially the C-drive... chkdsks on C: have
| been acceptably clean since I replaced the drive a month or so ago.
|
| TIA,
| Chris
|
| Here's the Warning Message:
| ----------------------------------
| Event Type: Warning
| Event Source: Disk
| Event Category: None
| Event ID: 32
| Date: 1/15/2004
| Time: 1:55:14 PM
| User: N/A
| Computer: BEAST
| Description:
| The driver detected that the device \Device\Harddisk1\DR1 has its write
| cache enabled. Data corruption may occur.
| Data:
| 0000: 0f 00 04 00 01 00 62 00 ......b.
| 0008: 00 00 00 00 20 00 04 80 .... ..?
| 0010: 01 00 00 00 10 00 00 c0 .......À
| 0018: 00 00 00 00 00 00 00 00 ........
| 0020: 00 00 00 00 00 00 00 00 ........
| 0028: 00 00 00 00 ....
|
| ***************************
|
| Also, this string of warnings is always interrupted exactly once. after the
| very first warning, by this single warning having event ID 51:
|
| Event Type: Warning
| Event Source: Disk
| Event Category: None
| Event ID: 51
| Date: 1/15/2004
| Time: 1:55:13 PM
| User: N/A
| Computer: BEAST
| Description:
| An error was detected on device \Device\Harddisk1\DR1 during a paging
| operation.
| Data:
| 0000: 04 00 24 00 01 00 72 00 ..$...r.
| 0008: 00 00 00 00 33 00 04 80 ....3..?
| 0010: 2d 01 00 00 00 00 00 00 -.......
| 0018: 00 00 00 00 00 00 00 00 ........
| 0020: 00 42 03 00 00 00 00 00 .B......
| 0028: 00 00 00 00 01 00 00 00 ........
| 0030: 00 00 00 00 2a 00 00 00 ....*...
| 0038: 02 c4 00 00 00 24 05 00 .Ä...$..
| 0040: 2a 00 00 00 01 a1 00 00 *....¡..
| 0048: 08 00 00 00 ....
|
|
|
|

 

[Jisha]

I've been seeing this warning frequently in my System Event log... always
about 8 times in a row during the course of about a minute shortly after
startup....

I've had such a sordid history regarding HDD longevity, that any hiccup
makes me nervous.

+ Can someone tell me what the below warning is intended to tell me?

+ Which exactly is "\Device\Harddisk1\DR1" ... I presume it refers to the
Master HDD on first IDE channel? (WD400bb - standard 2 mb cache), and not
necessarily any particular volume such as my C:, which is the first primary
volume on that HDD.

+ Why wouldn't I want "write cache enabled"? (...or why disable it? and
How?... a BIOS option?)

+ What "Data Corruption" could this be causing... ?

I chkdsk and defrag frequently, especially the C-drive... chkdsks on C: have
been acceptably clean since I replaced the drive a month or so ago.

TIA,
Chris

Here's the Warning Message:
----------------------------------
Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 32
Date: 1/15/2004
Time: 1:55:14 PM
User: N/A
Computer: BEAST
Description:
The driver detected that the device \Device\Harddisk1\DR1 has its write
cache enabled. Data corruption may occur.
Data:
0000: 0f 00 04 00 01 00 62 00 ......b.
0008: 00 00 00 00 20 00 04 80 .... ..€
0010: 01 00 00 00 10 00 00 c0 .......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 00 00 00 00 ....

***************************

Also, this string of warnings is always interrupted exactly once. after the
very first warning, by this single warning having event ID 51:

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 1/15/2004
Time: 1:55:13 PM
User: N/A
Computer: BEAST
Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging
operation.
Data:
0000: 04 00 24 00 01 00 72 00 ..$...r.
0008: 00 00 00 00 33 00 04 80 ....3..€
0010: 2d 01 00 00 00 00 00 00 -.......
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 42 03 00 00 00 00 00 .B......
0028: 00 00 00 00 01 00 00 00 ........
0030: 00 00 00 00 2a 00 00 00 ....*...
0038: 02 c4 00 00 00 24 05 00 .Ä...$..
0040: 2a 00 00 00 01 a1 00 00 *....¡..
0048: 08 00 00 00 ....

 

[Jisha]

Ah... I see... Thanks Dave.

....so the fact that it seems to occur only at startup-up would be akin to
gears grinding while "trying to put the car into gear before the engine's
fully started up" ?

But why so many times in a row?
And why only this device? why not any of the other 4 HDD devices on the
system?

Granted, this particular drive is the only one attached directly to the
Motherboard.
All others are attached to PCI IDE Controller Cards.

Perhaps the BIOS on the PCI Controller Cards is handling better than the MB
Controller? ...but the event _source_ appears to be the controller on the
Drive itself.

Clearly, I don't fully understand the ins-and-outs of the HDD Controller
workings... and I don't really need to!
....I'm just happy to know that this "warning" isn't going to mysteriously
develop into an "error" :]

Anyway, thanks again,
Chris

 

[David H. Lipman]

I don't have an explanation on why some hard disk' don't generate the error. It may have
something to do with the IDE/ATAPI drivers. I'm just wondering if their is a Registry
setting to turn off the error message.

I got the following using TechNet...

Dave

~ ~ ~

Event ID 32 and 34 Warnings May Be Logged When You Use an Iomega Zip 250 Drive in Windows
XP PSS ID Number: 324916

Article Last Modified on 5/29/2003


--------------------------------------------------------------------------------
The information in this article applies to:


Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Professional

--------------------------------------------------------------------------------

This article was previously published under Q324916
SYMPTOMS
When you are using an Iomega Zip 250 drive to copy files to and from your hard disk, you
may receive the following Event ID warning in the System event log:
Event ID: 32
Description: The driver detected that the device \Device\Harddisk1\DR4 has its write cache
enabled. Data corruption may occur.

CAUSE
The Iomega Zip 250 drive does not support requests by the operating system to turn off
write caching. Because of this, an Event ID 32 warning is logged in the event log. This
warning is by design. Event ID 34s are then incorrectly generated in the event log every
time you start your computer, although they are supposed to be Event ID 32s.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at
the beginning of this article.

MORE INFORMATION
The Iomega Zip 250 drive does not support the ForceUnitAccess bit, which the operating
system uses to bypass all caching when it sends commands to the drive. Because of this,
Windows tries to turn off write caching for the drive, and then retries the request. This
request also fails because the Iomega drive write cache is always on. As a last attempt,
Windows retries the request one more time without the ForceUnitAccess bit set.

As a result of the failed attempt to turn off write caching for the Iomega ZIP 250 drive,
an Event ID 32 warning message is displayed in the event log. When the computer starts
after this warning has been generated, Windows remembers that the drive does not support
ForceUnitAccess. Windows then tries to turn off the disk cache, and this attempt fails.
Windows lists these warnings as an Event ID 34 and not the appropriate Event ID 32.


Additional query words: fua

Keywords: kbbug kbenv kberrmsg kbpending KB324916
Technology: kbwin2000Pro kbwin2000ProSearch kbwin2000Search kbWinXPHome kbWinXPHomeSearch
kbWinXPPro kbWinXPProSearch kbWinXPSearch




| Ah... I see... Thanks Dave.
|
| ...so the fact that it seems to occur only at startup-up would be akin to
| gears grinding while "trying to put the car into gear before the engine's
| fully started up" ?
|
| But why so many times in a row?
| And why only this device? why not any of the other 4 HDD devices on the
| system?
|
| Granted, this particular drive is the only one attached directly to the
| Motherboard.
| All others are attached to PCI IDE Controller Cards.
|
| Perhaps the BIOS on the PCI Controller Cards is handling better than the MB
| Controller? ...but the event _source_ appears to be the controller on the
| Drive itself.
|
| Clearly, I don't fully understand the ins-and-outs of the HDD Controller
| workings... and I don't really need to!
| ...I'm just happy to know that this "warning" isn't going to mysteriously
| develop into an "error" :]
|
| Anyway, thanks again,
| Chris
|
| | > It's a warning only. If the PC looses power than the cache might not get
| flushed to disk
| > thus causing data corruption.
| >
| > This is true with any hard disk with a cache or a caching controller.
| Good caching
| > controllers have their own battery just in case of a power disruption.
| Hard disks don't
| > provide this however.
| >
| > To enable or disable it would be a hard disk manufacturers DOS or Win32
| utility or third
| > party product. For example, Adaptec has a utility to enable or disable
| the cache on SCSI
| > hard disks.
| >
| > Dave
| >
| >
| >
| | > | I've been seeing this warning frequently in my System Event log...
| always
| > | about 8 times in a row during the course of about a minute shortly after
| > | startup....
| > |
| > | I've had such a sordid history regarding HDD longevity, that any hiccup
| > | makes me nervous.
| > |
| > | + Can someone tell me what the below warning is intended to tell me?
| > |
| > | + Which exactly is "\Device\Harddisk1\DR1" ... I presume it refers to
| the
| > | Master HDD on first IDE channel? (WD400bb - standard 2 mb cache), and
| not
| > | necessarily any particular volume such as my C:, which is the first
| primary
| > | volume on that HDD.
| > |
| > | + Why wouldn't I want "write cache enabled"? (...or why disable it? and
| > | How?... a BIOS option?)
| > |
| > | + What "Data Corruption" could this be causing... ?
| > |
| > | I chkdsk and defrag frequently, especially the C-drive... chkdsks on C:
| have
| > | been acceptably clean since I replaced the drive a month or so ago.
| > |
| > | TIA,
| > | Chris
| > |
| > | Here's the Warning Message:
| > | ----------------------------------
| > | Event Type: Warning
| > | Event Source: Disk
| > | Event Category: None
| > | Event ID: 32
| > | Date: 1/15/2004
| > | Time: 1:55:14 PM
| > | User: N/A
| > | Computer: BEAST
| > | Description:
| > | The driver detected that the device \Device\Harddisk1\DR1 has its write
| > | cache enabled. Data corruption may occur.
| > | Data:
| > | 0000: 0f 00 04 00 01 00 62 00 ......b.
| > | 0008: 00 00 00 00 20 00 04 80 .... ..?
| > | 0010: 01 00 00 00 10 00 00 c0 .......À
| > | 0018: 00 00 00 00 00 00 00 00 ........
| > | 0020: 00 00 00 00 00 00 00 00 ........
| > | 0028: 00 00 00 00 ....
| > |
| > | ***************************
| > |
| > | Also, this string of warnings is always interrupted exactly once. after
| the
| > | very first warning, by this single warning having event ID 51:
| > |
| > | Event Type: Warning
| > | Event Source: Disk
| > | Event Category: None
| > | Event ID: 51
| > | Date: 1/15/2004
| > | Time: 1:55:13 PM
| > | User: N/A
| > | Computer: BEAST
| > | Description:
| > | An error was detected on device \Device\Harddisk1\DR1 during a paging
| > | operation.
| > | Data:
| > | 0000: 04 00 24 00 01 00 72 00 ..$...r.
| > | 0008: 00 00 00 00 33 00 04 80 ....3..?
| > | 0010: 2d 01 00 00 00 00 00 00 -.......
| > | 0018: 00 00 00 00 00 00 00 00 ........
| > | 0020: 00 42 03 00 00 00 00 00 .B......
| > | 0028: 00 00 00 00 01 00 00 00 ........
| > | 0030: 00 00 00 00 2a 00 00 00 ....*...
| > | 0038: 02 c4 00 00 00 24 05 00 .Ä...$..
| > | 0040: 2a 00 00 00 01 a1 00 00 *....¡..
| > | 0048: 08 00 00 00 ....
| > |
| > |
| > |
| > |
| >
| >
|
|

 

[Jisha]

Wow! Amazing...

After reading, I realized that I do have a Zip-disk inserted in my Zip-250
internal drive... so I popped it out and restarted... NO WARNING this time!

Dave, Do you have ESP or something? :] (LOL)

Thanks,
Chris

I don't have an explanation on why some hard disk' don't generate the error. It may have
something to do with the IDE/ATAPI drivers. I'm just wondering if their is a Registry
setting to turn off the error message.

I got the following using TechNet...

Dave

~ ~ ~

Event ID 32 and 34 Warnings May Be Logged When You Use an Iomega Zip 250 Drive in Windows
XP PSS ID Number: 324916

Article Last Modified on 5/29/2003


-------------------------------------------------------------------------- ------
The information in this article applies to:


Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Professional

-------------------------------------------------------------------------- ------

This article was previously published under Q324916
SYMPTOMS
When you are using an Iomega Zip 250 drive to copy files to and from your hard disk, you
may receive the following Event ID warning in the System event log:
Event ID: 32
Description: The driver detected that the device \Device\Harddisk1\DR4 has its write cache
enabled. Data corruption may occur.

CAUSE
The Iomega Zip 250 drive does not support requests by the operating system to turn off
write caching. Because of this, an Event ID 32 warning is logged in the event log. This
warning is by design. Event ID 34s are then incorrectly generated in the event log every
time you start your computer, although they are supposed to be Event ID 32s.

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at
the beginning of this article.

MORE INFORMATION
The Iomega Zip 250 drive does not support the ForceUnitAccess bit, which the operating
system uses to bypass all caching when it sends commands to the drive. Because of this,
Windows tries to turn off write caching for the drive, and then retries the request. This
request also fails because the Iomega drive write cache is always on. As a last attempt,
Windows retries the request one more time without the ForceUnitAccess bit set.

As a result of the failed attempt to turn off write caching for the Iomega ZIP 250 drive,
an Event ID 32 warning message is displayed in the event log. When the computer starts
after this warning has been generated, Windows remembers that the drive does not support
ForceUnitAccess. Windows then tries to turn off the disk cache, and this attempt fails.
Windows lists these warnings as an Event ID 34 and not the appropriate Event ID 32.


Additional query words: fua

Keywords: kbbug kbenv kberrmsg kbpending KB324916
Technology: kbwin2000Pro kbwin2000ProSearch kbwin2000Search kbWinXPHome kbWinXPHomeSearch
kbWinXPPro kbWinXPProSearch kbWinXPSearch




| Ah... I see... Thanks Dave.
|
| ...so the fact that it seems to occur only at startup-up would be akin to
| gears grinding while "trying to put the car into gear before the engine's
| fully started up" ?
|
| But why so many times in a row?
| And why only this device? why not any of the other 4 HDD devices on the
| system?
|
| Granted, this particular drive is the only one attached directly to the
| Motherboard.
| All others are attached to PCI IDE Controller Cards.
|
| Perhaps the BIOS on the PCI Controller Cards is handling better than the MB
| Controller? ...but the event _source_ appears to be the controller on the
| Drive itself.
|
| Clearly, I don't fully understand the ins-and-outs of the HDD Controller
| workings... and I don't really need to!
| ...I'm just happy to know that this "warning" isn't going to mysteriously
| develop into an "error" :]
|
| Anyway, thanks again,
| Chris
|
| | > It's a warning only. If the PC looses power than the cache might not get
| flushed to disk
| > thus causing data corruption.
| >
| > This is true with any hard disk with a cache or a caching controller.
| Good caching
| > controllers have their own battery just in case of a power disruption.
| Hard disks don't
| > provide this however.
| >
| > To enable or disable it would be a hard disk manufacturers DOS or Win32
| utility or third
| > party product. For example, Adaptec has a utility to enable or disable
| the cache on SCSI
| > hard disks.
| >
| > Dave
| >
| >
| >
| | > | I've been seeing this warning frequently in my System Event log...
| always
| > | about 8 times in a row during the course of about a minute shortly after
| > | startup....
| > |
| > | I've had such a sordid history regarding HDD longevity, that any hiccup
| > | makes me nervous.
| > |
| > | + Can someone tell me what the below warning is intended to tell me?
| > |
| > | + Which exactly is "\Device\Harddisk1\DR1" ... I presume it refers to
| the
| > | Master HDD on first IDE channel? (WD400bb - standard 2 mb cache), and
| not
| > | necessarily any particular volume such as my C:, which is the first
| primary
| > | volume on that HDD.
| > |
| > | + Why wouldn't I want "write cache enabled"? (...or why disable it? and
| > | How?... a BIOS option?)
| > |
| > | + What "Data Corruption" could this be causing... ?
| > |
| > | I chkdsk and defrag frequently, especially the C-drive... chkdsks on C:
| have
| > | been acceptably clean since I replaced the drive a month or so ago.
| > |
| > | TIA,
| > | Chris
| > |
| > | Here's the Warning Message:
| > | ----------------------------------
| > | Event Type: Warning
| > | Event Source: Disk
| > | Event Category: None
| > | Event ID: 32
| > | Date: 1/15/2004
| > | Time: 1:55:14 PM
| > | User: N/A
| > | Computer: BEAST
| > | Description:
| > | The driver detected that the device \Device\Harddisk1\DR1 has its write
| > | cache enabled. Data corruption may occur.
| > | Data:
| > | 0000: 0f 00 04 00 01 00 62 00 ......b.
| > | 0008: 00 00 00 00 20 00 04 80 .... ..?
| > | 0010: 01 00 00 00 10 00 00 c0 .......À
| > | 0018: 00 00 00 00 00 00 00 00 ........
| > | 0020: 00 00 00 00 00 00 00 00 ........
| > | 0028: 00 00 00 00 ....
| > |
| > | ***************************
| > |
| > | Also, this string of warnings is always interrupted exactly once. after
| the
| > | very first warning, by this single warning having event ID 51:
| > |
| > | Event Type: Warning
| > | Event Source: Disk
| > | Event Category: None
| > | Event ID: 51
| > | Date: 1/15/2004
| > | Time: 1:55:13 PM
| > | User: N/A
| > | Computer: BEAST
| > | Description:
| > | An error was detected on device \Device\Harddisk1\DR1 during a paging
| > | operation.
| > | Data:
| > | 0000: 04 00 24 00 01 00 72 00 ..$...r.
| > | 0008: 00 00 00 00 33 00 04 80 ....3..?
| > | 0010: 2d 01 00 00 00 00 00 00 -.......
| > | 0018: 00 00 00 00 00 00 00 00 ........
| > | 0020: 00 42 03 00 00 00 00 00 .B......
| > | 0028: 00 00 00 00 01 00 00 00 ........
| > | 0030: 00 00 00 00 2a 00 00 00 ....*...
| > | 0038: 02 c4 00 00 00 24 05 00 .Ä...$..
| > | 0040: 2a 00 00 00 01 a1 00 00 *....¡..
| > | 0048: 08 00 00 00 ....
| > |
| > |
| > |
| > |
| >
| >
|
|

 

[jrl]

sorry to but in..

i'm getting a similar error, but my win 2000 server keeps
crashing. the event viewer shows
event id 32 "the driver detected that the device
\device\harddisk0\dr0 has its write cache enabled. data
corruption may occur"

i have disabled write cache in my adaptec controller, but
it does not hold the setting

maybe you have some ideas!!!

thanks
jr

-----Original Message-----
I don't have an explanation on why some hard disk' don't

generate the error. It may have

something to do with the IDE/ATAPI drivers. I'm just

wondering if their is a Registry

setting to turn off the error message.

I got the following using TechNet...

Dave

~ ~ ~

Event ID 32 and 34 Warnings May Be Logged When You Use an

Iomega Zip 250 Drive in Windows

XP PSS ID Number: 324916

Article Last Modified on 5/29/2003


---------------------------------------------------------- ----------------------
The information in this article applies to:


Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Professional

---------------------------------------------------------- ----------------------

This article was previously published under Q324916
SYMPTOMS
When you are using an Iomega Zip 250 drive to copy files

to and from your hard disk, you

may receive the following Event ID warning in the System event log:
Event ID: 32
Description: The driver detected that the device

\Device\Harddisk1\DR4 has its write cache

enabled. Data corruption may occur.

CAUSE
The Iomega Zip 250 drive does not support requests by the operating system to turn off
write caching. Because of this, an Event ID 32 warning is logged in the event log. This
warning is by design. Event ID 34s are then incorrectly

generated in the event log every

time you start your computer, although they are supposed to be Event ID 32s.

STATUS
Microsoft has confirmed that this is a problem in the

Microsoft products that are listed at

the beginning of this article.

MORE INFORMATION
The Iomega Zip 250 drive does not support the

ForceUnitAccess bit, which the operating

system uses to bypass all caching when it sends commands to the drive. Because of this,
Windows tries to turn off write caching for the drive,

and then retries the request. This

request also fails because the Iomega drive write cache

is always on. As a last attempt,

Windows retries the request one more time without the ForceUnitAccess bit set.

As a result of the failed attempt to turn off write

caching for the Iomega ZIP 250 drive,

an Event ID 32 warning message is displayed in the event log. When the computer starts
after this warning has been generated, Windows remembers

that the drive does not support

ForceUnitAccess. Windows then tries to turn off the disk cache, and this attempt fails.
Windows lists these warnings as an Event ID 34 and not the appropriate Event ID 32.


Additional query words: fua

Keywords: kbbug kbenv kberrmsg kbpending KB324916
Technology: kbwin2000Pro kbwin2000ProSearch

kbwin2000Search kbWinXPHome kbWinXPHomeSearch

kbWinXPPro kbWinXPProSearch kbWinXPSearch




| Ah... I see... Thanks Dave.
|
| ...so the fact that it seems to occur only at startup- up would be akin to
| gears grinding while "trying to put the car into gear before the engine's
| fully started up" ?
|
| But why so many times in a row?
| And why only this device? why not any of the other 4 HDD devices on the
| system?
|
| Granted, this particular drive is the only one attached directly to the
| Motherboard.
| All others are attached to PCI IDE Controller Cards.
|
| Perhaps the BIOS on the PCI Controller Cards is handling better than the MB
| Controller? ...but the event _source_ appears to be the controller on the
| Drive itself.
|
| Clearly, I don't fully understand the ins-and-outs of the HDD Controller
| workings... and I don't really need to!
| ...I'm just happy to know that this "warning" isn't going to mysteriously
| develop into an "error" :]
|
| Anyway, thanks again,
| Chris
|
| | > It's a warning only. If the PC looses power than the cache might not get
| flushed to disk
| > thus causing data corruption.
| >
| > This is true with any hard disk with a cache or a caching controller.
| Good caching
| > controllers have their own battery just in case of a power disruption.
| Hard disks don't
| > provide this however.
| >
| > To enable or disable it would be a hard disk manufacturers DOS or Win32
| utility or third
| > party product. For example, Adaptec has a utility to enable or disable
| the cache on SCSI
| > hard disks.
| >
| > Dave
| >
| >
| >
| | > | I've been seeing this warning frequently in my System Event log...
| always
| > | about 8 times in a row during the course of about a minute shortly after
| > | startup....
| > |
| > | I've had such a sordid history regarding HDD longevity, that any hiccup
| > | makes me nervous.
| > |
| > | + Can someone tell me what the below warning is intended to tell me?
| > |
| > | + Which exactly is "\Device\Harddisk1\DR1" ... I presume it refers to
| the
| > | Master HDD on first IDE channel? (WD400bb - standard 2 mb cache), and
| not
| > | necessarily any particular volume such as my C:, which is the first
| primary
| > | volume on that HDD.
| > |
| > | + Why wouldn't I want "write cache enabled"? (...or why disable it? and
| > | How?... a BIOS option?)
| > |
| > | + What "Data Corruption" could this be causing... ?
| > |
| > | I chkdsk and defrag frequently, especially the C- drive... chkdsks on C:
| have
| > | been acceptably clean since I replaced the drive a month or so ago.
| > |
| > | TIA,
| > | Chris
| > |
| > | Here's the Warning Message:
| > | ----------------------------------
| > | Event Type: Warning
| > | Event Source: Disk
| > | Event Category: None
| > | Event ID: 32
| > | Date: 1/15/2004
| > | Time: 1:55:14 PM
| > | User: N/A
| > | Computer: BEAST
| > | Description:
| > | The driver detected that the device

\Device\Harddisk1\DR1 has its write