Please register or login. There are 0 registered and 854 anonymous users currently online. Current bandwidth usage: 326.30 kbit/s May 18 - 05:39pm EDT 
Hardware Analysis
Forums Product Prices

  Latest Topics 

More >>


  You Are Here: 
/ Forums / Other Hardware /

  "delayed Write failure" in WIN XP 
 Date Written 
Continue Reading on Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, Next >>
zhang lei Mar 31, 2004, 01:20am EST Report Abuse
>> Re: "delayed Write failure" in WIN XP
Hello everyone,

I've got the same problem as yours after yesterday I changed the memory usage setting from program first to system cache first, in the system property->advanced->performance options.
However in the safty mode, no error message pumps up. I changed the setting back in the safty mode, and the error disappeared up to now.
I believe this is a xp bug which is relatid to the large system cache technique.
Hope it's helpful to someone here.

Want to enjoy less advertisements and more features? Click here to become a Hardware Analysis registered user.
Martin S Mar 31, 2004, 08:02pm EST Report Abuse
>> Re: "delayed Write failure" in WIN XP
Hey guys.

One suggestion.
If you have a chance, go with S-ATA harddrives, much better choice.
I lost my 120 gig data drive just recently, but i managed to recover everything. My MFT on NTFS got pooped. Not sure how that happened, but it did. After that, i started getting DWF error on that same drive.
120 GB Maxtor (maxtor=crap). I'm running all Segate SATA drives now, and i'm happy.

If you lost important data and you need to recover it, try using Filerecovery Pro 3.2 ,
Very cool little softie. Unfortunately if you want to recover stuff you have to buy the program, but it's well worth the $$.

As to DWF error, I am not running ATI card and my HD got messed up anyway. There is a thing that got my attention in regards to the ATI cards. I used to have Radeon 9800 Pro and my computer was behaving strangly, and that it wasnt the software strange, it was hardware strange. I was getting power failures and such, and I started now thinking that maybe ATI's hardware does some internal damage to the overall system performance, that is irreversible. If you think about it hard enough it's quite possible, and of course ATI would never admit to it.

Let me know what you guys think

Corvus Raven Apr 02, 2004, 01:08am EST Report Abuse
>> Re: "delayed Write failure" in WIN XP
Chun Heng Phuah: XP _IS_ the bug. :)

