Re: BSOD
- From: "John Toner [MVP]" <jtoner@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 9 Apr 2007 17:17:28 -0400
Bug Check 0x8E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
The KERNEL_MODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000008E.
This indicates that a kernel-mode program generated an exception which the
error handler did not catch.
Parameters
The following parameters are displayed on the blue screen.
Parameter Description
1 The exception code that was not handled
2 The address at which the exception occurred
3 The trap frame
4 Reserved
Cause
This is a very common bug check. To interpret it, you must identify which
exception was generated.
Common exception codes include:
a.. 0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.
b.. 0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was
attached to the system.
c.. 0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.
For a complete list of exception codes, see the ntstatus.h file located in
the inc directory of the Windows Driver Kit.
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 may find it difficult to obtain a
stack trace. Parameter 2 (the exception address) should pinpoint the driver
or function that caused this problem.
If exception code 0x80000003 occurs, this indicates that 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 a kernel debugger is connected and the system is started with the
/DEBUG switch.
If exception code 0x80000002 occurs, the trap frame will supply additional
information.
If the specific cause of the exception is unknown, the following should be
considered:
Hardware incompatibility. First, make sure that any new hardware installed
is listed in the Microsoft Windows Marketplace Tested Products List.
Faulty device driver or system service. In addition, 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 need to 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, the
service can be removed by starting the system using the Recovery Console and
deleting the offending system service file.
Check the System Log in Event Viewer for additional error messages that
might help pinpoint the device or driver that is causing bug check 0x1E.
Disabling memory caching of the BIOS might also resolve the error. You
should also run hardware diagnostics, especially the memory scanner,
supplied by the system manufacturer. For details on 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. Check for and delete any unneeded temporary files, Internet cache
files, application backup files, and .chk files containing saved file
fragments from disk scans. You can also use another hard disk with more free
space for the installation. BIOS problems can be resolved by upgrading the
system BIOS version.
Regards,
John
<kcheng911@xxxxxxxxx> wrote in message
news:1176148873.041752.106240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
My boss' laptop runs XP SP2 and recently has been randomly giving him
the BSOD with the following error message:
0x0000008E (0xc0000005, 0xb4cbb302, 0xa44979a4, 0x00000000)
Tcpipbm.sys address base at b4cb8000,
Date Stamp 43f61fd2
Any idea? I've googled this error message left and right, inside and
out but found nothing.
Any help would be greatly appreciated.
Thanks
Kit
.
- References:
- BSOD
- From: kcheng911
- BSOD
- Prev by Date: Re: Diskpar
- Next by Date: 0x80070569: Logon failure: the user has not been granted the requested logon type at this computer.
- Previous by thread: BSOD
- Next by thread: NTBackup not always starting
- Index(es):
Relevant Pages
|
