STOP 0x0000007E after XP SP2 Security Fixes Applied

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

0xC0000005 0xFB040DB8 0xFBC668D0 0xFBC665CC
Working OK after SP2 upgrade, then applied all automatic updates, went on OK.
but after reboot get Stop code, can't boot to known good config (same
problem) and will not come up in any safe modes. Can only bring up WINDOWS
from XP/SP1 install disk....Totally stuck....don't want to re-install, but
can't think of any other way.....Then I will not allow security
updates...HELP PLEASE
 
glowworm said:
0xC0000005 0xFB040DB8 0xFBC668D0 0xFBC665CC
Working OK after SP2 upgrade, then applied all automatic updates, went on OK.
but after reboot get Stop code, can't boot to known good config (same
problem) and will not come up in any safe modes. Can only bring up WINDOWS
from XP/SP1 install disk....Totally stuck....don't want to re-install, but
can't think of any other way.....Then I will not allow security
updates...HELP PLEASE
Click to expand...

Then you need to start with recovery console and type the command chkdsk /r:
Description of the Windows XP Recovery Console
http://support.microsoft.com/kb/314058
How to install and use the Recovery Console in Windows XP
http://support.microsoft.com/kb/307654
How to Perform a Windows XP Repair Install:
http://michaelstevenstech.com/XPrepairinstall.htm

HTH.
nass
 
after reboot get Stop code
Click to expand...

What is this code? That code can be looked up and it may tell where (what
part of the system) the problem cropped up.

Updating involves changing system files. Changing system files sometimes
breaks drivers or startup programs. It's not always that simple but seems
worthwhile to check out instead of forgoing security updates.

This site:
http://www.aumha.org/a/stop.htm
Has a summary of the stop codes. Click the stop code in the left hand
column. Read a short summary about the usual causes. Then use the links on
that page to read relevant MS Knowledge Base articles.
 
STOP code 7E as per title,,,,tried CHKDSK ...removed a few bad sectors but
still w'ont boot anything...I'll try XP Repair Next...Bit bothered about
re-install since last time I used the XP CD on different m/c it said USED TOO
MANY TIMES ) or similiar)....but mone is cosha register m/c with this key at
MSN
 
STOP CODE 7E
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Does mean much to me...and doesn't help me solve the problem
 
Nass, I'm running a minimal level Laptop with SP2...3.8 GB Toshiba CDT just
meets XP SP2 Spec....might be that I've not enough disk space after doing the
installs..but chkdsk says 0.7 GB free which should be enough for pagefiles
etc. But these updates did grab a lot of my (not very much hard drive)..I've
deleted the larger KBxxxxxx.log files...anything else I can delete??? Don't
know how to get at other filenames other than WINDOWS and simple directory
names...like how do you do a CHANGE DIRECTORY (CD) to get Documents And
Settings from the Recovery Console Commands (MS DOS like)...Keith
 
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Does mean much to me...and doesn't help me solve the problem
Click to expand...

Did you check that web page that I referenced? The cause can be varied but
Event Viewer (if you can get to it) may add some info about which driver or
which process is erring. Remarkably, power management is mentioned often
but is not the only possibility.

I see in a response to nass I see that you're pushing the system
requirement limits to run XP SP2 and that you have very little free space
left on the disk. I've pushed the sys req limits on a Compaq laptop
without too much trouble so that doesn't concern me as much as the limited
free space. XP can get very quirky if there is less than 15% of total drive
space free.

Recovery console limits what directories you can access unless you set
something up ahead of time to get at other folders and files. It's too late
for that now in your case. You might try a third party boot CD such as
Bart's PE or Knoppix to move some files off the drive. Maybe with a little
extra space you can get things rolling again enough to look in Event Viewer
for specific causes or to perform a repair install.
 
Back
Top