Question Windows 11 freezes even after clean reinstall, and sometimes get "DPC Watchdog Violation" BSOD ?

[alex.loeflath]

Hey,

my 3 years old computer suddenly started randomly freezing, sometimes ending up in a DPC Watchdog Violation BSOD, mostly not reacting at all anymore. No Hardware was changed, no additional software installed, no windows update installed recently when the error started to occur. Happens with or without any cpu/gpu load, even while clicking through windows menus or browsing. I updateed drivers, chipset, BIOS, formated both SSDs and clean installed Windows, still happens. Temperatures are low for every component. What else can i try?

EDIT: one of the BSOD dumps:


************* 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.032 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:\Users\aloef\Downloads\101123-6937-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 (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`61800000 PsLoadedModuleList = 0xfffff800`624130c0
Debug session time: Wed Oct 11 14:43:47.477 2023 (UTC + 2:00)
System Uptime: 0 days 0:25:37.093
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000077`9fe64018). Type ".hh dbgerr001" for details
Loading unloaded module list
......................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`61c12740 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe580`79e6c9f0=0000000000000133
3: 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: fffff8006251d340, 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 ***
*** ***
*************************************************************************
*** WARNING: Check Image - Checksum mismatch - Dump: 0x2007f7, File: 0x200063 - C:\ProgramData\Dbg\sym\BTHport.sys\6D2AFE05200000\BTHport.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2233

Key : Analysis.Elapsed.mSec
Value: 2388

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

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

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

Key : Bugcheck.Code.LegacyAPI
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

Key : Failure.Bucket
Value: 0x133_ISR_nt!KeAccumulateTicks

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


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8006251d340

BUGCHECK_P4: 0

FILE_IN_CAB: 101123-6937-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

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: svchost.exe

STACK_TEXT:
ffffe580`79e6c9e8 fffff800`61a28859 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`6251d340 : nt!KeBugCheckEx
ffffe580`79e6c9f0 fffff800`61a280c1 : 00000531`e31a7cee ffffe580`79e52180 00000000`00018045 00000000`00000000 : nt!KeAccumulateTicks+0x239
ffffe580`79e6ca50 fffff800`61a256cf : 00000000`00000018 00000000`00001388 00000000`00018000 00000000`0000e50b : nt!KiUpdateRunTime+0xd1
ffffe580`79e6cc00 fffff800`61a262b8 : 00000000`00000000 00000000`00000000 ffffe580`79e52180 00000000`00000000 : nt!KiUpdateTime+0x63f
ffffe580`79e6cea0 fffff800`61a25b7a : fffff800`6245ff60 00000000`00000001 00000000`00000001 00000000`0000000c : nt!KeClockInterruptNotify+0x228
ffffe580`79e6cf40 fffff800`61aae6dc : 00000003`9480a5b6 ffff8004`f7745e60 ffff8004`f7745f10 00000000`00000000 : nt!HalpTimerClockInterrupt+0x10a
ffffe580`79e6cf70 fffff800`61c1489a : fffff687`e231edd0 ffff8004`f7745e60 ffffe580`79e52180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffe580`79e6cfb0 fffff800`61c15107 : fffff687`e231edd0 ffffffff`ffffffff 00000000`80000003 00000000`7e28e60d : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff687`e231ed50 fffff800`61a5657e : 00000000`00000000 ffffd08b`ac11f000 ffffd08b`ac11f138 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff687`e231eee0 fffff800`61bac2fd : 00000000`00000001 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KiIpiSendRequestEx+0x62
fffff687`e231ef20 fffff800`61c4a839 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0xa1
fffff687`e231ef90 fffff800`61b50f50 : 00000000`00000000 ffff928f`00000000 ffffb668`45be2800 00000000`00000000 : nt!KeFlushTb+0xf9879
fffff687`e231f010 fffff800`61b56ae7 : 00000000`00000000 00000000`00000004 84000001`33a58921 ffff8005`08bc9e00 : nt!MiFlushTbList+0x80
fffff687`e231f040 fffff800`61a14777 : ffff8005`0ccfa0d0 ffff8005`0ccfa0d0 ffff8005`08bc9e28 ffff8005`08bc9e28 : nt!MmSetAddressRangeModifiedEx+0x2c7
fffff687`e231f1a0 fffff800`61a1301f : fffff687`00000000 ffff8005`00016000 ffff8004`f79c92c8 00000000`00000000 : nt!CcFlushCacheOneRange+0xe7
fffff687`e231f270 fffff800`61a5e588 : fffff687`e231f3c8 00000000`00000000 00000000`00000000 ffffe580`79e52180 : nt!CcFlushCachePriv+0x10f
fffff687`e231f2e0 fffff800`667266d5 : 00000000`00000005 00000000`00000000 00000000`00000000 ffff928f`a8f9dbc0 : nt!CcCoherencyFlushAndPurgeCache+0x88
fffff687`e231f340 fffff800`667267be : ffff928f`a8f9dbc0 fffff687`e231f911 ffff8005`09f14870 ffff8005`09f147e8 : Ntfs!NtfsCoherencyFlushAndPurgeCache+0x55
fffff687`e231f380 fffff800`667239a1 : ffff928f`a8f9dbc0 ffff928f`a8f9dbc0 00000000`00000000 00000000`00000000 : Ntfs!NtfsFlushUserStream+0xaa
fffff687`e231f420 fffff800`66723d1c : ffff928f`a8f9dbc0 ffff928f`a8f9dbc0 fffff687`e231f550 ffff8005`0168c4c0 : Ntfs!NtfsPerformOptimisticFlush+0xa1
fffff687`e231f470 fffff800`66723a69 : ffff8005`09f147e8 ffff8005`0d3efaa0 fffff800`66723a01 fffff687`e231f911 : Ntfs!NtfsCommonFlushBuffers+0x228
fffff687`e231f580 fffff800`61b48c2a : fffff687`e231f690 ffff8005`09f147e8 fffff687`00000000 00000003`4cfcda2a : Ntfs!NtfsCommonFlushBuffersCallout+0x19
fffff687`e231f5b0 fffff800`61b48b9d : fffff800`66723a50 fffff687`e231f690 ffff8005`09f147e8 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x7a
fffff687`e231f620 fffff800`667827fe : ffff8005`0168c4c0 00000000`00060000 fffff687`e231f770 fffff800`666599d8 : nt!KeExpandKernelStackAndCalloutEx+0x1d
fffff687`e231f660 fffff800`66782725 : ffff8005`09f147e8 ffff8005`0d3efaa0 fffff687`e231f911 ffff8005`0d3efaa0 : Ntfs!NtfsCommonFlushBuffersOnNewStack+0x66
fffff687`e231f6d0 fffff800`61b14d95 : fffff687`e231f830 ffff8005`0d3efaa0 ffff8005`09f147e8 fffff687`e231f700 : Ntfs!NtfsFsdFlushBuffers+0xf5
fffff687`e231f760 fffff800`659fa1db : ffff8005`0d3f2501 ffff8005`087b67a0 00000000`00000000 ffff8005`0d3efaa0 : nt!IofCallDriver+0x55
fffff687`e231f7a0 fffff800`659f7e23 : fffff687`e231f830 00000000`00000000 ffff8005`0d3efa00 ffff8005`012d2100 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15b
fffff687`e231f810 fffff800`61b14d95 : ffff8005`0d3efaa0 00000000`00000000 ffff8005`0d3efb18 ffff8005`0d3efab0 : FLTMGR!FltpDispatch+0xa3
fffff687`e231f870 fffff800`61fcd140 : ffff8005`0d3efaa0 fffff687`e231f911 ffff8005`09638990 ffff8005`09638990 : nt!IofCallDriver+0x55
fffff687`e231f8b0 fffff800`61e9aa5a : 00000000`00000000 00000000`00000000 fffff687`e231fb20 ffff8005`09638990 : nt!IopSynchronousServiceTail+0x1d0
fffff687`e231f960 fffff800`61e9a7fc : ffff8005`09638990 00000000`00000000 fffff687`e231fa01 00000000`00000000 : nt!IopFlushBuffersFile+0x246
fffff687`e231fa00 fffff800`61e9b946 : ffff8005`0d3f2080 00000000`00000228 00000000`00000000 0000017f`ab38e55c : nt!NtFlushBuffersFileEx+0x7c
fffff687`e231fa60 fffff800`61c274e8 : ffff8005`0d3f2080 ffff8005`08b582e0 00000000`00000000 00000000`00000000 : nt!NtFlushBuffersFile+0x16
fffff687`e231faa0 00007ffc`ee8afd54 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000077`a5f7f898 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`ee8afd54


SYMBOL_NAME: nt!KeAccumulateTicks+239

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.2428

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 239

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

 

[Order 66]

Full system specs, as well as model and age of PSU?

 

[alex.loeflath]

Full system specs, as well as model and age of PSU?

AMD 5900X
ASUS ROG Dark Hero
GSKILL TridentZ Neo DDR4 32GB
Bequiet 1200W Dark Power Pro (3 years old)
MSI 3080 SuprimX
2x Samsung 980 Pro 500/1000 GB

i removed the auto overclocking from RAM and CPU and let them run at base clock, still happens.
While typing this it froze again.

 

[Order 66]

AMD 5900X
ASUS ROG Dark Hero
GSKILL TridentZ Neo DDR4 32GB
Bequiet 1200W Dark Power Pro (3 years old)
MSI 3080 SuprimX
2x Samsung 980 Pro 500/1000 GB

i removed the auto overclocking from RAM and CPU and let them run at base clock, still happens.
While typing this it froze again.

If you can, go to startup settings> restart and select safe mode. If it doesn't freeze in safe mode then chances are it is some form of driver issue. try uninstalling GPU drivers with DDU in safe mode and reinstall them.

 

[alex.loeflath]

If you can, go to startup settings> restart and select safe mode. If it doesn't freeze in safe mode then chances are it is some form of driver issue. try uninstalling GPU drivers with DDU in safe mode and reinstall them.

It just froze in basic safe mode (no Internet Connection) without display drivers installed

 

[Order 66]

It just froze in basic safe mode (no Internet Connection) without display drivers installed

weird, try taking out one of the drives and reinstalling Windows with all other drives disconnected. Having both drives connected when installing windows can cause issues.

 

[alex.loeflath]

weird, try taking out one of the drives and reinstalling Windows with all other drives disconnected. Having both drives connected when installing windows can cause issues.

Would it be more likely that the one currently used for windows is the mischief?

 

[Order 66]

Would it be more likely that the one currently used for windows is the mischief?

yes, so disconnect that drive and install windows on the other one as well as all the programs you normally use. (this is so that if it is a program that is causing the issue you can identify the program and get rid of it.)

 

[alex.loeflath]

yes, so disconnect that drive and install windows on the other one as well as all the programs you normally use. (this is so that if it is a program that is causing the issue you can identify the program and get rid of it.)

Ill try that, thanks. Currently there is 0 software installed, hopefully its just a semi-dead SSD

 

[Order 66]

Ill try that, thanks. Currently there is 0 software installed, hopefully its just a semi-dead SSD

I can't believe I forgot, but you should install (if you can) samsung magician to see the drive health to see whether it is failing.

 

[alex.loeflath]

I can't believe I forgot, but you should install (if you can) samsung magician to see the drive health to see whether it is failing.

i did that, and it froze while doing the SMART Diagnosis Scan. Tried it once with every SSD, froze both times, but since the magician is installed on the system SSD it still might only be that one at fault.
...Or its something with the chipset or any controller on the mainboard, then i might be f'd.
Both SSDs are still at 100% with no sign of failure, everything in that computer was bought new 3 years ago

 

[alex.loeflath]

okay, its neither one of the SSDs. Physically removed the non System SSD, it froze, removed the system SSD, build in the non system SSD on the slot it was before, tried to install windows and it froze while installing. Thus its neither one of the SSDs nor one of the M2 slots fault :/

 

[Bitpixel]

Out of curiosity, as I've been experiencing the same exact thing and symptoms for nearly 2 weeks now with a 5950x / Gigabyte X57Os/BeQuiet 12 system, did you happen to have a inpoutx64.sys driver in your PC (c:\windows\system32\drivers\)?

It's like I'm reading my own thread over at the MS forums ( constantly freezing, sometimes with a DPC WATCHDOG VIOLATION BSOD). I ended up doing a Win 11 Reset (kept files), yet it still freezes on both reg and safe modes. Not sure yet if the inpoutx64 driver that's related to RGB software is to blame, but it reappeared after a fresh installation of Win 11.

 

[baboma]

System freezes like yours would point to a HW issue. It can be any number of things, but high on the list would be the motherboard or RAM.

Do the RAM first, since it's easier (and cheaper) to replace. You can try the software approach: Windows has built-in memory diags. Run that. Then, try some of the popular 3rd-party mem testers.

But thorough mem testing takes a long time. I prefer the HW approach. Assuming you have 2 DDR4 sticks, then chances are if there's a failure, it'll be just one and not both. So, yank one. If BSODs continue, put it back and yank the other one. This will tell you if it's a RAM problem. DDR4 is dirt cheap now, so this would be a preferred outcome.

If not, then we come to the motherboard (I consider CPU failure to be low probability, unless you've been OC'ing all this time, then, yeah, it's a probability). There's not a shortcut here, you need to have a known-good board to swap out.

Edit: But before doing any major transplant, consider first to take system apart, clean everything of dust, then putting it back together. There isn't a completely logical reason for doing this, other than the weak rationale of a marginal connector somewhere being the culprit. But in my long experience of a DIYer, this "clean and hope" method has magically fixed my systems on more than one occasion.

 

[alex.loeflath]

Out of curiosity, as I've been experiencing the same exact thing and symptoms for nearly 2 weeks now with a 5950x / Gigabyte X57Os/BeQuiet 12 system, did you happen to have a inpoutx64.sys driver in your PC (c:\windows\system32\drivers\)?

It's like I'm reading my own thread over at the MS forums ( constantly freezing, sometimes with a DPC WATCHDOG VIOLATION BSOD). I ended up doing a Win 11 Reset (kept files), yet it still freezes on both reg and safe modes. Not sure yet if the inpoutx64 driver that's related to RGB software is to blame, but it reappeared after a fresh installation of Win 11.

i checked it, i dont have such a file. Was worth a try though, thanks.

 

[alex.loeflath]

System freezes like yours would point to a HW issue. It can be any number of things, but high on the list would be the motherboard or RAM.

Do the RAM first, since it's easier (and cheaper) to replace. You can try the software approach: Windows has built-in memory diags. Run that. Then, try some of the popular 3rd-party mem testers.

But thorough mem testing takes a long time. I prefer the HW approach. Assuming you have 2 DDR4 sticks, then chances are if there's a failure, it'll be just one and not both. So, yank one. If BSODs continue, put it back and yank the other one. This will tell you if it's a RAM problem. DDR4 is dirt cheap now, so this would be a preferred outcome.

i ran mem check and removed sticks/changed sockets, no help. When it happend for the first time ~2 weeks ago, it was once every few days, now its within minutes after booting windows . Im out of ideas by now. Seems like the hardware is rapidly dying without any clue why or what. I never ran OC except for xmp and PBO, it was always well cooled and dust free

 

[baboma]

>When it happend for the first time ~2 weeks ago, it was once every few days, now its within minutes after booting windows.

A steadily worsening fault is pretty symptomatic of a HW issue, as a marginal part gets worse.

Since you've gone thru clean Win install step, I assume you've done the rest of the troubleshooting mantra, viz stripped down to bare minimum config, both hardware & software (ie safe mode).

>Seems like the hardware is rapidly dying without any clue why or what

That's not true. All the steps above helps you to narrow down the possible cause by process of elimination. What's left is the board, the CPU, or a connector fault. From most to least likely: connector, board, CPU. So, proceed on that basis, and take everything apart, clean, and put back together.

After that, swap out either the CPU or board, whichever is cheaper and more expedient for you.

Edit: Oops, next step after disassemble/clean/reassemble should be to swap out GPU, before main board or CPU.

 

[alex.loeflath]

>When it happend for the first time ~2 weeks ago, it was once every few days, now its within minutes after booting windows.

A steadily worsening fault is pretty symptomatic of a HW issue, as a marginal part gets worse.

Since you've gone thru clean Win install step, I assume you've done the rest of the troubleshooting mantra, viz stripped down to bare minimum config, both hardware & software (ie safe mode).

>Seems like the hardware is rapidly dying without any clue why or what

That's not true. All the steps above helps you to narrow down the possible cause by process of elimination. What's left is the board, the CPU, or a connector fault. From most to least likely: connector, board, CPU. So, proceed on that basis, and take everything apart, clean, and put back together.

After that, swap out either the CPU or board, whichever is cheaper and more expedient for you.

Edit: Oops, next step after disassemble/clean/reassemble should be to swap out GPU, before main board or CPU.

The weird part is, i repeated a mem test right now, after it instantly froze within a minute for the last 3 startups, and it went through both leaps without freezing. After the check it booted into windows and i let it idle for 30 minutes, it was working fine after. Then i opened some windows settings and apps, and it froze.
I swapped out the 3080 for a 2080 and it still occured. which part isnt used at all in mem check but in windows? That shouldnt be RAM+CPU+Mainboards core functionality.
it kind of feels like something regarding the drives is at fault, but not the drives themself.
i tried different mouse+keyboard too

 

[SkyNetRising]

The weird part is, i repeated a mem test right now, after it instantly froze within a minute for the last 3 startups, and it went through both leaps without freezing.
That shouldnt be RAM+CPU+Mainboards core functionality.

What is your ram configuration?
How many ram modules.

Try with single ram module installed.

 

[alex.loeflath]

What is your ram configuration?
How many ram modules.

Try with single ram module installed.

i think i phrased it wrong, it froze on the last 3 *windows startups* (within 3 minutes of clicking through settings and apps), but the whole memory check went fine when i went directly into it after booting windows.
Im using 4 Sticks, but it also happens with only 1 4 GB stick from a different working computer.