Windows 11 BOSD - DPC Watchdog Violation

Hallo liebe Community,

seit einigen Wochen bekomme ich immer einen Bluescreen. Das tritt oft einfach so auf. Erst bekomme ich eine Bildschirm freeze für ca. 30 Sekunden und dann den Bluescreen.

Leider sind die Abstürze von davor nicht als Minidump vorhanden. Hatte die Systemeinstellungen erst angepasst.

Hier der Bluescreenviewer Screenshot:

Hier der Auszug aus dem WinDBG:

*******************************************************************************
*                                                                             *
*                        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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8000a905330, 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: 2608

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17276

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

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

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

FILE_IN_CAB:  050222-11796-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8000a905330

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

STACK_TEXT:  
ffff9b80`5b3ec9e8 fffff800`09e5483f     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`0a905330 : nt!KeBugCheckEx
ffff9b80`5b3ec9f0 fffff800`09e54451     : 00002027`3d4afb22 ffff9b80`5b3d2180 ffff3e01`eeab07d5 00000000`00094ed1 : nt!KeAccumulateTicks+0x20f
ffff9b80`5b3eca60 fffff800`09e51486     : 00000000`00094ed2 00000000`00058c45 00000016`311621fc 00000000`00000000 : nt!KiUpdateRunTime+0x61
ffff9b80`5b3ecac0 fffff800`09e52792     : ffffcf0c`c07c6600 00000000`00000000 fffff800`0a82b600 00000000`00000000 : nt!KiUpdateTime+0x686
ffff9b80`5b3eceb0 fffff800`09e500c2     : ffffcf0c`c07c6600 ffff8007`0712b650 ffff8007`00000000 00000000`00000002 : nt!KeClockInterruptNotify+0x272
ffff9b80`5b3ecf40 fffff800`09e21440     : 00000016`312d0962 ffff8007`0712b5a0 00000000`00000001 ffff8007`070fe040 : nt!HalpTimerClockInterrupt+0xe2
ffff9b80`5b3ecf70 fffff800`0a0185aa     : ffffcf0c`c07c6680 ffff8007`0712b5a0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa0
ffff9b80`5b3ecfb0 fffff800`0a018b77     : 00000000`00000000 ffff8007`070fe040 ffff9b80`5b3d2180 fffff800`0a018b84 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffcf0c`c07c6600 fffff800`09e6ba0c     : ffffffff`ffffffd1 fffff800`09f3408e 00000000`00000010 00000000`00040282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffcf0c`c07c6790 fffff800`09f3408a     : ffff9b80`5b3d2180 ffffcf0c`c07c6839 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1c
ffffcf0c`c07c67c0 fffff800`09f35659     : ffff8007`122ae080 00000000`00000002 ffffcf0c`c07c69d8 ffff8007`00000000 : nt!KiSwapThread+0xc8a
ffffcf0c`c07c68a0 fffff800`09e226b1     : 00000000`00000000 00000000`00000000 ffff8007`00000064 00000015`e992312c : nt!KiCommitThreadWait+0x159
ffffcf0c`c07c6940 fffff800`0a3786d5     : ffffcf0c`c07c6cf0 00000000`00000102 00000000`00000001 00000000`00000000 : nt!KeWaitForMultipleObjects+0x2b1
ffffcf0c`c07c6a40 fffffe41`e334c78e     : 00000000`00000000 00000000`00000000 00000000`00000001 fffffe41`e3f1ea08 : nt!ObWaitForMultipleObjects+0x2d5
ffffcf0c`c07c6f40 fffffe41`e3212056     : 00000000`00000001 fffffe20`8248e990 00000000`00000002 fffffe20`000014ff : win32kfull!xxxMsgWaitForMultipleObjectsEx+0xda
ffffcf0c`c07c6ff0 fffffe41`e30b7420     : ffff8007`122ae080 00000000`0814f070 ffff8007`00000002 00000000`000014ff : win32kfull!NtUserMsgWaitForMultipleObjectsEx+0x406
ffffcf0c`c07c7930 fffff800`0a028f75     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`0a3180c0 : win32k!NtUserMsgWaitForMultipleObjectsEx+0x20
ffffcf0c`c07c7970 00007ffe`9cc3ac04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0814e788 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`9cc3ac04

SYMBOL_NAME:  win32kfull!xxxMsgWaitForMultipleObjectsEx+da

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

IMAGE_VERSION:  10.0.22000.613

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  da

FAILURE_BUCKET_ID:  0x133_ISR_win32kfull!xxxMsgWaitForMultipleObjectsEx

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {c72a03fe-c581-13c1-2006-362593197f7d}

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

Vielen Dank schonmal im Voraus für die Hilfe :) 

P.S: Alle Treiber sind auf dem neuesten Stand