通过

如何解决0x133蓝屏问题

sir chen 0 信誉分
2026-02-26T09:47:11.53+00:00 
************* 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.016 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Users\
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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff800`e8000000 PsLoadedModuleList = 0xfffff800`e8ef5040
Debug session time: Thu Feb 26 17:06:50.686 2026 (UTC + 8:00)
System Uptime: 0 days 0:25:44.407
Loading Kernel 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
PEB is paged out (Peb.Ldr = 00000099`6c7fd018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
【版主注：已移除个人信息】
0: kd> !analyze -v
Loading Kernel 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
PEB is paged out (Peb.Ldr = 00000099`6c7fd018).  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: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff800e8fc43b8, 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: 1328

    Key  : Analysis.Elapsed.mSec
    Value: 23176

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.System.BIOSRevision
    Value: 5.27.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff800e8fc43b8

BUGCHECK_P4: 0

FILE_IN_CAB:  022626-13421-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Overwatch.exe

STACK_TEXT:  
fffff800`7ac8ac08 fffff800`e824850c     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`e8fc43b8 : nt!KeBugCheckEx
fffff800`7ac8ac10 fffff800`e8247a3b     : 00000000`00000000 00000000`00018219 00000000`00000000 fffff800`75fc9180 : nt!KeAccumulateTicks+0x59c
fffff800`7ac8ac80 fffff800`e82e323e     : 00000000`00000000 00000003`988a0746 fffff800`75fc9180 00000000`00000000 : nt!KiUpdateRunTime+0x9b
fffff800`7ac8ae40 fffff800`e82e3c3c     : fffff800`e8e10d60 fffff800`e8e10e10 fffff800`e8f8ebf0 fffff800`00000000 : nt!KeClockInterruptNotify+0x3ee
fffff800`7ac8af40 fffff800`e86ac7be     : 00000000`0010a002 fffff800`e8e10d60 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
fffff800`7ac8afb0 fffff800`e86acfcc     : 00000000`00000000 ffffc688`3e100000 00000000`00000000 fffff800`e8eeeb80 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff800`7ac82280 fffff800`91c8addc     : 00000000`00000000 00000000`0010a0f4 ffffc688`4ea3a310 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff800`7ac82410 00000000`00000000     : 00000000`0010a0f4 ffffc688`4ea3a310 00000000`00000000 00000000`00000020 : nvlddmkm+0x9addc


SY

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 

BUCKET_ID_FUNC_OFFSET:  

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {

Followup:     MachineOwner
---------
Windows 家庭版 | Windows 11 | “应用”
0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Ian-Ng 9,965 信誉分 Microsoft 外部员工 仲裁人
    2026-02-26T18:07:43.0133333+00:00

    此回复为自动翻译。因此，可能存在语法错误或表达生硬的地方。

    你好 @sir chen，

    欢迎来到 Microsoft Q&A 论坛。

    感谢你分享转储文件（dump）的详细信息。我明白在游戏过程中遇到蓝屏死机（BSOD）非常令人沮丧，尤其是当它中断比赛且发生得毫无规律时。

    根据你提供的信息，崩溃类型为 DPC_WATCHDOG_VIOLATION (0x133)。这通常意味着系统在高中断级别（DISPATCH_LEVEL 或以上）运行时间过长，最常见的原因是某个驱动程序未能在预期的窗口期内完成工作。

    你的追踪记录显示，在运行 Overwatch.exe 期间，堆栈中出现了 nvlddmkm.sys（NVIDIA 内核模式驱动程序）。这强烈表明显卡驱动路径涉及其中（尽管这本身并不总能证明它是唯一的“元凶”）。

    为了解决 0x133 超时问题，请优先执行以下三个基础步骤：

    1. 重新清洁安装驱动程序：
      从制造商（笔记本）或 NVIDIA 官网（台式机）下载最新驱动。运行安装程序，选择自定义（高级），并勾选“执行清洁安装”。这将替换损坏的组件并将所有配置文件重置为出厂默认设置。
    2. 固件和芯片组更新：
      访问主板或笔记本的支持页面，安装最新的 BIOS/UEFI 和芯片组驱动程序。这些更新通常包含针对 PCIe 电源管理和系统稳定性的关键修复，能解决 CPU 与 GPU 之间的“看门狗”异步问题。
    3. 电源稳定性调整：
      通过调整两项设置，防止 GPU 进入不稳定的低功耗状态：
      • NVIDIA 控制面板：将“电源管理模式”设置为“最高性能优先”。
      • Windows 电源选项：将“PCI Express > 链接状态电源管理”设置为“关闭”。
    4. 电源/显卡稳定性优化：
      • NVIDIA 控制面板 > 电源管理模式：尝试“最高性能优先”。
      • Windows 电源计划：测试“高性能”模式；设置 PCI Express > 链接状态电源管理 = 关闭。
    5. 切换硬件加速 GPU 计划 (HAGS)：
      • 设置 > 系统 > 屏幕 > 显示卡 > 更改默认图形设置 → 关闭 HAGS → 重启电脑。
    6. 硬件检查（散热/供电）：
      • 监控负载下的 GPU 温度，并确保 PCIe 电源线插接牢固；过热或供电不稳定在游戏负载下常表现为超时。

    如果问题仍然存在，为了进一步缩小范围，请告知以下信息：

    • 你的设备是台式机还是笔记本？GPU 型号是什么？
    • 目前安装的是哪个 NVIDIA 驱动版本？该问题是仅在《守望先锋》中出现，还是在其他游戏中也会发生？
    • 是否开启了任何超频/降压设置（涉及 GPU/CPU/内存）？

    回复这些详细信息后，我可以根据你的配置帮助你确定下一步的最佳操作。

你的答案

提问者可以将答案标记为“已接受”，版主可以将答案标记为“已推荐”，这有助于用户了解答案是否解决了提问者的问题。