OK, this maybe a dumb question, but I have my existing HD with a current
install gone bad. So I installed another HD that has the same WinXP install
(same key) That HD is OK. I last had it in the PC 8 months ago, so I have
totally updated all updates, incl SP3 and NET.3. My question is, is there
away to use this good operating system, make a back up, maybe ASR, and try a
recovery on the bad HD?
I am thinking not. One other issue is the good HD runs on the C: Windows,
whereas the corrupted one runs on J: Windows. Dont recall why that got
assigned.

Or is there anyother options for restoring my other HD. I did not make a
backup, nor a ASR or diskette for this one. So that is not an option. Just
thinking about other options rather than a brand new XP install on the
corrupted HD.

Stu

Can you elaborate on "Gone Bad" ? - A solution would depend on what is
wrong with the J: instance of Windows. Personally, I wouldn't spend much
time trying to recover the bad XP using pieces of the working instance. I
would concentrate on getting the 8 months of personal data migrated from
the bad instance to the good one.

I'd also suggest you switch backup methods to volume imaging - Acronis
True Image.

"Stu Hagen" <(E-Mail Removed)> wrote in message
news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> OK, this maybe a dumb question, but I have my existing HD with a current
> install gone bad. So I installed another HD that has the same WinXP
> install
> (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> totally updated all updates, incl SP3 and NET.3. My question is, is there
> away to use this good operating system, make a back up, maybe ASR, and try
> a
> recovery on the bad HD?
> I am thinking not. One other issue is the good HD runs on the C: Windows,
> whereas the corrupted one runs on J: Windows. Dont recall why that got
> assigned.
>
> Or is there anyother options for restoring my other HD. I did not make a
> backup, nor a ASR or diskette for this one. So that is not an option. Just
> thinking about other options rather than a brand new XP install on the
> corrupted HD.
>
> Stu

Gone bad like it wont boot in any mode available. I clicked on that thing
that stops the rebooting to get the blue screen of death stating I have a
problem......

I have already moved 8 gigs of the bad drive for future migration.

Stu

(Just wondering if I could even get to a safe mode in the bad HD)

"R. McCarty" wrote:

> Can you elaborate on "Gone Bad" ? - A solution would depend on what is
> wrong with the J: instance of Windows. Personally, I wouldn't spend much
> time trying to recover the bad XP using pieces of the working instance. I
> would concentrate on getting the 8 months of personal data migrated from
> the bad instance to the good one.
>
> I'd also suggest you switch backup methods to volume imaging - Acronis
> True Image.
>
> "Stu Hagen" <(E-Mail Removed)> wrote in message
> news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> > OK, this maybe a dumb question, but I have my existing HD with a current
> > install gone bad. So I installed another HD that has the same WinXP
> > install
> > (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> > totally updated all updates, incl SP3 and NET.3. My question is, is there
> > away to use this good operating system, make a back up, maybe ASR, and try
> > a
> > recovery on the bad HD?
> > I am thinking not. One other issue is the good HD runs on the C: Windows,
> > whereas the corrupted one runs on J: Windows. Dont recall why that got
> > assigned.
> >
> > Or is there anyother options for restoring my other HD. I did not make a
> > backup, nor a ASR or diskette for this one. So that is not an option. Just
> > thinking about other options rather than a brand new XP install on the
> > corrupted HD.
> >
> > Stu
>
>
>

"Stu Hagen" wrote:

> Gone bad like it wont boot in any mode available. I clicked on that thing
> that stops the rebooting to get the blue screen of death stating I have a
> problem......
>
> I have already moved 8 gigs of the bad drive for future migration.
>
> Stu
>
> (Just wondering if I could even get to a safe mode in the bad HD)
>
> "R. McCarty" wrote:
>
> > Can you elaborate on "Gone Bad" ? - A solution would depend on what is
> > wrong with the J: instance of Windows. Personally, I wouldn't spend much
> > time trying to recover the bad XP using pieces of the working instance. I
> > would concentrate on getting the 8 months of personal data migrated from
> > the bad instance to the good one.
> >
> > I'd also suggest you switch backup methods to volume imaging - Acronis
> > True Image.
> >
> > "Stu Hagen" <(E-Mail Removed)> wrote in message
> > news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> > > OK, this maybe a dumb question, but I have my existing HD with a current
> > > install gone bad. So I installed another HD that has the same WinXP
> > > install
> > > (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> > > totally updated all updates, incl SP3 and NET.3. My question is, is there
> > > away to use this good operating system, make a back up, maybe ASR, and try
> > > a
> > > recovery on the bad HD?
> > > I am thinking not. One other issue is the good HD runs on the C: Windows,
> > > whereas the corrupted one runs on J: Windows. Dont recall why that got
> > > assigned.
> > >
> > > Or is there anyother options for restoring my other HD. I did not make a
> > > backup, nor a ASR or diskette for this one. So that is not an option. Just
> > > thinking about other options rather than a brand new XP install on the
> > > corrupted HD.
> > >
> > > Stu
> >
> >
> >
Why would you do a brand new install on the "corrupted" drive when you have
a good install on the other drive? I can see trying to recover the install of
the non booting drive if you have applications installed there that you can't
recreate on the "good" drive. Otherwise master the good drive and slave the
bad drive and copy the data from bad to good, then reformat the bad to erase
it, then use it to store the Acronis images that R. McCarty suggested. You
can put it in a USB enclosure for less than $20 and keep it separate from
your computer. If you must restore the "bad" drive to use it's applications;
repost the bluescreen error codes and message. Maybe someone here can help
with that. We can't if we don't know what the error is.

Well, the reason why I did a new HD 8 moths ago was to increase storage. The
old one was ony 20 gigs, and I was having issues with all the programs. The
new one is 300 gigs (they keep getting cheaper) So yes, I could use this
older smaller one and do some house cleaning. Yes I could eventually use the
corrupted one as a mass storae device (I have enclosures) But........it
surely doesnt hurt to see if there would be away to fix it without loosing 6
months of program installs. I can get those all back, NP, but I am looking
for possible time savings.

I will write down the error code and post tomorrow. Something about a Kernel
thing.

"Mark Adams" wrote:

>
>
> "Stu Hagen" wrote:
>
> > Gone bad like it wont boot in any mode available. I clicked on that thing
> > that stops the rebooting to get the blue screen of death stating I have a
> > problem......
> >
> > I have already moved 8 gigs of the bad drive for future migration.
> >
> > Stu
> >
> > (Just wondering if I could even get to a safe mode in the bad HD)
> >
> > "R. McCarty" wrote:
> >
> > > Can you elaborate on "Gone Bad" ? - A solution would depend on what is
> > > wrong with the J: instance of Windows. Personally, I wouldn't spend much
> > > time trying to recover the bad XP using pieces of the working instance. I
> > > would concentrate on getting the 8 months of personal data migrated from
> > > the bad instance to the good one.
> > >
> > > I'd also suggest you switch backup methods to volume imaging - Acronis
> > > True Image.
> > >
> > > "Stu Hagen" <(E-Mail Removed)> wrote in message
> > > news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> > > > OK, this maybe a dumb question, but I have my existing HD with a current
> > > > install gone bad. So I installed another HD that has the same WinXP
> > > > install
> > > > (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> > > > totally updated all updates, incl SP3 and NET.3. My question is, is there
> > > > away to use this good operating system, make a back up, maybe ASR, and try
> > > > a
> > > > recovery on the bad HD?
> > > > I am thinking not. One other issue is the good HD runs on the C: Windows,
> > > > whereas the corrupted one runs on J: Windows. Dont recall why that got
> > > > assigned.
> > > >
> > > > Or is there anyother options for restoring my other HD. I did not make a
> > > > backup, nor a ASR or diskette for this one. So that is not an option. Just
> > > > thinking about other options rather than a brand new XP install on the
> > > > corrupted HD.
> > > >
> > > > Stu
> > >
> > >
> > >
> Why would you do a brand new install on the "corrupted" drive when you have
> a good install on the other drive? I can see trying to recover the install of
> the non booting drive if you have applications installed there that you can't
> recreate on the "good" drive. Otherwise master the good drive and slave the
> bad drive and copy the data from bad to good, then reformat the bad to erase
> it, then use it to store the Acronis images that R. McCarty suggested. You
> can put it in a USB enclosure for less than $20 and keep it separate from
> your computer. If you must restore the "bad" drive to use it's applications;
> repost the bluescreen error codes and message. Maybe someone here can help
> with that. We can't if we don't know what the error is.

"Stu Hagen" wrote:

> Well, the reason why I did a new HD 8 moths ago was to increase storage. The
> old one was ony 20 gigs, and I was having issues with all the programs. The
> new one is 300 gigs (they keep getting cheaper) So yes, I could use this
> older smaller one and do some house cleaning. Yes I could eventually use the
> corrupted one as a mass storae device (I have enclosures) But........it
> surely doesnt hurt to see if there would be away to fix it without loosing 6
> months of program installs. I can get those all back, NP, but I am looking
> for possible time savings.
>
> I will write down the error code and post tomorrow. Something about a Kernel
> thing.

If you were having "issues" with the installed programs, it might be because
of all the viruses, spyware, and other malware on it. ;-) Maybe that's why it
doesn't boot. If you decide to slave it, make sure you scan it with AV,
spyware and malware apps. Check out elephantboycomputers.com for suggestions.
>
> "Mark Adams" wrote:
>
> >
> >
> > "Stu Hagen" wrote:
> >
> > > Gone bad like it wont boot in any mode available. I clicked on that thing
> > > that stops the rebooting to get the blue screen of death stating I have a
> > > problem......
> > >
> > > I have already moved 8 gigs of the bad drive for future migration.
> > >
> > > Stu
> > >
> > > (Just wondering if I could even get to a safe mode in the bad HD)
> > >
> > > "R. McCarty" wrote:
> > >
> > > > Can you elaborate on "Gone Bad" ? - A solution would depend on what is
> > > > wrong with the J: instance of Windows. Personally, I wouldn't spend much
> > > > time trying to recover the bad XP using pieces of the working instance. I
> > > > would concentrate on getting the 8 months of personal data migrated from
> > > > the bad instance to the good one.
> > > >
> > > > I'd also suggest you switch backup methods to volume imaging - Acronis
> > > > True Image.
> > > >
> > > > "Stu Hagen" <(E-Mail Removed)> wrote in message
> > > > news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> > > > > OK, this maybe a dumb question, but I have my existing HD with a current
> > > > > install gone bad. So I installed another HD that has the same WinXP
> > > > > install
> > > > > (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> > > > > totally updated all updates, incl SP3 and NET.3. My question is, is there
> > > > > away to use this good operating system, make a back up, maybe ASR, and try
> > > > > a
> > > > > recovery on the bad HD?
> > > > > I am thinking not. One other issue is the good HD runs on the C: Windows,
> > > > > whereas the corrupted one runs on J: Windows. Dont recall why that got
> > > > > assigned.
> > > > >
> > > > > Or is there anyother options for restoring my other HD. I did not make a
> > > > > backup, nor a ASR or diskette for this one. So that is not an option. Just
> > > > > thinking about other options rather than a brand new XP install on the
> > > > > corrupted HD.
> > > > >
> > > > > Stu
> > > >
> > > >
> > > >
> > Why would you do a brand new install on the "corrupted" drive when you have
> > a good install on the other drive? I can see trying to recover the install of
> > the non booting drive if you have applications installed there that you can't
> > recreate on the "good" drive. Otherwise master the good drive and slave the
> > bad drive and copy the data from bad to good, then reformat the bad to erase
> > it, then use it to store the Acronis images that R. McCarty suggested. You
> > can put it in a USB enclosure for less than $20 and keep it separate from
> > your computer. If you must restore the "bad" drive to use it's applications;
> > repost the bluescreen error codes and message. Maybe someone here can help
> > with that. We can't if we don't know what the error is.

No..It probably isnt bad programs.....I had been using PareLogic Driver Cure
to keep drivers up to date, and when I did a driver update..it crashed. Dont
think I will ever use this software anymore~!

Stu

"Mark Adams" wrote:

>
>
> "Stu Hagen" wrote:
>
> > Well, the reason why I did a new HD 8 moths ago was to increase storage. The
> > old one was ony 20 gigs, and I was having issues with all the programs. The
> > new one is 300 gigs (they keep getting cheaper) So yes, I could use this
> > older smaller one and do some house cleaning. Yes I could eventually use the
> > corrupted one as a mass storae device (I have enclosures) But........it
> > surely doesnt hurt to see if there would be away to fix it without loosing 6
> > months of program installs. I can get those all back, NP, but I am looking
> > for possible time savings.
> >
> > I will write down the error code and post tomorrow. Something about a Kernel
> > thing.
>
> If you were having "issues" with the installed programs, it might be because
> of all the viruses, spyware, and other malware on it. ;-) Maybe that's why it
> doesn't boot. If you decide to slave it, make sure you scan it with AV,
> spyware and malware apps. Check out elephantboycomputers.com for suggestions.
> >
> > "Mark Adams" wrote:
> >
> > >
> > >
> > > "Stu Hagen" wrote:
> > >
> > > > Gone bad like it wont boot in any mode available. I clicked on that thing
> > > > that stops the rebooting to get the blue screen of death stating I have a
> > > > problem......
> > > >
> > > > I have already moved 8 gigs of the bad drive for future migration.
> > > >
> > > > Stu
> > > >
> > > > (Just wondering if I could even get to a safe mode in the bad HD)
> > > >
> > > > "R. McCarty" wrote:
> > > >
> > > > > Can you elaborate on "Gone Bad" ? - A solution would depend on what is
> > > > > wrong with the J: instance of Windows. Personally, I wouldn't spend much
> > > > > time trying to recover the bad XP using pieces of the working instance. I
> > > > > would concentrate on getting the 8 months of personal data migrated from
> > > > > the bad instance to the good one.
> > > > >
> > > > > I'd also suggest you switch backup methods to volume imaging - Acronis
> > > > > True Image.
> > > > >
> > > > > "Stu Hagen" <(E-Mail Removed)> wrote in message
> > > > > news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> > > > > > OK, this maybe a dumb question, but I have my existing HD with a current
> > > > > > install gone bad. So I installed another HD that has the same WinXP
> > > > > > install
> > > > > > (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> > > > > > totally updated all updates, incl SP3 and NET.3. My question is, is there
> > > > > > away to use this good operating system, make a back up, maybe ASR, and try
> > > > > > a
> > > > > > recovery on the bad HD?
> > > > > > I am thinking not. One other issue is the good HD runs on the C: Windows,
> > > > > > whereas the corrupted one runs on J: Windows. Dont recall why that got
> > > > > > assigned.
> > > > > >
> > > > > > Or is there anyother options for restoring my other HD. I did not make a
> > > > > > backup, nor a ASR or diskette for this one. So that is not an option. Just
> > > > > > thinking about other options rather than a brand new XP install on the
> > > > > > corrupted HD.
> > > > > >
> > > > > > Stu
> > > > >
> > > > >
> > > > >
> > > Why would you do a brand new install on the "corrupted" drive when you have
> > > a good install on the other drive? I can see trying to recover the install of
> > > the non booting drive if you have applications installed there that you can't
> > > recreate on the "good" drive. Otherwise master the good drive and slave the
> > > bad drive and copy the data from bad to good, then reformat the bad to erase
> > > it, then use it to store the Acronis images that R. McCarty suggested. You
> > > can put it in a USB enclosure for less than $20 and keep it separate from
> > > your computer. If you must restore the "bad" drive to use it's applications;
> > > repost the bluescreen error codes and message. Maybe someone here can help
> > > with that. We can't if we don't know what the error is.

Here is the Error code from Blue screen.

STOP: 0X0000007B (0XF7C4D528, 0XC0000034,00X00000000, 0X00000000)


Stu

"Mark Adams" wrote:

>
>
> "Stu Hagen" wrote:
>
> > Gone bad like it wont boot in any mode available. I clicked on that thing
> > that stops the rebooting to get the blue screen of death stating I have a
> > problem......
> >
> > I have already moved 8 gigs of the bad drive for future migration.
> >
> > Stu
> >
> > (Just wondering if I could even get to a safe mode in the bad HD)
> >
> > "R. McCarty" wrote:
> >
> > > Can you elaborate on "Gone Bad" ? - A solution would depend on what is
> > > wrong with the J: instance of Windows. Personally, I wouldn't spend much
> > > time trying to recover the bad XP using pieces of the working instance. I
> > > would concentrate on getting the 8 months of personal data migrated from
> > > the bad instance to the good one.
> > >
> > > I'd also suggest you switch backup methods to volume imaging - Acronis
> > > True Image.
> > >
> > > "Stu Hagen" <(E-Mail Removed)> wrote in message
> > > news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> > > > OK, this maybe a dumb question, but I have my existing HD with a current
> > > > install gone bad. So I installed another HD that has the same WinXP
> > > > install
> > > > (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> > > > totally updated all updates, incl SP3 and NET.3. My question is, is there
> > > > away to use this good operating system, make a back up, maybe ASR, and try
> > > > a
> > > > recovery on the bad HD?
> > > > I am thinking not. One other issue is the good HD runs on the C: Windows,
> > > > whereas the corrupted one runs on J: Windows. Dont recall why that got
> > > > assigned.
> > > >
> > > > Or is there anyother options for restoring my other HD. I did not make a
> > > > backup, nor a ASR or diskette for this one. So that is not an option. Just
> > > > thinking about other options rather than a brand new XP install on the
> > > > corrupted HD.
> > > >
> > > > Stu
> > >
> > >
> > >
> Why would you do a brand new install on the "corrupted" drive when you have
> a good install on the other drive? I can see trying to recover the install of
> the non booting drive if you have applications installed there that you can't
> recreate on the "good" drive. Otherwise master the good drive and slave the
> bad drive and copy the data from bad to good, then reformat the bad to erase
> it, then use it to store the Acronis images that R. McCarty suggested. You
> can put it in a USB enclosure for less than $20 and keep it separate from
> your computer. If you must restore the "bad" drive to use it's applications;
> repost the bluescreen error codes and message. Maybe someone here can help
> with that. We can't if we don't know what the error is.

"Stu Hagen" wrote:

> Here is the Error code from Blue screen.
>
> STOP: 0X0000007B (0XF7C4D528, 0XC0000034,00X00000000, 0X00000000)
>
>
> Stu

Check out the following article from the microsoft Knowledge Base
http://support.microsoft.com/kb/324103
I think you should cut your losses and reformat the drive and use it for
storage like I suggested before.
>
> "Mark Adams" wrote:
>
> >
> >
> > "Stu Hagen" wrote:
> >
> > > Gone bad like it wont boot in any mode available. I clicked on that thing
> > > that stops the rebooting to get the blue screen of death stating I have a
> > > problem......
> > >
> > > I have already moved 8 gigs of the bad drive for future migration.
> > >
> > > Stu
> > >
> > > (Just wondering if I could even get to a safe mode in the bad HD)
> > >
> > > "R. McCarty" wrote:
> > >
> > > > Can you elaborate on "Gone Bad" ? - A solution would depend on what is
> > > > wrong with the J: instance of Windows. Personally, I wouldn't spend much
> > > > time trying to recover the bad XP using pieces of the working instance. I
> > > > would concentrate on getting the 8 months of personal data migrated from
> > > > the bad instance to the good one.
> > > >
> > > > I'd also suggest you switch backup methods to volume imaging - Acronis
> > > > True Image.
> > > >
> > > > "Stu Hagen" <(E-Mail Removed)> wrote in message
> > > > news:9B562300-D9A2-424A-B6B6-(E-Mail Removed)...
> > > > > OK, this maybe a dumb question, but I have my existing HD with a current
> > > > > install gone bad. So I installed another HD that has the same WinXP
> > > > > install
> > > > > (same key) That HD is OK. I last had it in the PC 8 months ago, so I have
> > > > > totally updated all updates, incl SP3 and NET.3. My question is, is there
> > > > > away to use this good operating system, make a back up, maybe ASR, and try
> > > > > a
> > > > > recovery on the bad HD?
> > > > > I am thinking not. One other issue is the good HD runs on the C: Windows,
> > > > > whereas the corrupted one runs on J: Windows. Dont recall why that got
> > > > > assigned.
> > > > >
> > > > > Or is there anyother options for restoring my other HD. I did not make a
> > > > > backup, nor a ASR or diskette for this one. So that is not an option. Just
> > > > > thinking about other options rather than a brand new XP install on the
> > > > > corrupted HD.
> > > > >
> > > > > Stu
> > > >
> > > >
> > > >
> > Why would you do a brand new install on the "corrupted" drive when you have
> > a good install on the other drive? I can see trying to recover the install of
> > the non booting drive if you have applications installed there that you can't
> > recreate on the "good" drive. Otherwise master the good drive and slave the
> > bad drive and copy the data from bad to good, then reformat the bad to erase
> > it, then use it to store the Acronis images that R. McCarty suggested. You
> > can put it in a USB enclosure for less than $20 and keep it separate from
> > your computer. If you must restore the "bad" drive to use it's applications;
> > repost the bluescreen error codes and message. Maybe someone here can help
> > with that. We can't if we don't know what the error is.

Stu Hagen wrote:
> Here is the Error code from Blue screen.
>
> STOP: 0X0000007B (0XF7C4D528, 0XC0000034,00X00000000, 0X00000000)
>
>
> Stu
>

You are (probably) missing drivers for the chip-set in use.

See:
http://support.microsoft.com/kb/314082