winxp boots in safe mode with networking, but normal boot blue scr


U

unforgettable

winxp pro blue screen early in boot process doesn't report a filename, just
the numbers:
0x0000007e, and then some more in brackets like 0xc00006, 0x80ga37a9,
0xf7dc266e8, 0xf7d2634e4. Is there any way to step through the boot sequence
to find out exactly what is loading when the error happens? I seem to
remember there was an option like that for win98, so is it possible with
winxp?

I tried enabling boot logging, but it didn't create a log. Since it boots
fine in safe mode with networking, and I can browse the internet, it seems
like I should be able to fix this problem, without having to reinstall
windows, and spend the next month reinstalling and configuring all my
software.

This is an older hp desktop with amd Athlon2200+ cpu, 768mb ram.
Here is the history of the problems: Computer suddenly locked up and
wouldn't reboot. I suspected just a corrupt pagefile.sys, but deleting that
didn't help. I had a corrupt boot.ini, so I copied an old version. I booted
with ubcd, and restored an older copy of the registry, and after going back a
few days, it was able to boot in safe mode, but still wouldn't load normally.
I disabled reboot on errors, and found the blue screen actually was reporting
c0000218 unknown hard error. I tried using the repair function from the
windows cd, but it still wouldn't boot normally, and the install couldn't
complete in safe mode, so I restored the old registry again, to get back to
safe mode , and now I still had a blue screen, but the error had changed to
BAD_POOL_CALLER. Hoping that possibly bad files would be fixed by a service
pack, I downloaded the standalone service pack files. Reinstalled service
pack2, still blue screened on boot. Installed service pack 3 in safe mode,
reboot reports sp3 is installed, but I still have the blue screen. I have
tried using msconfig to try to boot with no system.ini, or boot.ini, but
still no luck. I also tried some of the other options, but sometimes lost my
safe mode booting, and had to boot from the ubcd and straighten it out again.
I ran some disc diags, and there was a corrupted tmp file, and maybe some
others, so I ran 3 different defrag programs, just to make sure my drive
could be written to okay. I suspect there are some other corrupt windows
system files, but how do I find out which files are bad? Is there anything
else I can try before I give up and reinstall everything?
 
Ad

Advertisements

J

John Wunderlich

=?Utf-8?B?dW5mb3JnZXR0YWJsZQ==?=
winxp pro blue screen early in boot process doesn't report a
filename, just the numbers:
0x0000007e, and then some more in brackets like 0xc00006,
0x80ga37a9, 0xf7dc266e8, 0xf7d2634e4. Is there any way to step
through the boot sequence to find out exactly what is loading when
the error happens? I seem to remember there was an option like
that for win98, so is it possible with winxp?

I tried enabling boot logging, but it didn't create a log. Since
it boots fine in safe mode with networking, and I can browse the
internet, it seems like I should be able to fix this problem,
without having to reinstall windows, and spend the next month
reinstalling and configuring all my software.

This is an older hp desktop with amd Athlon2200+ cpu, 768mb ram.
Here is the history of the problems: Computer suddenly locked up
and wouldn't reboot. I suspected just a corrupt pagefile.sys, but
deleting that didn't help. I had a corrupt boot.ini, so I copied
an old version. I booted with ubcd, and restored an older copy of
the registry, and after going back a few days, it was able to boot
in safe mode, but still wouldn't load normally. I disabled reboot
on errors, and found the blue screen actually was reporting
c0000218 unknown hard error. I tried using the repair function
from the windows cd, but it still wouldn't boot normally, and the
install couldn't complete in safe mode, so I restored the old
registry again, to get back to safe mode , and now I still had a
blue screen, but the error had changed to BAD_POOL_CALLER. Hoping
that possibly bad files would be fixed by a service pack, I
downloaded the standalone service pack files. Reinstalled service
pack2, still blue screened on boot. Installed service pack 3 in
safe mode, reboot reports sp3 is installed, but I still have the
blue screen. I have tried using msconfig to try to boot with no
system.ini, or boot.ini, but still no luck. I also tried some of
the other options, but sometimes lost my safe mode booting, and
had to boot from the ubcd and straighten it out again. I ran some
disc diags, and there was a corrupted tmp file, and maybe some
others, so I ran 3 different defrag programs, just to make sure my
drive could be written to okay. I suspect there are some other
corrupt windows system files, but how do I find out which files
are bad? Is there anything else I can try before I give up and
reinstall everything?

Try this:

"How to troubleshoot configuration errors by using the System
Configuration utility in Windows XP"

<http://support.microsoft.com/kb/310560>

HTH,
John
 
L

Leonard Grey

STOP 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
http://www.aumha.org/a/stop.php#0x7e

Excerpt:

"There are numerous individual causes for this problem, including
hardware incompatibility, a faulty device driver or system service, or
some software issues. Check Event Viewer [start > run > eventvwr.msc]
for additional information."
---
Leonard Grey
Errare Humanum Est

Security Tips for Everyone, from PC Magazine
http://www.pcmag.com/article2/0,2817,2334856,00.asp
 
U

unforgettable

Thanks for the hint. I used msconfig to select diagnostic startup, and it got
the exact same blue screen as the normal mode. That's strange, since safe
mode with networking is working every time. Any other ideas? How can I find
out exactly the difference in safe mode and normal mode. The error comes
quickly in the boot process, so it can't be very far down the line.
 
U

unforgettable

Oops, since I tried that diagnostic startup, now networking isn't working. I
went back in and selected normal startup, but it's worse now than before.
How'd that happen, and how do I get my network back? When I type ipconfig
/renew, it says the RPC server is unavailable.
 
Ad

Advertisements

J

John Wunderlich

=?Utf-8?B?dW5mb3JnZXR0YWJsZQ==?=
Oops, since I tried that diagnostic startup, now networking isn't
working. I went back in and selected normal startup, but it's
worse now than before. How'd that happen, and how do I get my
network back? When I type ipconfig /renew, it says the RPC server
is unavailable.

It sounds to me like a corrupted registry problem. When you said
that you restored the registry, I assume that you used "System
Restore" to do this? At this point, it seems that things are screwed
up enough that a re-install is warranted. In the long run it will
save you time and improve reliability. Back up your data and go for
it.

-- John
 
Ad

Advertisements


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top