Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: (BSOD) kernel mode exception not handled.. 0x1000008e

15 Mar 2012   #1

Windows 7 Ultimate x64
(BSOD) kernel mode exception not handled.. 0x1000008e

help me guys..... got this BSOD while i was installing adobe photoshop...... got from other guy... it was working for him
windows 7 ultimate 32bit... its not 64bit....

My System SpecsSystem Spec
15 Mar 2012   #2

Windows 10 Pro x64, Arch Linux

Do you have Folder Lock installed on your system?
WinDrvNT.sys is a file from FOLDER LOCK that may be causing the system crashes.

Uninstall folder lock and reboot. Folder Lock creates a file called windrvnt.sys, which can cause your computer to crash repeatedly when it conflicts with other software.
Lets see if your BSOD stops after uninstalling Folder Lock.

Update those:
Realtek HD Audio Codec Driver
ASACPI ASUSTeK Computer Inc. - Motherboards- ASUS P6T Deluxe
information   Information

Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005). You may have to use the Device Manager to install the driver.

*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
Arg1: c0000005, The exception code that was not handled
Arg2: 99b0d703, The address that the exception occurred at
Arg3: 9e323c40, Trap Frame
Arg4: 00000000

Debugging Details:

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

99b0d703 668b08          mov     cx,word ptr [eax]

TRAP_FRAME:  9e323c40 -- (.trap 0xffffffff9e323c40)
ErrCode = 00000000
eax=00000000 ebx=99b11142 ecx=00000000 edx=000841d4 esi=0028e2e8 edi=00000000
eip=99b0d703 esp=9e323cb4 ebp=9e323cd4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
99b0d703 668b08          mov     cx,word ptr [eax]        ds:0023:00000000=????
Resetting default scope






LAST_CONTROL_TRANSFER:  from 99b1123a to 99b0d703

WARNING: Stack unwind information not available. Following frames may be wrong.
9e323cd4 99b1123a 00000000 829773f0 c0600120 windrvNT+0x1703
9e323d18 8308748a 00000000 0028e2ec 0028e2fc windrvNT+0x523a
9e323d18 773e6344 00000000 0028e2ec 0028e2fc nt!KiFastCallEntry+0x12a
0028e304 00000000 00000000 00000000 00000000 0x773e6344


99b0d703 668b08          mov     cx,word ptr [eax]


SYMBOL_NAME:  windrvNT+1703

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  windrvNT.sys


FAILURE_BUCKET_ID:  0x8E_windrvNT+1703

BUCKET_ID:  0x8E_windrvNT+1703

Followup: MachineOwner
My System SpecsSystem Spec

 (BSOD) kernel mode exception not handled.. 0x1000008e

Thread Tools

Similar help and support threads
Thread Forum
Repeat BSOD: Interrupt Exception Not Handled
Boots fine, then crashes consistently after about 10min of on time. No recent changes of any kind that I can think of. In the past 6 months or so I've been slowly having little troubles with my 3-4 year old SSD. Its only a 60GB drive and I've been bad about keeping it pretty full. Could the...
BSOD Help and Support
Frequent BSOD - SYSTEM_SERVICE_EXCEPTION and exception not handled
Hi all, I've been trying to debug this machine for 2 weeks and I've been failing! It's an ASUS CM6870 running Win 7 Home 64bit. The machine has had the OS freshly re-installed, memtest ran without errors, checkdisk ran and we saw no errors, I setup driver verifier and saw an issue with AVAST,...
BSOD Help and Support
BSOD from System Service Exception and KMode Exception Not Handled
For a long time now i have been getting BSOD's, pretty much all of the time from System Service Exception and KMode Exception Not Handled. Sometimes the PC never gets to the BSOD and just freezes up and restarts. This happens at any time whether im doing nothing or on the internet, sometimes it...
BSOD Help and Support
Random BSOD: Interrupt Exception Not Handled
So I built this computer recently and it blue screens at what appears to be random times. Sometimes it happens when I'm using the internet or it happens right as my computer starts up. The blue screen says INTERRUPT_EXCEPTION_NOT_HANDLED at the top and at the bottom it says STOP: 0x0000003D. I also...
BSOD Help and Support
BSOD: kmode exception not handled
I have been trying to find an answer to this issue. I've started having a lot of BSOD errors this past week and can't seem to diagnose the issue. I've updated video drivers, updated my BIOS, un-installed and re-installed programs. I'm wondering if anyone can spot my issue in these files. Windows...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 14:31.
Twitter Facebook Google+