Windows Delayed Write Failed

  • Thread starter Thread starter shank
  • Start date Start date
S

shank

Windows Delayed Write Failed

I've been using my computer for over a year without issue. All of a sudden
I'm getting Windows Delayed Write Failed. I've tried all the solutions in
this KB article. http://support.microsoft.com/kb/330174 No joy. When I get
the error, the mouse goes wacky and the audio too. Can't get any work done
because the whole system is jerky and slows to a snail's pace.

Is there anything else I can try? Is the HDD going bad? It's less than a
year old and doesn't seem likely.

thanks
 
"shank" <shank@tampabay.rr.com> wrote in message
news:ulk$zsITIHA.4280@TK2MSFTNGP06.phx.gbl...
> Windows Delayed Write Failed
>
> I've been using my computer for over a year without issue. All of a sudden
> I'm getting Windows Delayed Write Failed. I've tried all the solutions in
> this KB article. http://support.microsoft.com/kb/330174 No joy. When I get
> the error, the mouse goes wacky and the audio too. Can't get any work done
> because the whole system is jerky and slows to a snail's pace.
>
> Is there anything else I can try? Is the HDD going bad? It's less than a
> year old and doesn't seem likely.
>
> thanks
>

I've seen HD's fail in as little as 5 weeks

run the mfg's harddrive diagnostic!
 
The system will become hesitant as the write errors happen. Several
things to do/check:
1.) Read-Only Chkdsk to determine if the volume is marked "Dirty"
2.) Check the Controller Advanced (TAB) and ensure the devices
are running in UDMA Mode 2 or greater. Device Manager &
expand the IDE/ATAPI category - Primary/Secondary
3.) Defrag the volume
NOTE: Chkdsk in Read-Only mode determines if the volume is Dirty
It may recommend a rerun with a /F or /R qualifier to fix any
errors it finds. If this is recommended do not do this unless
your data is backed up. Chkdsk /F /R can and does remove
data to resolve disk issues.

"shank" <shank@tampabay.rr.com> wrote in message
news:ulk$zsITIHA.4280@TK2MSFTNGP06.phx.gbl...
> Windows Delayed Write Failed
>
> I've been using my computer for over a year without issue. All of a sudden
> I'm getting Windows Delayed Write Failed. I've tried all the solutions in
> this KB article. http://support.microsoft.com/kb/330174 No joy. When I get
> the error, the mouse goes wacky and the audio too. Can't get any work done
> because the whole system is jerky and slows to a snail's pace.
>
> Is there anything else I can try? Is the HDD going bad? It's less than a
> year old and doesn't seem likely.
>
> thanks
>
 
On Tue, 1 Jan 2008 09:37:06 -0600, "philo" <philo@privacy.net> wrote:

>
> I've seen HD's fail in as little as 5 weeks


In fact, when it's relatively new is one of the two most likely times
for it to fail. The other is when it's relatively old.

That's true of most things, not just hard drives.

--
Ken Blake, Microsoft MVP Windows - Shell/User
Please Reply to the Newsgroup
 
"Ken Blake, MVP" <kblake@this.is.an.invalid.domain> wrote in message
news:ua2ln3tmn3605uqhll775ghplbievojc4g@4ax.com...
> On Tue, 1 Jan 2008 09:37:06 -0600, "philo" <philo@privacy.net> wrote:
>
>>
>> I've seen HD's fail in as little as 5 weeks
>
>
> In fact, when it's relatively new is one of the two most likely times
> for it to fail. The other is when it's relatively old.
>
> That's true of most things, not just hard drives.
>


Yep.

At any rate...the drive better be backed up ASAP...
and if it fails the diagnostic...replaced!

May still be under warranty
 
Not sure if I have good news or bad... I did chkdsk /f in safe mode command
prompt. It went through 2 of 3 stages without issue. In the 3rd stage
"verifying security descriptors 64% complete" it just stopped and returned
to the D: prompt. I tried running Chkdsk again but it wouldn't run. Likely
because it had to unmount the drive to do chkdsk. Anyway, I rebooted and I
have not seen the error once. Is the "verifying security descriptors " a
concern because it didn't go through to 100%? Should I chkdsk again?

thanks!


