我的windows电脑最近经常蓝屏

向东 李 0 信誉分
2025-10-23T09:16:50.9266667+00:00

我的windows电脑最近经常蓝屏，有时一天会蓝屏好几次，终止代码: SYSTEM SERVICE EXCEPTION (0x3B)，我使用windbg对蓝屏dmp文件进行分析，结果如下：

Loading Dump File [C:\Windows\Minidump\102325-61718-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 (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 26100.1.amd64fre.ge_release.240331-1435
Kernel base = 0xfffff805`cd000000 PsLoadedModuleList = 0xfffff805`cdef4f10
Debug session time: Thu Oct 23 00:51:24.346 2025 (UTC + 8:00)
System Uptime: 0 days 9:04:10.747
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000aa`e86e5018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`cd4f6430 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffda06`21a95ea0=000000000000003b
7: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000aa`e86e5018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff805cd94cbe3, Address of the instruction which caused the BugCheck
Arg3: ffffda0621a96800, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2328

    Key  : Analysis.Elapsed.mSec
    Value: 45892

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27920.1001

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_nt!PpmSetProfilePolicySetting

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

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

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

    Key  : Failure.Hash
    Value: {38ffd29c-15c8-1b96-dca6-5ce8d399e936}

    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  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 1.27.0.0


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff805cd94cbe3

BUGCHECK_P3: ffffda0621a96800

BUGCHECK_P4: 0

FILE_IN_CAB:  102325-61718-01.dmp

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


FAULTING_THREAD:  ffff9101ef4f6080

CONTEXT:  ffffda0621a96800 -- (.cxr 0xffffda0621a96800)
rax=fefff805cc0242e0 rbx=0000000000000000 rcx=fdba245e2a944e69
rdx=0000000000000002 rsi=fffff805cdfc55f8 rdi=0000000000000000
rip=fffff805cd94cbe3 rsp=ffffda0621a97250 rbp=0000000000000000
 r8=000000000000002b  r9=ffffa18f147f4002 r10=ffffa18f147f4044
r11=0000000000000001 r12=ffffa18f147f4034 r13=fffff805cdfc5600
r14=00000000000000a0 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
nt!PpmSetProfilePolicySetting+0x9b:
fffff805`cd94cbe3 0f1000          movups  xmm0,xmmword ptr [rax] ds:002b:fefff805`cc0242e0=????????????????????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:  
ffffda06`21a97250 fffff805`cd94bda6     : ffffa18f`147f4030 00000000`00000000 ffffa18f`147f4044 ffffa18f`147f4044 : nt!PpmSetProfilePolicySetting+0x9b
ffffda06`21a97310 fffff805`cda16a1e     : 00000000`00000000 ffffda06`21a97449 00000000`00000000 ffffa18f`147f4000 : nt!PopSetNewPolicyValue+0x9a
ffffda06`21a97370 fffff805`cda16978     : 00000000`6f706d55 00000000`00001000 00000000`00000100 fffff805`cd29cee2 : nt!PopUmpoProcessPowerMessage+0x16
ffffda06`21a973a0 fffff805`cda16874     : ffff9101`dbdddf90 ffffda06`21a975b0 00000000`00001000 00000000`00000000 : nt!PopUmpoProcessMessage+0x5c
ffffda06`21a974b0 fffff805`cd4441f9     : ffff9101`dbdddf90 ffff9101`db7ff900 ffff9101`db7ff950 00000000`00010004 : nt!PopUmpoProcessMessages+0x90
ffffda06`21a975d0 fffff805`cd2ad183     : ffffa18f`0ab3a940 ffff9101`dbde8b90 7fffffff`fffffffc 00000000`00000000 : nt!PopUmpoMessageCallback+0x9
ffffda06`21a97600 fffff805`cd8b7e81     : ffffa18f`0ab3a940 ffff9101`dbde8b90 ffff9101`db7ff940 00000000`00000000 : nt!ExNotifyCallback+0xc3
ffffda06`21a97640 fffff805`cd8b6f58     : ffff9101`dbde8b90 ffff9101`00000000 fffff805`00000004 00000000`00000000 : nt!AlpcpCompleteDispatchMessage+0xdf1
ffffda06`21a97730 fffff805`cd8bf22c     : 00000000`00010004 ffff9101`ef4f6080 00000000`00010004 00000000`0000004e : nt!AlpcpDispatchNewMessage+0x2e8
ffffda06`21a97790 fffff805`cd83e61e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!AlpcpSendMessage+0x96c
ffffda06`21a978e0 fffff805`cd6b1455     : ffffda06`21a97aa0 ffff9101`ef4f6080 000000aa`e93fdad8 000000aa`e93fd848 : nt!NtAlpcSendWaitReceivePort+0x24e
ffffda06`21a979b0 00007fff`c51e2da4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000aa`e93fdab8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`c51e2da4


SYMBOL_NAME:  nt!PpmSetProfilePolicySetting+9b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.6899

STACK_COMMAND: .cxr 0xffffda0621a96800 ; kb

BUCKET_ID_FUNC_OFFSET:  9b

FAILURE_BUCKET_ID:  AV_nt!PpmSetProfilePolicySetting

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {38ffd29c-15c8-1b96-dca6-5ce8d399e936}

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

帮忙分析一下是哪里的问题造成的蓝屏

Windows 商业版 | 面向 IT 专业人士的 Windows 客户端 | 性能 | Windows 桌面和 shell 体验
0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. Henry Mai 8,235 信誉分 独立顾问
    2025-10-23T16:51:10.04+00:00

    你好**向东李，**我是亨利。

    我们将从STACK_TEXT中阅读崩溃。 ****这是导致蓝屏的函数调用序列。让我们自下而上地阅读它，就像侦探追溯步骤一样：

    1. NT！KiSystemServiceCopyEnd：从用户模式（常规程序）到 Windows 内核的系统调用刚刚完成。
    2. NT！NtAlpcSendWaitReceivePort：系统调用用于 ALPC （高级本地过程调用）。这是系统服务 （（如 svchost.exe） ） 与内核模式驱动程序通信的主要方式。
    3. NT！PopUmpoProcessPowerMessage & nt！PopSetNewPolicyValue：通过 ALPC 发送的消息是 电源消息。Windows 电源管理器 （Pop） 收到它并开始处理设置新电源策略的请求。
    4. NT！PpmSetProfilePolicySetting：然后，电源管理器调用 处理器电源管理 （Ppm） 函数，将特定设置应用于电源配置文件。
    5. 崩溃： 在 PpmSetProfilePolicySettings 中，发生崩溃。指令 movups xmm0，xmmword ptr [拉克斯] 尝试从存储在 rax 寄存器中的内存地址读取数据。错误 c0000005（访问冲突）表示 rax 中的地址无效，指向不存在或受保护的内存。

    总之，在 svchost.exe 下运行的服务向 Windows 电源管理器发送了更改 CPU 电源设置的请求。电源管理器尝试满足此请求，但收到了一段损坏的数据（错误的内存地址）。当它试图使用这些数据时，整个系统崩溃了。

    这似乎是卸载不当的第三方驱动程序或服务的症状。

    此答案是否有帮助?

    0 个注释

你的答案

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