Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Spiele\steamapps\temp\020519-7625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`1ce03000 PsLoadedModuleList = 0xfffff804`1d21ead0
Debug session time: Tue Feb 5 20:04:42.192 2019 (UTC + 1:00)
System Uptime: 0 days 23:54:10.985
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff8041d345380}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded 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: TickPeriods ***
*** ***
*************************************************************************
Probably caused by : dxgmms2.sys ( dxgmms2!memset+78 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8041d345380, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17763.292 (WinBuild.160101.0800)
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P1.40
BIOS_DATE: 11/25/2015
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: H170A-X1/3.1
BASEBOARD_VERSION:
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8041d345380
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: Corsair.Servic
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: DESKTOP-KM75KH7
ANALYSIS_SESSION_TIME: 02-05-2019 20:43:22.0443
ANALYSIS_VERSION: 10.0.17134.12 amd64fre
LAST_CONTROL_TRANSFER: from fffff8041d059145 to fffff8041cfb6440
STACK_TEXT:
fffff804`1cbc8ba8 fffff804`1d059145 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`1cbc8bb0 fffff804`1cf26daf : 00003a2b`71a6777b fffff804`1b385180 00000000`00000286 00000000`005408bf : nt!KeAccumulateTicks+0x12ed25
fffff804`1cbc8c10 fffff804`1d87547c : 00000000`00000000 fffff804`1d8db6e0 fffff804`1cbc1540 fffff804`1d8db790 : nt!KeClockInterruptNotify+0xcf
fffff804`1cbc8f30 fffff804`1ce458b5 : fffff804`1d8db6e0 fffff804`1cfb7a0c fffff804`1cbc1540 ffffa081`daaada00 : hal!HalpTimerClockIpiRoutine+0x1c
fffff804`1cbc8f60 fffff804`1cfb7e3a : fffff804`1cbc1540 fffff804`1d8db6e0 00000000`0000fffd ffff8106`e9b72170 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`1cbc8fb0 fffff804`1cfb8387 : ffff8106`ed64a9f0 ffff8106`ed64ab38 00000000`00000745 00000000`7073534b : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804`1cbc14c0 fffff80b`7e7491f8 : fffff80b`7e73bc1e ffff8106`e9c2deb8 ffff8106`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804`1cbc1658 fffff80b`7e73bc1e : ffff8106`e9c2deb8 ffff8106`00000000 00000000`00000000 fffff80b`7ac52053 : dxgmms2!memset+0x78
fffff804`1cbc1660 fffff80b`7e734416 : ffff8106`e9b20000 00000000`00000000 ffff8106`e5b99030 fffff804`1cfb2850 : dxgmms2!VidSchiProcessDpcVSyncCookie+0x4e
fffff804`1cbc1920 fffff80b`7c144452 : fffff804`1cbc1a19 fffff80b`7fe80304 00000000`00000000 00000000`0000fffd : dxgmms2!VidSchDdiNotifyDpc+0x346
fffff804`1cbc19d0 fffff80b`7fe2b114 : ffff8106`e5b99030 00000000`00000000 ffff8106`e5b99030 ffff8106`e5e82000 : dxgkrnl!DxgNotifyDpcCB+0x92
fffff804`1cbc1a80 ffff8106`e5b99030 : 00000000`00000000 ffff8106`e5b99030 ffff8106`e5e82000 fffff80b`7fe2b0a7 : nvlddmkm+0x12b114
fffff804`1cbc1a88 00000000`00000000 : ffff8106`e5b99030 ffff8106`e5e82000 fffff80b`7fe2b0a7 ffff8106`e5e82000 : 0xffff8106`e5b99030
THREAD_SHA1_HASH_MOD_FUNC: 7863d03aa195b3e982ca9c6cea21c4ae9e43ad3f
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 633e667ff359173ca086630ff641ce8675c7079e
THREAD_SHA1_HASH_MOD: 9db674559870227959b7d85d01c09f61ac2a33c6
FOLLOWUP_IP:
dxgmms2!memset+78
fffff80b`7e7491f8 0f1101 movups xmmword ptr [rcx],xmm0
FAULT_INSTR_CODE: 4c01110f
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: dxgmms2!memset+78
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.17763.55
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 78
FAILURE_BUCKET_ID: 0x133_DPC_dxgmms2!memset
BUCKET_ID: 0x133_DPC_dxgmms2!memset
PRIMARY_PROBLEM_CLASS: 0x133_DPC_dxgmms2!memset
TARGET_TIME: 2019-02-05T19:04:42.000Z
OSBUILD: 17763
OSSERVICEPACK: 292
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: unknown_date
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17763.292
ANALYSIS_SESSION_ELAPSED_TIME: b43
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_dpc_dxgmms2!memset
FAILURE_ID_HASH: {55079073-b97d-152f-752f-944664b25131}
Followup: MachineOwner
---------
