win11 KMODE_EXCEPTION_NOT_HANDLED绿屏重启

mangyu 0 信誉分
2026-07-28T08:08:55.2+00:00

电脑经常绿屏重启

************* Path validation summary **************
Response                         Time (ms)     Location
OK                                             C:\Users\szqhu\Desktop
OK                                             C:\Users\szqhu\Desktop\dmp

************* 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

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

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


Loading Dump File [C:\Users\szqhu\Desktop\dmp\072826-22015-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 29634 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 29634.1000.amd64fre.rs_prerelease.260719-1319
Kernel base = 0xfffff800`ac000000 PsLoadedModuleList = 0xfffff800`acedf700
Debug session time: Tue Jul 28 14:09:09.993 2026 (UTC + 8:00)
System Uptime: 0 days 1:58:25.767
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols

Loading unloaded module list
............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`ac59f310 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc3d7`e1d9d100=000000000000001e
15: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols

Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800ac2c9b68, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ContextRecord                                 ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : AV.Page.Virtual
    Value: 0xffffffffffff0000

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 2484

    Key  : Analysis.Elapsed.mSec
    Value: 7045

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Failure.Bucket
    Value: AV_nt!KiDeferredReadySingleThread

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff800ac2c9b68

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x2c9b68

    Key  : Failure.Hash
    Value: {626f59d5-90cc-ab48-85f0-60e170096c96}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: rs_prerelease

    Key  : WER.OS.Version
    Value: 10.0.29634.1000

    Key  : WER.System.BIOSRevision
    Value: 5.17.0.0


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff800ac2c9b68

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB:  072826-22015-01.dmp

FAULTING_THREAD:  fffff632dba1c280

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff800acfbe510: Unable to get MiVisibleState
 ffffffffffffffff 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nt!KiDeferredReadySingleThread+2378
fffff800`ac2c9b68 488b4250        mov     rax,qword ptr [rdx+50h]

STACK_TEXT:  
ffffc3d7`e1d9d0f8 fffff800`ac646e46     : 00000000`0000001e ffffffff`c0000005 fffff800`ac2c9b68 00000000`00000000 : nt!KeBugCheckEx
ffffc3d7`e1d9d100 fffff800`ac74ac52     : ffffbc44`783cce88 ffffc3d7`e1d9d910 ffffc3d7`e1d9d1c0 00000000`00000000 : nt!KiFatalExceptionHandler+0x22
ffffc3d7`e1d9d140 fffff800`ac2d77c9     : 00000000`00000001 fffff800`ac74172e ffffc3d7`e1d9d770 ffffc3d7`e1d9d1c0 : nt!RtlpExecuteHandlerForException+0x12
ffffc3d7`e1d9d170 fffff800`ac2d707e     : 00000000`00000000 ffffc3d7`e1d9de10 00000000`00000000 00000000`00000000 : nt!RtlDispatchException+0x309
ffffc3d7`e1d9d8e0 fffff800`ac7406f2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x65e
ffffc3d7`e1d9dfb0 fffff800`ac7406c0     : fffff800`ac75675b 00000000`00000001 00000000`00000000 fffff632`dc69a880 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffbc44`783ccd48 fffff800`ac75675b     : 00000000`00000001 00000000`00000000 fffff632`dc69a880 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffbc44`783ccd50 fffff800`ac750b08     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x15b
ffffbc44`783ccf30 fffff800`ac2c9b68     : fffff632`dd8ac040 fffff633`10990000 fffff632`db71d940 fffff800`ac21f920 : nt!KiGeneralProtectionFaultDispatchTrap+0x68
ffffbc44`783cd0c0 fffff800`ac2c70c4     : ffffc3d7`e19cb180 00000000`00000000 00000000`00000000 ffffc3d7`e19cb180 : nt!KiDeferredReadySingleThread+0x2378
ffffbc44`783cd300 fffff800`ac2c74c5     : 00000000`00000002 00000000`00000023 ffffbc44`783cd7a0 fffff633`4b8ea1c0 : nt!KiProcessThreadWaitList+0x174
ffffbc44`783cd5e0 fffff800`ac3297ea     : fffff2dd`00000200 00000000`00000000 fffff633`4b8ea080 00000010`00000007 : nt!KiExitDispatcher+0x45
ffffbc44`783cd640 fffff800`ac32817e     : ffffc3d7`e1f17180 fffff800`ace1ae48 00000000`00000000 00000000`00000000 : nt!KeInsertPriQueue+0x35a
ffffbc44`783cd6d0 fffff800`ac327de5     : ffffc3d7`e1f17101 ffffbc44`783cd828 00000000`00000001 fffff800`ace1add8 : nt!ExpQueueWorkItemToQueue+0x1b6
ffffbc44`783cd750 fffff800`ac511dcd     : ffffbc44`00000010 ffffbc44`783cd8b9 fffff632`dba1c200 ffffc3d7`e1f17180 : nt!ExQueueWorkItem+0x1b5
ffffbc44`783cd7e0 fffff800`ac33f4df     : fffff800`ace1adc8 00000010`8b5e0fce 00000010`8b5e0fce fffff800`3b3be600 : nt!KiIdealProcessorRebalancerTimerCallback+0x4d
ffffbc44`783cd810 fffff800`ac33efa4     : fffff632`db9ff3e8 00000000`00000007 fffff632`db9ff498 fffff632`00000019 : nt!KiExpireTimer2+0x22f
ffffbc44`783cd920 fffff800`ac21cac4     : 00000010`8b5e0fce 00000000`00000000 00000000`00000001 ffffc3d7`e1f17180 : nt!KiTimer2Expiration+0x1b4
ffffbc44`783cd9e0 fffff800`ac74172e     : 00000000`00000000 fffff632`dba1c200 fffff800`ac741600 00000000`00000000 : nt!KiRetireDpcList+0x294
ffffbc44`783cdc10 00000000`00000000     : ffffbc44`783ce000 ffffbc44`783c8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KiDeferredReadySingleThread+2378

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.29634.1000

STACK_COMMAND: .process /r /p 0xfffff800acfcef40; .thread /r /p 0xfffff632dba1c280 ; kb

BUCKET_ID_FUNC_OFFSET:  2378

FAILURE_BUCKET_ID:  AV_nt!KiDeferredReadySingleThread

OS_VERSION:  10.0.29634.1000

BUILDLAB_STR:  rs_prerelease

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {626f59d5-90cc-ab48-85f0-60e170096c96}

Followup:     MachineOwner
---------
Windows 预览体验计划 | Windows Insider Preview | 性能和维护
0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Lucus-V 13,645 信誉分 Microsoft 外部员工 审查方
    2026-07-28T19:00:19.4333333+00:00

    免责声明：请注意，所提供的信息是使用自动翻译工具翻译的。尽管我们力求准确，但翻译内容可能无法完全反映原始内容的含义、上下文或意图。

    嗨 mangyu,

    感谢您提供转储分析结果。

    根据现有的小型转储文件，我们可以确认系统在执行 nt!KiDeferredReadySingleThread 时遇到了 KMODE_EXCEPTION_NOT_HANDLED** (0x1E) 错误，并伴有 Access Violation ****(0xC0000005)**（访问冲突）。该故障涉及无效的内存引用（0xFFFFFFFFFFFFFFFF），这通常表明存在内存损坏，而非 Windows 组件本身直接发生故障。

    由于调用堆栈中仅包含 Microsoft 内核函数，并且该转储文件属于小型内核转储，因此目前无法确定导致内存损坏的具体组件。

    为了帮助进一步缩小问题根源的范围，烦请您提供以下信息：

    • 绿屏是否会在进行某些特定操作时出现，例如玩游戏、播放视频、系统空闲、睡眠或唤醒、传输文件等？
    • 近期是否更换过任何硬件、更新过 BIOS 或驱动程序，或者安装过新的应用程序？
    • 系统是否正在使用任何第三方防病毒软件、RGB 灯效控制工具、硬件监控工具、超频软件、虚拟化软件，或者 VPN／网络筛选驱动程序？
    • 您能否提供电脑的具体型号或主板型号？
    • 是否还有其他转储文件可供分析？每次崩溃是否都会产生类似的错误检查代码？

    与此同时，建议您尝试以下步骤：

    1. 检查并安装驱动程序和固件更新。
    2. 排除可能造成系统不稳定的因素。暂时禁用或卸载以下项目：
      • 超频或降压配置；
      • 硬件调校软件；
      • RGB 灯效控制软件；
      • 第三方防病毒软件或安全软件。
    3. 验证 Windows 系统文件。以管理员身份打开命令提示符，然后依次运行以下命令： 
         DISM /Online /Cleanup-Image /RestoreHealth
   sfc /scannow
    4. 测试系统内存。 请使用 Memtest 或 Memtest86 等工具检查内存。建议在 DOS 或独立启动环境中执行内存测试，并至少完整运行 3 至 4 轮，以确保对内存进行充分检测。

    免责声明: 微软不提供任何暗示或其他保证和/或保证，对您从第三方链接网站获得的信息或任何与技术相关的支持不负责。

    完成上述操作后，请继续观察问题是否仍然存在。

    如果您有更多相关信息，欢迎随时告知我。

    此答案是否有帮助?

你的答案

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