Question Dump File Help - PC Shutting Off/Requires Restart Randomly

[VanquishHorrors]

This is a problem I've had for a while now. My PC often shuts down/requires a restart randomly for some reason. Most of the time, this happens when I'm watching video or playing games (almost always 2D games, not resource-heavy 3D ones). I tried diagnosing this problem with a friend sometime back and thought it was a PSU issue, for which I got a replacement unit through warranty. But as it turns out, it wasn't the PSU and whatever caused it is still around.

Can anybody help with this? I included my dump file from the last shutdown a few hours ago and a bugchecker output copy-paste. Thanks in advance!

Spoiler: Dump File

011724-6859-01.dmp

drive.google.com

Spoiler: Bugchecker Output

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff998872410460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80283646730, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_IMAGE_DOS_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_EPROCESS ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt!_KPRCB ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 15

Key : Analysis.Elapsed.mSec
Value: 3044

Key : Analysis.IO.Other.Mb
Value: 7

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 10

Key : Analysis.Init.CPU.mSec
Value: 124

Key : Analysis.Init.Elapsed.mSec
Value: 1485840

Key : Analysis.Memory.CommitPeak.Mb
Value: 69

Key : Bugcheck.Code.LegacyAPI
Value: 0x116

Key : Failure.Bucket
Value: WRONG_SYMBOLS_X64_22621.2506.amd64fre.ni_release_svc_prod3.231018-1809_TIMESTAMP_16B96037_nt_wrong_symbols!16B960371047000

Key : Failure.Hash
Value: {5ac8c634-971d-7870-a36b-569c4d60974c}

Key : WER.OS.Branch
Value: ni_release_svc_prod3

Key : WER.OS.Version
Value: 10.0.22621.2506


BUGCHECK_CODE: 116

BUGCHECK_P1: ffff998872410460

BUGCHECK_P2: fffff80283646730

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: 011724-6859-01.dmp

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

WRONG_SYMBOLS_TIMESTAMP: 16b96037

WRONG_SYMBOLS_SIZE: 1047000

