This error (7E) 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.
The other error (24) add the possibility of disk errors so be sure to 1st run SFC and CheckDisk as
indicated below. Once that is cleared then hopefully all you have to deal with is the 7E problem.
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 next message to
update drivers and test memory and then refer back to the troubleshooter if needed.
BCCode: 7E 0x0000007E
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:
0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
For a complete list of exception codes, see the Ntstatus.h file that is located in the inc 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.
This error (7E) 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.
The other error (24) add the possibility of disk errors so be sure to 1st run SFC and CheckDisk as
indicated below. Once that is cleared then hopefully all you have to deal with is the 7E problem.
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 next message to
update drivers and test memory and then refer back to the troubleshooter if needed.
BCCode: 7E 0x0000007E
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:
0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation occurred.
For a complete list of exception codes, see the Ntstatus.h file that is located in the inc 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.
การแปล กรุณารอสักครู่..