ASUS A7N8X Deluxe PCB 2.00 w/ BIOS 1005 (cause? Dunno.. ATM)
AMD XP 2800+ @ 0.0 GHz 0MHz FSB (overheating for no appearent reason)
(2) - Corsair XMS512-3500C2 (5-2-2-2T) @ 0MHz
ATI Radeon 9700 Pro @0
Enermax 500W p/s (ok.
Jay Cabs Apr 02, 2004, 10:22pm EST Report Abuse
>> Re: "delayed Write failure" in WIN XP
Well, I seem to have contracted the same problem as you guys. My laptop (P3 IBM Thinkpad on XP Pro) seemed to be working great, and everything was fine. But today, I downloaded a DirectX 9.0b update, and all this crazy stuff began to happen. I can't even log in and change the registry or anything! Before I can even type my password, I am flooded with an infinite amout of those messages stating:

Windows - Delayed Write Failed

Windows was unable to save all the data for the file C:\ (various different files appear each time I click OK). The data has been lost. This error may be caused by afailure of your compter hardware or network connection. Please try to save this file elsewhere.


Well, all I have access to is the BIOS. But forgive me, I'm not the most computer-literate person on the planet. Actually, scratch that, I know nothing about computers. If anyone is willing to help me out with this please post, or e-mail me. I really don't want to have to clean out my entire hard drive because of this...

Mira Apr 05, 2004, 02:37pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
I also have had the same problem. I have two computers setup to dual boot in ME and XP. This is because some software my kids use won't work in XP.

The first system does NOT have the delayed write failure problem:
Netvista 6058 KAU
Intel Pentium III, 866 mhz
256MB pc-100 sdram
lite-on ltr-16101B cd-rw
iomega zip drive
120 GB HD (4G120J6) Maxtor ata 133/eide 5400 rpm (partitioned in three parts, has ME)
60 GB HD (4W060h4) Maxtor Diamondmax ata 100/eide 5400 rpm (left at 60gb, has XP)
sb pci 512 sound card
agp 32mb nvidia geforce DDR video
Realtek RTL8135 family pc fast ethernet nic

However the second system does have the delayed write errors:
Gigabyte GA-7IXEH via KT133/KT133E AGPset motherboard
AMD DURON 800 mhz cpu
256 mb sdram
Samsung CD-Rom SC-148F
Iomega Zip Drive
80gb WD800jb-00eta0 hd (Western Digital Caviar ultra ata/eide 7200 rpm) (three partitions, ME)
60GB 4W060H4 HD (Maxtor Diamondmax ata 100/eide 5400 rpm) (two partitions, XP)
sb pci 128 sound card
agp 32mb nvidia geforce2 GTS video
Realtek RTL8135 family pc fast ethernet nic

The system that had the write failure messages has the lastest VIA 4 in 1 drivers. This is the only thing that I can think of as the problem.

I have partitioned the 80gb hard drive into three partitions and that one has ME on it. The 60 gb I had left as one drive, but I got the delayed write errors constantly. I redid the hard drive with two partitions, one 40gb and the other the rest (20gb). So far no delayed write errors.

I had no indication of problems until I started to load office XP onto the system. After that I had constant delayed write errors. I tried to turn off the write-caching feature but it kept coming back on its own. I have not changed any of the default settings from windows XP.

My solution was to keep the partitions down around 40gb or less and so far it seems to be working. I would sure love to know why this has to be done.

Both systems are fat 32.

Paris Miles-Brenden Apr 07, 2004, 05:57pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
I have been experiencing this problem ever since I encountered a virus/worm "pup.exe and over.exe" . In the process of removing the virus I may have deleted some neccessary files. However, this particular virus had files on multiple drives. In addition, I did a complete scans with Adaware and Spybot and deleted numerous files, so that may have been it.

Here is my config:

C:, D: - Main, IDE, WesternDigital120GB HD on IDE0
E:, F: - Extended, IDE, Maxtor120GB HD on IDE1
G:, H: - Media, SATA, Maxtor160GB HD on SATA (mobo)

I have not yet had the chance to swap drives but will soon.
These all seem to be possible causes however.

Matt Burleson Apr 14, 2004, 11:44pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
Well I have battled the delayed write error on my usb and 1394 drives for days......I had a 200GB drive and thought the drive was dying. So I bought another 160GB and cloned it. Tried to use the cloned drive and got the Delayed Write Errors again.

Get this....

Turns out that I was over the 137GB limit.....I removed files from the drive to get it below 137 GB and the error's went away.

This happened with USB 2.0, and two 1394 (different) enclosures that I had.


Corvus Raven Apr 15, 2004, 03:21pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
Again with USB device. Anyone see a connection?
Perhaps better USB drivers are in order?

IDE and S-ATA as well.. Kina buggers up my original idea. :)

Those that have the problem are you using FAT 32, like Mira?

I wonder if there is a common link (other then XP) that would suggest a problem with configs or hardware.
Alot of Maxtor drives seemed to be in there as well.

ASUS A7N8X Deluxe PCB 2.00 w/ BIOS 1005 (cause? Dunno.. ATM)
AMD XP 2800+ @ 0.0 GHz 0MHz FSB (overheating for no appearent reason)
(2) - Corsair XMS512-3500C2 (5-2-2-2T) @ 0MHz
ATI Radeon 9700 Pro @0
Enermax 500W p/s (ok.
Corvus Raven Apr 15, 2004, 03:25pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP

I mean.. we all KNOW how perfect Windoze XP is. :)

