Stop 7E indicates - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. We sould need to
look at the memory dump to investigate the root cause. In general based on
the windows debugging tools help you can follow the steps below to fix the
issue on your own.
If you are not equipped to debug this problem, you should use some basic
troubleshooting techniques.
Make sure you have enough disk space.
If a driver is identified in the bug check message, disable the driver or
check with the manufacturer for driver updates.
Try changing video adapters.
Check with your hardware vendor for any BIOS updates.
Disable BIOS memory options such as caching or shadowing.
If you plan to debug this problem, you might find it difficult to obtain a
stack trace. Parameter 2 (the exception address) should identify the driver
or function that caused this problem.
If exception code 0x80000003 occurs, a hard-coded breakpoint or assertion
was hit, but the system was started with the /NODEBUG switch. This problem
should rarely occur. If it occurs repeatedly, make sure that a kernel
debugger is connected and the system is started with the /DEBUG switch.
If exception code 0x80000002 occurs, the trap frame supplies additional
information.
If you do not know the specific cause of the exception, consider the
following issues:
Hardware incompatibility. Make sure that any new hardware that is installed
is listed in the Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service. A faulty device driver or system
service might be responsible for this error. Hardware issues, such as BIOS
incompatibilities, memory conflicts, and IRQ conflicts can also generate this
error.
If a driver is listed by name within the bug check message, disable or
remove that driver. Disable or remove any drivers or services that were
recently added. If the error occurs during the startup sequence and the
system partition is formatted with NTFS file system, you might be able to use
Safe Mode to rename or delete the faulty driver. If the driver is used as
part of the system startup process in Safe Mode, you must start the computer
by using the Recovery Console to access the file.
If the problem is associated with Win32k.sys, the source of the error might
be a third-party remote control program. If such software is installed, you
can remove the service by starting the computer by using the Recovery Console
and then deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that
might help identify the device or driver that is causing bug check 0x7E.
You can also disable memory caching of the BIOS might to try to resolve the
error. You should also run hardware diagnostics, especially the memory
scanner, that the system manufacturer supplies. For more information about
these procedures, see the owner's manual for your computer.
The error that generates this message can occur after the first restart
during Windows Setup, or after Setup is finished. A possible cause of the
error is lack of disk space for installation and system BIOS
incompatibilities. For problems during Windows installation that are
associated with lack of disk space, reduce the number of files on the target
hard disk drive. Check for and delete any temporary files that you do not
have to have, Internet cache files, application backup files, and .chk files
that contain saved file fragments from disk scans. You can also use another
hard disk drive with more free space for the installation. You can resolve
BIOS problems by upgrading the system BIOS version.
