BSOD DPC_WATCHDOG_VIOLATION 0x133

Question

Здравствуйте у меня возникла проблема начали часто вылетать BSOD каждый день по 7-10 раз код DPC_WATCHDOG_VIOLATION 0x133 проблема впервые выскочила год назад но после того как я закрепил диск m.2 понадежнее и сменил термопасту она пропала но вновь появилась смотрел много гайдов менял местами оперативку заменял ее менял блок питания менял видеокарту менял диск на котором винда проверял их целостности но ничего не помогает сейчас скачал прогу winDBG закинул туда 2 dmp файла просмотрел и вот что тут написано
первый как то связан с discord
второй с riot client

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff805`26000000 PsLoadedModuleList = 0xfffff805`26c2a830
Debug session time: Thu Jul 31 22:12:19.783 2025 (UTC + 3:00)
System Uptime: 0 days 9:29:41.516
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000da`78f9c018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`263fe2a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffb181`21b81e20=0000000000000133
10: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000da`78f9c018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        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: fffff80526cfb320, 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: 1484

    Key  : Analysis.Elapsed.mSec
    Value: 5966

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_DPC_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80526cfb320

FILE_IN_CAB:  073125-13546-01.dmp

FAULTING_THREAD:  ffffda085f7f4080

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffae8e672c7410 -- (.trap 0xffffae8e672c7410)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff80526c2b1a0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff805262d3ddc rsp=ffffae8e672c75a0 rbp=ffffae8e672c76a9
 r8=0000000000000001  r9=ffffae8e672c7790 r10=0000000000000000
r11=ffffae8e672c7700 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KxWaitForSpinLockAndAcquire+0x2c:
fffff805`262d3ddc 488b07          mov     rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:  
ffffb181`21b81e18 fffff805`264411c6     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffb181`21b81e20 fffff805`262689f3     : 00005a53`2bb7edd5 ffffb181`21b2f180 00000000`00000000 ffffb181`21b2f180 : nt!KeAccumulateTicks+0x1d5f56
ffffb181`21b81e80 fffff805`262684da     : ffffda08`50d2d3e0 ffffae8e`672c7490 ffffae8e`672bfa00 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffffb181`21b81f30 fffff805`262d3735     : ffffda08`50d2d3e0 00000000`00000000 00000000`00000000 ffff4202`225e40ed : nt!HalpTimerClockIpiRoutine+0x1a
ffffb181`21b81f60 fffff805`264002da     : ffffae8e`672c7490 ffffda08`50d2d3e0 00005a45`a512164c 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb181`21b81fb0 fffff805`26400b07     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffae8e`672c7410 fffff805`262d3ddc     : 00000000`00000000 00000000`00000000 00000000`00000009 fffff805`26263e3b : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffae8e`672c75a0 fffff805`262580ac     : fffff805`26c2b1a0 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x2c
ffffae8e`672c75d0 fffff805`2626f5ad     : ffffae8e`672c7790 fffff805`59433fbe 00000000`00000000 fffff805`26270344 : nt!KeAcquireSpinLockAtDpcLevel+0x5c
ffffae8e`672c7600 fffff805`2626f377     : 00000000`00000002 0f0f0f0f`00000000 00000000`00000002 ffffae8e`672c7e80 : nt!KeIntSteerPeriodic+0x5d
ffffae8e`672c7710 fffff805`26342730     : ffffae8e`672c7e80 ffffb181`21b2f180 00005a45`a512164c ffffb181`21b2f180 : nt!PpmParkSteerInterrupts+0x447
ffffae8e`672c7b40 fffff805`2621f4de     : ffffb181`21b32240 ffffda08`50fd8000 ffffb181`21b2f180 ffffda08`00000002 : nt!PpmCheckRun+0x40
ffffae8e`672c7bb0 fffff805`2621e7c4     : ffffb181`21b2f180 00000000`00000000 00000000`00000008 00000000`0013e27d : nt!KiExecuteAllDpcs+0x30e
ffffae8e`672c7d20 fffff805`26406b55     : 00000000`00000000 ffffb181`21b2f180 00000000`00000000 00000220`151f0018 : nt!KiRetireDpcList+0x1f4
ffffae8e`672c7fb0 fffff805`26406940     : 000000da`081fef98 0000021f`90993fd0 000000da`081ff120 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffae8e`6c7079d0 fffff805`26405d3d     : 00000220`151ec3b0 ffffda08`5d587080 00000000`00000000 ffffda08`00000000 : nt!KiDispatchInterruptContinue
ffffae8e`6c707a00 00007ffd`e4d8ce61     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2fd
000000da`081ff230 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e4d8ce61


SYMBOL_NAME:  nt!KeAccumulateTicks+1d5f56

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.4780

STACK_COMMAND: .process /r /p 0xffffda085d411080; .thread 0xffffda085f7f4080 ; kb

BUCKET_ID_FUNC_OFFSET:  1d5f56

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner
--------
************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff803`0c200000 PsLoadedModuleList = 0xfffff803`0ce2a830
Debug session time: Fri Aug  1 00:05:54.782 2025 (UTC + 3:00)
System Uptime: 0 days 0:58:37.515
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000016`57380018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`0c5fe2a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff9580`684cbe20=0000000000000133
9: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000016`57380018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        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: fffff8030cefb320, 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: 1406

    Key  : Analysis.Elapsed.mSec
    Value: 2023

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_DPC_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8030cefb320

FILE_IN_CAB:  080125-13250-01.dmp

FAULTING_THREAD:  ffffcd0a2ed68080

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  ffffca8745eb7410 -- (.trap 0xffffca8745eb7410)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8030ce2b1a0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8030c4d3ddc rsp=ffffca8745eb75a0 rbp=ffffca8745eb76a9
 r8=0000000000000001  r9=ffffca8745eb7790 r10=0000000000000000
