[Subaru_]

Резльтат дампа.

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: 808899d0, The address that the exception occurred at
Arg3: 91608cf0, 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 - <Unable to get error code text>

FAULTING_IP:
nt!KiServiceExit2+0
808899d0 fa cli

TRAP_FRAME: 91608cf0 -- (.trap 0xffffffff91608cf0)
ErrCode = 00000000
eax=0043001b ebx=40000006 ecx=0000e69f edx=00440064 esi=00430036 edi=00440064
eip=808899d0 esp=91608d64 ebp=91608d64 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!KiServiceExit2:
808899d0 fa cli
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: 1cv7.exe

CURRENT_IRQL: 0

CLI_FAULT_INSTR:
nt!KiServiceExit2+0
808899d0 fa cli

LAST_CONTROL_TRANSFER: from 8082d820 to 80827c83

STACK_TEXT:
916088bc 8082d820 0000008e c0000005 808899d0 nt!KeBugCheckEx+0x1b
91608c80 8088a2aa 91608c9c 00000000 91608cf0 nt!KiDispatchException+0x3a2
91608ce8 8088a25e 0000e69f b53b4752 badb0d00 nt!CommonDispatchException+0x4a
91608cf0 b53b4752 badb0d00 00440064 00000000 nt!Kei386EoiHelper+0x186
WARNING: Stack unwind information not available. Following frames may be wrong.
91608cf4 badb0d00 00440064 00000000 0000001f Haspnt+0x8752
91608cf8 00440064 00000000 0000001f b53b4754 0xbadb0d00
91608cfc 00000000 0000001f b53b4754 91608db0 0x440064


STACK_COMMAND: kb

FOLLOWUP_IP:
Haspnt+8752
b53b4752 c090e800000000 rcl byte ptr [eax+0E8h],0

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: Haspnt+8752

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: CLI_FAULT

BUCKET_ID: CLI_FAULT

Followup: MachineOwner