FAULTING_MODULE: fffff8025c400000 nt

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffff9787`9f99f128 fffff802`75d01a5e : 00000000`00000116 ffff9988`72410460 fffff802`83646730 ffffffff`c000009a : nt!KeBugCheckEx
ffff9787`9f99f130 00000000`00000116 : ffff9988`72410460 fffff802`83646730 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x301a5e
ffff9787`9f99f138 ffff9988`72410460 : fffff802`83646730 ffffffff`c000009a 00000000`00000004 00000000`01000000 : 0x116
ffff9787`9f99f140 fffff802`83646730 : ffffffff`c000009a 00000000`00000004 00000000`01000000 ffff9988`72410460 : 0xffff9988`72410460
ffff9787`9f99f148 ffffffff`c000009a : 00000000`00000004 00000000`01000000 ffff9988`72410460 fffff802`75cb18b2 : nvlddmkm+0x10f6730
ffff9787`9f99f150 00000000`00000004 : 00000000`01000000 ffff9988`72410460 fffff802`75cb18b2 fffff802`83646730 : 0xffffffff`c000009a
ffff9787`9f99f158 00000000`01000000 : ffff9988`72410460 fffff802`75cb18b2 fffff802`83646730 ffff9988`6e0d86e0 : 0x4
ffff9787`9f99f160 ffff9988`72410460 : fffff802`75cb18b2 fffff802`83646730 ffff9988`6e0d86e0 00000000`00000080 : 0x1000000
ffff9787`9f99f168 fffff802`75cb18b2 : fffff802`83646730 ffff9988`6e0d86e0 00000000`00000080 ffff9988`6e0d87a0 : 0xffff9988`72410460
ffff9787`9f99f170 fffff802`83646730 : ffff9988`6e0d86e0 00000000`00000080 ffff9988`6e0d87a0 00000000`01000000 : dxgkrnl+0x2b18b2
ffff9787`9f99f178 ffff9988`6e0d86e0 : 00000000`00000080 ffff9988`6e0d87a0 00000000`01000000 fffff802`75ca950d : nvlddmkm+0x10f6730
ffff9787`9f99f180 00000000`00000080 : ffff9988`6e0d87a0 00000000`01000000 fffff802`75ca950d ffff9988`6e103000 : 0xffff9988`6e0d86e0
ffff9787`9f99f188 ffff9988`6e0d87a0 : 00000000`01000000 fffff802`75ca950d ffff9988`6e103000 ffff9988`7d074040 : 0x80
ffff9787`9f99f190 00000000`01000000 : fffff802`75ca950d ffff9988`6e103000 ffff9988`7d074040 ffff9988`6e103b50 : 0xffff9988`6e0d87a0
ffff9787`9f99f198 fffff802`75ca950d : ffff9988`6e103000 ffff9988`7d074040 ffff9988`6e103b50 ffff9988`6e103b50 : 0x1000000
ffff9787`9f99f1a0 ffff9988`6e103000 : ffff9988`7d074040 ffff9988`6e103b50 ffff9988`6e103b50 00000000`00000000 : dxgkrnl+0x2a950d
ffff9787`9f99f1a8 ffff9988`7d074040 : ffff9988`6e103b50 ffff9988`6e103b50 00000000`00000000 ffff9787`98f11000 : 0xffff9988`6e103000
ffff9787`9f99f1b0 ffff9988`6e103b50 : ffff9988`6e103b50 00000000`00000000 ffff9787`98f11000 ffff9787`98f16ec0 : 0xffff9988`7d074040
ffff9787`9f99f1b8 ffff9988`6e103b50 : 00000000`00000000 ffff9787`98f11000 ffff9787`98f16ec0 00000000`00000000 : 0xffff9988`6e103b50
ffff9787`9f99f1c0 00000000`00000000 : ffff9787`98f11000 ffff9787`98f16ec0 00000000`00000000 ffff9988`7d074180 : 0xffff9988`6e103b50


STACK_COMMAND: .cxr; .ecxr ; kb

EXCEPTION_CODE_STR: 16B96037

EXCEPTION_STR: WRONG_SYMBOLS

PROCESS_NAME: ntoskrnl.wrong.symbols.exe

IMAGE_NAME: ntoskrnl.wrong.symbols.exe

MODULE_NAME: nt_wrong_symbols

SYMBOL_NAME: nt_wrong_symbols!16B960371047000

FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_22621.2506.amd64fre.ni_release_svc_prod3.231018-1809_TIMESTAMP_16B96037_nt_wrong_symbols!16B960371047000

OS_VERSION: 10.0.22621.2506

BUILDLAB_STR: ni_release_svc_prod3

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {5ac8c634-971d-7870-a36b-569c4d60974c}

Followup: MachineOwner
---------

 

[ubuysa]

It's always best to upload ALL the dumps you have, we often need to build a picture using as many dumps as possible, it's never wise to try and make a diagnosis based on only one dump. Upload other dumps if you have them.

That said, this one dump indicates a problem with either your graphics driver (nvlddmkm.sys) or with the graphics card itself. The 0x116 bugcheck is a VIDEO_TDR_FAILURE, indicating that there was a graphics hang and the Windows Timeout Detection and Recovery feature (TDR) recognised the hang and reset the graphics driver and graphics card to try and recover from the hang. Note that this always causes a crash to desktop of the running app. In this case, the driver and card reset failed to recover from the graphics hang and so we got the 0x116 BSOD.

If you look at the call stack in the dump (read from bottom up), which documents the function calls that led up to the bugcheck, you can see what happened...

4: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffff9787`9f99f128 fffff802`75d01a5e     nt!KeBugCheckEx
01 ffff9787`9f99f130 fffff802`75cb18b2     dxgkrnl!TdrBugcheckOnTimeout+0xfe
02 ffff9787`9f99f170 fffff802`75ca950d     dxgkrnl!ADAPTER_RENDER::Reset+0x12a
03 ffff9787`9f99f1a0 fffff802`75d011b5     dxgkrnl!DXGADAPTER::Reset+0x60d
04 ffff9787`9f99f250 fffff802`75d01312     dxgkrnl!TdrResetFromTimeout+0x15
05 ffff9787`9f99f280 fffff802`5c634f85     dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
06 ffff9787`9f99f2c0 fffff802`5c707167     nt!ExpWorkerThread+0x155
07 ffff9787`9f99f4b0 fffff802`5c81bb94     nt!PspSystemThreadStartup+0x57
08 ffff9787`9f99f500 00000000`00000000     nt!KiStartSystemThread+0x34

You can see the dxgkrnl.sys Windows DirectX driver being called via TDR to perform a reset. You can see first the driver is reset (dxgkrnl!TdrResetFromTimeout) and then the graphics card (the adapter) is reset (dxgkrnl!DXGADAPTER::Reset). Note that the full call stack also shows dxgkrnl.sys calling nvlddmkm.sys, since that's the only way to access the graphics card. Later on you see that the attempted the reset has failed (dxgkrnl!TdrBugcheckOnTimeout) and we get the bugcheck.

The best way to check whether this issue is a driver or card issue is to swap test the card. That's not always possible though, so a good alternative is to download DDU and three most recent versions of the driver, from the Nvidia website and do the following...

1. Use DDU to fully uninstall the current driver (the system will reboot).
2. Install the latest version of the driver and test the system.
3. If it still BSODs then use DDU to uninstall the current driver (the system will reboot).
4. Install the immediately prior version of the driver and test the system.
5. If it still BSODs then use DDU to uninstall the current driver (the system will reboot).
6. Install the two versions back driver and test the system.

If it BSODs on all three of the most recent versions of the driver then the problem is almost certainly with the graphics card. You can try popping it out and reseating it fully, that sometimes helps. Otherwise you have no alternative but to try another graphics card.

 

[VanquishHorrors]

It's always best to upload ALL the dumps you have, we often need to build a picture using as many dumps as possible, it's never wise to try and make a diagnosis based on only one dump. Upload other dumps if you have them.

That said, this one dump indicates a problem with either your graphics driver (nvlddmkm.sys) or with the graphics card itself. The 0x116 bugcheck is a VIDEO_TDR_FAILURE, indicating that there was a graphics hang and the Windows Timeout Detection and Recovery feature (TDR) recognised the hang and reset the graphics driver and graphics card to try and recover from the hang. Note that this always causes a crash to desktop of the running app. In this case, the driver and card reset failed to recover from the graphics hang and so we got the 0x116 BSOD.

If you look at the call stack in the dump (read from bottom up), which documents the function calls that led up to the bugcheck, you can see what happened...

4: kd> knL
 # Child-SP          RetAddr               Call Site
00 ffff9787`9f99f128 fffff802`75d01a5e     nt!KeBugCheckEx
01 ffff9787`9f99f130 fffff802`75cb18b2     dxgkrnl!TdrBugcheckOnTimeout+0xfe
02 ffff9787`9f99f170 fffff802`75ca950d     dxgkrnl!ADAPTER_RENDER::Reset+0x12a
03 ffff9787`9f99f1a0 fffff802`75d011b5     dxgkrnl!DXGADAPTER::Reset+0x60d
04 ffff9787`9f99f250 fffff802`75d01312     dxgkrnl!TdrResetFromTimeout+0x15
05 ffff9787`9f99f280 fffff802`5c634f85     dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
06 ffff9787`9f99f2c0 fffff802`5c707167     nt!ExpWorkerThread+0x155
07 ffff9787`9f99f4b0 fffff802`5c81bb94     nt!PspSystemThreadStartup+0x57
08 ffff9787`9f99f500 00000000`00000000     nt!KiStartSystemThread+0x34

You can see the dxgkrnl.sys Windows DirectX driver being called via TDR to perform a reset. You can see first the driver is reset (dxgkrnl!TdrResetFromTimeout) and then the graphics card (the adapter) is reset (dxgkrnl!DXGADAPTER::Reset). Note that the full call stack also shows dxgkrnl.sys calling nvlddmkm.sys, since that's the only way to access the graphics card. Later on you see that the attempted the reset has failed (dxgkrnl!TdrBugcheckOnTimeout) and we get the bugcheck.

The best way to check whether this issue is a driver or card issue is to swap test the card. That's not always possible though, so a good alternative is to download DDU and three most recent versions of the driver, from the Nvidia website and do the following...

1. Use DDU to fully uninstall the current driver (the system will reboot).
2. Install the latest version of the driver and test the system.
3. If it still BSODs then use DDU to uninstall the current driver (the system will reboot).
4. Install the immediately prior version of the driver and test the system.
5. If it still BSODs then use DDU to uninstall the current driver (the system will reboot).
6. Install the two versions back driver and test the system.

If it BSODs on all three of the most recent versions of the driver then the problem is almost certainly with the graphics card. You can try popping it out and reseating it fully, that sometimes helps. Otherwise you have no alternative but to try another graphics card.

I don't think I remember the previous times I had this error in the past few weeks, but I might update this thread later on if I do run into it again.

But I'll try your GPU fixes for now. Thanks!