我的系统在运行游戏后按windows键,单击任务栏中图标(edge)后系统发生无响应然后桌面黑屏后蓝屏。或者什么都不动大型游戏时也会不定时出现此问题。之前虚拟内存由系统管理时无法错误日志转存,现改变虚拟内存到其他硬盘后得到了日志,希望帮忙分析文件得到帮助,万分感谢!dmp文件已上传到 https://wwn.lanzout.com/i7izO06y7y1i其他信息:主板BIOS为厂商最新版本 驱动为最新版本 系统为最新版本 CPU内存无超频均为默认以下是粗略内容Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Rui\Desktop\062622-5312-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff806`0d800000 PsLoadedModuleList = 0xfffff806`0e42a2b0 Debug session time: Sun Jun 26 03:02:27.389 2022 (UTC 8:00) System Uptime: 0 days 0:03:07.063 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: fffff806`0dbf7dd0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffff282`f16cd3d0=0000000000000124 9: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details. Arguments: Arg1: 0000000000000010, Device Driver Error Arg2: ffffbd8c8d307028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: ffffbd8c7e38baec Arg4: ffffbd8c7e3d91a0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1811 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1803 Key : Analysis.Init.CPU.mSec Value: 280 Key : Analysis.Init.Elapsed.mSec Value: 17531 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 062622-5312-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 124 BUGCHECK_P1: 10 BUGCHECK_P2: ffffbd8c8d307028 BUGCHECK_P3: ffffbd8c7e38baec BUGCHECK_P4: ffffbd8c7e3d91a0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff282`f16cd3c8 fffff806`0ddb668c : 00000000`00000124 00000000`00000010 ffffbd8c`8d307028 ffffbd8c`7e38baec : nt!KeBugCheckEx fffff282`f16cd3d0 fffff806`0ddb71e9 : ffffbd8c`8c784710 ffffbd8c`8c784710 ffffbd8c`7e38bac0 ffffbd8c`8c848128 : nt!WheaReportHwError 0x3ec fffff282`f16cd4b0 fffff806`0ddb7305 : 00000000`00000000 00000000`00000062 ffffbd8c`8c784710 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver 0xe9 fffff282`f16cd4e0 fffff806`13303311 : 00000000`00000000 fffff282`f16cd700 ffffbd8c`7e3d91a0 01000000`00100000 : nt!WheaReportFatalHwErrorDeviceDriverEx 0xf5 fffff282`f16cd540 fffff806`132fc6f0 : 00000000`00000000 ffffbd8c`7e3d91a0 ffffbd8c`7e3e01a0 00000000`00000001 : storport!StorpWheaReportError 0x9d fffff282`f16cd5d0 fffff806`132e4994 : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed 0x358 fffff282`f16cd860 fffff806`1338b3bd : fffff806`0e525440 ffffbd8c`7e3ca020 00000000`00000000 00000000`00000000 : storport!StorPortNotification 0x17174 fffff282`f16cd930 fffff806`1338e5b2 : ffffbd8c`00000001 00000000`c1000002 ffffbd8c`7e3ca020 00000000`00000003 : stornvme!ControllerReset 0x1a1 fffff282`f16cd9b0 fffff806`1338d52f : ffffbd8c`7e3ca020 ffffbd8c`7e3d9050 ffffbd8c`8d1adb40 80000000`00002000 : stornvme!NVMeControllerReset 0x10a fffff282`f16cd9e0 fffff806`132f9de6 : ffffbd8c`8d1adb40 ffffbd8c`7e3d9050 ffffbd8c`7e37c080 ffffbd8c`7ac98a20 : stornvme!NVMeControllerAsyncResetWorker 0x3f fffff282`f16cda10 fffff806`0daf3265 : ffffbd8c`8cda3a40 ffffbd8c`8cda3a40 ffffbd8c`7e3d9050 fffff806`289f5dc0 : storport!StorPortWorkItemRoutine 0x46 fffff282`f16cda40 fffff806`0dabfae5 : ffffbd8c`7e39e080 ffffbd8c`7e39e080 fffff806`0daf3130 ffffbd8c`00000000 : nt!IopProcessWorkItem 0x135 fffff282`f16cdab0 fffff806`0daeea75 : ffffbd8c`7e39e080 00000000`00000080 ffffbd8c`7acd91c0 000fe47f`bd9bbfff : nt!ExpWorkerThread 0x105 fffff282`f16cdb50 fffff806`0dbff428 : fffff806`0bf6c180 ffffbd8c`7e39e080 fffff806`0daeea20 00000000`00000000 : nt!PspSystemThreadStartup 0x55 fffff282`f16cdba0 00000000`00000000 : fffff282`f16ce000 fffff282`f16c7000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread 0x28 MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel.sys STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x124_16_GenuineIntel__UNKNOWN_IMAGE_GenuineIntel.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {37af9407-4a3e-0b08-acdd-dadffdc34c3c} Followup: MachineOwner ---------

欢迎咨询本站!。有显示多种错误,存储,硬盘,cpu,网卡等相关的异常。(建议升级一下系统)建议先更改虚拟内存为“系统自动管理所有分页文件的大小”然后参考以下链接,检测一下内存和硬盘:https://answers.microsoft.com/zh-hans/windows/f.


点赞(71) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部