Re: windows delayed write failed
From: WinGuy (no_spam_at_nomail.bot)
Date: 09/07/04
- Next message: .: "XP SP and program conflict"
- Previous message: Greg Palmer: "RE: Windows messenger"
- In reply to: trainer: "windows delayed write failed"
- Next in thread: Greg Palmer: "RE: windows delayed write failed"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 07 Sep 2004 16:08:52 GMT
"trainer" <trainer@discussions.microsoft.com> wrote in message
news:E5B0418A-5D1F-4C48-8E7F-A3286D16FAE6@microsoft.com...
> Windows delayed write failed. Windows was unable to save the data. This
was
> caused by a failure of the computer hardware or network connection.
> Checked the network connection - was ok. Can anyone tell me how to fix?
By network failure, it means if the system was trying to write something to
a shared network resource (perhaps a folder on one of your other LAN
computers, etc. if you even do that sort of thing). It does not necessarily
mean a general network failure (as you discovered).
It does mean that Event Viewer is probably going to show that there are
serious problems associated with your hard drive and that it is failing. If
so, then it is time (before the damage becomes completely unrecoverable) to
STOP using the computer and power it down, take it to a repair shop (or, if
you're competent enough then you could do it), replace the failing HDD with
one the same size or larger, and use the HDD utility that comes with the new
HDD to make a cloned bootable disk copy of you existing but failing drive. I
would advise that before booting that cloned drive for the very first time
that it be very thoroughly checked for bad file structures AND for bad
sectors as it has been my experience, (many times!) with XP only, that the
new bootable cloned XP drive will NOT work unless that procedure has been
performed after the clone process and before the initial boot of the new
clone drive -- and could instead result in BSOD!
Note that a failing HDD might not be the culprit. A failing CD or floppy
drive can electronically load the motherboard IDE controller chip to the
point of malfunction with other devices (such as a HDD) and in time even
itself get damaged. Or that IDE controller could already be damaged or heat
sensitive etc. Bad motherboard solder joints are always a possibility, too.
You might try removing the flat ribbon cables (note their orientation, they
do have red striped sides) for everything except for the HDD and see if the
problem goes away. Never connect or disconnect or improperly connect those
flat ribbon cables, especially if the power cord is connected to the
computer, they are NOT intended to be "hot swapped" or connected wrongly and
very serious electronic damage can result if that occurs. Only USB allows
hot swapping (and even then, some attached USB devices, such as external
HDD's, might not allow hot swapping without first doing special procedures).
- Next message: .: "XP SP and program conflict"
- Previous message: Greg Palmer: "RE: Windows messenger"
- In reply to: trainer: "windows delayed write failed"
- Next in thread: Greg Palmer: "RE: windows delayed write failed"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|