ASUS A7N8X Deluxe PCB 2.00 w/ BIOS 1005 (cause? Dunno.. ATM)
AMD XP 2800+ @ 0.0 GHz 0MHz FSB (overheating for no appearent reason)
(2) - Corsair XMS512-3500C2 (5-2-2-2T) @ 0MHz
ATI Radeon 9700 Pro @0
Enermax 500W p/s (ok.
Joseph Perkins Apr 18, 2004, 12:36pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
Hi, all.

I don't /yet/ have THE solution, but I do have an important clue to these mysterious "delayed write failures". They always come after installing a new piece of hardware, or updating drivers for existing hardware. Either by your own hands or by applying a patch (from MS or the software supplier). Oh, and the rare few drive failures. I have personally recycled about 18 drives that had simply had their internal drive info corrupted by these failures.

What I can tell you about that is that some Crucial data for any given drive is stored in the best place, from the drive makers point of view, possible.. the drive platters themselves. That way, all boards are identical and initializing the drive makes the magic. If you can get access to someone who has the software/hardware for this (if you don't want to return the drive for refurb), you can return them to operating status with out even using a screwdriver :) Best drives (for me, so far): Maxtor (newer than 1995), worst: WD Caviar series.

Now, the clue: Windows XP is one of the first OS to use system resource sharing. This is still new enough (more later on this) that many software writers (mainly driver coders for add on hardware makers) don't know all about it.. and MS, as usual, is being very tight fisted about details. This means that, although there appear to be no conflicts with IRQ/DMA and so on, THIS AIN'T SO !!

What appears to be happening is that the resource handlers in XP are being told little white lies about requirements of a given piece of hardware.. or outright garbled lies.. and you're getting memory corruption. Reason is badly written drivers.

Most frequent culprit.. USB and TCP/IP stack handlers (some NICs) are fighting it out, and Windows is completely clueless.

Step one (for those of you who care) - remove ALL hardware (except the obvious). Go back to a bare bones system. Reload XP and proceed from there (other OSes, too, boys and girls).

Most common headaches: (Dell, Compaq, IBM and 29 other mixed breed mutts)

USB2 hardware.. NEC #1, Ali #2
NICs based on TI chipsets.
SB cards (Audigy, mostly) and Turtle

Some have been made to live together in harmony, some not.

Moral: Not all of this BS is the fault of M$. But, M$ is seriously lacking in fixing the situation. They should be storming the doors of many of the worlds add on makers and offerring the required info FREE, if neccessary, so we get properly written drivers.

Oh, and the resource sharing issue ? They had IRQ sharing figured out and working back in the days of CPM and HDOS.. I used to write drivers for those old OSes.. always made me steam that M$ never got around to it until XP.. what a joke.

Corvus Raven Apr 18, 2004, 04:20pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
" This means that, although there appear to be no conflicts with IRQ/DMA and so on, THIS AIN'T SO !!"

That partially explains the BIOS corruption I experienced.
I ..atleast figured that I .. knew that there was an IRQ/DMA conflict, yet M$ XP wouldn't see any propblems. Everything was reported as working properly, when there obviously was something wrong (Video and TV Tuner.. easy to SEE the problem :) )

And that it was Driver related. (ATI vs MSI drivers) Although mine wasn't a Delayed Write Failure, there was definately something funny going on. At first.. not too big a deal, hardware just wouldn't work. Next install I watched what was going on, instead of hitting 'OK' everytime it asked. ( .. Who knew.. I had other things to do the wait for this to be finished.. :) ) As I watched it install, Windowze came up with it's own drivers to install.. This WAS NOT OK.. The drivers simply didn't work. (forget which exactly, but someone else may know) anyways, this is where the problem arose. Even when I specified the loaction and asked to install from there it would default to the windoze drivers. That is when I decided on the ATI drivers, instead of trying the MSI ones.. It worked.. somewhat, I could get video but it was in a small 2"x3" area of the screen. And doing anything else with the display, (even clicking off screen..(off the window) would cause it to freeze.

Wait.. I though that 'XP' was uncrashable? Or atleast would 'reset itself' on it's own? Appearently not. 95 was easier to unfreeze - 3 finger salute.

The problem was resolved by re.. wait.. can't re-install, my key is no good. No matter, just wipe the drive.. wait.. (I posted the errors at one time) STOP e0/..bah.. I forget.. 5 different ones, 2 that weren't documented. None pointed to existing or used memory locations.

got p**sed, turned XP cd into frizbee.. and 2 coasters at once. Prior to that I DLed a keygen for XP, I went through 27 keys ..none were any good. Maybe the keygen wasn't working.. Oh well. but the original keys didn't work either. M$ was no help. ..ooh.. surprise. PIcked up new OEM version of XP, used Knoppix to wipe the drive (I love that little tool. :) ) re-installed, returned MSI card, picked up ATI version (wasn't there at the time I purchaced MSI one.. or no headaches at all I am .. sure?).. installed that.

Everything.. ok? (well so far) Don't hold your breath. :) (This is where I vowed to not purchace anymore M$ products. No more OS problems, no more HARDWARE problems, no more SOFTWARE problems of anykind requireing a 'hot fix' from M$.. (Which reminds me.. I'll have to email for the fix I need for my graphics software.. unless I saved it.. M$ XP corrupts data fiels to some programs. 3ds max is one, atleast discreet/Autodesk does what it can from it's end. Informs the user that M$ has a fix for M$'s problem.. Getting that fix is a hassle though, they want to know why this and why that.. I tell them because your stupid OS iss**t. and my 3 weeks of work is destroyed because of it. IF ONLY I COULD AFFORD ALAWYER.. balbla.. Like I'd win)

What annoys me the most is that M$ knows about most of the problems. And those that they don't know about .. well they get informed - quickly. In the meantime instead of helping the companies with hardware issues, they say 'our os is fine, it must be your software/hardware..'

Say.. how many of you are goiing to pickup SP2 for XP? Appearently is resolves some issues by elimiating the problem of seing them in the first place. That is, those trublesome items won't be recignised by SP2.

Atleast it is 'free'.

Well .. ain't tha perdie. Martha.. ges me tha shut-gunn.. wez guts us annoder varmin 'ere ta take cares off.
*BLAM!* *BLAM!* *BLAM!* *BLAM!* Martha.. Me thinks is still a twitch'n.. *BLAM!* *BLAM!*

ASUS A7N8X Deluxe PCB 2.00 w/ BIOS 1005 (cause? Dunno.. ATM)
AMD XP 2800+ @ 0.0 GHz 0MHz FSB (overheating for no appearent reason)
(2) - Corsair XMS512-3500C2 (5-2-2-2T) @ 0MHz
ATI Radeon 9700 Pro @0
Enermax 500W p/s (ok.
angryhippy Apr 18, 2004, 09:23pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
Joseph and others. If you think you have corrupted system files go to Start/Run and type in sfc /scannow. You may need your XP CD if you installed from one. If you have a proprietary system like Dell compaq etc. you wont need the CD. The OS will prompt you if it needs it. This scans all the critical system files and repairs as needed.

Get Hippied out!
Me at work:
My rig! A Blah blah.With a blah blah! SWEET!
Da Beast!
i5 3570K 4.6GHz
Win7-8 Pro 64bit
Corvus Raven Apr 19, 2004, 12:23am EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
Mine was to the point it wouldn't boot. Just recived the STOP errors and a request to re-install, which was difficult when the key I had was not being accepted as valid. (It was the original key for that COA)

Oh well. ..'.. and another one bite the dust, ahh.. "

ASUS A7N8X Deluxe PCB 2.00 w/ BIOS 1005 (cause? Dunno.. ATM)
AMD XP 2800+ @ 0.0 GHz 0MHz FSB (overheating for no appearent reason)
(2) - Corsair XMS512-3500C2 (5-2-2-2T) @ 0MHz
ATI Radeon 9700 Pro @0
Enermax 500W p/s (ok.
Michael Yeang Apr 24, 2004, 08:08pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
I found a site that has good info on Windows XP NTFS that might help with our problems:

Look under the heading "Disabling unnecessary NTFS behaviors". It says:

To manipulate the MFT's zone reservation, go to the HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \FileSystem registry key, and add a REG_DWORD value NtfsMftZoneReservation. The default value is 1, possible values are 1 to 4 (1 reserves 12.5 percent, 2 reserves 25 percent, 3 reserves 37.5 percent, and 4 reserves 50 percent of the NTFS volume for the MFT's buffer zone).

Perhaps we could change the space allocated to the MFT by setting the NtfsMftZoneReservation Dword in the registry to 2. Any opinions?

Stephen Donlan Apr 26, 2004, 05:53am EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
All I can say is... "AAAAAGHHH!!!"

I bought a 160gb h/drive about 10 months ago (Maxtor Diamond 9, 8mb cache). I never installed the patch for SP1 on XP and never had any problems. About 4-5 months ago, when I did install the patch, I had some weird and wonderful errors.

Firstly, I noticed these 'Write Delay Failure' - I had my h/d as primary slave to my 30gb drive which was my system drive. I wasn't getting these errors in Win ME (I was dual booting my 30gb and had my 160gb formatted to NTFS). I was only getting them in XP with SP1 installed. My system would quite often momentarily freeze up in XP, too (it still does) - everything locks up for about a second and then the system resumes as normal.

I checked Maxtor's website and downloaded, as they recommended, the Large Drive Enabler program (apparently, Windows XP out-of-the-box supports LBA 48bit access, but SP1 overwrites that and disables it - thereby screwing up the h/drive if anything is saved after the 137gb partition). So, as far as I am aware, my system is running correctly, as it should. I was kinda expecting these errors to go away - sadly not. I knew that something was badly wrong when the drive froze up in Dos mode as I was running the PowerMax software (led me to believe that there was a prob with the h/d and not a software issue) - so i returned the h/d to sender. They sent it back a week later saying that it was fine.

I reformatted my 30gig h/d, thinking that it was a prob with some s/ware on Windows - for some strange reason, it totally screwed up the format of my 160gig, so I lost over 70gigs of info! This happened twice. Not a happy camper.

So, I'm stuck with a 30gig IBM drive (working fine) with a 160gig hard drive (now it's running on a separate PCI IDE card - trying to rule out any kind of problem) but my system still momentarily freezes up and still keep getting the delayed write failures.

Any ideas anyone?

My system is as follows:
Gigabyte Nforce 2 motherboard (7N400L1)
AMD Athlon XP 3200+
1 Gig DDR 400 RAM
XP Pro (SP 1 with the Maxtor large drive enabler patch)
Radeon 9700pro
550w power supply

Thanks - Stephen

Mithrandir Greybeard May 06, 2004, 10:47pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
There are very numerous references to the radeon software being involved with delay write failure. I would check that first.

P.s. If I were you, I would use the 160 as the primary master (system drive) and the 30 on the secondary ide. If the 30 isn't big enough for your data, I would replace it. As it must be older, it is more prone to failure and I wouldn't want it on the same ide as my newer, probably faster drive possibly slowing it down. You've got some really cool hardware though.

Stephen Donlan May 07, 2004, 08:39am EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
Hehehe - it does run pretty well :o)

Just thought that I'd let everyone know that, I don't know WHAT I've done, but the problem has vanished! I reformatted my system (low level reformatted) and installed Windows XP Media centre edition. Touch-wood, I've had it running for over a week now, and not a single hiccup! I've not altered any of my BIOS settings or anything - I'm guessing that I had a dodgy file/driver on Windows (now THERE'S a surprise NOT)


Rhialto the Marvellous May 07, 2004, 11:12am EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
You'll be OK until you try to tweak XP like many of us love to do!

See the other thread about Deleyed Write Failed:

Corvus Raven May 07, 2004, 11:26pm EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
To make it work better; no less. :)

ASUS A7N8X Deluxe PCB 2.00 w/ BIOS 1005 (cause? Dunno.. ATM)
AMD XP 2800+ @ 0.0 GHz 0MHz FSB (overheating for no appearent reason)
(2) - Corsair XMS512-3500C2 (5-2-2-2T) @ 0MHz
ATI Radeon 9700 Pro @0
Enermax 500W p/s (ok.
Dave Emily May 09, 2004, 05:55am EDT Report Abuse
>> Re: "delayed Write failure" in WIN XP
Regarding Stephens post:
I think I have lost almost 250GB of data due this phenomena.
Without explanation or warning, two days ago I restarted my system and have not been able to get past the "Delayed Write Failed" error message.
I am not a computer tech and would be grateful for any suggestions that may recover some of the data.
Some background:
The large drive utility from Maxtor never worked for me.
I could not get past 136GB. I do not remember why now, but there were issues and I was unable to format the drive as one large partition. Nothing worked.
Out of frustration I gave up on it and wrote off 24 GB per drive. I configured 2 drives on IDE 1 and the 3rd drive on IDE 2.
It has been stable for the last 6-8 months.
I did have have a scare when I updated the 9700 a few months ago.
I was able to undo the update and re-instaled the previous drivers.
This is much more serious. The system has done the check drive for errors, and tries to re-boot only to repeat the same, "write failed" message again. I get as far as entering my password to login and after that it has a blue background and the cycle starts over.
I did not create any recovery disks and I am paying the price.
Safe mode does not do anything. No alternate anything works yet.
I tried the Powermax utility from Maxtor today and got the following error message:
"can't load BDOS kernal file A:\ IBMDOS.COM" I will try it again on a new floppy and see if that helps.
Lastly I did get a message that said:
.."unmountable boot volume"
this came up sometime today and has not been back. I think this is the final nail.
Currently I am using an old 30GB IBM deskstar drive that I have. It seems to be ok.
I use Panda AntiVirus/firewall, very pleased with it, is a great product, so-long Mac Aflea, and I defrag weekly.
Intel 2.4 Celeron
512 Mb PC400 DDR RAM
3ea Maxtor DiamondMax 160GB ATA/133 HD
(+1 that was not installed)
(this is really weird-it has been on a shelf and when I used it today it is doing the same thing)
Radeon 9700 Pro
Audigy SB w/Klipsch Pro-Media
XP Prosessional
Yamaha CRW-F1 & CRW 3200E
Thermaltake Xaser 3 Case
420W Thermaltake PS
19" Mitsubishi Diamond Pro 920

Continue Reading on Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, Next >>



  Topic Tools 
RSS UpdatesRSS Updates

  Related Articles 

A weekly newsletter featuring an editorial and a roundup of the latest articles, news and other interesting topics.

Please enter your email address below and click Subscribe.