original title: KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008e

For a few weeks now I have been experiencing the same BSOD at start up (at the chose user screen and, the welcome screen, and immediately after login.

Using Nirsoft Blue Screen View I was able to get this from the .dmp



6/27/2010 6:41:52 PM








ntkrnlpa.exe+1eb238NT Kernel & SystemMicrosoft® Windows® Operating SystemMi

crosoft Corporation6.1.7600.16539 (win7_gdr.100226-1909)32-bit


It appears to be caused by ntkrnlpa.exe 

What's more disturbing is that after the recent BSOD many of the setting to my programs have been reset for example System Explorer setting have now been rest to their default.

Also some services have stopped most disturbing being windows error reporting and the service for Microsoft Security Essentials (I have restarted the services).

I do not believe this is a virus problem as I have run three virus scans with MSE today and they are all clean.
If it is relevant before this I was experiencing BSODs with ticalc.sys but I have uninstalled all Ti applications on my computer.

I am running windows 7 32 bit

oddly my processor frequency is fluctuating between 1050=2100 Mhz




These are my usual troubleshooters for the BCCode: 8E issue and they may help you. However
because of the processor frequency fluctuation I would contact the System Maker or if a custom
system the motherboard maker. Try updating the BIOS and if not help take to a real computer
shop (not leeks and peeks at a BestBuy or other BigBox stores) or the System maker's Support.


See this thread for information on using BlueScreenView, MyEventViewer, and other methods to
troubleshoot BlueScreens - top 3 replies.


Two primary causes of this blue screen are video drivers and BIOS - Check with System Maker's
Site for Display Adapter (Video) and BIOS and then Device Maker's site for latest Video. It can be
other drivers so check those also. Antivirus/antispyware/security programs are other possibilities.

See Generic Driver Update Methods in next message.

BCCode: 8E  0x0000008E is same as 0x1000008E


The KERNEL_MODE_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 that a memory access violation occurred.

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 you do not know the specific cause of the exception, consider the following items:

  • Hardware incompatibility. Make sure that any new hardware 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 the bug check message lists a driver by name , disable or remove that driver. Also, 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 have 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, you can remove the service by starting the system 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 0x1E. You can disable memory caching of the BIOS 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: 8E  0x0000008E is same as 0x1000008E  <-- read this*1151.html?order=date


Look in the Event Viewer to see if anything is reported about those.

MyEventViewer - Free - a simple alternative to the standard event viewer of Windows.
TIP - Options - Advanced Filter allows you to see a time frame instead of the whole file.


Also do this so you can see the likely bluescreens.

Windows Vista automatically restarts if your PC encounters an error that causes it to crash.


Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen
info that would help. Such as the BCC and the other 4 entries on the lower left. And any other
error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

As examples :

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys - Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during 'blue screen of death'
crashes, and displays the information about all crashes in one table - Free

Many BlueScreens are caused by old or corrupted drivers, especially video drivers however
there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or
Recovery Options if your system has that installed by the maker.

How to Boot to the System Recovery Options in Windows 7

You can try a System Restore back to a point before the problem started if there is one.

How to Do a System Restore in Windows 7


Start - type this in Search Box ->  COMMAND   find at top and RIGHT CLICK  -  RUN AS ADMIN

Enter this at the prompt - sfc /scannow

How to Repair Windows 7 System Files with System File Checker

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log (and Windows 7)

The log might give you the answer if there was a corrupted driver. (Does not tell all the possible
driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.

How to Run Check Disk at Startup in Windows 7


Often updating drivers will help, usually Video, Sound, Network Card  (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

Installing and updating drivers in 7

How To Disable Automatic Driver Installation In Windows Vista - Drivers


How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart

Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)

Understanding and Decoding BSOD (blue screen of death) Messages

Windows - Troubleshooting Blue Screen Errors


In some cases this might be required.

StartUp Repair from Recovery Options or Windows 7 disk

How to Run a Startup Repair in Windows 7

How to Boot to the System Recovery Options in Windows 7

How to Create a Windows 7 System Repair Disc

How to Do a Repair Install to Fix Windows 7

Hope this helps.

Rob Brown - MS MVP - Windows Desktop Experience : Bicycle - Mark Twain said it right.
Rob Brown - past Microsoft MVP - Windows Insider MVP 2016 - 2021
Microsoft MVP Windows and Devices for IT 2009 - 2020

1 person found this reply helpful


Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


That the computer powers off during the memory diagnostic is troubling, and is likely an indication of a hardware problem.

The verifier bugcheck was caused by NTIDrvr.sys from Dec 21, 2004 incorrectly processing an IRP.

The other dumps showed the  KERNEL_MODE_EXCEPTION_NOT_HANDLED_M bugcheck seemed to be caused by some kind of memory corruption, and a THREAD_STUCK_IN_DEVICE_DRIVER_M bugcheck that seems attributable to a stale video driver, atikmdag.sys from July 29, 2009.  (You commented on this, and it seems you are aware of an updated driver for it.)

In addition to the above, you have stale drivers that should be updated, or uninstalled, or the software that they came with should be uninstalled:

Aspi32.SYS 9/10/1999 (more than 10 years old)

NTIDrvr.sys 12/21/2004

lmimirr.sys 4/10/2007 

RaInfo.sys 1/4/2008 

ahcix86s.sys 5/27/2008 

windrvr6.sys 7/3/2008 

LMIRfsDriver.sys 7/14/2008 

tos_sps32.sys 6/24/2009 

FwLnk.sys 7/6/2009 


So, given the problems you're having, I'd suggest trying the memory test again - test one RAM module at a time - and see if you can get each tested.  Run with a subset of RAM modules installed, to try to identify/isolate one that may be involved in the behavior.

Also check into updating or removing the stale drivers, including updated ATI drivers.

2 people found this reply helpful


Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated December 7, 2020 Views 124,163 Applies to: