Delayed Write


I have a Gigabyte 8KNXP Rev 1 motherboards that gave up the ghost. It had a RAID 0 array of two Maxtor DiamondMax 10 drives on the Gigabyte board’s onboard IT8212F RAID controller.

I replaced the dead motherboard with an EVGA nForce680i SLI board. Not wanting to risk the loss of 150GB of data from the last four years, I bought an IDE RAID controller card with the same IT8212F chipset and reinstalled XP SP2.

When I access the RAID drive, I can read the directories and even open the folders within. Yet, Windows XP will give me a balloon in the lower right-hand corner saying: “Windows – Delayed Write failed. Windows was unable to save all the data for the file G:\xxx. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.”

How might I ensure that I can save my data from this drive without risking permanent data loss?

—Paul Andrew

Delayed write failures can happen in XP SP2 if your RAID drivers are out of date. Try downloading the driver version from ITE’s website ( ). You should also upgrade your XP install to SP3.

Delayed write errors can also happen if your LargeSystemCache registry setting has been set to 1. Enabling the LargeSystemCache was useful in ye olden days, but there’s really no need to enable it in modern systems. Go to your Start menu, hit Run, and type regedit. Then navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\MemoryManagement and check the LargeSystemCache entry. If it’s been set to 1, change it back to 0.

Delayed write errors can be the fault of the LargeSystemCache registry entry.

SUBMIT YOUR QUESTION Are flames shooting out of the back of your rig? First, grab a fire extinguisher and douse the flames. Once the pyrotechnic display has fizzled, email the doctor at for advice on how to solve your technological woes.

Around the web

by CPMStar (Sponsored) Free to play