"R. McCarty" <PcEngWork-NoSpam_@mindspring.com> wrote in message
news:%23Bk1yyITIHA.2000@TK2MSFTNGP05.phx.gbl...
> The system will become hesitant as the write errors happen. Several
> things to do/check:
> 1.) Read-Only Chkdsk to determine if the volume is marked "Dirty"
> 2.) Check the Controller Advanced (TAB) and ensure the devices
> are running in UDMA Mode 2 or greater. Device Manager &
> expand the IDE/ATAPI category - Primary/Secondary
> 3.) Defrag the volume
> NOTE: Chkdsk in Read-Only mode determines if the volume is Dirty
> It may recommend a rerun with a /F or /R qualifier to fix any
> errors it finds. If this is recommended do not do this unless
> your data is backed up. Chkdsk /F /R can and does remove
> data to resolve disk issues.
>
> "shank" <shank@tampabay.rr.com> wrote in message
> news:ulk$zsITIHA.4280@TK2MSFTNGP06.phx.gbl...
>> Windows Delayed Write Failed
>>
>> I've been using my computer for over a year without issue. All of a
>> sudden I'm getting Windows Delayed Write Failed. I've tried all the
>> solutions in this KB article. http://support.microsoft.com/kb/330174 No
>> joy. When I get the error, the mouse goes wacky and the audio too. Can't
>> get any work done because the whole system is jerky and slows to a
>> snail's pace.
>>
>> Is there anything else I can try? Is the HDD going bad? It's less than a
>> year old and doesn't seem likely.
>>
>> thanks
>>
>
>
 
"shank" <shank@tampabay.rr.com> wrote in message
news:uOF7m7KTIHA.5516@TK2MSFTNGP02.phx.gbl...
> Not sure if I have good news or bad... I did chkdsk /f in safe mode
> command prompt. It went through 2 of 3 stages without issue. In the 3rd
> stage "verifying security descriptors 64% complete" it just stopped and
> returned to the D: prompt. I tried running Chkdsk again but it wouldn't
> run. Likely because it had to unmount the drive to do chkdsk. Anyway, I
> rebooted and I have not seen the error once. Is the "verifying security
> descriptors " a concern because it didn't go through to 100%? Should I
> chkdsk again?
>
> thanks!
>
>


NO

You need to download the HD mfg's diagnostic and run it.

If it finds a problem...the disk needs to be replaced. period!
 
"philo" <philo@privacy.net> wrote in message
news:OTOD0HLTIHA.4272@TK2MSFTNGP06.phx.gbl...
>
> "shank" <shank@tampabay.rr.com> wrote in message
> news:uOF7m7KTIHA.5516@TK2MSFTNGP02.phx.gbl...
>> Not sure if I have good news or bad... I did chkdsk /f in safe mode
>> command prompt. It went through 2 of 3 stages without issue. In the 3rd
>> stage "verifying security descriptors 64% complete" it just stopped and
>> returned to the D: prompt. I tried running Chkdsk again but it wouldn't
>> run. Likely because it had to unmount the drive to do chkdsk. Anyway, I
>> rebooted and I have not seen the error once. Is the "verifying security
>> descriptors " a concern because it didn't go through to 100%? Should I
>> chkdsk again?
>>
>> thanks!
>>
>>
>
>
> NO
>
> You need to download the HD mfg's diagnostic and run it.
>
> If it finds a problem...the disk needs to be replaced. period!
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =

I downloaded the Windows version of Seagate/Maxtor diagnostics and it
failed - ouch! Their website recommended I d/l the DOS bootable version and
run the long version of diagnostics which can also repair sectors. In fact,
that's what the problem was. One bad sector!

Thanks to all for the tips!
 
"shank" <shank@tampabay.rr.com> wrote in message
news:%23KYQ5$NTIHA.4740@TK2MSFTNGP02.phx.gbl...
>
> "philo" <philo@privacy.net> wrote in message
> news:OTOD0HLTIHA.4272@TK2MSFTNGP06.phx.gbl...
>>
>> "shank" <shank@tampabay.rr.com> wrote in message
>> news:uOF7m7KTIHA.5516@TK2MSFTNGP02.phx.gbl...
>>> Not sure if I have good news or bad... I did chkdsk /f in safe mode
>>> command prompt. It went through 2 of 3 stages without issue. In the 3rd
>>> stage "verifying security descriptors 64% complete" it just stopped and
>>> returned to the D: prompt. I tried running Chkdsk again but it wouldn't
>>> run. Likely because it had to unmount the drive to do chkdsk. Anyway, I
>>> rebooted and I have not seen the error once. Is the "verifying security
>>> descriptors " a concern because it didn't go through to 100%? Should I
>>> chkdsk again?
>>>
>>> thanks!
>>>
>>>
>>
>>
>> NO
>>
>> You need to download the HD mfg's diagnostic and run it.
>>
>> If it finds a problem...the disk needs to be replaced. period!
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>
> I downloaded the Windows version of Seagate/Maxtor diagnostics and it
> failed - ouch! Their website recommended I d/l the DOS bootable version
> and run the long version of diagnostics which can also repair sectors. In
> fact, that's what the problem was. One bad sector!
>
> Thanks to all for the tips!
>

I'm glad you found the problem...
and hopefully it will stay fixed...
but I would see if the mfg would replace the drive under warranty.

If you do not replace the drive...just make sure to always backup your
data...
and test it again from time to time.

If more bad sectors are found...definately replace the drive.

Some machines that I've worked on...that have bad sectors...just get
worse...
but OTOH: I've had some drives that had bad sectors that have been going
fine for years...
and no more have ever popped up
 
Back
Top