Kernel_mode_exception_not_handled

Hi everyone,

Been getting BSOD for the last few months (at least 2 a day!). Rebuilt the machine from scratch still get BSOD. Tested RAM (21 passes) with memtest no issues. The kernel dump below is from the crash today .. just can't make sense of it
Any help would be greatly appreciated.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: bf837895, The address that the exception occurred at
Arg3: edae5a68, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


PEB is paged out (Peb.Ldr = 7ffd400c). Type ".hh dbgerr001" for details

PEB is paged out (Peb.Ldr = 7ffd400c). Type ".hh dbgerr001" for details

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

FAULTING_IP:
win32k!HMUnlockObjectInternal+1c
bf837895 8a5109 mov dl,byte ptr [ecx+9]

TRAP_FRAME: edae5a68 -- (.trap 0xffffffffedae5a68)
ErrCode = 00000000
eax=edae5b08 ebx=000002c4 ecx=bbd54700 edx=bbd10000 esi=bbec1ef8 edi=00000000
eip=bf837895 esp=edae5adc ebp=edae5adc iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
win32k!HMUnlockObjectInternal+0x1c:
bf837895 8a5109 mov dl,byte ptr [ecx+9] ds:0023:bbd54709=??
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iexplore.exe

LAST_CONTROL_TRANSFER: from 8051d6ef to 8053354e

STACK_TEXT:
edae5630 8051d6ef 0000008e c0000005 bf837895 nt!KeBugCheckEx+0x1b
edae59f8 804df235 edae5a14 00000000 edae5a68 nt!KiDispatchException+0x3b1
edae5a60 804df1e6 edae5adc bf837895 badb0d00 nt!CommonDispatchException+0x4d
edae5adc bf823a4a edae5b08 bf823f48 bbec1ef8 nt!KiExceptionExit+0x18a
edae5adc bf823a4a edae5b08 bf823f48 bbec1ef8 win32k!ThreadLockExchangeAlways+0x23
edae5ae4 bf823f48 bbec1ef8 edae5afc 000002c2 win32k!ThreadLockExchangeAlways+0x23
edae5b08 bf823e9d bbed4778 000002c2 000002c4 win32k!xxxWindowHitTest+0x2f
edae5b40 bf823f5a bbe506e8 000002c2 000002c4 win32k!xxxWindowHitTest2+0xfd
edae5b70 bf825068 bbe506e8 000002c2 000002c4 win32k!xxxWindowHitTest+0x41
edae5c94 bf801ee5 00000200 edae5d14 00000000 win32k!xxxScanSysQueue+0x442
edae5ce8 bf80370a edae5d14 000025ff 00000000 win32k!xxxRealInternalGetMessage+0x335
edae5d48 804de7ec 0197ff64 00000000 00000000 win32k!NtUserPeekMessage+0x40
edae5d48 7c90eb94 0197ff64 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0197ff10 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!HMUnlockObjectInternal+1c
bf837895 8a5109 mov dl,byte ptr [ecx+9]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HMUnlockObjectInternal+1c

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45f013f6

FAILURE_BUCKET_ID: 0x8E_win32k!HMUnlockObjectInternal+1c

BUCKET_ID: 0x8E_win32k!HMUnlockObjectInternal+1c

Followup: MachineOwner

 

Hi, Kritter. Welcome to Windows BBS!

Please carefully follow all the instructions in this link and then paste DebugWiz-generated BSOD dump log analysis reports (the complete reports) for two or three of your most recent BSODs in this thread.

The additional information the complete DebugWiz-generated reports provide might help us narrow down the culprit more quickly.

NOTE:

 

• Microsoft KB134503:
  

A More Reliable RAM Testing Method:

1. Remove some of the memory modules from the computer (while the computer is off, of course).
   • For example, if two RAM modules are installed in your computer, remove one of the RAM modules.
2. Start your computer and see if the problem goes away.
3. If you continue to have unexpected BSODs, then replace that RAM module with another module, or install the module in a different memory slot.
4. Start your computer and see if the problem goes away.

Continue this process to see if you can pinpoint the cause of your problem to a specific RAM module or slot.