电脑玩游戏时发生蓝屏,附件为两次蓝屏的dmp文件,烦请帮忙看看是何原因Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\WWeiT\Desktop\111322-6187-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 22621 MP (20 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 22621.1.amd64fre.ni_release.220506-1250 Machine Name: Kernel base = 0xfffff804`4b800000 PsLoadedModuleList = 0xfffff804`4c413410 Debug session time: Sun Nov 13 21:17:52.023 2022 (UTC 8:00) System Uptime: 0 days 1:54:10.756 Loading Kernel Symbols ............................................................... ................................................................ ............................................................... Loading User Symbols Loading unloaded module list ........ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff804`4bc283c0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffd080`77c27370=0000000000000050 2: 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: ffff920d51e008dc, 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: fffff8044ba749a3, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : AV.Type Value: Read Key : Analysis.CPU.mSec Value: 624 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 5399 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 2 Key : Analysis.Init.CPU.mSec Value: 77 Key : Analysis.Init.Elapsed.mSec Value: 6712 Key : Analysis.Memory.CommitPeak.Mb Value: 93 Key : Bugcheck.Code.DumpHeader Value: 0x50 Key : Bugcheck.Code.Register Value: 0x50 Key : WER.OS.Branch Value: ni_release Key : WER.OS.Timestamp Value: 2022-05-06T12:50:00Z Key : WER.OS.Version Value: 10.0.22621.1 FILE_IN_CAB: 111322-6187-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b BUGCHECK_CODE: 50 BUGCHECK_P1: ffff920d51e008dc BUGCHECK_P2: 0 BUGCHECK_P3: fffff8044ba749a3 BUGCHECK_P4: 2 READ_ADDRESS: fffff8044c51c468: 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 ffff920d51e008dc MM_INTERNAL_CODE: 2 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: ffffd08077c27590 -- (.trap 0xffffd08077c27590) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=ffffffffffffff40 rbx=0000000000000000 rcx=0000000000018c3b rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8044ba749a3 rsp=ffffd08077c27720 rbp=0000000000000046 r8=00000000fffffe2c r9=0000000000000001 r10=0000000000007fff r11=ffff920c41daa3c8 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe cy nt!RtlpHpSegPageRangeCommit 0x2e3: fffff804`4ba749a3 0fb7461c movzx eax,word ptr [rsi 1Ch] ds:00000000`0000001c=???? Resetting default scope STACK_TEXT: ffffd080`77c27368 fffff804`4bc8102f : 00000000`00000050 ffff920d`51e008dc 00000000`00000000 ffffd080`77c27590 : nt!KeBugCheckEx ffffd080`77c27370 fffff804`4ba53c4c : 00000000`00000000 00000000`00000000 ffffd080`77c27529 00000000`00000000 : nt!MiSystemFault 0x2302ff ffffd080`77c27470 fffff804`4bc39029 : ffff920c`41daa000 00000000`00000000 00000000`00000000 00000000`00100000 : nt!MmAccessFault 0x29c ffffd080`77c27590 fffff804`4ba749a3 : ffff920d`1e013100 ffff920d`51e00000 00000000`fffffe2c fffff804`4bb24fe1 : nt!KiPageFault 0x369 ffffd080`77c27720 fffff804`4ba78967 : 00000000`00000000 ffff920d`51e008c0 00000000`00000000 ffff920d`00000074 : nt!RtlpHpSegPageRangeCommit 0x2e3 ffffd080`77c277c0 fffff804`4bb248ba : ffff920d`00000000 ffff920d`51e00000 ffff920d`51e008c0 ffff920d`1e010140 : nt!RtlpHpSegPageRangeCoalesce 0x237 ffffd080`77c27820 fffff804`4bb24738 : 00000000`00000000 00000000`00000000 ffffd080`77c27a40 ffff920d`1e0102c0 : nt!RtlpHpSegContextCompact 0x14a ffffd080`77c27880 fffff804`4bb246a5 : 00000000`00000001 00000000`00000000 ffffd080`00000000 00000000`00000000 : nt!RtlpHpHeapCompact 0x74 ffffd080`77c278b0 fffff804`4ba14f95 : 00000000`00000001 ffffd080`0000003f ffff920d`00000001 fffff804`00000000 : nt!ExpHpCompactionRoutine 0x205 ffffd080`77c27940 fffff804`4bb088b7 : ffff920d`4b7ad040 00000000`000008f4 ffff920d`4b7ad040 fffff804`4ba14e40 : nt!ExpWorkerThread 0x155 ffffd080`77c27b30 fffff804`4bc2d324 : ffffe180`1caa2180 ffff920d`4b7ad040 fffff804`4bb08860 00000000`00000246 : nt!PspSystemThreadStartup 0x57 ffffd080`77c27b80 00000000`00000000 : ffffd080`77c28000 ffffd080`77c21000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread 0x34 SYMBOL_NAME: nt!RtlpHpSegPageRangeCommit 2e3 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.819 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 2e3 FAILURE_BUCKET_ID: AV_R_(null)_nt!RtlpHpSegPageRangeCommit OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {7a9a017b-7178-dc3b-513b-9341e8fed525} Followup: MachineOwner --------- 2: kd> lmvm nt Browse full module list start end module name fffff804`4b800000 fffff804`4c847000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\6E86DE116E792A4CC2447B8D88147AFB1\ntkrnlmp.pdb Loaded symbol image file: ntkrnlmp.exe Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\3CBF97091047000\ntkrnlmp.exe Image path: ntkrnlmp.exe Image name: ntkrnlmp.exe Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: 3CBF9709 (This is a reproducible build file hash, not a timestamp) CheckSum: 00B7E513 ImageSize: 01047000 File version: 10.0.22621.819 Product version: 10.0.22621.819 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.22621.819 FileVersion: 10.0.22621.819 (WinBuild.160101.0800) FileDescription: NT Kernel & System LegalCopyright: © Microsoft Corporation. All rights reserved.

您好,A&K,前来提供帮助。您提供的信息显示了系统内核的问题,这是一个很普通的错误,可能是驱动程序导致的,但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序(GPU、芯片组等),然后前往设备制造商官网下载最新版本并重新安装。


点赞(97) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部