Quelle EventId.net
Mihai Andrei (Last update 10/5/2005):
This event may occur when you try to write data to a Serial Bus Protocol 2 (SBP-2) device, such as an IEEE (Institute of Electrical and Electronics Engineers) 1394 drive. See M885464 for a hotfix applicable to Microsoft Windows XP.
Ionut Marin (Last update 8/16/2005):
As per Microsoft: "An input/output (I/O) request to a memory-mapped file failed and the operation was retried. If these events are logged regularly on a primary system drive, replace the device. Otherwise, no user action is required". See MSW2KDB for more details on this event.
This event may appear if you have a Windows server booting from a Storage Area Network (SAN). See M305547 for more detailed information.
As per Microsoft: "This problem occurs if an Input/Output (I/O) operation to a hard disk is unsuccessful. When an I/O operation to a hard disk is unsuccessful, Windows Server 2003 logs Event ID 51 in the system log. This problem occurs even if the I/O operation is retried and is subsequently successful". See M834910 for a hotfix.
As per Microsoft: "This problem occurs if you have installed one or more storage devices that do not support cache commands. The Windows 2000 SP4 Disk.sys driver writes many events to the system log when it performs write operations to a storage device that does not support cache commands". See M830051 for a hotfix.
From a newsgroup post: "If you have Intel's Application Accelerator installed this is what can cause the error. I have found that it is a false detection and it is nothing to you should worry about. I read it on Intel's web site. I get this error sometimes but it never causes any problems".
See M835473 for additional information on this event.
Al Marklin (Last update 11/8/2004):
This error is generated along with EventID 32 from source Disk (and erroneously error 34), when Windows 2000 SP4 is installed in a system with and Iomega Zip 250. I have tracked this for several months without loss of data, and it appears to be spurious though it does fill up the System log.
From M324916: "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".
Per Ionut Marin's comment: "The Windows 2000 SP4 Disk.sys driver writes many events to the system log when it performs write operations to a storage device that does not support cache commands. See M830051 for a hotfix".
Anonymous (Last update 8/19/2004):
To fix this problem I disabled the “Write cache” feature on my disk. To do this go to Device Manager -> Disk Drives, right click on your disk and choose Properties. Here you can disable this feature.
Mashiki (Last update 6/27/2004):
Intel's Application Accelerator does seem to cause, the event ID 51 in many instances. The best advice is to troubleshoot the actual code in each instance (see M244780). I have now seen this in many computers, those I have built and my own. This code does seem to come up in all of them; they all use the chipset I845 or I850. Only with the most recent driver release from Intel (2.3.0.2160) does this happen. The drives and memory are fine. The specific code in each case is a 0x40 SRB_STATUS_QUEUE_FROZEN, I believe it’s an error in the IAA driver itself. Removing the IAA, removes the problem in each instance.
Michael Papalabrou (Last update 5/17/2004):
If this disk is your system disk or a disk that contains sensitive data, consider taking regular backups and/or replacing this disk as soon as possible. It will fail soon. In my system it started generating errors, it had degraded performance and it failed a month later.
Captain Fizz (Last update 2/9/2004):
I had the same message due to a faulty HDD.
Anonymous (Last update 10/15/2003):
I was burning a cd with Nero Burning Rom 6 + data verification. The data verification did freeze near 97%, and after 3 minutes I aborted the process and the event log reported this warning.
Adrian Grigorof (Last update 8/2/2003):
This event may be recorded when a digital camera is attached to the system to transfer images from its internal hard drive to the computer. If the camera's batteries run out of power during this process one of the effects is the recording of this message. An example of device reported in such cases is "\Device\Harddisk2\DR10" - and it is the footprint of an IBM SmartMedia hard drive.
Ron Glaister (Last update 5/9/2003):
This will also occur on a Windows 2000 server connected to a compaq EMA SAN (HSG80s) utilizing triple-mirroring. When the "Broken" mirror set is inserted back into the SAN for remirroring, you will see this occur. Compaq claims this is entirely normal and from my end, has occurred since it was installed and has never affected anything.
Kmex
This event occurs when multiple clusters that are attached to the same storage subsystem are not configured properly. See M304415 and M311081 links.
Brian Soegaard (AKA Cerw)
According to Microsoft, this error can be hardware related. See the information provided for event 9 and 11.
Pablo Rivera
On a Windows 2000 server, this error could be caused when a process is taking a long time to process data on the partition that holds the page file. Processes like a scheduled virus scan on all partitions, a file backup procedure, or just by having the page file on a fragmented and heavily utilized partition that has little free space.
If the error only happens at the same time as one of the above scheduled tasks, you may not need to worry, as long as it goes away after the task is done and the page file returns to normal.
Check Microsoft articles M123747 and M197379 to learn more about page file and performance.
