Common reasons for parsing windows write cache failures

Today, a netizen asks a question. Xiaobian has encountered the same problem for a while. I will transfer this problem and solution here and share it with everyone. User consultation: My computer A, on the LAN When other computers open the shared EXECL file on A, Windows slows down the write failure. You can open the shared mp3 and other files. How to solve this problem?

Windows uses a special subsystem for Support for some disk-based operations, such as a technique that temporarily caches writes to the disk and then waits until the system is idle. This technique, called "write cache", can improve system performance, but by default the system may not have this feature turned on.

Windows XP sometimes pops up a "Delayed write failed" prompt, telling you that there may be some problems with slowing down the write system. Although this is not a fatal error, it is worthy of your attention.

Here are some common reasons for "writing cache failure":

1. The reason for the disk drive itself. This happens especially on SCSI or RAID drives. There are some RAID driver drivers that report a fake message in the XP operating system with SP2 to tell the user "Write cache failed". So you should install the latest version of the driver for your disk drive.

2. The reason for the data line. Some errors or broken data lines, especially external USB lines and FireWire, can cause this. If your data cable is too long, or if the data cable is connected to a USB HUB of unqualified quality, the write cache will fail. Finally, it's probably because you have a UDMA driver that requires an 80-pin data cable, but you're using a 40-pin data cable.

3.SCSI termination error. Although this happens rarely on SCSI devices that use self-terminating technology, we still have to take it into account.

4. Media error. This is the most serious situation that can happen, in other words, the disk drive is broken. If you can get disk drive statistics through SMART (such as SMART & Simple) software, then you can use this information to determine the mechanical (physical) failure of the disk drive. You can also use a tool called Gibson Research's SpinRite to help you diagnose media errors, but it takes a long time to fully detect the disk drive.

5. The BIOS setting of the computer forcibly turns on the UDMA mode that is not supported by the drive controller. Although UDMA mode can enhance the performance of the disk, it will cause some errors if the drive controller does not support it. This situation is rare, mainly on newly installed hardware devices (the hardware device supports UDMA mode), users can restore the BIOS or restore the BIOS's options on the hard drive to the default "automatic detection" ; mode to solve this problem. For example: If there is a problem with a device set to UDMA Mode6 mode, you can set it to Mode5 mode. Previous12Next page Total 2 pages