Question Locked

Yet again, another series of unfortuate errors.

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello, fellow techs

A while back I asked a question about an unusal error I began recieving on one of our PCs.

The error:

Windows - Delayed Write Failed

Windows was unable to save all the data for the file \Device\HarddiskVolume5\$Mft. The data has been lost. This error may be caused by a failure of your company hardware or network connection. Please try to save this file elsewhere.

I was advised by a couple of friendly people on the forum to check both my drives and the drive controllers. I swapped out the drives, changed ribbon cables, and swapped parts between other machines. The hardware checked out. The error still shows up in the original PC.

Now, I have another problem. ANOTHER computer, an IBM 300GL, has developed this error, and nothing I do seems to stop it, and I'm getting worried.

There are 4 PC's, and they are on a 6 port hub.

The PC's are:

Three Dell Optiplex GX150's.
BIOS is A11 (Latest)
All run Windows 2000 Professional w/SP4
All have 512 MB system memory.
all have one 3.5" USB 2.0 External Hard Drive Enclosure with a 320GB hard drive.

The fourth PC:

IBM 300GL
Running Windows 2000 Professional w/SP4
512 MB System Memory.
20GB Hard Drive.

All PC's are currently running Bit Defender v10 Antivirus/Antispyware

Also, I cannot seem to turn off 'Write Caching' on one of my machines. When I 'check off' the box in the Drive Properties, it shows up as 'checked' when I look at it later!

Can anyone give me a hand? I am really stumped here, and confused. ~_~

Thanks!

2 replies

by zombiebot

Hi,

I'm sorry I don't know the solution to the "Write Caching" problem, but I did experience a similar problem to the one you were having with "Windows - Delayed Write Failed" a while back.

My problem occurred when my user was trying to update an Access database on a network drive. We were running Kaspersky AV. In the end I resolved the problem by configuring the user's AV client not to scan the network drives.

I've not used Bit Defender so I don't know if you can change the config this way, but it may be worth a try.

Good Luck,
Rob

This discussion is closed to new replies.