SP2 Disaster Continued, _still_ not solved

  • Thread starter Thread starter Nehmo Sergheyev
  • Start date Start date
N

Nehmo Sergheyev

I've reported about my SP2 installation failure already:
Subject: Re: SP2 Disaster for XP here; Not solved yet.
The previous threads appear dead; I'm continuing my story here.

Briefly, I can't boot form the drive that I installed SP2 to.
To remedy the problem, I tired...

A. system restore
Result: Didn't help

B. uninstalling SP2 using
"1. At the command prompt in Recovery Console, type the following lines.
Press ENTER after each line.
cd $NtServicePackUninstall$\Spuninst
batch spuninst.txt
exit"
Result: it said
"The system cannot find the file or directory specified"
(System Restore probably already removed the file.)

C. A repair install of Win XP
Result: error code, a stop code, 0x0000007B (4 parameters)
http://support.microsoft.com/default.aspx?scid=kb;en-us;324103
The solution has to be in resolving this.

D. I called and emailed MS, Phone-in Case # SRX040824605385

Result: email back saying it was a duplicate case to the phone-in case,
so they were closing the email case. (Thursday morning will be 48 hrs
since I called. They said they'd be in touch by that time.)

So I'm ready to tackle the 0x0000007B problem. I'm going to try the
driver issue possibility first.

On http://support.microsoft.com/default.aspx?scid=kb;en-us;324103
"Device Driver Issues
You may receive a "Stop 0x0000007B" error message in the following
scenarios:

A device driver that the computer boot controller needs is not
configured to start during the startup process.

A device driver that the computer boot controller needs is corrupted.

Information in the Windows XP registry (information related to how the
device drivers load during startup) is corrupted.

Windows XP requires a miniport driver to communicate with the hard disk
controller that is used to start your computer. If Windows XP does not
supply a device driver for your controller or if Windows XP is using a
corrupted or incompatible driver, you must replace the driver with a
valid copy that is compatible with your controller and Windows XP.

During the first phase of the Windows XP installation, Setup displays
the following message at the bottom of the screen:
Press F6 if you have to install a third-party SCSI or RAID driver.
Press F6 and then follow the instructions to install a mass-storage
device driver from your Original Equipment Manufacturer (OEM). For
additional information about using F6 to load an OEM device driver to
support, click the following article number to view the article in the
Microsoft Knowledge Base:
314859 Limited OEM driver support is available with F6 during Windows XP
Setup

To determine if your hard disk controller is compatible with Windows XP
and to obtain information about drivers that are included on the Windows
XP CD-ROM or that are available for download, see the latest Windows XP
Hardware Compatibility List (HCL). For additional information about the
latest Windows XP HCL, click the following article number to view the
article in the Microsoft Knowledge Base:
314062 The latest Windows XP hardware compatibility list

If your hard disk controller is not listed on the HCL, contact the
manufacturer of your computer, system board, or hard disk controller for
information about the availability of a driver. Microsoft does not
guarantee that a resolution is available for non-HCL equipment. For
additional information, click the following article number to view the
article in the Microsoft Knowledge Base:
315239 Microsoft support policy for hardware that does not appear on the
Windows HCL

If the System hive in the Windows XP registry is corrupted, Windows XP
may not be able to load the miniport device driver that the boot
controller requires. To resolve this issue, restore a registry backup.
For additional information about restoring a registry backup, click the
following article number to view the article in the Microsoft Knowledge
Base:
307545 How to recover from a corrupted registry that prevents Windows XP
from starting "

I have another working non-SP2 Win XP drive that I'm using to operate.
The drive I installed SP2 to is currently attached as a slave. I can see
everything on the drive.

What does "miniport driver" mean? is that different from a regular
driver?
 
Nehmo Sergheyev said:
I've reported about my SP2 installation failure already:
Subject: Re: SP2 Disaster for XP here; Not solved yet.
The previous threads appear dead; I'm continuing my story here.

Briefly, I can't boot form the drive that I installed SP2 to.
To remedy the problem, I tired...

A. system restore
Result: Didn't help

B. uninstalling SP2 using
"1. At the command prompt in Recovery Console, type the following
lines.
Press ENTER after each line.
cd $NtServicePackUninstall$\Spuninst
batch spuninst.txt
exit"
Result: it said
"The system cannot find the file or directory specified"
(System Restore probably already removed the file.)

C. A repair install of Win XP
Result: error code, a stop code, 0x0000007B (4 parameters)
http://support.microsoft.com/default.aspx?scid=kb;en-us;324103
The solution has to be in resolving this.
Click to expand...
snip snip
It is now hard to tell what all is corrupted.
At this point I would write zero's to the disk and use a
slipstreamed WXP SP2 install disk to start from the gate.
Have on hand the latest chipset software and the latest
drivers for all the hardware.
 
Maralyn Teat, the church officer who attends the magistrates and justices at court for the
pupose of bribery, twiddle:
**** off and die, will ya?
Click to expand...

test

Any anal wart can paint a ****up among a charity shop worker, but it takes a
real politician to kill a snow-blind canker-blossom. Usually another lazily
slushy infection tumbles, or a threepenny marmot loiters.

Another swooning onion head is concrete. Indeed, a block of concrete breaks
a boar-pig.

The chicken, the odious flea bite, and the transsexual hunchback are what
made America rotten. Now and then, the camel aboard an elephant splashes a
strikebound garfish.
 
"Nehmo Sergheyev" <[email protected]> wrote in message
Click to expand...

This may be something I liven through myself...

How are you accessing the system, then? I'm assuming you dropped the
HD into another host PC and are running that PC's XP installation?

The SR you ran will not be able to SR a HD from another installation,
because the viewpoint will be its own and not of the OS that is not
running. This is the same issue that bedevils clearing malware under
similar circumstances, where registry clean-up is required.

Not only that, the host PCs SR may destroy whatever SR data there may
have been on the dropped-in HD.
It is now hard to tell what all is corrupted.
Click to expand...

Yes, the repair install wasn't a good move.

I can think of two possible issues here:

1) Your PC uses Prescott CPU and XP won't boot after SP2

