HELP!!!! Any way to recover??

[Guest]

I was helping my dad quiet down his PC. In the middle, somehow the PC
stopped booting. Yeah, I know... great help son... sh*t!! thats the last
time I try to help people out... this is what I get for it.

Anyways, after a lot of hair pulling, it seems the hard drive got corrupted
somehow.

I pulled all the cards, XP kept crashing in NTFS.sys, AGP...SYS, etc. Kept
getting a BSOD

Safe mode wouldn't work.

Tried connecting the hard drive to my PC, hoping I could boot off my hard
drive and at least take a look at the bad one and maybe copy files off of it


Even with that drive attached to my PC at a slave, I get a BSOD on bootup. I
tried "hot powering" the hard drive hoping to skip any volume checking XP
did... no luck... as soon as I did add hardware, BSOD city.

Can't get in the recovery console either... BSOD

Can't "upgrade" XP... BSOD.

Any other ideas?

This is an NTFS drive.

 

[Michael Stevens]

I was helping my dad quiet down his PC. In the middle, somehow the PC
stopped booting. Yeah, I know... great help son... sh*t!! thats the
last time I try to help people out... this is what I get for it.

Anyways, after a lot of hair pulling, it seems the hard drive got
corrupted somehow.

I pulled all the cards, XP kept crashing in NTFS.sys, AGP...SYS, etc.
Kept getting a BSOD

Safe mode wouldn't work.

Tried connecting the hard drive to my PC, hoping I could boot off my
hard drive and at least take a look at the bad one and maybe copy
files off of it

Even with that drive attached to my PC at a slave, I get a BSOD on
bootup. I tried "hot powering" the hard drive hoping to skip any
volume checking XP did... no luck... as soon as I did add hardware,
BSOD city.

Can't get in the recovery console either... BSOD

Can't "upgrade" XP... BSOD.

Any other ideas?

This is an NTFS drive.

Not sure what "quiet down" is referring to, and would need some more
specific error messages to give more help.
When you hooked up the hard drive to your computer, did you jumper it to the
slave position?
--

Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Guest]

"quiet down"... you know... it was a noisy PC... we were trying to trouble
shoot where the noise was coming from.

yes, I jumpered it to slave.

with the bad drive attached to my working PC, I get a BSOD in NTFS.SYS in
normal mode and it safe and in debug, etc... basically every boot option
gives me a BSOD in NTFS.SYS on the bad drive.

When this drive is set as the lone master drive... same thing... Windows XP
boot up screen comes up, moments later, BSOD in NTFS.sys.

Recovery Console, BSOD in NTFS with either the bad drive connected or both
drives connected and the bad one set to secondary slave.

 

[Michael Stevens]

"quiet down"... you know... it was a noisy PC... we were trying to
trouble shoot where the noise was coming from.

yes, I jumpered it to slave.

with the bad drive attached to my working PC, I get a BSOD in
NTFS.SYS in normal mode and it safe and in debug, etc... basically
every boot option gives me a BSOD in NTFS.SYS on the bad drive.

When this drive is set as the lone master drive... same thing...
Windows XP boot up screen comes up, moments later, BSOD in NTFS.sys.

Recovery Console, BSOD in NTFS with either the bad drive connected or
both drives connected and the bad one set to secondary slave.

If it was the hard drive [very likely as it causes BSOD's on both computers]
that was making the noise, it may have failed and was not your fault. If
important imformation was valuable enough that needs to be retreaved, you
should stop any further access to the hard drive and take it to a
professional hard drive service.

--

Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Guest]

No it was not the hard drive making the noise.

Bottom line:

full tower case
3 case fans
boxed intel CPU fan
northbridge fan
nvidia "racing strip" (ie. useless) video card fan
noisy power supply

Thats a noisy SOB! We were playing with the various fans trying to see which
one made the most noise.

Somehow, and at 3:12AM in the morning, I don't really give a s*it how, the
hard drive got corrupted.

WinXP repair console would BSOD
Setup would BSOD
Connecting it to another PC would BSOD
etc, etc.

