D
Dave Crawley (dcrawley)
Have several VMs that are randomly bluescreening.
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: 8088fea5, The address that the exception occurred at
Arg3: 8089be3c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
8088fea5 8b18 mov ebx,dword ptr [eax]
TRAP_FRAME: 8089be3c -- (.trap 0xffffffff8089be3c)
ErrCode = 00000000
eax=00011000 ebx=00000001 ecx=3132000a edx=3132000b esi=00000000 edi=42504354
eip=8088fea5 esp=8089beb0 ebp=808a8ae0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExpInterlockedPopEntrySListFault:
8088fea5 8b18 mov ebx,dword ptr [eax] ds:0023:00011000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from ****0b43 00000000 00000000 42504354 nt!ExAllocatePoolWithTag+0x805
8089bfe4 f54b7c44 00000000 00000604 42504354 nt!ExAllocatePoolWithTagPriority+0x13f
WARNING: Stack unwind information not available. Following frames may be wrong.
****c****0+0x3e06
****1c ba6ad770 vmbkmcl+0x1****360 ffdffa48 80832cfc bab601b0 vmbus+0x3e92
8089c600 8088fbdf 00000000 0000000e 00000000 vmbus+0x3360
8089c604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37
STACK_COMMAND: kb
FOLLOWUP_IP:
netvsc50+3e06
f695ee06 ?? ???
SYMBOL_STACK_INDEX: c
SYMBOL_NAME: netvsc50+3e06
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netvsc50
IMAGE_NAME: netvsc50.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x8E_netvsc50+3e06
BUCKET_ID: 0x8E_netvsc50+3e06
Followup: MachineOwner
---------
Continue reading...
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: 8088fea5, The address that the exception occurred at
Arg3: 8089be3c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!ExpInterlockedPopEntrySListFault+0
8088fea5 8b18 mov ebx,dword ptr [eax]
TRAP_FRAME: 8089be3c -- (.trap 0xffffffff8089be3c)
ErrCode = 00000000
eax=00011000 ebx=00000001 ecx=3132000a edx=3132000b esi=00000000 edi=42504354
eip=8088fea5 esp=8089beb0 ebp=808a8ae0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!ExpInterlockedPopEntrySListFault:
8088fea5 8b18 mov ebx,dword ptr [eax] ds:0023:00011000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from ****0b43 00000000 00000000 42504354 nt!ExAllocatePoolWithTag+0x805
8089bfe4 f54b7c44 00000000 00000604 42504354 nt!ExAllocatePoolWithTagPriority+0x13f
WARNING: Stack unwind information not available. Following frames may be wrong.
****c****0+0x3e06
****1c ba6ad770 vmbkmcl+0x1****360 ffdffa48 80832cfc bab601b0 vmbus+0x3e92
8089c600 8088fbdf 00000000 0000000e 00000000 vmbus+0x3360
8089c604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37
STACK_COMMAND: kb
FOLLOWUP_IP:
netvsc50+3e06
f695ee06 ?? ???
SYMBOL_STACK_INDEX: c
SYMBOL_NAME: netvsc50+3e06
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netvsc50
IMAGE_NAME: netvsc50.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x8E_netvsc50+3e06
BUCKET_ID: 0x8E_netvsc50+3e06
Followup: MachineOwner
---------
Continue reading...