该主题

蓝屏问题ntkrnlmp.exe

TheJoker — Sat, 14 Jan 2023 05:15:43 GMT

DUMP文件：链接：https://pan.baidu.com/s/11b29h_ZkbtbwcaF8qlhgNQ 提取码：5imx

系统信息：操作系统：Windows 11 (Build 22621), 64-bit
主板：HP 8787
显示器：通用即插即用监视器
处理器：AMD Ryzen 7 4800H with Radeon Graphics 八核
内存：15.36 GB
硬盘：三星(SAMSUNG) (476GB) 三星(SAMSUNG) (931GB)
显卡：NVIDIA GeForce RTX 2060
AMD Radeon(TM) Graphics (512 MB)
声卡：Realtek High Definition Audio
NVIDIA High Definition Audio
AMD Audio Device
网卡：Realtek Gaming GbE Family Controller
Hyper-V Virtual Ethernet Adapter
VMware Virtual Ethernet Adapter for VMnet1
VMware Virtual Ethernet Adapter for VMnet8
Sangfor SSL VPN CS Support System VNIC
Intel(R) Wi-Fi 6 AX200 160MHz
Microsoft Wi-Fi Direct Virtual Adapter
Microsoft Wi-Fi Direct Virtual Adapter #2
外网IP：未知
IE版本：11.1.22621.0
Flash版本：未知
开机时间：2023年01月14日 12:45:38 系统已运行：0小时22分钟54秒
上次关机时间：2023年01月14日 12:08:48
系统安装日期：2022年10月09日 21:16:07

以上是今天三次蓝屏的dump文件，已运行惠普uefi硬件检测，无问题；

已重装惠普官网最新驱动；

送到惠普售后，售后表示，当前系统（win11）与官网提供驱动的系统（win10）不匹配，无法找出具体问题；

这种蓝屏间歇性发生，开了蓝屏自动重启，但会卡在蓝屏界面；

另一个现象是，有时候会用着用着突然卡住（有时候是屏幕卡住，有时候是黑屏只剩一个光标，但都是卡住完全动不了也不响应操作），任何按键都无作用，只能强制关机，开机后没有蓝屏记录。

这个问题已困扰我很久，尝试过多种方法，希望能够提供一些有用的建议，谢谢！

回复：蓝屏问题ntkrnlmp.exe

y2kim — Sat, 14 Jan 2023 05:28:45 GMT

用这个APP查看蓝屏dump文件

https://www.microsoft.com/store/apps/9pgjgd53tn86

回复：蓝屏问题ntkrnlmp.exe

TheJoker — Sat, 14 Jan 2023 05:35:10 GMT

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000b3, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2327

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3761

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xd1

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0


FILE_IN_CAB:  011423-14140-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  d1

BUGCHECK_P1: 0

BUGCHECK_P2: ff

BUGCHECK_P3: b3

BUGCHECK_P4: 0

PROCESS_NAME:  System

ADDITIONAL_DEBUG_TEXT:  The trap occurred when interrupts are disabled on the target.

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

TRAP_FRAME:  fffffe073c8532d0 -- (.trap 0xfffffe073c8532d0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=00000000000100de
rdx=0420000000000414 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffffe073c853460 rbp=00000000000100de
 r8=0000000000000002  r9=fffffe073c853560 r10=0000fffff8061f53
r11=ffffb37ac4c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz ac po nc
00000000`00000000 ??              ???
Resetting default scope

IP_IN_FREE_BLOCK: 0

STACK_TEXT:  
fffffe07`3c853188 fffff806`21c3e5a9     : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`000000b3 : nt!KeBugCheckEx
fffffe07`3c853190 fffff806`21c39c34     : fffff806`21814a98 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffffe07`3c8532d0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8770`e26545e0 : nt!KiPageFault+0x474


SYMBOL_NAME:  nt!KiPageFault+474

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1105

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  474

FAILURE_BUCKET_ID:  DISABLED_INTERRUPT_FAULT_CODE_AV_nt!KiPageFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {22523384-75ca-2e7e-4899-20e7e5aa6dea}

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

回复：蓝屏问题ntkrnlmp.exe

TheJoker — Sat, 14 Jan 2023 05:37:49 GMT

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 00000000000000ff, IRQL
Arg3: 00000000000000b3, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2327

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3761

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

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

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

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xd1

    Key  : Bugcheck.Code.Register
    Value: 0xa

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0


FILE_IN_CAB:  011423-14140-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  d1

BUGCHECK_P1: 0

BUGCHECK_P2: ff

BUGCHECK_P3: b3

BUGCHECK_P4: 0

PROCESS_NAME:  System

ADDITIONAL_DEBUG_TEXT:  The trap occurred when interrupts are disabled on the target.

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

TRAP_FRAME:  fffffe073c8532d0 -- (.trap 0xfffffe073c8532d0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000000 rbx=0000000000000000 rcx=00000000000100de
rdx=0420000000000414 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffffe073c853460 rbp=00000000000100de
 r8=0000000000000002  r9=fffffe073c853560 r10=0000fffff8061f53
r11=ffffb37ac4c00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz ac po nc
00000000`00000000 ??              ???
Resetting default scope

IP_IN_FREE_BLOCK: 0

STACK_TEXT:  
fffffe07`3c853188 fffff806`21c3e5a9     : 00000000`0000000a 00000000`00000000 00000000`000000ff 00000000`000000b3 : nt!KeBugCheckEx
fffffe07`3c853190 fffff806`21c39c34     : fffff806`21814a98 00000000`00000001 00000000`00000000 00000000`00000001 : nt!KiBugCheckDispatch+0x69
fffffe07`3c8532d0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff8770`e26545e0 : nt!KiPageFault+0x474


SYMBOL_NAME:  nt!KiPageFault+474

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1105

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  474

FAILURE_BUCKET_ID:  DISABLED_INTERRUPT_FAULT_CODE_AV_nt!KiPageFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {22523384-75ca-2e7e-4899-20e7e5aa6dea}

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

该主题

蓝屏问题ntkrnlmp.exe

回复： 蓝屏问题ntkrnlmp.exe

回复： 蓝屏问题ntkrnlmp.exe

回复： 蓝屏问题ntkrnlmp.exe

回复：蓝屏问题ntkrnlmp.exe

回复：蓝屏问题ntkrnlmp.exe

回复：蓝屏问题ntkrnlmp.exe