*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.24117.amd64fre.win7sp1_ldr_escrow.180422-1430
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 4
CPU_MHZ: 91d
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 17
CPU_STEPPING: a
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 11-24-2019 18:01:51.0329
ANALYSIS_VERSION: 10.0.18362.1 x86fre
EXCEPTION_RECORD: fffff80000b9c2c8 -- (.exr 0xfffff80000b9c2c8)
ExceptionAddress: fffff800032b0612 (nt!KiTimerWaitTest+0x00000000000001e2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80000b9c370 -- (.trap 0xfffff80000b9c370)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000102 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032b0612 rsp=fffff80000b9c500 rbp=fffffa8004077978
r8=fffff8000343db01 r9=0000000000000005 r10=000000000000006f
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KiTimerWaitTest+0x1e2:
fffff800`032b0612 f0490fbaaf904c000000 lock bts qword ptr [r15+4C90h],0 ds:00000000`00004c90=????????????????
Resetting default scope
DPC_STACK_BASE: FFFFF80000BA2FB0
STACK_OVERFLOW: Stack Limit: fffff80000b9cfb0. Use (kF) and (!stackusage) to investigate stack usage.
LAST_CONTROL_TRANSFER: from fffff800032f882e to fffff800032f5470
STACK_TEXT:
fffff800`00b9b3b8 fffff800`032f882e : fffff800`032e45ec fffff800`03406364 fffff800`00b9bb30 fffff800`032c0b50 : nt!KeBugCheck
fffff800`00b9b3c0 fffff800`032fcd5d : fffff800`034cdcf4 fffff800`03411040 fffff800`03251000 fffff800`00b9c2c8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b3f0 fffff800`032c17b5 : fffff800`03400b0c fffff800`00b9b468 fffff800`00b9c2c8 fffff800`03251000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b420 fffff800`033d4e8e : fffff800`00b9c2c8 fffff800`00b9bb30 fffff800`00000000 fffffa80`04077970 : nt!RtlDispatchException+0x415
fffff800`00b9bb00 fffff800`03305942 : fffff800`00b9c2c8 fffffa80`04077978 fffff800`00b9c370 00000000`00000000 : nt!KiDispatchException+0x17e
fffff800`00b9c190 fffff800`03302835 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c370 fffff800`032b0612 : 00000000`00610024 fffff880`0f258c38 fffffa80`0700f168 fffff880`0f258730 : nt!KiGeneralProtectionFault+0x3f5
fffff800`00b9c500 fffff800`032b026d : fffffa80`04077970 fffffa80`0700f168 fffffa80`0700f168 00000000`00000102 : nt!KiTimerWaitTest+0x1e2
fffff800`00b9c580 fffff800`032b1e8e : 00000001`6d3c4ba2 fffff800`00b9cc18 00000000`0000996f fffff800`0343eb68 : nt!KiProcessExpiredTimerList+0x6d
fffff800`00b9cbf0 fffff800`032b2157 : fffff880`0f16c2c4 fffff800`0000996f 00000000`53b5cd5f 00000000`0000006f : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`032f8b6a : fffff800`0343b180 fffff800`0344b1c0 00000000`00000000 fffff880`0f16cbb0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a
THREAD_SHA1_HASH_MOD_FUNC: ad44af258c566fd9c20773e0eafd6585dba065b6
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b786014c14e00a09f37a12dae3e53f21c414c032
THREAD_SHA1_HASH_MOD: dc844b1b94baa204d070855e43bbbd27eee98b94
FOLLOWUP_IP:
nt!KiKernelCalloutExceptionHandler+e
fffff800`032f882e 90 nop
FAULT_INSTR_CODE: cccccc90
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5add19ea
IMAGE_VERSION: 6.1.7601.24117
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
BUCKET_ID: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
PRIMARY_PROBLEM_CLASS: X64_0x1E_nt!KiKernelCalloutExceptionHandler+e
TARGET_TIME: 2019-11-24T10:14:25.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-04-23 02:25:30
BUILDDATESTAMP_STR: 180422-1430
BUILDLAB_STR: win7sp1_ldr_escrow
BUILDOSVER_STR: 6.1.7601.24117.amd64fre.win7sp1_ldr_escrow.180422-1430
ANALYSIS_SESSION_ELAPSED_TIME: 975
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1e_nt!kikernelcalloutexceptionhandler+e
FAILURE_ID_HASH: {31b31670-23d4-78dd-b3a6-d5566ed846e6}
Followup: MachineOwner
---------
drive.google.com
