STOP 7E on bootup/startup of Windows XP Home

[eljainc]

Hello,

I have a Windows XP Home box that had a STOP 7E message on the screen
when I came into work this morning. No new programs or hardware have
been added recently.

I ran a MEMCHECK test and let it run several passes: no errors
reported.

This machine is running WinXP SP2.

The error happens when booting up (during the graphical portion where
the green/yellow blip is going from left to right.

There are no drivers associated with the BSOD 7E error. I tried safe
mode and that also causes a BSOD. The last driver that is loaded/
shown on the screen is MUP.SYS

How can I fix this problem?

Thanks.
Mike McWhinney
elja, Inc.

 

[Gerry]

You can start here:
http://msdn2.microsoft.com/en-us/library/ms795746.aspx


--



Hope this helps.

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

 

[Ron Martell]

Hello,

I have a Windows XP Home box that had a STOP 7E message on the screen
when I came into work this morning. No new programs or hardware have
been added recently.

The primary suspects for a STOP 0x0000007E:
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED error are:
- incompatible hardware
- faulty device driver
- buggy application software.

There are 4 parameter values that are also reported with a STOP error,
and these parameters contain additional information that can be
extremely useful in diagnosing the cause of the error.

In the case of your specific error the second parameter value will be
the memory address at which the exception occurred. If it is at all
possible to get the machine running, even in Safe Mode, then it would
be possible to trace the specific device driver (assuming it is a
driver) that triggered the exception.

I ran a MEMCHECK test and let it run several passes: no errors
reported.

With memory testing it is often best to run the program for an
extended period, such as overnight.

This machine is running WinXP SP2.

The error happens when booting up (during the graphical portion where
the green/yellow blip is going from left to right.

There are no drivers associated with the BSOD 7E error. I tried safe
mode and that also causes a BSOD. The last driver that is loaded/
shown on the screen is MUP.SYS

That last driver name would be normal. If the machine cannot be
booted in Safe Mode or in "Last known good configuration" then your
next best option might be a repair install of Windows XP. However
before trying this it may be worthwhile to attempt to boot the machine
in a "stripped down" hardware configuration.

Unplug all accessories and periperherals, including printers,
scanners, webcam, external hard drives, other USB devices etc. If
the machine is using USB or wireless keyboard and/or mouse replace
these with standard PS/2 connected devices. If possible open the
computer case and remove any network cards, modems, scanner adapters
or other accessory cards that are not absolutely essential (the only
one that applies to should be the video card).

Now try booting the computer in both normal and safe modes and see
what happens. If the problems persist then try a "Repair Install" of
Windows XP as per the instructions at
http://michaelstevenstech.com/XPrepairinstall.html


Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."

 

[eljainc]

I got my machine back and running, after doing a repair install, then
reapplying SP2.

However, one of the more recent Microsoft hotfixes/patches has caused
this problem to resurface.
I am stuck again

I'm going to try to use recovery console to fix this problem,
restoring a recent SYSTEM/SAM/SECURITY from the
repair folder.

Mike