Hello people from AMD Community, hope everyone that reads my post are having a nice day^^
Before I start, I apologize if I make spelling spelling mistakes, English is not my main language.
The thing is that when I'm playing RE4 my game totally freezes and after a minute I get BSOD with the error code: DPC WATCHDOG VIOLATION, I've tried everything like reinstalling the game, uninstalling AMD Drivers with DDU, checked my RAM health, updated BIOS version, updated my chipset drivers, checked my pc for any malware, updated Windows to the latest version and none of them seemed to help me.
I also checked my temps, everything is OK, temps under 80ºC with my graphic and less than 60ºC with my CPU, so the temps are definitely not the problem here.
I'm having this problem since I installed the game, please if someone knows how to help me to solve my issue I'll be very grateful.
I will be leaving my full PC specs along with the info that my .dmp file dropped me with Windbg
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\041423-26187-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 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`3da00000 PsLoadedModuleList = 0xfffff801`3e613420
Debug session time: Fri Apr 14 00:56:46.153 2023 (UTC - 5:00)
System Uptime: 0 days 0:18:52.750
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`3de293a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8180`c3546c70=0000000000000133
2: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8013e71c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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
Key : Analysis.CPU.mSec
Value: 1515
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4087
Key : Analysis.IO.Other.Mb
Value: 6
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 30
Key : Analysis.Init.CPU.mSec
Value: 249
Key : Analysis.Init.Elapsed.mSec
Value: 31601
Key : Analysis.Memory.CommitPeak.Mb
Value: 98
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 1008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
FILE_IN_CAB: 041423-26187-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8013e71c340
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8180`c3546c68 fffff801`3dcbb9af : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`3e71c340 : nt!KeBugCheckEx
ffff8180`c3546c70 fffff801`3dcba7f4 : 00000416`2f19b8fa ffff8180`c3526180 00000000`00011b2f 00000000`00000000 : nt!KeAccumulateTicks+0x23f
ffff8180`c3546cd0 fffff801`3dcb8c83 : fffff801`3e65ffd8 00000000`00000000 ffff8180`c3526180 fffffa88`5b5a8060 : nt!KiUpdateRunTime+0xf4
ffff8180`c3546e90 fffff801`3dcb810a : fffff801`3e65ffd8 ffffe40b`b8f452b0 ffffe40b`b8f452b0 00000000`00000000 : nt!KeClockInterruptNotify+0x763
ffff8180`c3546f40 fffff801`3dd4b46e : 00000002`a36970d1 ffffe40b`b8f45200 ffff8180`c3526180 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a
ffff8180`c3546f70 fffff801`3de2b4fa : fffffa88`5b5a80e0 ffffe40b`b8f45200 00000000`d99b569e ffffe40b`c6976c60 : nt!KiCallInterruptServiceRoutine+0x19e
ffff8180`c3546fb0 fffff801`3de2bd67 : fffffa88`5b5a82b0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffa88`5b5a8060 fffff801`3dc3410a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffa88`5b5a81f0 fffff801`3dcc6f9d : ffffe40b`beb26bb0 ffffe40b`c1812860 00000000`00003255 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x11a
fffffa88`5b5a8250 fffff801`656368a4 : ffffe40b`beb26bb0 ffffe40b`c1812860 00000000`00069800 ffffe40b`c1812860 : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x3d
fffffa88`5b5a8280 ffffe40b`beb26bb0 : ffffe40b`c1812860 00000000`00069800 ffffe40b`c1812860 fffff801`65c53fe0 : amdkmdag+0xc68a4
fffffa88`5b5a8288 ffffe40b`c1812860 : 00000000`00069800 ffffe40b`c1812860 fffff801`65c53fe0 00000000`00000000 : 0xffffe40b`beb26bb0
fffffa88`5b5a8290 00000000`00069800 : ffffe40b`c1812860 fffff801`65c53fe0 00000000`00000000 ffffe40b`beb26bb9 : 0xffffe40b`c1812860
fffffa88`5b5a8298 ffffe40b`c1812860 : fffff801`65c53fe0 00000000`00000000 ffffe40b`beb26bb9 00000000`00000000 : 0x69800
fffffa88`5b5a82a0 fffff801`65c53fe0 : 00000000`00000000 ffffe40b`beb26bb9 00000000`00000000 ffffe40b`beb26b01 : 0xffffe40b`c1812860
fffffa88`5b5a82a8 00000000`00000000 : ffffe40b`beb26bb9 00000000`00000000 ffffe40b`beb26b01 00000000`00000000 : amdkmdag+0x6e3fe0
SYMBOL_NAME: amdkmdag+c68a4
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: c68a4
FAILURE_BUCKET_ID: 0x133_ISR_amdkmdag!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ce335412-b260-6bc1-3af9-ea5584f041c4}
Followup: MachineOwner
---------
PC Specs:
CPU: AMD Ryzen 5 5600g
RAM: G.Skill Trident Z Royal Series 16 GB (2 x 8 GB)
GPU: XFX RX 580 GTS 4GB
MOBO: Asus ROG STRIX B550-F GAMING
SSD: Xpg Spectrix S40G 512GB
HDD 1: TOSHIBA DT01ACA200
HDD 2: ST2000DM008-2FR102
PSU: EVGA SuperNOVA 650 GT, 80 Plus Gold
