V
Vile
From: Theriex ([email protected])
Subject: Windows XP Pro Locks Up When Hard Drive Crashes...
View this article only
Newsgroups: microsoft.public.windowsxp.help_and_support
Date: 2004-05-22 22:40:41 PST
I'm running Windows XP Pro w/complete updates. I have a failing 40Gb
hard
drive and when it crashes it locks up the entire OS. What I can't
figure
out is why?
The OS is on a completely different 'working' HD, the page file is on
the
same 'working' HD. The failing HD is being used for storage and that
is it.
The working HD is on the primary ide controller on the MoBo and the
failing
HD is on the secondary ide controller on the MoBo.
I've had failing HD's before, and it never used to do this in previous
versions of Windows.
I'm not sure if anyone knows why this is happening and how i can fix
it, and
i'm not sure what information about my system would be helpful.
I have 2 Maxtor 40Gb HD's capable and running in UDMA-6 mode and are
both
NTFS.
Before replying to this, I have tired absolutely everything i can
think of
and yes removing the failing HD fixes the problem, obviously. But i
need
the HD in there and there is no reason it should be causing the system
to
hang when it is only used for storage and windows doesn't have any
files on
it.
If anyone has any ideas, please email me at (e-mail address removed)
*Snip*
I bought a new compaq presario sr1130nx and put my old 40 gig
harddrive in with the new 160 gig and got a cross error. I took it in
and they told me the jumper settings needed to be changed. I have
another problem I am about to post about and saw this and wanted to
let you know.
Subject: Windows XP Pro Locks Up When Hard Drive Crashes...
View this article only
Newsgroups: microsoft.public.windowsxp.help_and_support
Date: 2004-05-22 22:40:41 PST
I'm running Windows XP Pro w/complete updates. I have a failing 40Gb
hard
drive and when it crashes it locks up the entire OS. What I can't
figure
out is why?
The OS is on a completely different 'working' HD, the page file is on
the
same 'working' HD. The failing HD is being used for storage and that
is it.
The working HD is on the primary ide controller on the MoBo and the
failing
HD is on the secondary ide controller on the MoBo.
I've had failing HD's before, and it never used to do this in previous
versions of Windows.
I'm not sure if anyone knows why this is happening and how i can fix
it, and
i'm not sure what information about my system would be helpful.
I have 2 Maxtor 40Gb HD's capable and running in UDMA-6 mode and are
both
NTFS.
Before replying to this, I have tired absolutely everything i can
think of
and yes removing the failing HD fixes the problem, obviously. But i
need
the HD in there and there is no reason it should be causing the system
to
hang when it is only used for storage and windows doesn't have any
files on
it.
If anyone has any ideas, please email me at (e-mail address removed)
*Snip*
I bought a new compaq presario sr1130nx and put my old 40 gig
harddrive in with the new 160 gig and got a cross error. I took it in
and they told me the jumper settings needed to be changed. I have
another problem I am about to post about and saw this and wanted to
let you know.