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 atikmdag.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 fffff800038bc300
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707
SYSTEM_MANUFACTURER: To be filled by O.E.M.
SYSTEM_PRODUCT_NAME: To be filled by O.E.M.
SYSTEM_SKU: SKU
SYSTEM_VERSION: To be filled by O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 2501
BIOS_DATE: 04/07/2014
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: M5A99FX PRO R2.0
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 4
CPU_MHZ: f3d
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 1
CPU_STEPPING: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-18V31A3
ANALYSIS_SESSION_TIME: 02-18-2020 16:07:37.0487
ANALYSIS_VERSION: 10.0.18362.1 x86fre
EXCEPTION_RECORD: fffff880009f2338 -- (.exr 0xfffff880009f2338)
ExceptionAddress: fffff880043a3f7d (dxgmms1!VidSchiProcessDpcVSyncCookie+0x00000000000000e9)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
TRAP_FRAME: fffff880009f23e0 -- (.trap 0xfffff880009f23e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043a3f7d rsp=fffff880009f2570 rbp=fffffa800a34d9a0
r8=0000000000000000 r9=0000000000000000 r10=fffffa800a34c1f0
r11=fffff880009f2628 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9:
fffff880`043a3f7d 48f7f1 div rax,rcx
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800036b60ee to fffff800036b2e70
STACK_TEXT:
fffff880`009f1428 fffff800`036b60ee : 00000000`00000000 00000000`00000000 fffff880`009f1ba0 fffff800`0367ade0 : nt!KeBugCheck
fffff880`009f1430 fffff800`036ba1fd : fffff800`03895388 fffff800`037e8634 fffff800`0361f000 fffff880`009f2338 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009f1460 fffff800`0367a125 : fffff800`037c8b94 fffff880`009f14d8 fffff880`009f2338 fffff800`0361f000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009f1490 fffff800`03799eee : fffff880`009f2338 fffff880`009f1ba0 fffff880`00000000 fffffa80`00000004 : nt!RtlDispatchException+0x415
fffff880`009f1b70 fffff800`036c13c2 : fffff880`009f2338 fffffa80`0a21c410 fffff880`009f23e0 00000000`00000000 : nt!KiDispatchException+0x17e
fffff880`009f2200 fffff800`036bc1e2 : fffffa80`00000002 fffffa80`09ed4ce0 fffffa80`0a34c000 fffff880`043a9769 : nt!KiExceptionDispatch+0xc2
fffff880`009f23e0 fffff880`043a3f7d : fffffa80`0a21c410 00000000`00000000 fffffa80`0a34c000 fffffa80`0a468710 : nt!KiDivideErrorFault+0x2e2
fffff880`009f2570 fffff880`043a3d24 : fffff880`00000000 fffffa80`00000022 fffffa80`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcVSyncCookie+0xe9
fffff880`009f2630 fffff880`043a3c88 : 000000f4`03fc0000 fffffa80`0a21c410 fffffa80`078c03e0 fffffa80`078c06c8 : dxgmms1!VidSchDdiNotifyDpcWorker+0x80
fffff880`009f2680 fffff880`042a91cf : fffffa80`081b5040 00000000`00000000 00000000`00000001 fffffa80`078c06c8 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`009f26d0 fffff880`11198eb7 : fffffa80`078c03e0 fffffa80`078c03e0 000000f4`03fc0000 fffffa80`078c03e0 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`009f2700 fffffa80`078c03e0 : fffffa80`078c03e0 000000f4`03fc0000 fffffa80`078c03e0 00000000`00000000 : atikmdag+0xcaeb7
fffff880`009f2708 fffffa80`078c03e0 : 000000f4`03fc0000 fffffa80`078c03e0 00000000`00000000 fffff880`009f2760 : 0xfffffa80`078c03e0
fffff880`009f2710 000000f4`03fc0000 : fffffa80`078c03e0 00000000`00000000 fffff880`009f2760 00000000`00000000 : 0xfffffa80`078c03e0
fffff880`009f2718 fffffa80`078c03e0 : 00000000`00000000 fffff880`009f2760 00000000`00000000 00000000`00000000 : 0x000000f4`03fc0000
fffff880`009f2720 00000000`00000000 : fffff880`009f2760 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`078c03e0
THREAD_SHA1_HASH_MOD_FUNC: 2df6cf70641b455bff5b51f38841351a51a58ca2
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 83d9e26f91db6b761d2324d7f0e37ae930eb7437
THREAD_SHA1_HASH_MOD: 8e360ce24f604d9f5968fee6e125f1d35ee72d1c
FOLLOWUP_IP:
dxgmms1!VidSchiProcessDpcVSyncCookie+e9
fffff880`043a3f7d 48f7f1 div rax,rcx
FAULT_INSTR_CODE: 48f1f748
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms1!VidSchiProcessDpcVSyncCookie+e9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5d5222c1
IMAGE_VERSION: 6.1.7601.24513
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
BUCKET_ID: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
PRIMARY_PROBLEM_CLASS: X64_0x1E_dxgmms1!VidSchiProcessDpcVSyncCookie+e9
TARGET_TIME: 2020-02-18T12:42:39.000Z
OSBUILD: 7601
OSSERVICEPACK: 1000
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
OSEDITION: Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2020-01-03 05:56:30
BUILDDATESTAMP_STR: 200102-1707
BUILDLAB_STR: win7sp1_ldr_escrow
BUILDOSVER_STR: 6.1.7601.24545.amd64fre.win7sp1_ldr_escrow.200102-1707
ANALYSIS_SESSION_ELAPSED_TIME: 111d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x1e_dxgmms1!vidschiprocessdpcvsynccookie+e9
FAILURE_ID_HASH: {563df3f2-b5ac-cd6b-d157-580c3b7f02da}
Followup: MachineOwner
---------
