蓝屏代码 pnp detected fatal error已使用windbg分析 下面是相关代码Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\082622-9265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`51a14000 PsLoadedModuleList = 0xfffff801`51e2b510
Debug session time: Fri Aug 26 22:56:11.171 2022 (UTC + 8:00)
System Uptime: 0 days 3:13:19.038
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
Loading unloaded module list
..................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`51bcc9c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8d8f`1d42f8a0=00000000000000ca
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 000000000000000a, Incorrect notify callback behavior
    Driver failed to preserve IRQL or combined APC disable across
    a PnP notification.
Arg2: ffff958f899cfe30, Driver Object.
Arg3: 0000000000000000, IRQL after returning from driver callback.
Arg4: 000000000000fffd, Combined APC disable count after returning from driver callback.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2296

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 95682

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xca

    Key  : Bugcheck.Code.Register
    Value: 0xca

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  082622-9265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  ca

BUGCHECK_P1: a

BUGCHECK_P2: ffff958f899cfe30

BUGCHECK_P3: 0

BUGCHECK_P4: fffd

DEVICE_OBJECT: ffff958f899cfe30

DRIVER_OBJECT: 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff8d8f`1d42f898 fffff801`521f0e06     : 00000000`000000ca 00000000`0000000a ffff958f`899cfe30 00000000`00000000 : nt!KeBugCheckEx
ffff8d8f`1d42f8a0 fffff801`52116e37     : ffffd38d`36605ef0 ffffd38d`4a34de90 00000000`ffffffff ffffd38d`36605ef0 : nt!PnpNotifyDriverCallback+0xe1192
ffff8d8f`1d42f950 fffff801`51fa2379     : ffffd38d`4a34ddf0 ffff958f`9b0860c0 ffff8d8f`00000000 00000000`00000000 : nt!PnpNotifyDeviceClassChange+0x183
ffff8d8f`1d42f9f0 fffff801`51a42f1a     : ffff958f`79e9aa20 ffff958f`8eda4040 fffff801`51fa2180 ffff958f`9b0860c0 : nt!PnpDeviceEventWorker+0x1f9
ffff8d8f`1d42fa70 fffff801`51b472a5     : ffff958f`8eda4040 ffff958f`79e99300 ffff958f`8eda4040 00ffffff`00ffffff : nt!ExpWorkerThread+0x16a
ffff8d8f`1d42fb10 fffff801`51bd3e6c     : ffffc081`09960180 ffff958f`8eda4040 fffff801`51b47250 00db903a`00ffffff : nt!PspSystemThreadStartup+0x55
ffff8d8f`1d42fb60 00000000`00000000     : ffff8d8f`1d430000 ffff8d8f`1d429000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


SYMBOL_NAME:  nt!PnpNotifyDriverCallback+e1192

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.17763.3346

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  e1192

FAILURE_BUCKET_ID:  0xCA_a_nt!PnpNotifyDriverCallback

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {50c16676-c583-e05e-3ea7-996c43dbc0c4}

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 000000000000000a, Incorrect notify callback behavior
    Driver failed to preserve IRQL or combined APC disable across
    a PnP notification.
Arg2: ffff958f899cfe30, Driver Object.
Arg3: 0000000000000000, IRQL after returning from driver callback.
Arg4: 000000000000fffd, Combined APC disable count after returning from driver callback.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1906

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1909

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xca

    Key  : Bugcheck.Code.Register
    Value: 0xca

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  082622-9265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  ca

BUGCHECK_P1: a

BUGCHECK_P2: ffff958f899cfe30

BUGCHECK_P3: 0

BUGCHECK_P4: fffd

DEVICE_OBJECT: ffff958f899cfe30

