Kernel 41 Error while playing Warzone. How do I find the problem?!

[FizzFantom]

Hi, could someone help me with my Kernel Error. I know this is very unspesific. I already dug out the memory.dmp file but i have no idea what i have before me.

 

To the Error:

My PC is quite new. Maybe 2 months old. It only blacks out while playing CoD Warzone and also restarts imediatly afterwards. Never happend in any other case. I use it to edit 4k videos and some other content creation so the load is no that high on a normal day.

 

I really got no clue what to do.

When the session gets longer it happens more often. I thought about overheating but the ventilation is quite good and non of the parameters spike very hard in HWinfo.

 

 

 

 

 

 

 

PCPartPicker Part List

Type	Item	Price
CPU	AMD Ryzen 9 3950X 3.5 GHz 16-Core Processor	Purchased For €656.00
CPU Cooler	Corsair iCUE H150i RGB PRO XT 75 CFM Liquid CPU Cooler	Purchased For €150.00
Motherboard	Asus ROG Strix X570-E Gaming ATX AM4 Motherboard	Purchased For €219.00
Memory	G.Skill Trident Z Neo 32 GB (2 x 16 GB) DDR4-3200 CL16 Memory	Purchased For €155.00
Memory	G.Skill Trident Z Neo 32 GB (2 x 16 GB) DDR4-3200 CL16 Memory	Purchased For €155.00
Storage	Samsung 970 Evo 1 TB M.2-2280 NVME Solid State Drive	Purchased For €145.00
Storage	Samsung 970 Evo 1 TB M.2-2280 NVME Solid State Drive	Purchased For €145.00
Video Card	Gigabyte Radeon RX 5700 XT 8 GB GAMING OC Video Card	Purchased For €369.00
Case	Lian Li O11D-PCMR ATX Full Tower Case	Purchased For €155.00
Power Supply	NZXT C 750 W 80+ Gold Certified Fully Modular ATX Power Supply	Purchased For €96.00
Case Fan	Noctua NF-F12 PWM chromax.black.swap 54.97 CFM 120 mm Fan	Purchased For €19.00
Case Fan	Noctua NF-F12 PWM chromax.black.swap 54.97 CFM 120 mm Fan	Purchased For €19.00
Case Fan	Noctua NF-F12 PWM chromax.black.swap 54.97 CFM 120 mm Fan	Purchased For €19.00
Case Fan	Noctua NF-A14 PWM chromax.black.swap 82.52 CFM 140 mm Fan	Purchased For €22.00
Case Fan	Noctua NF-A14 PWM chromax.black.swap 82.52 CFM 140 mm Fan	Purchased For €22.00
	Prices include shipping, taxes, rebates, and discounts
	Total	€2346.00
	Generated by PCPartPicker 2020-09-06 20:34 CEST+0200

 

[FizzFantom]

Short update. BugCheckcode is 278. This translates to 0x00000116. I think this is an Error originating in the graphics card. Should I get in touch with Gigabyte so they change it or is it an software error?

 

 

[BlackManINC]

1 hour ago, FizzFantom said:

Short update. BugCheckcode is 278. This translates to 0x00000116. I think this is an Error originating in the graphics card. Should I get in touch with Gigabyte so they change it or is it an software error?

 

 

I would check and make sure you don't have any leftover display drivers in the device manager screen first. Just click on the view tab and click on "show hidden devices". It will be greyed put if anything is there. I would also update the bios if you haven't already, check each ram stick for faults with the app below. 

 

Link: https://www.memtest86.com/

[FizzFantom]

@BlackManINC 

hi, thanks for the advice. No additional driver and the memory test came back negative. BIOS is updated and u also deinstalled the graphics driver in safe mode and reinstalled it. 
is there anything else i could do?

[BlackManINC]

13 hours ago, FizzFantom said:

@BlackManINC 

hi, thanks for the advice. No additional driver and the memory test came back negative. BIOS is updated and u also deinstalled the graphics driver in safe mode and reinstalled it. 
is there anything else i could do?

Ok, so what did the memory dump file say? You'll need to post it so we can see. 

[FizzFantom]

On 9/14/2020 at 11:15 PM, BlackManINC said:

Ok, so what did the memory dump file say? You'll need to post it so we can see. 

So it did stop for a while now. 2 Days ago it started again and is now killing of my PC every hour or so.

 

How can I post it? its about 1,5 Gb. Can I reset it and wait for the next crash so its not that huge?

