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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002ef8300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8139
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 34611
Key : Analysis.Init.CPU.mSec
Value: 1280
Key : Analysis.Init.Elapsed.mSec
Value: 10830
Key : Analysis.Memory.CommitPeak.Mb
Value: 62
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9e510 -- (.trap 0xfffff80000b9e510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000682
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800505410c rsp=fffff80000b9e6a0 rbp=fffff80000b9e709
r8=fffffa80131a82e0 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
vgk+0x4710c:
fffff880`0505410c ?? ???
Resetting default scope
DPC_STACK_BASE: FFFFF80000BA4FB0
STACK_OVERFLOW: Stack Limit: fffff80000b9efb0. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff800`00b9d558 fffff800`02cf20ee : 0000a595`12a60010 00000014`13c70006 fffff800`00b9dcd0 fffff800`02cb6de0 : nt!KeBugCheck
fffff800`00b9d560 fffff800`02cf61fd : fffff800`02ed1388 fffff800`02e24634 fffff800`02c5b000 fffff800`00b9e468 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9d590 fffff800`02cb6125 : fffff800`02e04b94 fffff800`00b9d608 fffff800`00b9e468 fffff800`02c5b000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9d5c0 fffff800`02dd5eee : fffff800`00b9e468 fffff800`00b9dcd0 fffff800`00000000 fffffa80`131a8190 : nt!RtlDispatchException+0x415
fffff800`00b9dca0 fffff800`02cfd3c2 : fffff800`00b9e468 fffff800`00b9e800 fffff800`00b9e510 fffffa80`131a82e0 : nt!KiDispatchException+0x17e
fffff800`00b9e330 fffff800`02cfac78 : fffff800`02e3f180 fffff880`02d0a110 fffff800`02e41b80 fffff800`02e4f1c0 : nt!KiExceptionDispatch+0xc2
fffff800`00b9e510 fffff880`0505410c : fffff800`00b9e800 00000000`00000000 fffffa80`131a82e0 00000000`00000000 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00b9e6a0 fffff800`00b9e800 : 00000000`00000000 fffffa80`131a82e0 00000000`00000000 00000000`00000000 : vgk+0x4710c
fffff800`00b9e6a8 00000000`00000000 : fffffa80`131a82e0 00000000`00000000 00000000`00000000 00000000`00002000 : 0xfffff800`00b9e800
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002ee5300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 37544
Key : Analysis.Init.CPU.mSec
Value: 1249
Key : Analysis.Init.Elapsed.mSec
Value: 7777
Key : Analysis.Memory.CommitPeak.Mb
Value: 65
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9e510 -- (.trap 0xfffff80000b9e510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000680
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800770810c rsp=fffff80000b9e6a0 rbp=fffff80000b9e709
r8=fffffa8013ba2780 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
vgk+0x4710c:
fffff880`0770810c ?? ???
Resetting default scope
DPC_STACK_BASE: FFFFF80000BA4FB0
STACK_OVERFLOW: Stack Limit: fffff80000b9efb0. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff800`00b9d558 fffff800`02cdf0ee : 00000000`0000000d 00000000`00000000 fffff800`00b9dcd0 fffff800`02ca3de0 : nt!KeBugCheck
fffff800`00b9d560 fffff800`02ce31fd : fffff800`02ebe388 fffff800`02e11634 fffff800`02c48000 fffff800`00b9e468 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9d590 fffff800`02ca3125 : fffff800`02df1b94 fffff800`00b9d608 fffff800`00b9e468 fffff800`02c48000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9d5c0 fffff800`02dc2eee : fffff800`00b9e468 fffff800`00b9dcd0 fffff800`00000000 fffffa80`13ba2630 : nt!RtlDispatchException+0x415
fffff800`00b9dca0 fffff800`02cea3c2 : fffff800`00b9e468 fffff800`00b9e800 fffff800`00b9e510 fffffa80`13ba2780 : nt!KiDispatchException+0x17e
fffff800`00b9e330 fffff800`02ce7c78 : 00000000`00000104 fffff880`0f2c32d7 00000000`00000020 fffff800`00b9e540 : nt!KiExceptionDispatch+0xc2
fffff800`00b9e510 fffff880`0770810c : fffff800`00b9e800 fffff880`0f262c08 fffffa80`13ba2780 fffffa80`130c2000 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00b9e6a0 fffff800`00b9e800 : fffff880`0f262c08 fffffa80`13ba2780 fffffa80`130c2000 00000000`00610740 : vgk+0x4710c
fffff800`00b9e6a8 fffff880`0f262c08 : fffffa80`13ba2780 fffffa80`130c2000 00000000`00610740 fffffa80`13494940 : 0xfffff800`00b9e800
fffff800`00b9e6b0 fffffa80`13ba2780 : fffffa80`130c2000 00000000`00610740 fffffa80`13494940 fffffa80`130c2000 : nvlddmkm+0x1d3c08
fffff800`00b9e6b8 fffffa80`130c2000 : 00000000`00610740 fffffa80`13494940 fffffa80`130c2000 fffff880`0f263853 : 0xfffffa80`13ba2780
fffff800`00b9e6c0 00000000`00610740 : fffffa80`13494940 fffffa80`130c2000 fffff880`0f263853 00000000`00000004 : 0xfffffa80`130c2000
fffff800`00b9e6c8 fffffa80`13494940 : fffffa80`130c2000 fffff880`0f263853 00000000`00000004 fffff880`04062a5c : 0x610740
fffff800`00b9e6d0 fffffa80`130c2000 : fffff880`0f263853 00000000`00000004 fffff880`04062a5c fffff800`02c84760 : 0xfffffa80`13494940
fffff800`00b9e6d8 fffff880`0f263853 : 00000000`00000004 fffff880`04062a5c fffff800`02c84760 fffff800`00b9e760 : 0xfffffa80`130c2000
fffff800`00b9e6e0 00000000`00000004 : fffff880`04062a5c fffff800`02c84760 fffff800`00b9e760 fffffa80`130c2000 : nvlddmkm+0x1d4853
fffff800`00b9e6e8 fffff880`04062a5c : fffff800`02c84760 fffff800`00b9e760 fffffa80`130c2000 00000000`00000007 : 0x4
fffff800`00b9e6f0 fffff880`02c4cc79 : fffffa80`13963060 fffffa80`13ba2768 fffffa80`13ba2780 fffff800`00b9e800 : HIDPARSE!HidP_GetUsages+0x78
fffff800`00b9e770 fffff800`02c7b681 : fffffa80`1383ea83 fffff800`00000000 00000000`00000000 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x69d
fffff800`00b9e7f0 fffff880`02c359c4 : fffffa80`13b9f5b0 fffffa80`13b9f506 fffffa80`13b9f100 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00b9e8e0 fffff880`02c35c2d : fffffa80`13915702 fffffa80`13915740 fffffa80`13b9f1d0 00000000`00000005 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff800`00b9e970 fffff800`02c7b681 : fffffa80`13625a13 00000000`00000000 fffffa80`13b9f001 fffffa80`13625790 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff800`00b9ea00 fffff880`03ba36e7 : fffffa80`132a4050 fffffa80`130d3000 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00b9eaf0 fffff880`03ba3bcf : fffffa80`14675c02 fffffa80`13625790 00000000`00000000 fffffa80`14a596a0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x83f
fffff800`00b9ebc0 fffff880`03ba18fb : fffffa80`132a4eb0 fffffa80`132a41a0 fffffa80`132a5050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00b9ec20 fffff880`03b92f69 : fffffa80`132a4050 00000000`00000000 fffffa80`132a4e02 fffffa80`132a4eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00b9ec60 fffff800`02c88cbc : fffff800`02e2c180 fffffa80`132a4eb0 fffffa80`132a4ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ec90 fffff800`02cdf42a : fffff800`02e2c180 fffff800`02e3c1c0 00000000`00000000 fffff880`03b92d90 : nt!KiRetireDpcList+0x1bc
fffff800`00b9ed40 00000000`00000000 : fffff800`00b9f000 fffff800`00b99000 fffff800`00b9ed00 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002eaf300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8577
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 33779
Key : Analysis.Init.CPU.mSec
Value: 1264
Key : Analysis.Init.Elapsed.mSec
Value: 13047
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9e510 -- (.trap 0xfffff80000b9e510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000683
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800647110c rsp=fffff80000b9e6a0 rbp=fffff80000b9e709
r8=fffffa801378d880 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
vgk+0x4710c:
fffff880`0647110c ?? ???
Resetting default scope
DPC_STACK_BASE: FFFFF80000BA4FB0
STACK_OVERFLOW: Stack Limit: fffff80000b9efb0. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff800`00b9d558 fffff800`02ca90ee : 00000000`00005000 00000000`00000000 fffff800`00b9dcd0 fffff800`02c6dde0 : nt!KeBugCheck
fffff800`00b9d560 fffff800`02cad1fd : fffff800`02e88388 fffff800`02ddb634 fffff800`02c12000 fffff800`00b9e468 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9d590 fffff800`02c6d125 : fffff800`02dbbb94 fffff800`00b9d608 fffff800`00b9e468 fffff800`02c12000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9d5c0 fffff800`02d8ceee : fffff800`00b9e468 fffff800`00b9dcd0 fffff800`00000000 fffffa80`1378d730 : nt!RtlDispatchException+0x415
fffff800`00b9dca0 fffff800`02cb43c2 : fffff800`00b9e468 fffff800`00b9e800 fffff800`00b9e510 fffffa80`1378d880 : nt!KiDispatchException+0x17e
fffff800`00b9e330 fffff800`02cb1c78 : 00000000`00000104 fffff880`0f2cf2d7 00000000`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff800`00b9e510 fffff880`0647110c : fffff800`00b9e800 fffff880`0f26ec08 fffffa80`1378d880 fffffa80`1322d000 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00b9e6a0 fffff800`00b9e800 : fffff880`0f26ec08 fffffa80`1378d880 fffffa80`1322d000 00000000`00610740 : vgk+0x4710c
fffff800`00b9e6a8 fffff880`0f26ec08 : fffffa80`1378d880 fffffa80`1322d000 00000000`00610740 fffff880`0f16459e : 0xfffff800`00b9e800
fffff800`00b9e6b0 fffffa80`1378d880 : fffffa80`1322d000 00000000`00610740 fffff880`0f16459e fffffa80`1322d000 : nvlddmkm+0x1d3c08
fffff800`00b9e6b8 fffffa80`1322d000 : 00000000`00610740 fffff880`0f16459e fffffa80`1322d000 fffff880`0f26f853 : 0xfffffa80`1378d880
fffff800`00b9e6c0 00000000`00610740 : fffff880`0f16459e fffffa80`1322d000 fffff880`0f26f853 00000000`00000004 : 0xfffffa80`1322d000
fffff800`00b9e6c8 fffff880`0f16459e : fffffa80`1322d000 fffff880`0f26f853 00000000`00000004 fffff880`0403ca5c : 0x610740
fffff800`00b9e6d0 fffffa80`1322d000 : fffff880`0f26f853 00000000`00000004 fffff880`0403ca5c fffff800`02c4e760 : nvlddmkm+0xc959e
fffff800`00b9e6d8 fffff880`0f26f853 : 00000000`00000004 fffff880`0403ca5c fffff800`02c4e760 fffff800`00b9e760 : 0xfffffa80`1322d000
fffff800`00b9e6e0 00000000`00000004 : fffff880`0403ca5c fffff800`02c4e760 fffff800`00b9e760 fffffa80`1322d000 : nvlddmkm+0x1d4853
fffff800`00b9e6e8 fffff880`0403ca5c : fffff800`02c4e760 fffff800`00b9e760 fffffa80`1322d000 00000000`00000007 : 0x4
fffff800`00b9e6f0 fffff880`03de8c79 : fffffa80`1404dcf0 fffffa80`1378d868 fffffa80`1378d880 fffff800`00b9e800 : HIDPARSE!HidP_GetUsages+0x78
fffff800`00b9e770 fffff800`02c45681 : fffffa80`12c6ab33 fffff800`00000000 fffff800`00000000 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x69d
fffff800`00b9e7f0 fffff880`03cb39c4 : fffffa80`14024ed0 fffffa80`14024e06 fffffa80`14019800 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00b9e8e0 fffff880`03cb3c2d : fffffa80`1378d002 fffffa80`1378d010 fffffa80`14019880 00000000`00000005 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff800`00b9e970 fffff800`02c45681 : fffffa80`12c80293 00000000`00000000 fffffa80`14019701 fffffa80`12c80010 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff800`00b9ea00 fffff880`02c136e7 : fffffa80`1363f050 fffffa80`13e39d00 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00b9eaf0 fffff880`02c13bcf : fffffa80`137be802 fffffa80`12c80010 00000000`00000000 fffffa80`14051170 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x83f
fffff800`00b9ebc0 fffff880`02c118fb : fffffa80`1363feb0 fffffa80`1363f1a0 fffffa80`13640050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00b9ec20 fffff880`02c02f69 : fffffa80`1363f050 00000000`00000000 fffffa80`1363fe02 fffffa80`1363feb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00b9ec60 fffff800`02c52cbc : fffff800`02df6180 fffffa80`1363feb0 fffffa80`1363fec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ec90 fffff800`02ca942a : fffff800`02df6180 fffff800`02e061c0 00000000`00000000 fffff880`02c02d90 : nt!KiRetireDpcList+0x1bc
fffff800`00b9ed40 00000000`00000000 : fffff800`00b9f000 fffff800`00b99000 fffff800`00b9ed00 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002ea3300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 7780
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 33319
Key : Analysis.Init.CPU.mSec
Value: 1186
Key : Analysis.Init.Elapsed.mSec
Value: 17251
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9e510 -- (.trap 0xfffff80000b9e510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000683
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003b0410c rsp=fffff80000b9e6a0 rbp=fffff80000b9e709
r8=fffffa801779df30 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
vgk+0x4710c:
fffff880`03b0410c ?? ???
Resetting default scope
DPC_STACK_BASE: FFFFF80000BA4FB0
STACK_OVERFLOW: Stack Limit: fffff80000b9efb0. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff800`00b9d558 fffff800`02c9d0ee : fffffa80`16a785c0 00000000`00000002 fffff800`00b9dcd0 fffff800`02c61de0 : nt!KeBugCheck
fffff800`00b9d560 fffff800`02ca11fd : fffff800`02e7c388 fffff800`02dcf634 fffff800`02c06000 fffff800`00b9e468 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9d590 fffff800`02c61125 : fffff800`02dafb94 fffff800`00b9d608 fffff800`00b9e468 fffff800`02c06000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9d5c0 fffff800`02d80eee : fffff800`00b9e468 fffff800`00b9dcd0 fffff800`00000000 fffffa80`1779dde0 : nt!RtlDispatchException+0x415
fffff800`00b9dca0 fffff800`02ca83c2 : fffff800`00b9e468 fffff800`00b9e800 fffff800`00b9e510 fffffa80`1779df30 : nt!KiDispatchException+0x17e
fffff800`00b9e330 fffff800`02ca5c78 : fffffa80`16cf41a0 fffff880`0f24e2d7 ffff0091`00000001 00000000`ffffffff : nt!KiExceptionDispatch+0xc2
fffff800`00b9e510 fffff880`03b0410c : fffff800`00b9e800 fffff880`0f1edc08 fffffa80`1779df30 fffffa80`16e00000 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00b9e6a0 fffff800`00b9e800 : fffff880`0f1edc08 fffffa80`1779df30 fffffa80`16e00000 00000000`00610740 : vgk+0x4710c
fffff800`00b9e6a8 fffff880`0f1edc08 : fffffa80`1779df30 fffffa80`16e00000 00000000`00610740 fffff880`0f0e359e : 0xfffff800`00b9e800
fffff800`00b9e6b0 fffffa80`1779df30 : fffffa80`16e00000 00000000`00610740 fffff880`0f0e359e fffffa80`16e00000 : nvlddmkm+0x1d3c08
fffff800`00b9e6b8 fffffa80`16e00000 : 00000000`00610740 fffff880`0f0e359e fffffa80`16e00000 fffff880`0f1ee853 : 0xfffffa80`1779df30
fffff800`00b9e6c0 00000000`00610740 : fffff880`0f0e359e fffffa80`16e00000 fffff880`0f1ee853 00000000`00000004 : 0xfffffa80`16e00000
fffff800`00b9e6c8 fffff880`0f0e359e : fffffa80`16e00000 fffff880`0f1ee853 00000000`00000004 fffff880`05988a5c : 0x610740
fffff800`00b9e6d0 fffffa80`16e00000 : fffff880`0f1ee853 00000000`00000004 fffff880`05988a5c fffff800`02c42760 : nvlddmkm+0xc959e
fffff800`00b9e6d8 fffff880`0f1ee853 : 00000000`00000004 fffff880`05988a5c fffff800`02c42760 fffff800`00b9e760 : 0xfffffa80`16e00000
fffff800`00b9e6e0 00000000`00000004 : fffff880`05988a5c fffff800`02c42760 fffff800`00b9e760 fffffa80`16e00000 : nvlddmkm+0x1d4853
fffff800`00b9e6e8 fffff880`05988a5c : fffff800`02c42760 fffff800`00b9e760 fffffa80`16e00000 00000000`00000007 : 0x4
fffff800`00b9e6f0 fffff880`05992c79 : fffffa80`1779d940 fffffa80`1779df18 fffffa80`1779df30 fffff800`00b9e800 : HIDPARSE!HidP_GetUsages+0x78
fffff800`00b9e770 fffff800`02c39681 : fffffa80`172b7b73 fffff800`00000000 00000000`00000000 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x69d
fffff800`00b9e7f0 fffff880`059729c4 : fffffa80`177886d0 fffffa80`17788606 fffffa80`16b95c00 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00b9e8e0 fffff880`05972c2d : fffffa80`16b95902 fffffa80`16b95900 fffffa80`16b95c90 00000000`00000005 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff800`00b9e970 fffff800`02c39681 : fffffa80`16b7eee3 00000000`00000000 fffffa80`16b95b01 fffffa80`16b7ec60 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff800`00b9ea00 fffff880`044136e7 : fffffa80`16ac2050 fffffa80`168be400 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00b9eaf0 fffff880`04413bcf : fffffa80`13cd0002 fffffa80`16b7ec60 00000000`00000000 fffffa80`133dc770 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x83f
fffff800`00b9ebc0 fffff880`044118fb : fffffa80`16ac2eb0 fffffa80`16ac21a0 fffffa80`16ac3050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00b9ec20 fffff880`04402f69 : fffffa80`16ac2050 00000000`00000000 fffffa80`16ac2e02 fffffa80`16ac2eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00b9ec60 fffff800`02c46cbc : fffff800`02dea180 fffffa80`16ac2eb0 fffffa80`16ac2ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ec90 fffff800`02c9d42a : fffff800`02dea180 fffff800`02dfa1c0 00000000`00000000 fffff880`04402d90 : nt!KiRetireDpcList+0x1bc
fffff800`00b9ed40 00000000`00000000 : fffff800`00b9f000 fffff800`00b99000 fffff800`00b9ed00 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002ef7300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8249
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 31693
Key : Analysis.Init.CPU.mSec
Value: 1468
Key : Analysis.Init.Elapsed.mSec
Value: 19728
Key : Analysis.Memory.CommitPeak.Mb
Value: 63
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: LeagueClient.e
DPC_STACK_BASE: FFFFF80000BA4FB0
TRAP_FRAME: fffff80000ba4780 -- (.trap 0xfffff80000ba4780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000680
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880048a610c rsp=fffff80000ba4910 rbp=fffff80000ba4979
r8=fffffa801720c900 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
vgk+0x4710c:
fffff880`048a610c ?? ???
Resetting default scope
STACK_TEXT:
fffff800`00ba37c8 fffff800`02cf10ee : 00000000`00000000 00000000`00000000 fffff800`00ba3f40 fffff800`02cb5de0 : nt!KeBugCheck
fffff800`00ba37d0 fffff800`02cf51fd : fffff800`02ed0388 fffff800`02e23634 fffff800`02c5a000 fffff800`00ba46d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba3800 fffff800`02cb5125 : fffff800`02e03988 fffff800`00ba3878 fffff800`00ba46d8 fffff800`02c5a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba3830 fffff800`02dd4eee : fffff800`00ba46d8 fffff800`00ba3f40 fffff800`00000000 fffffa80`1720c7b0 : nt!RtlDispatchException+0x415
fffff800`00ba3f10 fffff800`02cfc3c2 : fffff800`00ba46d8 fffff800`00ba4a70 fffff800`00ba4780 fffffa80`1720c900 : nt!KiDispatchException+0x17e
fffff800`00ba45a0 fffff800`02cf9c78 : 00000000`00000000 fffffa80`13940060 fffff800`40930000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00ba4780 fffff880`048a610c : fffff800`00ba4a70 fffff800`02c8d794 fffffa80`1720c900 00000000`00000042 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00ba4910 fffff800`00ba4a70 : fffff800`02c8d794 fffffa80`1720c900 00000000`00000042 fffff800`02e3e180 : vgk+0x4710c
fffff800`00ba4918 fffff800`02c8d794 : fffffa80`1720c900 00000000`00000042 fffff800`02e3e180 00000000`00000000 : 0xfffff800`00ba4a70
fffff800`00ba4920 fffffa80`176da5a0 : fffffa80`176d89e8 00000000`00000006 00000000`00000006 00000000`00000000 : nt!IopfCompleteRequest+0x454
fffff800`00ba4a10 fffffa80`176d89e8 : 00000000`00000006 00000000`00000006 00000000`00000000 00000000`00000000 : 0xfffffa80`176da5a0
fffff800`00ba4a18 00000000`00000006 : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`176d89e8
fffff800`00ba4a20 00000000`00000006 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`171da010 : 0x6
fffff800`00ba4a28 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`171da010 00000000`00000000 : 0x6
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002eb0300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8640
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 26575
Key : Analysis.Init.CPU.mSec
Value: 1453
Key : Analysis.Init.Elapsed.mSec
Value: 22444
Key : Analysis.Memory.CommitPeak.Mb
Value: 63
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff80000b9e510 -- (.trap 0xfffff80000b9e510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000683
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800725010c rsp=fffff80000b9e6a0 rbp=fffff80000b9e709
r8=fffffa800cb1a2e0 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
vgk+0x4710c:
fffff880`0725010c ?? ???
Resetting default scope
DPC_STACK_BASE: FFFFF80000BA4FB0
STACK_OVERFLOW: Stack Limit: fffff80000b9efb0. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff800`00b9d558 fffff800`02caa0ee : 00004b8a`0b860010 00000014`0d3f0006 fffff800`00b9dcd0 fffff800`02c6ede0 : nt!KeBugCheck
fffff800`00b9d560 fffff800`02cae1fd : fffff800`02e89388 fffff800`02ddc634 fffff800`02c13000 fffff800`00b9e468 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9d590 fffff800`02c6e125 : fffff800`02dbcb94 fffff800`00b9d608 fffff800`00b9e468 fffff800`02c13000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9d5c0 fffff800`02d8deee : fffff800`00b9e468 fffff800`00b9dcd0 fffff800`00000000 fffffa80`0cb1a190 : nt!RtlDispatchException+0x415
fffff800`00b9dca0 fffff800`02cb53c2 : fffff800`00b9e468 fffff800`00b9e800 fffff800`00b9e510 fffffa80`0cb1a2e0 : nt!KiDispatchException+0x17e
fffff800`00b9e330 fffff800`02cb2c78 : 00000000`00401902 fffff880`0f2c22d7 00000000`00000050 00000000`1bb634ea : nt!KiExceptionDispatch+0xc2
fffff800`00b9e510 fffff880`0725010c : fffff800`00b9e800 fffff800`02c46794 fffffa80`0cb1a2e0 00000000`00000002 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00b9e6a0 fffff800`00b9e800 : fffff800`02c46794 fffffa80`0cb1a2e0 00000000`00000002 fffff800`20707249 : vgk+0x4710c
fffff800`00b9e6a8 fffff800`02c46794 : fffffa80`0cb1a2e0 00000000`00000002 fffff800`20707249 00000000`00000000 : 0xfffff800`00b9e800
fffff800`00b9e6b0 fffffa80`0cb34500 : fffffa80`0cb26d38 00000000`00000006 00000000`00000006 00000000`00000000 : nt!IopfCompleteRequest+0x454
fffff800`00b9e7a0 fffffa80`0cb26d38 : 00000000`00000006 00000000`00000006 00000000`00000000 00000000`00000000 : 0xfffffa80`0cb34500
fffff800`00b9e7a8 00000000`00000006 : 00000000`00000006 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`0cb26d38
fffff800`00b9e7b0 00000000`00000006 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0c5ddc60 : 0x6
fffff800`00b9e7b8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0c5ddc60 00000000`00000000 : 0x6
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002ea7300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 7327
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 28382
Key : Analysis.Init.CPU.mSec
Value: 1296
Key : Analysis.Init.Elapsed.mSec
Value: 24253
Key : Analysis.Memory.CommitPeak.Mb
Value: 62
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
DPC_STACK_BASE: FFFFF80000BA4FB0
TRAP_FRAME: fffff80000ba4780 -- (.trap 0xfffff80000ba4780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000683
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007e6b10c rsp=fffff80000ba4910 rbp=fffff80000ba4979
r8=fffffa800cb1d800 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
vgk+0x4710c:
fffff880`07e6b10c ?? ???
Resetting default scope
STACK_TEXT:
fffff800`00ba37c8 fffff800`02ca10ee : 00000000`0000000a 00000000`00000000 fffff800`00ba3f40 fffff800`02c65de0 : nt!KeBugCheck
fffff800`00ba37d0 fffff800`02ca51fd : fffff800`02e80388 fffff800`02dd3634 fffff800`02c0a000 fffff800`00ba46d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba3800 fffff800`02c65125 : fffff800`02db3988 fffff800`00ba3878 fffff800`00ba46d8 fffff800`02c0a000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba3830 fffff800`02d84eee : fffff800`00ba46d8 fffff800`00ba3f40 fffff800`00000000 fffffa80`0cb1d6b0 : nt!RtlDispatchException+0x415
fffff800`00ba3f10 fffff800`02cac3c2 : fffff800`00ba46d8 fffff800`00ba4a70 fffff800`00ba4780 fffffa80`0cb1d800 : nt!KiDispatchException+0x17e
fffff800`00ba45a0 fffff800`02ca9c78 : fffff800`02dee180 fffff800`00000000 fffffa80`40370088 ffffffff`ff676980 : nt!KiExceptionDispatch+0xc2
fffff800`00ba4780 fffff880`07e6b10c : fffff800`00ba4a70 fffff880`0f4b9c08 fffffa80`0cb1d800 fffffa80`018af000 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00ba4910 fffff800`00ba4a70 : fffff880`0f4b9c08 fffffa80`0cb1d800 fffffa80`018af000 00000000`00610740 : vgk+0x4710c
fffff800`00ba4918 fffff880`0f4b9c08 : fffffa80`0cb1d800 fffffa80`018af000 00000000`00610740 fffff880`03e59189 : 0xfffff800`00ba4a70
fffff800`00ba4920 fffffa80`0cb1d800 : fffffa80`018af000 00000000`00610740 fffff880`03e59189 fffffa80`018af000 : nvlddmkm+0x1d3c08
fffff800`00ba4928 fffffa80`018af000 : 00000000`00610740 fffff880`03e59189 fffffa80`018af000 fffff880`0f4ba853 : 0xfffffa80`0cb1d800
fffff800`00ba4930 00000000`00610740 : fffff880`03e59189 fffffa80`018af000 fffff880`0f4ba853 00000000`00000004 : 0xfffffa80`018af000
fffff800`00ba4938 fffff880`03e59189 : fffffa80`018af000 fffff880`0f4ba853 00000000`00000004 fffff880`043aea5c : 0x610740
fffff800`00ba4940 fffff800`00ba49d0 : fffffa80`018af000 00000000`00000007 fffffa80`00040100 00000000`00000000 : USBPORT!USBPORT_ReleaseEpListLock+0x21
fffff800`00ba4970 fffffa80`018af000 : 00000000`00000007 fffffa80`00040100 00000000`00000000 fffffa80`0cb39db0 : 0xfffff800`00ba49d0
fffff800`00ba4978 00000000`00000007 : fffffa80`00040100 00000000`00000000 fffffa80`0cb39db0 00000000`00000001 : 0xfffffa80`018af000
fffff800`00ba4980 fffffa80`00040100 : 00000000`00000000 fffffa80`0cb39db0 00000000`00000001 fffffa80`0cb1d7f8 : 0x7
fffff800`00ba4988 00000000`00000000 : fffffa80`0cb39db0 00000000`00000001 fffffa80`0cb1d7f8 fffffa80`0cb1d7f4 : 0xfffffa80`00040100
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff88002fa4718
Arg3: fffff88002fa3f80
Arg4: fffff880012b8bce
Debugging Details:
------------------
GetUlongPtrFromAddress: unable to read from fffff80002eeb300
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 6046
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 26828
Key : Analysis.Init.CPU.mSec
Value: 1312
Key : Analysis.Init.Elapsed.mSec
Value: 5555
Key : Analysis.Memory.CommitPeak.Mb
Value: 67
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 24
BUGCHECK_P1: 1904fb
BUGCHECK_P2: fffff88002fa4718
BUGCHECK_P3: fffff88002fa3f80
BUGCHECK_P4: fffff880012b8bce
EXCEPTION_RECORD: fffff88002fa4718 -- (.exr 0xfffff88002fa4718)
ExceptionAddress: fffff880012b8bce (Ntfs!NtfsFullDeleteLcb+0x00000000000000be)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88002fa3f80 -- (.cxr 0xfffff88002fa3f80)
rax=fffff8a0035fcb60 rbx=fffff88002fa49c8 rcx=ffbff8a0035fcb60
rdx=0000000000000001 rsi=0000000000000000 rdi=fffff8a0035fcf68
rip=fffff880012b8bce rsp=fffff88002fa4950 rbp=0000000000000000
r8=fffffa8017b3c018 r9=0000000000000000 r10=fffff80002c4e000
r11=0000000000000001 r12=fffff8a0035fcb40 r13=fffff8a0057bebc0
r14=fffff8a0035fce00 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
Ntfs!NtfsFullDeleteLcb+0xbe:
fffff880`012b8bce 48894108 mov qword ptr [rcx+8],rax ds:002b:ffbff8a0`035fcb68=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
READ_ADDRESS: Unable to get MmSystemRangeStart
GetUlongPtrFromAddress: unable to read from fffff80002eeb2f0
GetUlongPtrFromAddress: unable to read from fffff80002eeb4a8
ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek u olamaz %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
EXCEPTION_STR: 0xc0000005
STACK_TEXT:
fffff880`02fa4950 fffff880`01234159 : fffff8a0`035fcb40 fffff800`02e5e7a0 fffff880`02fa4b01 fffff880`012bbdbb : Ntfs!NtfsFullDeleteLcb+0xbe
fffff880`02fa4980 fffff880`012b9b0c : fffffa80`0e1c7cf0 fffffa80`12fb2180 fffff8a0`035fcb40 fffff8a0`035fced8 : Ntfs!NtfsTeardownFromLcb+0x129
fffff880`02fa4a10 fffff880`0123cb82 : fffffa80`0e1c7cf0 fffffa80`0e1c7cf0 fffff8a0`035fcb40 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xcc
fffff880`02fa4a90 fffff880`012c9403 : fffffa80`0e1c7cf0 fffff800`02e5e7a0 fffff8a0`035fcb40 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`02fa4ad0 fffff880`0131c772 : fffffa80`0e1c7cf0 fffff8a0`035fcc70 fffff8a0`035fcb40 fffffa80`12fb2180 : Ntfs!NtfsCommonClose+0x353
fffff880`02fa4ba0 fffff800`02c91dc9 : 00000000`00000000 fffff800`02f57b01 fffffa80`027cf000 fffff800`00000002 : Ntfs!NtfsFspCloseInternal+0x186
fffff880`02fa4c70 fffff800`02f8d2e8 : 00000000`00000000 fffff880`009e7180 00000000`00000080 00000000`00000001 : nt!ExpWorkerThread+0x111
fffff880`02fa4d00 fffff800`02ce7ec6 : fffff880`009e7180 fffffa80`027cf040 fffff880`009f60c0 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`02fa4d40 00000000`00000000 : fffff880`02fa5000 fffff880`02f9f000 fffff880`02fa49a0 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_NAME: Ntfs!NtfsFullDeleteLcb+be
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
IMAGE_VERSION: 6.1.7601.24382
STACK_COMMAND: .cxr 0xfffff88002fa3f80 ; kb
FAILURE_BUCKET_ID: 0x24_Ntfs!NtfsFullDeleteLcb+be
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {ac474f9e-e2bc-740f-6538-af86d2c7fb3e}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002eb3300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 7312
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 27458
Key : Analysis.Init.CPU.mSec
Value: 1327
Key : Analysis.Init.Elapsed.mSec
Value: 27307
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
DPC_STACK_BASE: FFFFF80000BA4FB0
TRAP_FRAME: fffff80000ba4780 -- (.trap 0xfffff80000ba4780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=0000000000000683
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880072ab10c rsp=fffff80000ba4910 rbp=fffff80000ba4979
r8=fffffa800d1a8f30 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
vgk+0x4710c:
fffff880`072ab10c ?? ???
Resetting default scope
STACK_TEXT:
fffff800`00ba37c8 fffff800`02cad0ee : 00000000`0000000d 00000000`00000000 fffff800`00ba3f40 fffff800`02c71de0 : nt!KeBugCheck
fffff800`00ba37d0 fffff800`02cb11fd : fffff800`02e8c388 fffff800`02ddf634 fffff800`02c16000 fffff800`00ba46d8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba3800 fffff800`02c71125 : fffff800`02dbf988 fffff800`00ba3878 fffff800`00ba46d8 fffff800`02c16000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba3830 fffff800`02d90eee : fffff800`00ba46d8 fffff800`00ba3f40 fffff800`00000000 fffffa80`0d1a8de0 : nt!RtlDispatchException+0x415
fffff800`00ba3f10 fffff800`02cb83c2 : fffff800`00ba46d8 fffff800`00ba4a70 fffff800`00ba4780 fffffa80`0d1a8f30 : nt!KiDispatchException+0x17e
fffff800`00ba45a0 fffff800`02cb5c78 : ff000000`00000000 ffffc400`18ae5f07 00000001`40d02a89 00000000`00000002 : nt!KiExceptionDispatch+0xc2
fffff800`00ba4780 fffff880`072ab10c : fffff800`00ba4a70 fffff880`0f262c08 fffffa80`0d1a8f30 fffffa80`0c273000 : nt!KiGeneralProtectionFault+0x2f8
fffff800`00ba4910 fffff800`00ba4a70 : fffff880`0f262c08 fffffa80`0d1a8f30 fffffa80`0c273000 00000000`00610740 : vgk+0x4710c
fffff800`00ba4918 fffff880`0f262c08 : fffffa80`0d1a8f30 fffffa80`0c273000 00000000`00610740 fffff880`0f15859e : 0xfffff800`00ba4a70
fffff800`00ba4920 fffffa80`0d1a8f30 : fffffa80`0c273000 00000000`00610740 fffff880`0f15859e fffffa80`0c273000 : nvlddmkm+0x1d3c08
fffff800`00ba4928 fffffa80`0c273000 : 00000000`00610740 fffff880`0f15859e fffffa80`0c273000 fffff880`0f263853 : 0xfffffa80`0d1a8f30
fffff800`00ba4930 00000000`00610740 : fffff880`0f15859e fffffa80`0c273000 fffff880`0f263853 00000000`00000004 : 0xfffffa80`0c273000
fffff800`00ba4938 fffff880`0f15859e : fffffa80`0c273000 fffff880`0f263853 00000000`00000004 fffff880`0427aa5c : 0x610740
fffff800`00ba4940 fffffa80`0c273000 : fffff880`0f263853 00000000`00000004 fffff880`0427aa5c fffff800`02c52760 : nvlddmkm+0xc959e
fffff800`00ba4948 fffff880`0f263853 : 00000000`00000004 fffff880`0427aa5c fffff800`02c52760 fffff800`00ba49d0 : 0xfffffa80`0c273000
fffff800`00ba4950 00000000`00000004 : fffff880`0427aa5c fffff800`02c52760 fffff800`00ba49d0 fffffa80`0c273000 : nvlddmkm+0x1d4853
fffff800`00ba4958 fffff880`0427aa5c : fffff800`02c52760 fffff800`00ba49d0 fffffa80`0c273000 00000000`00000007 : 0x4
fffff800`00ba4960 fffff880`019d3c79 : fffffa80`0d1ab060 fffffa80`0d1a8f18 fffffa80`0d1a8f30 fffff800`00ba4a70 : HIDPARSE!HidP_GetUsages+0x78
fffff800`00ba49e0 fffff800`02c49681 : fffffa80`0c9f3813 fffff800`00000000 00000000`00000000 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x69d
fffff800`00ba4a60 fffff880`02de99c4 : fffffa80`0d1bc210 fffffa80`0d1bc206 fffffa80`0d19d100 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00ba4b50 fffff880`02de9c2d : fffffa80`0d1b6e02 fffffa80`0d1b6e40 fffffa80`0d19d1d0 00000000`00000005 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff800`00ba4be0 fffff800`02c49681 : fffffa80`0d14b9c3 00000000`00000000 fffffa80`0d19d001 fffffa80`0d14b740 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff800`00ba4c70 fffff880`03d796e7 : fffffa80`0c444050 fffffa80`0c9ce000 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`00ba4d60 fffff880`03d79bcf : fffffa80`0d137402 fffffa80`0d14b740 00000000`00000000 fffffa80`0d48c4a0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x83f
fffff800`00ba4e30 fffff880`03d778fb : fffffa80`0c444eb0 fffffa80`0c4441a0 fffffa80`0c445050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`00ba4e90 fffff880`03d68f69 : fffffa80`0c444050 00000000`00000000 fffffa80`0c444e02 fffffa80`0c444eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`00ba4ed0 fffff800`02c56cbc : fffff800`02dfa180 fffffa80`0c444eb0 fffffa80`0c444ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00ba4f00 fffff800`02cac5e5 : 00000000`00000000 fffffa80`018d2660 00000000`00000000 fffff880`03d68d90 : nt!KiRetireDpcList+0x1bc
fffff800`00ba4fb0 fffff800`02cac3fc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`031081e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
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:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff80002efc300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6265
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 25772
Key : Analysis.Init.CPU.mSec
Value: 1311
Key : Analysis.Init.Elapsed.mSec
Value: 29517
Key : Analysis.Memory.CommitPeak.Mb
Value: 65
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-01-02T17:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24545
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff80004087510 -- (.trap 0xfffff80004087510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000681
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88006e5a10c rsp=fffff800040876a0 rbp=fffff80004087709
r8=fffffa800c7282e0 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
vgk+0x4710c:
fffff880`06e5a10c ?? ???
Resetting default scope
DPC_STACK_BASE: FFFFF8000408DFB0
STACK_OVERFLOW: Stack Limit: fffff80004087fb0. Use (kF) and (!stackusage) to investigate stack usage.
STACK_TEXT:
fffff800`04086558 fffff800`02cf60ee : 00000000`00000000 00000000`00000000 fffff800`04086cd0 fffff800`02cbade0 : nt!KeBugCheck
fffff800`04086560 fffff800`02cfa1fd : fffff800`02ed5388 fffff800`02e28634 fffff800`02c5f000 fffff800`04087468 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`04086590 fffff800`02cba125 : fffff800`02e08b94 fffff800`04086608 fffff800`04087468 fffff800`02c5f000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`040865c0 fffff800`02dd9eee : fffff800`04087468 fffff800`04086cd0 fffff800`00000000 fffffa80`0c728190 : nt!RtlDispatchException+0x415
fffff800`04086ca0 fffff800`02d013c2 : fffff800`04087468 fffff800`04087800 fffff800`04087510 fffffa80`0c7282e0 : nt!KiDispatchException+0x17e
fffff800`04087330 fffff800`02cfec78 : 00000000`00000104 fffff880`0f3072d7 00000000`00000020 fffff800`04087540 : nt!KiExceptionDispatch+0xc2
fffff800`04087510 fffff880`06e5a10c : fffff800`04087800 fffff880`0f2a6c08 fffffa80`0c7282e0 fffffa80`018f2000 : nt!KiGeneralProtectionFault+0x2f8
fffff800`040876a0 fffff800`04087800 : fffff880`0f2a6c08 fffffa80`0c7282e0 fffffa80`018f2000 00000000`00610740 : vgk+0x4710c
fffff800`040876a8 fffff880`0f2a6c08 : fffffa80`0c7282e0 fffffa80`018f2000 00000000`00610740 fffff880`0f19c59e : 0xfffff800`04087800
fffff800`040876b0 fffffa80`0c7282e0 : fffffa80`018f2000 00000000`00610740 fffff880`0f19c59e fffffa80`018f2000 : nvlddmkm+0x1d3c08
fffff800`040876b8 fffffa80`018f2000 : 00000000`00610740 fffff880`0f19c59e fffffa80`018f2000 fffff880`0f2a7853 : 0xfffffa80`0c7282e0
fffff800`040876c0 00000000`00610740 : fffff880`0f19c59e fffffa80`018f2000 fffff880`0f2a7853 00000000`00000004 : 0xfffffa80`018f2000
fffff800`040876c8 fffff880`0f19c59e : fffffa80`018f2000 fffff880`0f2a7853 00000000`00000004 fffff880`03e53a5c : 0x610740
fffff800`040876d0 fffffa80`018f2000 : fffff880`0f2a7853 00000000`00000004 fffff880`03e53a5c fffff800`02c9b760 : nvlddmkm+0xc959e
fffff800`040876d8 fffff880`0f2a7853 : 00000000`00000004 fffff880`03e53a5c fffff800`02c9b760 fffff800`04087760 : 0xfffffa80`018f2000
fffff800`040876e0 00000000`00000004 : fffff880`03e53a5c fffff800`02c9b760 fffff800`04087760 fffffa80`018f2000 : nvlddmkm+0x1d4853
fffff800`040876e8 fffff880`03e53a5c : fffff800`02c9b760 fffff800`04087760 fffffa80`018f2000 00000000`00000007 : 0x4
fffff800`040876f0 fffff880`03e5dc79 : fffffa80`0c728cf0 fffffa80`0c7282c8 fffffa80`0c7282e0 fffff800`04087800 : HIDPARSE!HidP_GetUsages+0x78
fffff800`04087770 fffff800`02c92681 : fffffa80`0c5c6323 fffff800`00000000 00000000`00000000 fffff880`00000000 : mouhid!MouHid_ReadComplete+0x69d
fffff800`040877f0 fffff880`03e3d9c4 : fffffa80`0c673600 fffffa80`0c673506 fffffa80`0c678100 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`040878e0 fffff880`03e3dc2d : fffffa80`0c678602 fffffa80`0c678630 fffffa80`0c6781d0 00000000`00000005 : HIDCLASS!HidpDistributeInterruptReport+0x130
fffff800`04087970 fffff800`02c92681 : fffffa80`0c226953 00000000`00000000 fffffa80`0c678001 fffffa80`0c2266d0 : HIDCLASS!HidpInterruptReadComplete+0x235
fffff800`04087a00 fffff880`03c136e7 : fffffa80`0c093050 fffffa80`0d569500 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff800`04087af0 fffff880`03c13bcf : fffffa80`0c08ac02 fffffa80`0c2266d0 00000000`00000000 fffffa80`0c72f5e0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x83f
fffff800`04087bc0 fffff880`03c118fb : fffffa80`0c093eb0 fffffa80`0c0931a0 fffffa80`0c094050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff800`04087c20 fffff880`03c02f69 : fffffa80`0c093050 00000000`00000000 fffffa80`0c093e02 fffffa80`0c093eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff800`04087c60 fffff800`02c9fcbc : fffff800`02e43180 fffffa80`0c093eb0 fffffa80`0c093ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`04087c90 fffff800`02cf642a : fffff800`02e43180 fffff800`02e531c0 00000000`00000000 fffff880`03c02d90 : nt!KiRetireDpcList+0x1bc
fffff800`04087d40 00000000`00000000 : fffff800`04088000 fffff800`04082000 fffff800`04087d00 00000000`00000000 : nt!KiIdleLoop+0x5a
SYMBOL_NAME: vgk+4710c
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4710c
OS_VERSION: 7.1.7601.24545
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c8392e90-cf2e-cfc3-1d7e-7ac7693a3b59}
Followup: MachineOwner
---------
