Keep blue screening help!

Question

Over the past few days, I've encountered repeated BSODs with the error code "DPC_WATCHDOG_VIOLATION." To resolve this issue, I've done the following steps:

1. BIOS Update: Successfully updated the BIOS to the latest version available from the motherboard manufacturer's website.
2. System Reformat: Conducted a full system reformat. After the reinstallation of the os, I removed the GPU drivers using Display Driver Uninstaller and reinstalled the driver.
3. Windows Updates and Drivers: After the reinstallation, I made sure to install all available Windows updates. Additionally, I downloaded and installed the latest lan driver from the motherboard site.

Despite these efforts, the issue persists.

WinDbg Analysis:

*******************************************************************************
*                                                                             *
*                        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: fffff806380fb320, 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: 2718

    Key  : Analysis.Elapsed.mSec
    Value: 13550

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806380fb320

BUGCHECK_P4: 0

FILE_IN_CAB:  030124-25281-01.dmp

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffb70847dc25b0 -- (.trap 0xffffb70847dc25b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000b1159c24 rbx=0000000000000000 rcx=ffffb70847dc27a0
rdx=ffffb70847dca7f8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff806376c8c87 rsp=ffffb70847dc2740 rbp=ffffffffffffffff
 r8=ffffcc8653102208  r9=0000000000000038 r10=0000000000000000
r11=ffffb70847dc2828 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff806`376c8c87 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff806`3a484e18 fffff806`37837896     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`380fb320 : nt!KeBugCheckEx
fffff806`3a484e20 fffff806`376539e3     : 0000048a`b308fb9b fffff806`3257f180 00000000`00000000 fffff806`3257f180 : nt!KeAccumulateTicks+0x1e1656
fffff806`3a484e80 fffff806`376534ca     : fffff806`380f3a00 ffffb708`47dc2630 fffff806`55972700 00000000`00006401 : nt!KeClockInterruptNotify+0x453
fffff806`3a484f30 fffff806`37700825     : fffff806`380f3a00 fffff806`3a484f40 00000000`0000000c ffff4899`c89f3e99 : nt!HalpTimerClockIpiRoutine+0x1a
fffff806`3a484f60 fffff806`377ff59a     : ffffb708`47dc2630 fffff806`380f3a00 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`3a484fb0 fffff806`377ffda7     : fffff806`380f3a00 ffffb708`47dc2800 00000000`00000082 fffff806`377ffe34 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffb708`47dc25b0 fffff806`376c8c87     : 00000000`00000010 00000000`00040286 ffffb708`47dc2768 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffb708`47dc2740 fffff806`3765fc4a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x17
ffffb708`47dc2770 fffff806`3765fbfb     : 00000000`b1159c24 00000000`00000000 ffffba82`d4cec7c0 fffff806`37645c07 : nt!KxWaitForLockOwnerShip+0x2a
ffffb708`47dc27a0 fffff806`376fa1e3     : ffffba82`ce3acb80 ffffcc86`5311d790 00000000`00000000 fffff806`376f733c : nt!KeAcquireInStackQueuedSpinLock+0x7b
ffffb708`47dc27d0 fffff806`376f71e3     : 00000000`00000000 ffffb708`47dc28e0 ffffffff`ffffffff ffffb708`47dc28e0 : nt!CcUninitializeVolumeCacheMap+0x33
ffffb708`47dc2830 fffff806`37660829     : 00000000`00000000 ffffb708`47dc28f9 ffffba82`dbf40d00 ffffba82`d4cec7c0 : nt!CcDeleteSharedCacheMap+0x187
ffffb708`47dc2880 fffff806`376f9471     : ffffba82`dc07a140 00000000`00000000 ffffba82`c6e3bb00 ffffba82`00000000 : nt!CcWriteBehindInternal+0x389
ffffb708`47dc2960 fffff806`376f6c11     : ffffba82`d6331040 ffffba82`c6cbe100 ffffba82`dc07a140 ffffba82`d2f7b030 : nt!CcWriteBehind+0x91
ffffb708`47dc2a50 fffff806`376c46b5     : ffffba82`d6331040 ffffba82`c6ca57e0 ffffba82`c6cbe100 00000000`00000200 : nt!CcCachemapUninitWorkerThread+0xf1
ffffb708`47dc2b30 fffff806`377078e5     : ffffba82`d6331040 00000000`00000080 ffffba82`c6c89080 000fe067`b4bbbdff : nt!ExpWorkerThread+0x105
ffffb708`47dc2bd0 fffff806`37806378     : ffffde00`96ed6180 ffffba82`d6331040 fffff806`37707890 ff044dc0`ff0952c5 : nt!PspSystemThreadStartup+0x55
ffffb708`47dc2c20 00000000`00000000     : ffffb708`47dc3000 ffffb708`47dbc000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  nt!KeAccumulateTicks+1e1656

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.4046

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1e1656

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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

Answer 1

1. Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

https://www.tenforums.com/bsod-crashes-debugging/162488-batch-files-use-bsod-debugging-2.html#post2177966

https://www.tenforums.com/bsod-crashes-debugging/162488-batch-files-use-bsod-debugging-post2177966.html#post2177966

2. Run Memtest86+ for 8 or more passes > take pictures > post share links

https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html

https://www.memtest.org/

3. Download and install one of these temperature monitoring software:

https://www.ccleaner.com/speccy

https://www.cpuid.com/softwares/hwmonitor.html https://www.almico.com/speedfan.php

4. Run Prime95 for 3 hrs (see warnings) > take pictures > post share links

https://www.tenforums.com/tutorials/16474-prime95-stress-test-your-cpu.html

5. Run Furmark for 30 minutes (see warnings) > take pictures > post share links

https://www.tenforums.com/tutorials/13081-furmark-gpu-stress-test.html

Answer 2

Hi questions,

Thank you for your assistance. i have run the V2 log file collector as instructed. Here is the link to the files.

DESKTOP-1T732OM-(2024-03-02_00-18-32).zip

Please let me know if there is any issue with accessing the files or if you need further information.

Answer 3

Hi Dyaribarham,

Thank you for offering your assistance. I have attached the link to the mini dump here

BSOD minidump

Please let me if there are any issue accessing the file.

Answer 4

Please run the V2 log collector > post a share link into this thread using one drive, drop box, or google drive

https://www.tenforums.com/bsod-crashes-debugging/

https://www.elevenforum.com/t/bsod-posting-instructions.103/

Make sure that share links are available without sign in.

Answer 5

Hi tony,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Please go to C:\Windows\Minidump and copy any minidump files you find to your desktop. Afterward, share these files through OneDrive or Google Drive so we can analyze them and identify the specific file that's causing the crash.

https://answers.microsoft.com/en-us/windows/for...