Next Problem: Random HDD Write Errors

Thanks to those who recommended various hardware identifying utils for
my client's "dead HDD" system -- Using a combination of them, I was able
to identify everything and download the correct drivers.

But now I have yet another problem -- As I'm installing applications on
her system, at random and unexpected times, I'm getting the BSOD saying
"Disk Write Error". When I "press any key to continue", I get an
interesting "crazy quilt" display that reminds me of my long-departed
days as a high school geek debugging assembly language progs on the
Commodore 64. When I cold boot (nothing else works), I can resume the
aborted installation without further error, but always wondering when
the next error will come.

I've run Scandisk with full surface scan (twice) and run all the
diagnostic tests packaged with this HDD (a Maxtor), and everything
checks out fine.

Bearing in mind that this is a system that got zapped by a black out +
power surge (why the original HDD died), is there something else causing
these intermittant errors? -- It's always the same error: BSOD saying
"Disk Write Error on drive C", but it strikes at random times, and all
diagnostic progs indicate no problem with the drive.

--
Dave

Dave Hardenbrook

You have either got a bad HD or a bad system board. BTW... Where did
you find the "ANY" key. I've never been able to find it!

Dave Hardenbrook wrote:
> Thanks to those who recommended various hardware identifying utils for
> my client's "dead HDD" system -- Using a combination of them, I was able
> to identify everything and download the correct drivers.
>
> But now I have yet another problem -- As I'm installing applications on
> her system, at random and unexpected times, I'm getting the BSOD saying
> "Disk Write Error". When I "press any key to continue", I get an
> interesting "crazy quilt" display that reminds me of my long-departed
> days as a high school geek debugging assembly language progs on the
> Commodore 64. When I cold boot (nothing else works), I can resume the
> aborted installation without further error, but always wondering when
> the next error will come.
>
> I've run Scandisk with full surface scan (twice) and run all the
> diagnostic tests packaged with this HDD (a Maxtor), and everything
> checks out fine.
>
> Bearing in mind that this is a system that got zapped by a black out +
> power surge (why the original HDD died), is there something else causing
> these intermittant errors? -- It's always the same error: BSOD saying
> "Disk Write Error on drive C", but it strikes at random times, and all
> diagnostic progs indicate no problem with the drive.
>
> --
> Dave

Glenn

It really sounds to me like you have a bad MB. Alot of the problems you've
had seem to point to the MB.


"Dave Hardenbrook" <> wrote in message
news: k.net...
> Thanks to those who recommended various hardware identifying utils for
> my client's "dead HDD" system -- Using a combination of them, I was able
> to identify everything and download the correct drivers.
>
> But now I have yet another problem -- As I'm installing applications on
> her system, at random and unexpected times, I'm getting the BSOD saying
> "Disk Write Error". When I "press any key to continue", I get an
> interesting "crazy quilt" display that reminds me of my long-departed
> days as a high school geek debugging assembly language progs on the
> Commodore 64. When I cold boot (nothing else works), I can resume the
> aborted installation without further error, but always wondering when
> the next error will come.
>
> I've run Scandisk with full surface scan (twice) and run all the
> diagnostic tests packaged with this HDD (a Maxtor), and everything
> checks out fine.
>
> Bearing in mind that this is a system that got zapped by a black out +
> power surge (why the original HDD died), is there something else causing
> these intermittant errors? -- It's always the same error: BSOD saying
> "Disk Write Error on drive C", but it strikes at random times, and all
> diagnostic progs indicate no problem with the drive.
>
> --
> Dave

SBFan2000

In article <D_TTg.898$pS3.750@trnddc01>,
says...
> It really sounds to me like you have a bad MB. Alot of the problems you've
> had seem to point to the MB.

Could be -- I've been running some DOS-based burn-in tests and I'm
getting some weird random errors. Like for example, I was running one
that used a Mersenne Prime generator, and when I hit CTRL-C to end, I
got the error: "Spurious interrupt generated: IRQ7".

????

Dave Hardenbrook