win10 64位，频繁蓝屏 dmp显示原因是ntkrnlmp.exe

      win10 64位，频繁蓝屏 dmp显示原因是ntkrnlmp.exe在我分析一下是那里的问题，谢谢我想把DMP文件上传这个是微云的网盘 https://share.weiyun.com/Ca2kUSPDMicrosoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\HEDONG\Desktop\102522-11390-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff805`39200000 PsLoadedModuleList = 0xfffff805`39e2a270
Debug session time: Tue Oct 25 18:50:34.458 2022 (UTC + 8:00)
System Uptime: 0 days 0:02:19.202
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:
fffff805`395f90f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9980`4743db50=0000000000000050
12: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffffafd40000000, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: 0000000000000000, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000006, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 5233

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6354

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x50

    Key  : Bugcheck.Code.Register
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  102522-11390-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  50

BUGCHECK_P1: fffffafd40000000

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 6

READ_ADDRESS: fffff80539efb390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 fffffafd40000000

MM_INTERNAL_CODE:  6

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WmiPrvSE.exe

TRAP_FRAME:  ffff99804743de70 -- (.trap 0xffff99804743de70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8000000000 rbx=0000000000000000 rcx=fffffafd40000000
rdx=fffffa8000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8053f4997bd rsp=ffff99804743e008 rbp=ffff860b2022ba30
 r8=0000007ffffffff8  r9=0000000000000000 r10=fffff8053951ccb0
r11=ffff99804743e2f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
Ntfs!NtfsInitializeIrpContextInternal+0x11d:
fffff805`3f4997bd 85c0            test    eax,eax
Resetting default scope

STACK_TEXT: 
ffff9980`4743db48 fffff805`3962b62c     : 00000000`00000050 fffffafd`40000000 00000000`00000000 fffffafd`7ea00000 : nt!KeBugCheckEx
ffff9980`4743db50 fffff805`3943a4cd     : ffff9980`4743dd90 ffff9980`4743dcd0 ffff9980`4743dcd8 ffff9980`4743dce8 : nt!MiZeroFault+0x1f416c
ffff9980`4743dc40 fffff805`3943974a     : 4f9e5305`1138b001 00000000`00000000 ffff9980`4743def0 00000000`00000000 : nt!MiUserFault+0x80d
ffff9980`4743dcd0 fffff805`3960725e     : 00000000`00000120 00000000`00000000 ffff860b`0000000d 00000000`00000a9a : nt!MmAccessFault+0x16a
ffff9980`4743de70 fffff805`3f4997bd     : fffff805`3951cd4a ffff860b`1c2698c8 00000000`00000000 ffff9980`4743f000 : nt!KiPageFault+0x35e
ffff9980`4743e008 ffff860b`2022ba30     : fffff805`3f57bd72 ffff860b`2022ba00 00000000`00000000 ffff860b`2022ba00 : Ntfs!NtfsInitializeIrpContextInternal+0x11d
ffff9980`4743e078 fffff805`3f57bd72     : ffff860b`2022ba00 00000000`00000000 ffff860b`2022ba00 00000000`00000002 : 0xffff860b`2022ba30
ffff9980`4743e080 fffff805`3942a6b5     : ffff860b`100f0030 ffff860b`2022ba30 ffff9980`4743e300 ffff860b`220c77e0 : Ntfs!NtfsFsdCreate+0xb2
ffff9980`4743e300 fffff805`37e370cf     : ffff860b`220c7800 ffff9980`4743e3f0 ffff9980`4743e3f9 fffff805`37e35f3a : nt!IofCallDriver+0x55
ffff9980`4743e340 fffff805`37e69f54     : ffff9980`4743e3f0 ffff860b`220c7838 ffff860b`08f3c2b0 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28f
ffff9980`4743e3b0 fffff805`3942a6b5     : 00000000`00000000 ffff860b`100a6060 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x324
ffff9980`4743e460 fffff805`3942bcb4     : 00000000`00000003 ffff860b`2022ba30 ffff860b`6d4e6f49 fffff805`3942b8e3 : nt!IofCallDriver+0x55
ffff9980`4743e4a0 fffff805`39817bdd     : ffff9980`4743e760 ffff860b`100a6060 ffff860b`220c7878 00000000`00000000 : nt!IoCallDriverWithTracing+0x34
ffff9980`4743e4f0 fffff805`397ffb0e     : ffff860b`100a6060 00000000`00000060 ffff860b`20fee6c0 ffff860b`20fee601 : nt!IopParseDevice+0x117d
ffff9980`4743e660 fffff805`3982a86a     : ffff860b`20fee600 ffff9980`4743e8c8 ffff860b`00000040 ffff860b`08fd7380 : nt!ObpLookupObjectName+0x3fe
ffff9980`4743e830 fffff805`39874a9f     : ffffd680`00000000 000000fc`9f3fb068 00000000`00000000 00000000`00000001 : nt!ObOpenObjectByNameEx+0x1fa
ffff9980`4743e960 fffff805`398745e8     : 000000fc`9f3faff0 00000000`00000000 000000fc`9f3fb068 000000fc`9f3fb058 : nt!IopCreateFile+0x40f
ffff9980`4743ea00 fffff805`3960aab8     : 00000000`000007c0 ffff860b`1efb4080 000000fc`9f3fc768 000002bf`5f60c5a0 : nt!NtOpenFile+0x58
ffff9980`4743ea90 00007ff9`5898d724     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000fc`9f3faf98 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`5898d724


SYMBOL_NAME:  nt!MiZeroFault+1f416c

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.2130

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1f416c

FAILURE_BUCKET_ID:  AV_R_(null)_nt!MiZeroFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b7319d6a-58d6-1ac2-09d4-37a3afdc2ea9}

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

12: kd> lmvm nt
Browse full module list
start             end                 module name
fffff805`39200000 fffff805`3a246000   nt         (pdb symbols)          C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\87A327C6C356B7E2BAC1D75E779701651\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\C103E0DA1046000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        C103E0DA (This is a reproducible build file hash, not a timestamp)
    CheckSum:         00A5F358
    ImageSize:        01046000
    File version:     10.0.19041.2130
    Product version:  10.0.19041.2130
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   10.0.19041.2130
        FileVersion:      10.0.19041.2130 (WinBuild.160101.0800)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.      您好东何，非常欢迎您来技术支持本站咨询。让我为您解决电脑蓝屏的问题。通过您的日志文件分析来看，导致蓝屏的进程为：ntkrnlmp.exe、WmiPrvSE.exe，这两个进程为系统进程，出现这个问题的原因可能是某些驱动程序不兼容触发了这两个进程。请问出现这个问题之前你是更新过硬件驱动？建议您尝试通过设备品牌官网（不要通过任何第三方软件）下载对应设备型号的主要驱动程序BIOS、独立显卡、核心显卡驱动程序的安装包，覆盖安装到设备中，安装完毕后重启设备，照常使用一段时间电脑，看是否还会出现相同的问题。如果以上操作问题依然存在，请使用DISM命令修复下系统镜像。同时按Windows徽标键+X，启动WindowsPowerShell（管理员），分别执行以下命令，请务必在上一条完成后再执行下一条命令,执行后重启电脑确认.DISM/Online/Cleanup-Image/ScanHealthDISM/Online/Cleanup-Image/CheckHealthDISM/Online/Cleanup-image/RestoreHealthSFC/scannowLenka
        您好东何，您是否仍然遇到这个问题？如果有任何进展，请让我知道。最好的问候。Lenka