Stop: 0x0000007E

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/windows-7-64-blue-screen-stop-error-0x00000050/acee635c-990e-4553-a158-4442e51a4aa1
There are two different Bug_Checks 50 (2) and 7E. The CAUSE of the 7E was ndis.sys which is a
Windows component meaning something else drove it into Fault. The CAUSE of the 50 was MEMORY
CORRUPTION so check the MEMORY carefully
1. Be sure to update the BIOS and low level chipset drivers
2. Check for updated drives to the network drivers (NIC and WiFi) and ASUStek if on-board and
with their device makers if separate devices (tcpip.sys was implicated in the 7E).
3. Check the memory carefully using the methods in the troubleshooter above.
4. Update all the major drivers and run driver verifier if needed afterward if the BSOD continues.
Driver Verifier can help find some BSOD issues :
Using Driver Verifier to identify issues with Windows drivers for advanced users
http://support.microsoft.com/kb/244617
How To Troubleshoot Driver Problems in Windows Vista or 7.
http://www.winvistaclub.com/t79.html
Using Driver Verifier
http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx
How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM
Driver Verifier
http://www.techsupportforum.com/2110308-post3.html
Using Driver Verifier
http://www.faultwire.com/solutions/using_driver_verifier.php
How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver Issueshttp://www.youtube.com/watch?v=_VwIDD9xngM
You can disable Driver Verifier
http://support.microsoft.com/kb/244617
Start - type in Search box -> verifier /reset      hit enter to disable
--------------------------------
5. Check the methods in the previous troubleshooter and the Faultwire links.
==================
Check these KB articles :
"Stop 0x0000007E" or "Stop 0x00000050" Stop error message in Windows 7 or Windows Server
2008 R2
http://support.microsoft.com/kb/979538
"Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" error when the GPU is under
heavy load conditions in Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/983615
---------------------------------------------------------------------------------------------

---------------------------------------------------------------------------------------------
References to Vista also apply to Windows 7.
This error is usually a driver issue and display adapter (video) driver is the most suspect though it
could be others. Antivirus/antispyware/security programs, hardware (heat) and major software issues
can also cause the error. When you get to the driver section of the troubleshooter use my generic
methods in the next message and then return to the troubleshooter if needed.
Have you added hardware recently or updated drivers? Be sure to look in Control Panel - Windows
Updates to see if any drivers were updated there. Other lessor possibilities include antivirus/anti-
spyware/security programs.
When you get to the driver and memory sections of the troubleshooter refer to the previous messages
to update drivers and test memory and then refer back to the troubleshooter if needed.
BCCode: 7E      0x0000007E  which is also 0x1000007E
Cause
The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED bug check is a very common bug check. To
interpret it, you must identify which exception was generated.
Common exception codes include the following:

• 0xC0000096: no information.

For a complete list of exception codes, see the Ntstatus.h file that is located in theinc directory of
the Microsoft Windows Driver Kit (WDK).
Resolving the Problem
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.chkfiles 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.
BCCode: 7E    0x00000007E  which is also 0x1000007E <-- link="" read="" strong="" this="">
http://www.faultwire.com/solutions-fatal_error/SYSTEM-THREAD-EXCEPTION-NOT-HANDLED-0x0000007E-*1141.html?order=votes