How to fix 'DPC Watchdog Violation' BSOD on Nitro AN715-51?

Leap
Leap Member Posts: 1 New User
edited November 2023 in 2020 Archives
Hi, I have installed a new nvme SSD on my laptop Nitro AN715-51. I can install games there with or copy files no issue. However, I am getting the 'DPC Watchdog Violation' BSOD whenever a game updates on Kingston A2000 M.2 NVMe SSD.

I tried to reinstall drivers and even update them but it didnt solve my issue.

I am on windows 10 (version 2004)

This is driving me crazy. This laptop is still 2 month old. Can someone help me? If it helps, I opened WinDbg preview and this is what it displays:


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: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff805206fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout

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: 3359

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on LAPTOP-6ST6P8BM

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 3410

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

    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:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff805206fb320

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8052500c4f0 -- (.trap 0xfffff8052500c4f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000001eed2c24 rbx=0000000000000000 rcx=fffff8052500c6f0
rdx=fffffd08500df3e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8051fcbee17 rsp=fffff8052500c680 rbp=0000000000000000
 r8=ffffdf831afeacf0  r9=0000000000000000 r10=0000000000000002
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff805`1fcbee17 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT:  
fffff805`2501bc88 fffff805`1fe87a14     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff805`2501bc90 fffff805`1fd2b7cd     : 0000031a`25ac32a8 fffff805`1ba6a180 00000000`00000246 00000000`00016197 : nt!KeAccumulateTicks+0x15dd24
fffff805`2501bcf0 fffff805`1fd2bd71     : 00000000`00000000 00000000`0000d2c1 fffff805`1ba6a180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff805`2501bd40 fffff805`1fd26823     : fffff805`1ba6a180 00000000`00000000 fffff805`20631a08 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff805`2501be80 fffff805`1fd2e382     : fffff805`2500c4f0 fffff805`2500c570 fffff805`2500c500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff805`2501bf30 fffff805`1fc2ecd5     : 00000003`4b1d4f80 fffff805`206f39e0 fffff805`206f3a90 ffff4f2a`3642c643 : nt!HalpTimerClockInterrupt+0xe2
fffff805`2501bf60 fffff805`1fdf604a     : fffff805`2500c570 fffff805`206f39e0 fffff805`2500ca10 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff805`2501bfb0 fffff805`1fdf65b7     : 00000000`00000000 00000000`00000001 fffff805`2500c7b0 fffff805`1fdf65c4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`2500c4f0 fffff805`1fcbee17     : 00000000`00000010 00000000`00000202 fffff805`2500c6a8 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`2500c680 fffff805`1ff101a4     : 00000000`00000000 00000000`00000000 fffff805`2500c720 00000000`00000002 : nt!KeYieldProcessorEx+0x17
fffff805`2500c6b0 fffff805`1ff0ffa2     : 00400a02`00000010 0000030e`f64c05f6 ffffdf83`1eed2c24 ffffdf83`1a272040 : nt!KxWaitForLockOwnerShipWithIrql+0x24
fffff805`2500c6e0 fffff805`1fe126e8     : fffff805`2500c7b0 00000000`00000001 fffff805`1ba6a180 ffffdf83`1afa2458 : nt!KiAcquireQueuedSpinLockInstrumented+0x66
fffff805`2500c720 fffff805`23cbc51d     : fffff805`2500c7b0 fffff805`1fc8ae46 00000000`00000000 ffffdf83`1a25f000 : nt!KeAcquireInStackQueuedSpinLock+0x106a88
fffff805`2500c750 fffff805`23cbc473     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff805`2500c878 : storport!RaidAdapterAcquireStartIoLock+0x25
fffff805`2500c780 fffff805`1fcbf7c2     : 00000000`00000004 fffff805`1ba6a180 fffff805`2500ca18 00000000`00000000 : storport!RaidpAdapterTimerDpcRoutine+0x53
fffff805`2500c7e0 fffff805`1fce4b6d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000cfdd : nt!KiProcessExpiredTimerList+0x172
fffff805`2500c8d0 fffff805`1fdf810e     : 00000000`00000000 fffff805`1ba6a180 fffff805`20727600 ffffdf83`3c36e340 : nt!KiRetireDpcList+0x5dd
fffff805`2500cb60 00000000`00000000     : fffff805`2500d000 fffff805`25006000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  storport!RaidAdapterAcquireStartIoLock+25

MODULE_NAME: storport

IMAGE_NAME:  storport.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  25

FAILURE_BUCKET_ID:  0x133_DPC_storport!RaidAdapterAcquireStartIoLock

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {39a82191-b868-988a-2d1e-beb94d89fdde}

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