Windows uses a special subsystem to provide support for some disk-based operations, such as a technology that temporarily caches the write operation of the disk, and then wait until the system is idle, perform the corresponding operation. This technique called "write cache" can improve system performance, but the system may not turn on by default.
Want to know how to set the "Write Cache" option? Please open "Device Manager" to expand "Disk Drive", then click the right mouse button on any of the drive icons below and select Properties, then switch to the Policy tab. Here you should see two options: "Optimize for quick deletion" (all things are written directly to hard drives) and "optimize performance" (written to cache). The first option allows you to quickly disconnect the device to the computer, such as a USB flash memory, you don't have to click the "Secure Delete Hardware" icon in the taskbar to disconnect these devices and computers. If both options are in a gray, you cannot select, then your disk drive has already opened the Write Cache option by default. (To see more information about delaying writing the default status, see Microsoft's article "Windows XP and surprise removal of hardware")
Sometimes the "Delayed Write Failed" is sometimes popped up in the Windows XP system, telling you that there may be some problems in the write system. Although this is not a fatal mistake, but it is worth causing you enough attention.
Here are some common causes of "write cache failure":
1. The cause of the disk drive itself. This situation occurs, in particular, on the SCSI or RAID driver. Some RAID drivers are reported to report a false message in the XP operating system installed in the 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 cable. Some erroneous or damaged data lines, especially external USB cables and fire lines, can cause this. If your data line is too long, or the data cable is connected to a quality unqualified USB HUB, it will also cause the write cache to fail. Finally, it may be because you have a UDMA drive that requires 80-pin data cable, but you use a 40-pin data cable.
3. SCSI terminates errors. Although this situation rarely occurs on SCSI devices that use Self-Terminating technology, we must still take it into account.
4. Media error. This is the most serious situation, in other words, that is, the disk drive is broken. If you can get the statistics of the disk drive via the Smart (such as Smart & Simple), you can judge the disk drive with mechanical (physical) failure through this information. You can also use a tool called Gibson Research's Spinrite to help you diagnose media errors, just this software consumes a considerable time when fully detecting the disk drive.
5. The computer's BIOS setting enforces the UDMA mode that the drive controller is not supported. Although the UDMA mode enhances the performance of the disk, if the drive controller is not supported, some errors will occur. This situation is not much, mainly on the newly installed hardware device (the hardware device supports UDMA mode), and the user can restore BIOS or restore the option of the hard drive to the default "Auto Detection" mode by upgrading the BIOS. To solve this problem. For example: If you set it into a UDMA Mode6 mode, you can set it to Mode5 mode.
6. Drive controller problem. I have encountered a USB controller and other hardware devices conflicts and generate a way to write a buffer failure. If your system has long and short two PCI slots (64-bit and 32 digits), try unplug the USB controller from the long PCI slot. Some older PCI cards do not support this type of slot. 7. Memory parity error. This happens when you have added a memory, it is probably that the memory type supported by your new memory module and the motherboard is incompatible, or there is a problem in memory itself. (There is a problem with memory, there will be other errors, such as random dead locks, etc.)
8. LargeSystemCache key value error in the registry. This situation rarely, usually happened to those machines that have an ATI display adapter with memory greater than 521MB. There is a key called LargeSystemCache (HKY LOCAL MACHINE / SYSTEM / CURRENTCONTROLSET / Control / System / CurrentControlSet / Control / System / CurrentControlSet / Control / SESSION Manager / Memory Management), which is used to manage the memory capacity assigned to some core processes, if the key value If set to 1 (this setting can enhance the performance of the machine than 512MB), it is possible to cause data errors and errors in some systems to generate write cache failures. If this happens, turn this key value to 0.
