SP2 Disaster Continued

  • 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.

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. I
can attach, as a slave, the problem drive and see everything.

What does "miniport driver" mean? is that different from a regular
driver?
 
Nehmo,

I installed SP2 on my Windows XP Pro Media Center system without any
problems. After the install and restart, SP2 goes through a configuration
phase. You have an opportunity to turn on the new firewall and make a few
other choices. If you did not turn off your anti-virus and Zone Alarm
before starting the SP2 install, this may have caused your problem.

If it were me, I think I would connect the 120Gb drive as a slave, and back
up any data needed to CD or DVD. Then I would clone the working XP boot
drive onto the 120Gb drive using Ghost. After doing this you should be able
to boot from the 120gb drive. If that doesn't work, the boot sector on the
drive could be damaged or unuseable.
 
I'm wondering if you haven't coincidentally suffered some unrelated HW
failure. The best way to check that possibility is to start with a clean HD
and do a clean XP install.
 
Hello
I too sufferd a fate as yours upgrading a friends pc.
It all being caused from some spyware that was not fully removed from the
system' Befor installing sp2.
7 other systems I had no problems with.
Put other drive as slave gather as much as you can and reformat.
Sorry I couldent be of more help.
Old Hippy
 
Nehmo 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.

I obviously did something wrong too.

I made a full image backup, installed SP2, installed a NOD32 beta update to
get it recognized by the Security Center, and now everything is working
perfectly.

Bummer!
 
- lgadbois -
If it were me, I think I would connect the 120Gb drive as a slave, and back
up any data needed to CD or DVD.

- Nehmo -
I only have a floppy drive, a CD reader, a 15 GB HD, a 120 GB HD (these
just described; the 120 is now connected as a slave to the 15 master),
and I also have an 80 GB HD (not currently attached). So I suppose, I
could copy the important stuff from the 120 to the 80. - This is getting
to be a mess with the files. Actually, before this SP2 incident, I
wasn't through copping stuff _from_ the 80!

- lgadbois -
Then I would clone the working XP boot
drive onto the 120Gb drive using Ghost. After doing this you should be able
to boot from the 120gb drive.

- Nehmo -
Okay, then I would be able to boot from the 120 GB, but then what? The
working 15 GB, which I would be coppying from, doesn't have SP2
installed. I'd like to be able to install SP2 on my 120, but the same
thing probably will happen. I'll kill the boot-ability of the 120 drive
again. I need to find out what went wrong. It's probably just one little
thing somewhere.

- lgadbois -
If that doesn't work, the boot sector on the
drive could be damaged or unuseable.

- Nehmo -
The 120 is a new drive, and I ran SCNDSK, finding nothing wrong. But if
it is bad, I could make the 80 a boot drive and live with that. The 120
is under warantee.

MS said they would call within 48 hours of my phone-in incident report.
Thats going to be up tomorrow morning. They must have seen similar
events.
 
Back
Top