Forceflow
New Member
- Joined
- May 13, 2018
- Messages
- 9 (0.00/day)
Can't really pin down when it happens, but I've experienced some hard crashes using the latest GPU-Z and the latest Nvidia Drivers. I can usually trigger it by launching Vermintide 2 with GPU-Z open.
Here's the WinDBG analysis. I can provide minidump file if needed.
Here's the WinDBG analysis. I can provide minidump file if needed.
Code:
Microsoft (R) Windows Debugger Version 10.0.17134.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\jerba\Downloads\051318-6937-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 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`77614000 PsLoadedModuleList = 0xfffff801`779d11d0
Debug session time: Sun May 13 16:39:02.591 2018 (UTC + 2:00)
System Uptime: 0 days 0:01:23.473
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, fffff80179f3de50, ffffc28235838fc0, fffff8017766e92f}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1fa953 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff80179f3de50
Arg3: ffffc28235838fc0
Arg4: fffff8017766e92f
Debugging Details:
------------------
KEY_VALUES_STRING: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7A12
SYSTEM_SKU: Default string
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.90
BIOS_DATE: 01/25/2018
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: Z170A GAMING PRO CARBON (MS-7A12)
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: 8
BUGCHECK_P2: fffff80179f3de50
BUGCHECK_P3: ffffc28235838fc0
BUGCHECK_P4: fffff8017766e92f
BUGCHECK_STR: 0x7f_8
TRAP_FRAME: fffff80179f3de50 -- (.trap 0xfffff80179f3de50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc28235839180 rbx=0000000000000000 rcx=ffffc28235839060
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8017766e92f rsp=ffffc28235838fc0 rbp=0000000000000000
r8=0000000000000020 r9=0000000000000000 r10=0000000000000091
r11=ffffc282358390c8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!EtwWriteEx+0x4f:
fffff801`7766e92f e8cc111500 call nt!memset (fffff801`777bfb00)
Resetting default scope
CPU_COUNT: 8
CPU_MHZ: fa8
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: BE'00000000 (cache) BE'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: GPU-Z.2.9.0.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: CORELLIA
ANALYSIS_SESSION_TIME: 05-13-2018 18:15:17.0940
ANALYSIS_VERSION: 10.0.17134.1 amd64fre
STACK_OVERFLOW: Stack Limit: ffffc28235839000. Use (kF) and (!stackusage) to investigate stack usage.
LAST_CONTROL_TRANSFER: from fffff801777be829 to fffff801777ab670
STACK_TEXT:
fffff801`79f3dd08 fffff801`777be829 : 00000000`0000007f 00000000`00000008 fffff801`79f3de50 ffffc282`35838fc0 : nt!KeBugCheckEx
fffff801`79f3dd10 fffff801`777b93ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff801`79f3de50 fffff801`7766e92f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0x32c
ffffc282`35838fc0 fffff801`7766e8cc : 00000000`00000000 00000000`00000000 00000000`00000000 fffff801`7766e9bf : nt!EtwWriteEx+0x4f
ffffc282`358390d0 fffff80f`07e5a953 : 00000000`00000000 00000000`00000000 000000dc`04010401 00000000`207c0080 : nt!EtwWrite+0x2c
ffffc282`35839120 00000000`00000000 : 00000000`00000000 000000dc`04010401 00000000`207c0080 ffffc282`35839180 : nvlddmkm+0x1fa953
THREAD_SHA1_HASH_MOD_FUNC: 20e2fc4436fdad8b1b950799298da9a5844b9cba
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 600086b9554c4d7a7f3a703bf2dda5841bc916ae
THREAD_SHA1_HASH_MOD: f2113cf119696bbdf4b93f6a6ccb797757579413
FOLLOWUP_IP:
nvlddmkm+1fa953
fffff80f`07e5a953 4883c438 add rsp,38h
FAULT_INSTR_CODE: 38c48348
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: nvlddmkm+1fa953
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5af0a4c9
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1fa953
FAILURE_BUCKET_ID: 0x7f_8_nvlddmkm!unknown_function
BUCKET_ID: 0x7f_8_nvlddmkm!unknown_function
PRIMARY_PROBLEM_CLASS: 0x7f_8_nvlddmkm!unknown_function
TARGET_TIME: 2018-05-13T14:39:02.000Z
OSBUILD: 17134
OSSERVICEPACK: 48
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-04-28 05:58:00
BUILDDATESTAMP_STR: 180410-1804
BUILDLAB_STR: rs4_release
BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
ANALYSIS_SESSION_ELAPSED_TIME: 172b3
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7f_8_nvlddmkm!unknown_function
FAILURE_ID_HASH: {1e2b201d-3868-7883-c455-91a3ec283c76}
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff80179f3de50
Arg3: ffffc28235838fc0
Arg4: fffff8017766e92f
Debugging Details:
------------------