Появляется ошибка DPC_WATCHDOG_VIOLATION (133), пробовал менять на разные драйвера(удалял каждый раз с помощью DDU не в безопасном режиме), при одинаковой эксплуатации ошибка может не появляться неделю, а потом по 1-3 раза в день, прилагаю дамп памяти.

Dmitrii 0 Баллы репутации
2026-04-03T07:46:16.2033333+00:00 

ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:
ExtensionGallery ExtensionRepository: Implicit

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
OK                                             C:\Windows\Minidump

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- 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.094 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29547.1002 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040326-18515-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 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff806`84200000 PsLoadedModuleList = 0xfffff806`850f50c0
Debug session time: Fri Apr  3 14:31:13.558 2026 (UTC + 7:00)
System Uptime: 1 days 2:26:14.751
Loading Kernel Symbols
..DBGHELP: Timeout to store: C:\ProgramData\Dbg\sym*https://msdl.microsoft.com/download/symbols
DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols


Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
................................................................
..................
Loading User Symbols

Loading unloaded module list
.............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`846fb990 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff806`16e111d0=0000000000000133
0: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
..................
Loading User Symbols

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: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff806851c43b8, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: 1062

    Key  : Analysis.Elapsed.mSec
    Value: 13817

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    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_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.System.BIOSRevision
    Value: 1.32.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff806851c43b8

BUGCHECK_P4: 0

FILE_IN_CAB:  040326-18515-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff806851d15c0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff806`16e111c8 fffff806`8449c95c     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`851c43b8 : nt!KeBugCheckEx
fffff806`16e111d0 fffff806`8449be8b     : 00000000`00000000 00000000`005cf1af 00000000`00000000 fffff806`10e25180 : nt!KeAccumulateTicks+0x59c
fffff806`16e11240 fffff806`8453a9ce     : 00000000`00000000 000000dd`9892a2e3 fffff806`10e25180 ffffbfdf`eff7ff80 : nt!KiUpdateRunTime+0x9b
fffff806`16e11400 fffff806`8453b3cc     : fffff806`85010e00 fffff806`85010eb0 fffff806`8518eec8 ffffd08f`2a6f5000 : nt!KeClockInterruptNotify+0x3ee
fffff806`16e11500 fffff806`848ace3e     : 00000000`00611e08 fffff806`85010e00 fffff806`8518efa0 fffff806`8461838a : nt!KiCallInterruptServiceRoutine+0x32c
fffff806`16e11570 fffff806`848ad64c     : 00000000`00000046 fffff806`16e116b0 00000000`00b81014 fffff806`848ace3e : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff806`16e115c0 fffff806`34e63523     : 00000000`00000000 fffff806`16e11a80 00000000`00000000 fffff806`16e11a01 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff806`16e11750 00000000`00000000     : fffff806`16e11a80 00000000`00000000 fffff806`16e11a01 00000000`00000000 : nvlddmkm+0xe3523


SYMBOL_NAME:  nvlddmkm+e3523

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xfffff806851cef00; .thread /r /p 0xfffff806851d15c0 ; kb

BUCKET_ID_FUNC_OFFSET:  e3523

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------
Windows для дома | Windows 11 | Снижение производительности и системные сбои
Комментариев: 0

1 ответ

Сортировать по: Наиболее полезные
Наиболее полезные Новейшие Самые старые
  1. DaveM121 939.6K Баллы репутации Независимый помощник
    2026-04-03T08:19:08.69+00:00

    Данные файла минидампа указывают на то, что причиной сбоев вашего ПК являются драйверы Nvidia; других проблем в вашей системе не обнаружено.

    Полностью удалите текущий драйвер устройства Nvidia с помощью широко доступной бесплатной утилиты DDU, затем перезагрузите компьютер и перейдите на веб-сайт Nvidia, чтобы загрузить и установить несколько немного более старых версий драйвера устройства Nvidia, чтобы попытаться найти стабильную версию для вашей системы.

    Этот ответ помог вам?

Ваш ответ

Автор вопроса может устанавливать для ответов пометку "Принято", а модераторы — пометку "Рекомендуется". Благодаря этому пользователям становится проще понять, какой из ответов помог решить проблему автора.