Parameters
The following parameters are displayed on the blue screen.
Parameter Description
1 The exception code that was not handled 0xc0000005
2 The address at which the exception occurred 0xf7163ab0
3 Parameter 0 of the exception 0x00000000
4 Parameter 1 of the exception 0x00000000
Cause
This is a very common bug check. To interpret it, you must identify which
exception was generated.
Common exception codes include:
0x80000002: STATUS_DATATYPE_MISALIGNMENT
An unaligned data reference was encountered.
0x80000003: STATUS_BREAKPOINT
A breakpoint or ASSERT was encountered when no kernel debugger was attached
to the system.
0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred. (Parameter 4 of the bug check is the
address that the driver attempted to access.)
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 on the Microsoft Windows Hardware Compatibility List (HCL).
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 a system BIOS incompatibility. BIOS problems can be resolved by
upgrading the system BIOS version.
On the bluescreen it should have faulted a driver and told you which driver
or file was to blame for the exception. If you captured a memory.dmp file
from the crash you can debug it. Go here:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx download a
copy of windbg and once you have your symbols in place I would run a
"!analyze -v" without qoutes and see what it says it thinks is the faulting
module. You could also run sigverif.exe and then review the sigverif.txt to
check for old and/or out of date drivers and update them as needed.
Good Luck!
Elijah Landreth [MSFT]
Microsoft Server Setup Team
Search our Knowledge Base at
http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at
http://www.microsoft.com/ntserver/
NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of
Microsoft.
or opinions of Microsoft.