DRIVER_OBJECT: 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff8d8f`1d42f898 fffff801`521f0e06     : 00000000`000000ca 00000000`0000000a ffff958f`899cfe30 00000000`00000000 : nt!KeBugCheckEx
ffff8d8f`1d42f8a0 fffff801`52116e37     : ffffd38d`36605ef0 ffffd38d`4a34de90 00000000`ffffffff ffffd38d`36605ef0 : nt!PnpNotifyDriverCallback+0xe1192
ffff8d8f`1d42f950 fffff801`51fa2379     : ffffd38d`4a34ddf0 ffff958f`9b0860c0 ffff8d8f`00000000 00000000`00000000 : nt!PnpNotifyDeviceClassChange+0x183
ffff8d8f`1d42f9f0 fffff801`51a42f1a     : ffff958f`79e9aa20 ffff958f`8eda4040 fffff801`51fa2180 ffff958f`9b0860c0 : nt!PnpDeviceEventWorker+0x1f9
ffff8d8f`1d42fa70 fffff801`51b472a5     : ffff958f`8eda4040 ffff958f`79e99300 ffff958f`8eda4040 00ffffff`00ffffff : nt!ExpWorkerThread+0x16a
ffff8d8f`1d42fb10 fffff801`51bd3e6c     : ffffc081`09960180 ffff958f`8eda4040 fffff801`51b47250 00db903a`00ffffff : nt!PspSystemThreadStartup+0x55
ffff8d8f`1d42fb60 00000000`00000000     : ffff8d8f`1d430000 ffff8d8f`1d429000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


SYMBOL_NAME:  nt!PnpNotifyDriverCallback+e1192

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.17763.3346

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  e1192

FAILURE_BUCKET_ID:  0xCA_a_nt!PnpNotifyDriverCallback

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {50c16676-c583-e05e-3ea7-996c43dbc0c4}

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 000000000000000a, Incorrect notify callback behavior
    Driver failed to preserve IRQL or combined APC disable across
    a PnP notification.
Arg2: ffff958f899cfe30, Driver Object.
Arg3: 0000000000000000, IRQL after returning from driver callback.
Arg4: 000000000000fffd, Combined APC disable count after returning from driver callback.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1921

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1927

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xca

    Key  : Bugcheck.Code.Register
    Value: 0xca

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  082622-9265-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  ca

BUGCHECK_P1: a

BUGCHECK_P2: ffff958f899cfe30

BUGCHECK_P3: 0

BUGCHECK_P4: fffd

DEVICE_OBJECT: ffff958f899cfe30

DRIVER_OBJECT: 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff8d8f`1d42f898 fffff801`521f0e06     : 00000000`000000ca 00000000`0000000a ffff958f`899cfe30 00000000`00000000 : nt!KeBugCheckEx
ffff8d8f`1d42f8a0 fffff801`52116e37     : ffffd38d`36605ef0 ffffd38d`4a34de90 00000000`ffffffff ffffd38d`36605ef0 : nt!PnpNotifyDriverCallback+0xe1192
ffff8d8f`1d42f950 fffff801`51fa2379     : ffffd38d`4a34ddf0 ffff958f`9b0860c0 ffff8d8f`00000000 00000000`00000000 : nt!PnpNotifyDeviceClassChange+0x183
ffff8d8f`1d42f9f0 fffff801`51a42f1a     : ffff958f`79e9aa20 ffff958f`8eda4040 fffff801`51fa2180 ffff958f`9b0860c0 : nt!PnpDeviceEventWorker+0x1f9
ffff8d8f`1d42fa70 fffff801`51b472a5     : ffff958f`8eda4040 ffff958f`79e99300 ffff958f`8eda4040 00ffffff`00ffffff : nt!ExpWorkerThread+0x16a
ffff8d8f`1d42fb10 fffff801`51bd3e6c     : ffffc081`09960180 ffff958f`8eda4040 fffff801`51b47250 00db903a`00ffffff : nt!PspSystemThreadStartup+0x55
ffff8d8f`1d42fb60 00000000`00000000     : ffff8d8f`1d430000 ffff8d8f`1d429000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c

<365>SYMBOL_NAME:  nt!PnpNotifyDriverCallback+e1192

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.17763.3346

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  e1192

FAILURE_BUCKET_ID:  0xCA_a_nt!PnpNotifyDriverCallback

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {50c16676-c583-e05e-3ea7-996c43dbc0c4}

Followup:     MachineOwner
---------您好,A&K,前来提供帮助。您的dump文件显示了系统内核的问题,这是一个很普通的错误,可能是驱动程序导致的,但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序(GPU、芯片组等),然后前往设备制造商官网下载最新版本并重新安装。
dmp文件链接:https://pan.baidu.com/s/1KMjIh0Lo1fgNZNmEE6s5zg?pwd=ndzc提取码:ndzc
您好,A&K,前来提供帮助。您的dump文件显示了系统内核的问题,这是一个很普通的错误,可能是驱动程序导致的,但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序(GPU、芯片组等),然后前往设备制造商官网下载最新版本并重新安装。

点赞(53) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部