I was this close to formating/fdisking the drive when I decided to google
around for a bit and found a DOS based NTFS driver... Ran it and was able to
see the drive and everything on it. It included a DOS version of NTFSCheck,
which I ran and it found some errors in the MBR and corrected them.

Now it stopped BSODing, but still wouldn't boot up, but now I was able to do
an "upgrade" and repair everything.

Finally I am back up and my dad wont kill me

And now I can go to sleep.

"quiet down"... you know... it was a noisy PC... we were trying to
trouble shoot where the noise was coming from.

yes, I jumpered it to slave.

with the bad drive attached to my working PC, I get a BSOD in
NTFS.SYS in normal mode and it safe and in debug, etc... basically
every boot option gives me a BSOD in NTFS.SYS on the bad drive.

When this drive is set as the lone master drive... same thing...
Windows XP boot up screen comes up, moments later, BSOD in NTFS.sys.

Recovery Console, BSOD in NTFS with either the bad drive connected or
both drives connected and the bad one set to secondary slave.

If it was the hard drive [very likely as it causes BSOD's on both computers]
that was making the noise, it may have failed and was not your fault. If
important imformation was valuable enough that needs to be retreaved, you
should stop any further access to the hard drive and take it to a
professional hard drive service.

--

Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Michael Stevens]

No it was not the hard drive making the noise.

Bottom line:

full tower case
3 case fans
boxed intel CPU fan
northbridge fan
nvidia "racing strip" (ie. useless) video card fan
noisy power supply

Thats a noisy SOB! We were playing with the various fans trying to
see which one made the most noise.

Somehow, and at 3:12AM in the morning, I don't really give a s*it
how, the hard drive got corrupted.

WinXP repair console would BSOD
Setup would BSOD
Connecting it to another PC would BSOD
etc, etc.

I was this close to formating/fdisking the drive when I decided to
google around for a bit and found a DOS based NTFS driver... Ran it
and was able to see the drive and everything on it. It included a DOS
version of NTFSCheck, which I ran and it found some errors in the MBR
and corrected them.

Now it stopped BSODing, but still wouldn't boot up, but now I was
able to do an "upgrade" and repair everything.

Finally I am back up and my dad wont kill me

And now I can go to sleep.

Congrats, but next time[heaven forbid] try to be more helpful with your
explanation.
You made it really sound like it was the hard drive.
When you get some rest, can you share the name of the DOS utility you used
and other pertinent info. Was it NTFSdos from Wininternals? This is a peer
support newsgroup and we all learn from each other so share your experience
with the group.
--

Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm

 

[Guest]

Yup, NTFSDos... saved my ass...

No it was not the hard drive making the noise.

Bottom line:

full tower case
3 case fans
boxed intel CPU fan
northbridge fan
nvidia "racing strip" (ie. useless) video card fan
noisy power supply

Thats a noisy SOB! We were playing with the various fans trying to
see which one made the most noise.

Somehow, and at 3:12AM in the morning, I don't really give a s*it
how, the hard drive got corrupted.

WinXP repair console would BSOD
Setup would BSOD
Connecting it to another PC would BSOD
etc, etc.

I was this close to formating/fdisking the drive when I decided to
google around for a bit and found a DOS based NTFS driver... Ran it
and was able to see the drive and everything on it. It included a DOS
version of NTFSCheck, which I ran and it found some errors in the MBR
and corrected them.

Now it stopped BSODing, but still wouldn't boot up, but now I was
able to do an "upgrade" and repair everything.

Finally I am back up and my dad wont kill me

And now I can go to sleep.

Congrats, but next time[heaven forbid] try to be more helpful with your
explanation.
You made it really sound like it was the hard drive.
When you get some rest, can you share the name of the DOS utility you used
and other pertinent info. Was it NTFSdos from Wininternals? This is a peer
support newsgroup and we all learn from each other so share your experience
with the group.
--

Michael Stevens MS-MVP XP
(e-mail address removed)
http://michaelstevenstech.com
For a better newsgroup experience. Setup a newsreader.
http://michaelstevenstech.com/outlookexpressnewreader.htm