Windows Delayed Write Failed

[dr_roberts49]

I recently got this windows prompt after trying to run a sweep with Webroots Spysweeper with Anti Virus. Never got it before. Pops up when Spysweeper completes the registry sweep and is gathering cookies info. The write error is related to the data file in Windows Event log (EVT file). The only way to keep the error message from popping up is to reboot. Sometimes, during the Spysweep, it will go right into the BSOD that displays memory dump in progress. If I hit my reset button, I boot right back into Windows with no problems.

I first got this error problem about 4 days ago, and my computer ran just fine once I did a reboot. I could do everything. Play games, internet, file work, and even burn CDs and DVDs. No errors, but if I ran Spysweeper, the errors would return. Any suggestions?

Windows XP Pro SP2
ABIT 975X motherboard
Intel Dual Core
2x 512MB Corsair DDR2 800
Nvidia GT 7600
2 IDE drives running on High Rocket 100 ATA card (Maxtor 160GB & Maxtor 200GB)
1 SATA Maxtor 160GB
2 Optical drives connected to single IDE port on motherboard
500 watt ANTEC Earthwatts powersupply
Floppy drive
Thermaltake Super beetle cooling fan/heatsink (38-40c at idle) no overclocking.
All the usual stuff from there. All drivers up-to-date.

Robert

[RamonGTP]

This error usually occurs when the system was unable to write a file to the hard drive. I see it every once in a while on my file server and it's always related to my external USB drive and usually happens when I move the drive and the power cable comes loose. If you have no USB drives that may have come disconnected for a split second, then it could be an early sign of hard drive failure.

[dr_roberts49]

I do have an external USB drive, and I don't always have it powered up. I bet that's it. Thanks for the tip, RamonGTP. I have to head into work right now, but I'll give it a try when I get home. I'll keep you posted. Thanks again.

Robert

[dr_roberts49]

Well, connecting my USB drive didn't fix the problem. I did some investigating, and there are several options open to me. If I can get out of my lazy mood, I'll give some of them a try today.

Robert

[DanU]

I agree with RamonGTP. It could be a sign that you hard drive is starting to die. Back up NOW!

Once everything is safetly backed up, then check the drive for errors, and activate both options to fix file system errors and scan for bad sectors.

[Steve R Jones]

All sorts of things can cause the error besides the drive being bad...

Few years ago ATI vid cards caused it if you chnage windows system cache settings...

Here's a link about a certain Raid controller..
http://support.microsoft.com/kb/870894/en-us

[dr_roberts49]

Thanks guys for the input. I did do a surface scan of my hard drive and it came up clean. No errors. Webroot also suggested that I uninstall their program and then reinstall it. I'm going to try that too. I'm just so busy at work right now, that when I get home, I'm just too tired to deal with it. My computer runs great, no other problems, I just can't run a complete spyware/virus sweep without getting that sequence of errors. There is a vast amount of information on the internet, a good amount of it coming from Microsoft, but most all of it deals with servers and most appears to be pre SP2. I've never been comfortable with editing my registry, and most all the solutions call for that. If all else fails, I can do a format and clean install on my next day off

I do appreciate the input and will leave no stone unturned. I'll keep everyone posted. Thanks again.

Robert

[dr_roberts49]

Took some time, but I finally figured out my problem. A few weeks ago, I had downloaded a new version of SpySweeper from their website and installed it. Apparently, there was a setting in the newer version called "Direct Disk Screen". By disabling this function, the entire problem went away. I was able to do my first full sweep scan in several weeks without that annoying error message and the BSOD that followed. All is right with the world

Robert