WinXP Pro Hibernate Delayed Write Errors

[Michael Gerbasio]

Hi,
I just started having a problem on a ThinkPad X31 running WinXP with all
latest patches applied. When I power up after hibernating I keep getting
repeated messages saying "Windows Delayed Write Failed" and it gives me
numerous file names in c:\windows\system32.

I checked the drive and it doesn't have any errors. I also did a google and
ms site search and didn't find anything. Any ideas what could be wrong? I
haven't installed any software recently and there haven't been any hardware
changes or registry changes.

TIA.
Regards-Michael G.

 

[R. McCarty]

Delayed Write failure is more of a Controller issue not necessarily
the drives it serves. You should check IDE/ATAPI category in the
Device Manager. Double-Click each controller ( Primary/Secondary )
and examine the operating mode of each tap. It's possible that your
drive has had it's operating mode reduced from UDMA back to PIO
to avoid error(s). If this has happened the throughput speed of the
drives/opticals will be significantly slower than if running in it's normal
or optimal mode.

Usually with most Chipset controllers the "Advanced" (TAB) will
show the specific information about devices connected.

 

[Poprivet]

Delayed Write failure is more of a Controller issue not necessarily
the drives it serves. You should check IDE/ATAPI category in the
Device Manager. Double-Click each controller ( Primary/Secondary )
and examine the operating mode of each tap. It's possible that your
drive has had it's operating mode reduced from UDMA back to PIO
to avoid error(s). If this has happened the throughput speed of the
drives/opticals will be significantly slower than if running in it's
normal or optimal mode.

Usually with most Chipset controllers the "Advanced" (TAB) will
show the specific information about devices connected.

Okaaayyyy, assuming that points something out, what steps should the OP
take? I don't see any alternatives listed.

 

[R. McCarty]

Uninstall the Primary/Secondary or both controllers and reboot.
XP will redetect the controllers and then the devices connected
to them. Usually, the devices will be setup with their optimal
operating mode. But if error(s) continue to be logged then it's
likely XP will again reset the operating mode to a slower value
to try and avoid errors.

 

[Michael Gerbasio]

Thanks, but now it got really ugly and I didn't do anything other than power
cycle.

I get the Windows boot screen but then get an Unmountable Boot Volume BSOD.
So I load up and run recovery console. I try fixmbr and get the following:
"The new master boot record could not be written.
"The disk may be damaged"

I try fixboot and get the following errors:
"FIXBOOT is wirting a new boot sector"
"The boot sector cannot be fixed."

So would you agree it sounds like a faulty drive?

Regards-Michael G.

 

[R. McCarty]

Very likely - If you have access to another PC you might want to
download the drive manufacturer's diagnostic program. Usually it's
bootable in the form of an .Iso module. Many drives now have a
warranty period of 3-5 years and if the diagnostic determines the
drive has failed it ( diagnostics ) will help you to file an RMA.
(Return Merchandise Authorization).