r11=ffffca8745eb7700 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KxWaitForSpinLockAndAcquire+0x2c:
fffff803`0c4d3ddc 488b07          mov     rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  RiotClientServices.exe

STACK_TEXT:  
ffff9580`684cbe18 fffff803`0c6411c6     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9580`684cbe20 fffff803`0c4689f3     : 00000951`8c35161e ffff9580`68479180 00000000`00000000 ffff9580`68479180 : nt!KeAccumulateTicks+0x1d5f56
ffff9580`684cbe80 fffff803`0c4684da     : ffffcd0a`2593c780 ffffca87`45eb7490 ffffca87`45eafa00 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffff9580`684cbf30 fffff803`0c4d3735     : ffffcd0a`2593c780 00000000`00000000 00000000`00000000 ffffe165`756e4e6a : nt!HalpTimerClockIpiRoutine+0x1a
ffff9580`684cbf60 fffff803`0c6002da     : ffffca87`45eb7490 ffffcd0a`2593c780 00000944`06320df6 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9580`684cbfb0 fffff803`0c600b07     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffca87`45eb7410 fffff803`0c4d3ddc     : 00000001`00000000 00000000`00000000 00000000`00000000 ffffca87`45eb75a0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffca87`45eb75a0 fffff803`0c4580ac     : fffff803`0ce2b1a0 00000000`00000002 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x2c
ffffca87`45eb75d0 fffff803`0c46f5ad     : ffffca87`45eb7790 00000000`00000002 00000000`00000002 fffff803`0c470344 : nt!KeAcquireSpinLockAtDpcLevel+0x5c
ffffca87`45eb7600 fffff803`0c46f377     : 00000000`00000002 0f0f0f0f`00000000 00000000`00000002 ffffca87`45eb7e80 : nt!KeIntSteerPeriodic+0x5d
ffffca87`45eb7710 fffff803`0c542730     : ffffca87`45eb7e80 ffff9580`68479180 00000944`06320df6 ffff9580`68479180 : nt!PpmParkSteerInterrupts+0x447
ffffca87`45eb7b40 fffff803`0c41f4de     : ffff9580`6847c240 ffffcd0a`25bdc000 ffff9580`68479180 ffffcd0a`00000002 : nt!PpmCheckRun+0x40
ffffca87`45eb7bb0 fffff803`0c41e7c4     : ffff9580`68479180 00010000`00000000 00000000`00000008 00000000`0002092e : nt!KiExecuteAllDpcs+0x30e
ffffca87`45eb7d20 fffff803`0c606b55     : 00000000`00000000 ffff9580`68479180 00000000`00000000 00000000`00000000 : nt!KiRetireDpcList+0x1f4
ffffca87`45eb7fb0 fffff803`0c606940     : ffffcd0a`2ed68080 ffffca87`4a5afa80 ffffca87`4a5afa80 00000000`00000002 : nt!KxRetireDpcList+0x5
ffffca87`4a5af9d0 fffff803`0c605d3d     : ffffcd0a`2ed68080 ffffca87`4a5afa10 ffffffff`fffc2f70 ffffcd0a`00000000 : nt!KiDispatchInterruptContinue
ffffca87`4a5afa00 00007ffc`7e49361d     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2fd
00000016`591ff440 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`7e49361d


SYMBOL_NAME:  nt!KeAccumulateTicks+1d5f56

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.4780

STACK_COMMAND: .process /r /p 0xffffcd0a2e0c7080; .thread 0xffffcd0a2ed68080 ; kb

BUCKET_ID_FUNC_OFFSET:  1d5f56

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

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

Answer 1

Привет

Удалите Riot Games вместе с Vanguard и играми

https://support.microsoft.com/en-us/topic/how-to-execute-a-simple-boot-start-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd

Откройте командную строку (admin) и выполните команды: sfc /scannow и dism /online /cleanup-image /restorehealth, дождитесь завершения процесса и перезагрузите компьютер.

Затем выполните чистую загрузку и если вы хотите удалить приложения, которыми вы не пользуетесь.

Обновите BIOS и установите драйверы чипсета.

https://download.asrock.com/BIOS/1200/H510M-HDV(L1.92)ROM.zip

Как обновить: https://www.asrock.com/support/BIOSIG.br.asp?cat=BIOS9

Установка драйверов

https://download.asrock.com/Drivers/Intel/Others/ME(v14.1.60.1790v4_Consumer).zip

https://download.asrock.com/Drivers/Intel/INF/INF(v10.1.18634.8254_Public).zip

Подписаться: https://support.microsoft.com/pt-br/windows/op%C3%A7%C3%B5es-para-otimizar-o-desempenho-dos-jogos-no-windows-11-a255f612-2949-4373-a566-ff6f3f474613

Примечание: Этот веб-сайт не принадлежит Microsoft. Кажется, что страница предоставляет точную и безопасную информацию. Остерегайтесь рекламы на сайте, которая может рекламировать товары, часто классифицируемые как потенциально нежелательные товары. Тщательно изучите любой продукт, рекламируемый на сайте, прежде чем вы решите его скачать и установить.

Дайте обратную связь, была ли информация полезной или нет.

Спасибо

Answer 2

Привет

Если возможно, зайдите в проводник Windows в каталоге c:\windows\minidump. Скопируйте мини-дампы на рабочий стол и загрузите их в OneDrive.

Поделитесь ссылкой здесь, чтобы мы могли проверить, что вызывает BSOD. Чтобы увидеть модель, вы можете набрать msinfo32.exe в строке поиска Windows и сделать скриншот

Спасибо