Windows XP SP3 appears to break my PC (stop code 0x0000007B)

  • Thread starter Thread starter RedDouyglas
  • Start date Start date
R

RedDouyglas

Hi all,

Yesterday I installed XP SP3 onto my PC - which has been fairly stable and
reliable over the years. However, when the computer restarted, it failed to
boot with a 0x0000007B stop code. It would do the same whichever mode I tried
to boot it into - including safe mode. Great.

Luckily, I'm very computer literate (I'm an Operating Systems Principal
Engineer), so I was able to revcover from the situation.

I booted from my original XP CD, and used the recovery console to uninstall
SP3 (as per MS KB article) - running the batch spuninst.txt command and then
the registry hack on the RpcSs field. This got my computer booting again.

So to sumnarize:

1. I had a working computer.

2. I installed SP3 and it would not boot.

3. I uninstalled SP3 and it would boot again.

So clearly there is something about SP3 that does not work with my computer.

What?

How can I diagnose this problem?

How can I fix it?

Also, I notice that now I've uninstall SP3, my list of software in Add
Remove Software still has SP3 in it. I've tried REMOVE from there, but that
fails and the entry for SP3 remains. Automatic Updates is offering to install
updates that I apparently already have, and it's offering to install updates
for SP3, which I thought I uninstalled.

What a mess!

How can I get my computer into a nice tidy state once more?
(I have a feeling that's actually impossible!)

Thanks
 
Sorry, but none of these apply.

Only when I installed SP3 did I see this problem. When I uninstalled it the
PC booted fine.

The hard disk is not broken. It works fine. It isn't a virus either. I'm
behind a firewall, and I run anti-virus software. It's clean. I haven't
changed the motherboard or any other hardware. It all works fine without SP3.

I'd already read all of the articles to which you refer and none of them
seem to apply to my case. None of them mention this problem occuring when you
install SP3.

Red
 
RedDouyglas said:
Hi all,

Yesterday I installed XP SP3 onto my PC - which has been fairly
stable and reliable over the years. However, when the computer
restarted, it failed to boot with a 0x0000007B stop code. It would do
the same whichever mode I tried to boot it into - including safe
mode. Great.

Luckily, I'm very computer literate (I'm an Operating Systems
Principal Engineer), so I was able to revcover from the situation.

I booted from my original XP CD, and used the recovery console to
uninstall SP3 (as per MS KB article) - running the batch spuninst.txt
command and then the registry hack on the RpcSs field. This got my
computer booting again.

So to sumnarize:

1. I had a working computer.

2. I installed SP3 and it would not boot.

3. I uninstalled SP3 and it would boot again.

So clearly there is something about SP3 that does not work with my
computer.

What?

How can I diagnose this problem?

How can I fix it?

Also, I notice that now I've uninstall SP3, my list of software in Add
Remove Software still has SP3 in it. I've tried REMOVE from there,
but that fails and the entry for SP3 remains. Automatic Updates is
offering to install updates that I apparently already have, and it's
offering to install updates for SP3, which I thought I uninstalled.

What a mess!

How can I get my computer into a nice tidy state once more?
(I have a feeling that's actually impossible!)
Click to expand...

Might there be a typo?

If this is what you get:
Error 0x0000007E

See:

http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&dlc=en&cc=us&docname=c01457284
 
Red

With respect the items posted do apply! However, diagnosing Stop Errors
is often far from simple and you have to start somewhere. What Peter
provided is a logical starting point. Heres another:
Advanced troubleshooting for "Stop 0x0000007B" errors in Windows XP
http://support.microsoft.com/kb/324103/en-us

You have have not provided the comlete bug check code with the four
parameters. This would help. You will find the details in a copy in
Event Viewer.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the meaning
of the error, information regarding Event ID, Source and Description
are important.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

Have you located and examined the dump report?

--


Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
No they do not.

My computer does not have a virus. The hardware isn't broken. The boot
sector isn't corrupted. I haven't changed the motherboard. I don't rely on
OEM drivers to boot . I've got the hardware I've got, and before SP3 it
worked for nearly ten years, and it still works without SP3. It doesn't
matter to me whether I'm in the MS HCL or not, because I've got my hardware,
and that's that. I don't care about F6. I don't have a second computer to run
a debugger on. I don't have a boot partition that was created on NT 4.0. The
suggestion of repartitioning and formatting is ridiculous. The disk drive is
fine. I know how to cut and paste.

Basically, the articles referred to are nothing more than "pissing in the
wind" (Microsoft call it Troubleshooting) - a set of articles that may or may
not account for some 0x7B stop codes, but nowhere near all. They do not show
you how to diagnose a specific crash, they just give you things to "try".
That's not diagnosis, it's experimentation, and often it can do you more harm
than good.

Can you imagine a non-computer person doing all this?

Red
 
Red

Why do you ask for help if you know all the answers?


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Hi all,

Yesterday I installed XP SP3 onto my PC - which has been fairly stable and
reliable over the years. However, when the computer restarted, it failed to
boot with a 0x0000007B stop code. It would do the same whichever mode I tried
to boot it into - including safe mode. Great.

Luckily, I'm very computer literate (I'm an Operating Systems Principal
Engineer), so I was able to revcover from the situation.

I booted from my original XP CD, and used the recovery console to uninstall
SP3 (as per MS KB article) - running the batch spuninst.txt command and then
the registry hack on the RpcSs field. This got my computer booting again.

So to sumnarize:

1. I had a working computer.

2. I installed SP3 and it would not boot.

3. I uninstalled SP3 and it would boot again.

So clearly there is something about SP3 that does not work with my computer.

What?

How can I diagnose this problem?

How can I fix it?

Also, I notice that now I've uninstall SP3, my list of software in Add
Remove Software still has SP3 in it. I've tried REMOVE from there, but that
fails and the entry for SP3 remains. Automatic Updates is offering to install
updates that I apparently already have, and it's offering to install updates
for SP3, which I thought I uninstalled.

What a mess!

How can I get my computer into a nice tidy state once more?
(I have a feeling that's actually impossible!)

Thanks
Click to expand...

http://support.microsoft.com/kb/324103
 
I was asking for help because I've read all of the KB articles and none of
them apply. I was hoping that there would be a kernel expert who could save
me a little bit of time by explaining how to debug a specific 0x7B crash.

No problem that nobody does, I'm quite happy to learn myself, I've got
plenty of experience in this field. In fact I fixed the problem last night,
and my PC is now running SP3 quite happily.

My hard drive and all it's data are absolutely fine. Good job I didn't "try
repartitioning and reformatting your hard drive" as one of the KB articles
suggested eh?

Thanks,

Red
 
In case someone else has the same exact issue, it would be helpful if
you would tell us what you specifically did to fix your problem.
 
Then make a complete backup to the external hard drive and keep it in a safe
place. :)

"RedDouyglas"
 
Back
Top