[BlackManINC]

12 hours ago, FizzFantom said:

So it did stop for a while now. 2 Days ago it started again and is now killing of my PC every hour or so.

 

How can I post it? its about 1,5 Gb. Can I reset it and wait for the next crash so its not that huge?

1.5 gbs? Holy shit!!! Nah, thats way too much. You are better off either just copying & pasting the error code, like what the bug check code is, the module names given, stuff like that. Waiting for it to crash again is counter intuitive me thinks, but you can try that I guess. You probably need to drastically reduce the crash dump file size though for next time. 

[FizzFantom]

2 hours ago, BlackManINC said:

1.5 gbs? Holy shit!!! Nah, thats way too much. You are better off either just copying & pasting the error code, like what the bug check code is, the module names given, stuff like that. Waiting for it to crash again is counter intuitive me thinks, but you can try that I guess. You probably need to drastically reduce the crash dump file size though for next time. 

Okok,

So if i read out the dump file with WinDbg this is the text. Maybe this can help.

Also i got a Minidump file. Maybe that helps? I'll attach it.

 

 

 

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\100420-7625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`08c00000 PsLoadedModuleList = 0xfffff803`0982a310
Debug session time: Sun Oct  4 20:07:52.128 2020 (UTC + 2:00)
System Uptime: 0 days 0:08:46.816
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`08ff3ea0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff102`ae292a00=0000000000000116
12: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\u0359518.inf_amd64_ddc5c961c2795261\B359297\amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4655

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on FELIZIAN

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 25315

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  116

BUGCHECK_P1: ffffbd0a49318010

BUGCHECK_P2: fffff8031de51940

BUGCHECK_P3: ffffffffc0000001

BUGCHECK_P4: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff102`ae2929f8 fffff803`174f128e     : 00000000`00000116 ffffbd0a`49318010 fffff803`1de51940 ffffffff`c0000001 : nt!KeBugCheckEx
fffff102`ae292a00 fffff803`1749960b     : fffff803`1de51940 ffffbd0a`419a6000 ffffbd0a`419a60f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffff102`ae292a40 fffff803`1749a3de     : ffffbd0a`00000101 00000000`00002000 ffffbd0a`419a6000 00000000`01000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x1a3
fffff102`ae292a90 fffff803`174f09b5     : 00000000`00000100 ffffbd0a`419a6a50 00000000`40bff460 fffff803`08e96b1c : dxgkrnl!DXGADAPTER::Reset+0x28e
fffff102`ae292b10 fffff803`174f0b27     : fffff803`09924440 ffffbd0a`4fd06d70 00000000`00000000 00000000`00000100 : dxgkrnl!TdrResetFromTimeout+0x15
fffff102`ae292b40 fffff803`08ec1f15     : ffffbd0a`3c7070c0 fffff803`174f0b00 ffffbd0a`2e09d4a0 ffffbd0a`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
fffff102`ae292b70 fffff803`08e66dd5     : ffffbd0a`3c7070c0 00000000`00000080 ffffbd0a`2e09c040 000f8067`b4bbbdff : nt!ExpWorkerThread+0x105
fffff102`ae292c10 fffff803`08ffb4f8     : ffffd081`22dd5180 ffffbd0a`3c7070c0 fffff803`08e66d80 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff102`ae292c60 00000000`00000000     : fffff102`ae293000 fffff102`ae28d000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  amdkmdag+b1940

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_amdkmdag.sys

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1c94a7e8-453f-c7b9-1484-0a0454a0ee36}

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

100420-7625-01.zip

[BlackManINC]

@FizzFantom

 

Its an issue related to your GPU. Bug check code 116 in particular is about something called "Timeout Detection and Recovery". From my understanding, it usually happens when the GPU is trying to process data while running intensive apps like video games, and the PC will either crash and reboot, or the screen will freeze and blackout if it can't get the job done in time. It can happen due to a number of things, like outdated drivers, or overclocking, etc. This actually happened to me just yesterday while playing Squad with the screen blacking out. The guy in the link below suggests accessing the registry to change the TDR delay value from its default 2 seconds to something like 5 or 10 seconds. I'm overclocking so I pretty much have a good idea as to why it happened to me, so I'd rather just mess around with the GPU clock/voltage settings than tamper with anything in the registry. It doesn't happen to me that often anyway. 

 

Link: The TDR Setting