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

[rohanchougule]

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....

 

[yowanvista]

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 http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=8&PFid=14&Level=3&Conn=2
ASACPI ASUSTeK Computer Inc. - Motherboards- ASUS P6T Deluxe

   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                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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
happening.
Arguments:
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.

FAULTING_IP: 
windrvNT+1703
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
windrvNT+0x1703:
99b0d703 668b08          mov     cx,word ptr [eax]        ds:0023:00000000=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  Adobe AIR Appl

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 99b1123a to 99b0d703

STACK_TEXT:  
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


STACK_COMMAND:  kb

FOLLOWUP_IP: 
windrvNT+1703
99b0d703 668b08          mov     cx,word ptr [eax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  windrvNT+1703

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: windrvNT

IMAGE_NAME:  windrvNT.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  409f405c

FAILURE_BUCKET_ID:  0x8E_windrvNT+1703

BUCKET_ID:  0x8E_windrvNT+1703

Followup: MachineOwner
---------