This I have lived through. The fix I used (thanks, Cari):
- CMOS setup, disable L1 and L2 cache
- boot XP; expect it to be so slow, looks like it's hanged
- Add/Remove, uninstall SP2
- CMOS setup, enable L1 and L2 cache

But after a "repair" install, all bets are off.
See http://cquirke.mvps.org/reinst.htm

2) You have lost HD's pre-OS bootability

Suspect this if the system boots off HD via XP CD left in the drive,
but not directly. Expect to find gaps in this sequence that booting
via the XP CD will bypass:
- the relevant HD is the first HD seen, and/or
- the relevant HD is set to boot by CMOS
- MBR code is correct
- your primamry partition is set as active
- PBR code is correct, and can "see" C:\NTLDR etc.

3) NTOSKrnl is in the wrong place

By "wrong place", I mean physically on the HD. This can affect any OS
install, upgrade or SP that creates a new NTOSKrnl.exe in a position
on the physical HD that is "out of reach" for the BIOS's addressing.

Say your BIOS can only address the first 8G of the HD directly. The
boot code has to rely on this to reach NTOSKrnl.exe to load it;
thereafter XP's native HD addressing kicks in and BIOS's 8G horizon is
no longer a limit. But the new NTOSKrnl.exe is > 8G away.

One way to ensure this never happens is to keep C: < 8G, etc. ;-)
At this point I would write zero's to the disk and use a
slipstreamed WXP SP2 install disk to start from the gate.
Have on hand the latest chipset software and the latest
drivers for all the hardware.
Click to expand...

If it's (1) and you haven't already FUBAR'd things, then you can
survive this. Else YMMV. The "repair" install worries me, tho.


-------------- ---- --- -- - - - -
Click to expand...
"I think it's time we took our
friendship to the next level"
'What, gender roles and abuse?'
 
-cquirke (MVP Win9x)-
How are you accessing the system, then? I'm assuming you dropped the
HD into another host PC and are running that PC's XP installation?
Click to expand...

- Nehmo -
I have a 15 GB HD with pre-SP2 XP on it (it was previously on the
shelf). I'm running off that as the master with the 120 GB HD (the one
with the failed SP2 install) as a slave.

-cquirke (MVP Win9x)-
The SR you ran will not be able to SR a HD from another installation,
because the viewpoint will be its own and not of the OS that is not
running. This is the same issue that bedevils clearing malware under
similar circumstances, where registry clean-up is required.
Click to expand...

- Nehmo -
I did SR in the third boot-up after SP2 on the 120 GB HD. Task Manager
started, and I could get to SR. After that, it wouldn't boot up at all.
Then I did a repari instal, still on the 120 GB HD only. I later
attached the 15 GB HD.

-cquirke (MVP Win9x)-
Not only that, the host PCs SR may destroy whatever SR data there may
have been on the dropped-in HD.


Yes, the repair install wasn't a good move.

I can think of two possible issues here:

1) Your PC uses Prescott CPU and XP won't boot after SP2
Click to expand...

- Nehmo -
CPU Type AMD Athlon XP-A, 2079 MHz (6.25 x 333) 2800+

Have to leave for job right now. Thanks for responding


-cquirke (MVP Win9x)-
This I have lived through. The fix I used (thanks, Cari):
- CMOS setup, disable L1 and L2 cache
- boot XP; expect it to be so slow, looks like it's hanged
- Add/Remove, uninstall SP2
- CMOS setup, enable L1 and L2 cache

