"Unexpected Kernel mode trap..."
Twigofthetree
zeros...and a message that says
"unexpected kernel mode trap...."
and then the computer shuts down before I can read the
rest.
The computer then restarts itself. The blue string
flashes so quickly that I cannot read the full message,
but it is annoying that this occurs without warning.
I'm running Windows 2000 with all SP's, virus protection,
and firewall installed. How can I fix my "kernel"
problem? Thanks!
Luci Sandor
UNEXPECTED_KERNEL_MODE_TRAP
Explanation:
This Stop message means that one of two types of problems occurred in
kernel-mode, either the kind of condition that the kernel is not allowed to
have or catch (a bound trap), or an unrecoverable error. Occasionally, this
message can be caused by software problems, but the most common cause is
hardware failure. It usually occurs after the installation of faulty or
mismatched hardware (especially memory) or in the event that installed
hardware fails. Setting the CPU to run at speeds above the rated
specification (known as overclocking the CPU) can also cause this error.
User Action:
If hardware was recently added to the system, remove it to see if the error
recurs. If existing hardware has failed, remove or replace the faulty
component. Run hardware diagnostics supplied by the system manufacturer,
especially the memory scanner, to determine which hardware component has
failed. For details on these procedures, see the owner's manual for your
computer. Check that all network adapters in the computer are properly
seated. Use an ink eraser or an electrical contact treatment, available at
electronics supply stores, to ensure network adapter contacts are clean. If
the error appears on a newly installed system, check the availability of
updates for the following: firmware on RISC systems, as well as BIOS
revisions on the motherboard, the SCSI controller, or network adapters.
Updates of this kind are typically available on the web site or BBS of the
hardware manufacturer. Confirm that all hard disks, hard disk controllers,
and SCSI adapters are listed on the Microsoft Windows 2000 Hardware
Compatibility List (HCL) on http://www.microsoft.com/. If the error occurred
after the installation of a new or updated device driver, remove or replace
the driver. If, under this circumstance, the error occurs during the startup
sequence and the system partition is formatted with NTFS, 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, start the computer
using the Recovery Console in order to access the file. Restart your
computer, and then press F8 at the character-mode menu that displays the
operating system choices. At the resulting Windows 2000 Advanced Options
menu, choose the Last Known Good Configuration option. This option is most
effective when only one driver or service is added at a time. If the CPU was
overclocked, return the CPU to the default clock speed setting. Check the
System Log in Event Viewer for additional error messages that might help
pinpoint the device or driver causing the error. Disabling memory caching of
the BIOS might also resolve it. If you encountered this error while
upgrading to Windows 2000, it might be caused by a device driver, a system
service, a virus scanner, or a backup tool that is incompatible with the new
version. If possible, remove all third-party device drivers and system
services and disable any virus scanners prior to upgrading. Contact the
software manufacturer to obtain updates of these tools. Finally, if all the
above steps fail to resolve the error, take the system motherboard to a
repair facility for diagnostic testing. A crack, a scratched trace, or a
defective component on the motherboard can also cause this error. For more
troubleshooting information about this Stop message, refer to the Microsoft
Knowledge Base at http://support.microsoft.com/support.
Also check
https://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000pro/proddocs/progs/pgsappb.asp
and
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q137/5/39.asp&NoWebContent=1
and
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winntas/tips/techrep/bsod.asp
and
http://support.microsoft.com/?kbid=264045
and
http://support.microsoft.com/?kbid=252182
and
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_ukdq.asp
(this one is said for WinXP, but I thnk it works for 2000 either)
and so on...there are lots of hardware-driver configuration errors that can
bring you this blue screen.
"Twigofthetree" <Twigof...@comcast.net> wrote in message
news:096001c366ef$4ee456b0$a401...@phx.gbl...