Question DPC WATCHDOG VIOLATION on Acer Nitro V 13th Gen RTX 4050 blue screen of death

[Vahin Angral]

I've had this laptop for about a month now and I've gotten this DPC WATCHDOG VIOLATION blue screen of death again and again whilst I'm playing a game. Please help fix this issue. I can give all the details needed. It's very sad to have a new laptop that you spent money on not even be able to handle simple games and cause a blue screen of death for no reason.



I have used WinDbg to view the dmp files created in C:\Windows\Minidump


************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : false
AllowNugetExeUpdate : false
AllowNugetMSCredentialProviderInstall : false
AllowParallelInitializationOfLocalRepositories : true

-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 36

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


Loading Dump File [C:\Windows\Minidump\030124-10328-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 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Kernel base = 0xfffff803`52a00000 PsLoadedModuleList = 0xfffff803`53613550
Debug session time: Fri Mar 1 02:53:32.179 2024 (UTC + 5:30)
System Uptime: 0 days 2:07:22.809
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.................................................
Loading User Symbols

Loading unloaded module list
..........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`52e16c30 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff803`56510c90=0000000000000133
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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff8035371c340, 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: 2046

Key : Analysis.Elapsed.mSec
Value: 11102

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

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

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

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x133

Key : Failure.Bucket
Value: 0x133_ISR_nvlddmkm!unknown_function

Key : Failure.Hash
Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

Key : Hypervisor.Enlightenments.ValueHex
Value: 1417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 21631230

Key : Hypervisor.Flags.ValueHex
Value: 14a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8035371c340

BUGCHECK_P4: 0

FILE_IN_CAB: 030124-10328-01.dmp

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffe20b5e836a60 -- (.trap 0xffffe20b5e836a60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000014000d0 rbx=0000000000000000 rcx=0000000000042d4b
rdx=000000000010b52c rsi=0000000000000000 rdi=0000000000000000
rip=fffff8039893e234 rsp=ffffe20b5e836bf0 rbp=ffff96052fc7abf0
r8=ffffe20b5e836c38 r9=000000000010b52c r10=ffff96052fc7dd30
r11=ffffe20b5e836cf0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nvlddmkm+0xbe234:
fffff803`9893e234 488b5c2430 mov rbx,qword ptr [rsp+30h] ss:ffffe20b`5e836c20=ffff96052fc7a000
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff803`56510c88 fffff803`52c12bb9 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`5371c340 : nt!KeBugCheckEx
fffff803`56510c90 fffff803`52c12421 : 0000122a`3fd4910b 00000000`000776b3 00000000`000776b2 00000000`00000000 : nt!KeAccumulateTicks+0x239
fffff803`56510cf0 fffff803`52c104b1 : 00000000`00000000 ffffa981`4bf2c100 fffff803`4ed29180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
fffff803`56510ea0 fffff803`52c0feda : fffff803`5365ff88 ffffa981`4bf2c1f0 ffffa981`4bf2c1f0 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
fffff803`56510f40 fffff803`52d24cdc : 00000011`cb7b6c50 fffff803`5370d4f0 fffff803`5370d5a0 fffff803`52e18b8b : nt!HalpTimerClockInterrupt+0x10a
fffff803`56510f70 fffff803`52e18dea : ffffe20b`5e836ae0 fffff803`5370d4f0 ffff9605`2fc7abf0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff803`56510fb0 fffff803`52e19697 : 00000000`000000ff 00000000`00000001 00000000`00000180 fffff803`52c80b97 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffe20b`5e836a60 fffff803`9893e234 : ffff9605`00000000 00000000`00000000 00000000`0010b52c 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffe20b`5e836bf0 ffff9605`00000000 : 00000000`00000000 00000000`0010b52c 00000000`00000000 00000000`0010b52c : nvlddmkm+0xbe234
ffffe20b`5e836bf8 00000000`00000000 : 00000000`0010b52c 00000000`00000000 00000000`0010b52c fffff803`9896d909 : 0xffff9605`00000000


SYMBOL_NAME: nvlddmkm+be234

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: be234

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

0: kd> lmvm nvlddmkm
Browse full module list
start end module name
fffff803`98880000 fffff803`9c2d4000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nvacig.inf_amd64_1499c7986df7046d\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Thu Feb 15 17:08:19 2024 (65CDF7AB)
CheckSum: 0393875D
ImageSize: 03A54000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:

Kindly help.

I have tried redownloading Nvidia driver after uninstalling through DDU.

Here is the minidump files from C:\Windows\Minidump if you want to take a look at it yourself.

OneDrive

1drv.ms

 

[Lutfij]

Welcome to the forums, newcomer!

nvlddmkm.sys
You might want to make sure your laptop is on the latest BIOS version. Then use DDU in Safe Mode, remove all GPU drivers(Intel, AMD and Nvidia) then manually reinstall with the latest GPU driver sourced from Nvidia's support site, in an elevated command, i.e, Right click installer>Run as Administrator.

 

[Vahin Angral]

I'm on laptop. So I should delete and reinstall the intel GPU first then Nvidia GPU right.

 

[Vahin Angral]

Welcome to the forums, newcomer!

nvlddmkm.sys
You might want to make sure your laptop is on the latest BIOS version. Then use DDU in Safe Mode, remove all GPU drivers(Intel, AMD and Nvidia) then manually reinstall with the latest GPU driver sourced from Nvidia's support site, in an elevated command, i.e, Right click installer>Run as Administrator.

i've got the bsod again