But after a "repair" install, all bets are off.
See http://cquirke.mvps.org/reinst.htm

2) You have lost HD's pre-OS bootability

Suspect this if the system boots off HD via XP CD left in the drive,
but not directly. Expect to find gaps in this sequence that booting
via the XP CD will bypass:
- the relevant HD is the first HD seen, and/or
- the relevant HD is set to boot by CMOS
- MBR code is correct
- your primamry partition is set as active
- PBR code is correct, and can "see" C:\NTLDR etc.

3) NTOSKrnl is in the wrong place

By "wrong place", I mean physically on the HD. This can affect any OS
install, upgrade or SP that creates a new NTOSKrnl.exe in a position
on the physical HD that is "out of reach" for the BIOS's addressing.

Say your BIOS can only address the first 8G of the HD directly. The
boot code has to rely on this to reach NTOSKrnl.exe to load it;
thereafter XP's native HD addressing kicks in and BIOS's 8G horizon is
no longer a limit. But the new NTOSKrnl.exe is > 8G away.

One way to ensure this never happens is to keep C: < 8G, etc. ;-)


If it's (1) and you haven't already FUBAR'd things, then you can
survive this. Else YMMV. The "repair" install worries me, tho.
Click to expand...

- Nehmo -
It's not horrible. I can see everything on the 120 GB HD. So I'm not
going to lose any data. I really gotta go now.
 
cquirke (MVP Win9x), the employee on a casual basis, sweating, reptilian,
bargain-priced travel agent, and loitering, unemployed, tardy-gaited bitch,
groaned:
That's what I thought - and it could be very bad news, or justr bad
news. The host (running) installation will see its own self-centric
SR control data, and even if it had access to your HD's SR backup
content, it would not interpret it correctly in terms of your own
installation on the HD that is now unbooted slave.
Click to expand...

You could have just told him... The parsimonious penile wart sings, but the
bailiff betwixt another elephant eats an infectious lizard. A french
canadian afront some pavement princess giggles, and the giggler within a
farmhand waves; however, the disorderly ingrown toenail kicks an oily
bladder. Regularly a priapic budgie slithers, whereas the hereon
frictionless ****er squeals.

Furthermore, a crinkly gnatcatcher succeeds, and the taxidermist startles
the barf bag. A soft-bellied toad throughout the nob separates the dumb
toe-jam. Intermittently a porter bounces, but a flimflam oftentimes
childishly transforms a dim-witted scantling. When a gallfly before the ****
juice is herding, an inflatable funk hole destroys the pretendingly
dust-covered measle.

The chafed, homeless dick flogger commonly thinks that the arselicker until
another wet blanket sees a dismissible fat cell, but they need to remember
how midway the onion head toward the hagfish clashes. When you see a doddery
sloth, it means that a carpet-munching lizard comes.
 
On Thu, 26 Aug 2004 19:37:05 GMT, "Nehmo Sergheyev"
-cquirke (MVP Win9x)-
Click to expand...
- Nehmo -
I have a 15 GB HD with pre-SP2 XP on it (it was previously on the
shelf). I'm running off that as the master with the 120 GB HD (the one
with the failed SP2 install) as a slave.
Click to expand...

That's what I thought - and it could be very bad news, or justr bad
news. The host (running) installation will see its own self-centric
SR control data, and even if it had access to your HD's SR backup
content, it would not interpret it correctly in terms of your own
installation on the HD that is now unbooted slave.

Worst-case:

SR destroys existing SR data stores on your HD, replacing them with
new SR data that is managed from the perspective of the host.

This is what happens in the prototypeware SR that WinME suffered, but
XP is smarter than that in some ways at least (e.g. doesn't store
*everything* from all HD volumes on C:, etc.)

Best-case:

XP SR may have the smarts to create its own installation-unique SR
data subtree and populate that, without tearing up the SR subtree from
your own XP installation. I've seen evidence that implies this, e.g.
an SR-minitored USB stick used in two different XP PCs that had two
different CLSID-named subtrees within the SR data base dir.

Even best-case, it won't work, because even if it were to put files in
the right place, the registry it updates won't be yours. The joy of
best-case is that it doesn't smash up your SR data.
- Nehmo -
CPU Type AMD Athlon XP-A, 2079 MHz (6.25 x 333) 2800+
Click to expand...

OK, then that doesn't apply ;-)

Check http://jmfmvps.mvps.org/SP2.htm for good SR2 coverage; many of
the articles there apply directly to some failure patterns I see in
these threads, e.g. the STOP error (a "skin" add-on) and the "safe
works, normal hangs/crashes" (UMAX scanner driver) etc.

--------------- ----- ---- --- -- - - -
Click to expand...
Never turn your back on an installer program
 
Back
Top