这是错误相关信息，帮忙看下是哪里问题，谢谢这是minidump相关文件链接https://1drv.ms/u/s!ArfKGbazKcDYjz-4ldWCVItke5X_?e=c7KgBh这是错误事件信息计算机已经从检测错误后重新启动。检测错误: 0x00000124 (0x0000000000000010, 0xffffe00d634e8028, 0xffffe00d3fbf592c, 0xffffe00d3fb151a0)。已将转储的数据保存在: C:\WINDOWS\MEMORY.DMP。报告 ID: 93e7c889-46bd-40e4-a59c-f3a6f074617b。 - System - Provider [ Name] Microsoft-Windows-WER-SystemErrorReporting [ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952} [ EventSourceName] BugCheck - EventID 1001 [ Qualifiers] 16384 Version 0 Level 2 Task 0 Opcode 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2022-09-02T12:45:38.8475938Z EventRecordID 1359 Correlation - Execution [ ProcessID] 0 [ ThreadID] 0 Channel System Computer DESKTOP-MDJM216 Security - EventData param1 0x00000124 (0x0000000000000010, 0xffffce05209ef028, 0xffffce05041ee92c, 0xffffce050411c1a0) param2 C:\WINDOWS\MEMORY.DMP param3 377cd6ca-f3ce-492c-9c10-7acbe5032c9e =========================================== Microsoft (R) Windows Debugger Version 10.0.22621.1 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_EPROCESS *** *** *** ************************************************************************* Windows 10 Kernel Version 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff803`71000000 PsLoadedModuleList = 0xfffff803`71c2a250 Debug session time: Fri Sep 2 20:44:01.322 2022 (UTC 8:00) System Uptime: 0 days 13:15:06.166 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............... Loading User Symbols Loading unloaded module list ................ For analysis of this file, run !analyze -v 2: 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: ffffce05209ef028, Address of the nt!_WHEA_ERROR_RECORD structure. Arg3: ffffce05041ee92c Arg4: ffffce050411c1a0 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4656 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 33140 Key : Analysis.Init.CPU.mSec Value: 5546 Key : Analysis.Init.Elapsed.mSec Value: 168068 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: 124 BUGCHECK_P1: 10 BUGCHECK_P2: ffffce05209ef028 BUGCHECK_P3: ffffce05041ee92c BUGCHECK_P4: ffffce050411c1a0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: fffff38f`b72bf388 fffff803`715b62ec : 00000000`00000124 00000000`00000010 ffffce05`209ef028 ffffce05`041ee92c : nt!KeBugCheckEx fffff38f`b72bf390 fffff803`715b6e49 : ffffce05`2138a510 ffffce05`2138a510 ffffce05`041ee900 ffffce05`2126f128 : nt!WheaReportHwError 0x3ec fffff38f`b72bf470 fffff803`715b6f65 : 00000000`00000000 00000000`00000062 ffffce05`2138a510 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver 0xe9 fffff38f`b72bf4a0 fffff803`75c635f1 : 00000000`00000000 fffff38f`b72bf6c0 ffffce05`0411c1a0 ffffce05`20109040 : nt!WheaReportFatalHwErrorDeviceDriverEx 0xf5 fffff38f`b72bf500 fffff803`75c5c9d0 : 00000000`00000000 ffffce05`0411c1a0 ffffce05`041331a0 00000000`00000000 : storport!StorpWheaReportError 0x9d fffff38f`b72bf590 fffff803`75c46f6c : 00000000`00000000 ffffffff`fffe7960 00000000`00000000 00000000`00000000 : storport!StorpMarkDeviceFailed 0x358 fffff38f`b72bf820 fffff803`75bfdac7 : ffffce05`04121020 ffffce05`04121020 00000000`00000000 00000000`00000000 : storport!StorPortNotification 0x1878c fffff38f`b72bf8f0 fffff803`75bfe583 : ffffce05`04121020 ffffce05`225ed700 ffffce05`c1000002 00000000`00000003 : stornvme!NVMeControllerInitPart1 0x7b fffff38f`b72bf970 fffff803`75bfd52f : ffffce05`04121020 ffffce05`0411c050 ffffce05`225ed740 80000000`00002000 : stornvme!NVMeControllerReset 0xdb fffff38f`b72bf9a0 fffff803`75c5a0c6 : ffffce05`225ed740 ffffce05`0411c050 ffffce05`04113080 ffffce05`000ac010 : stornvme!NVMeControllerAsyncResetWorker 0x3f fffff38f`b72bf9d0 fffff803`712d57d5 : ffffce05`217c3dc0 ffffce05`217c3dc0 ffffce05`0411c050 ffffce05`17c6fda0 : storport!StorPortWorkItemRoutine 0x46 fffff38f`b72bfa00 fffff803`71286265 : ffffce05`20109040 ffffce05`20109040 fffff803`712d56a0 ffff8e00`00000000 : nt!IopProcessWorkItem 0x135 fffff38f`b72bfa70 fffff803`71358235 : ffffce05`20109040 00000000`00000080 ffffce05`00092040 00000000`00000000 : nt!ExpWorkerThread 0x105 fffff38f`b72bfb10 fffff803`713fff48 : ffff8e00`6e5e3180 ffffce05`20109040 fffff803`713581e0 00000000`00000246 : nt!PspSystemThreadStartup 0x55 fffff38f`b72bfb60 00000000`00000000 : fffff38f`b72c0000 fffff38f`b72b9000 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 OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {37af9407-4a3e-0b08-acdd-dadffdc34c3c} Followup: MachineOwner ---------
您好，A&K，前来提供帮助。您的dump文件显示了致命硬件错误，由Intel驱动导致。如果您的CPU或GPU来自Intel，这代表它们可能损坏或者出现了驱动程序故障。我建议先排除驱动程序问题，请先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。
您好，A&K，前来提供帮助。您的dump文件显示了致命硬件错误，由Intel驱动导致。如果您的CPU或GPU来自Intel，这代表它们可能损坏或者出现了驱动程序故障。我建议先排除驱动程序问题，请先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。谢谢您的，请问卸载所有主要设备驱动程序具体该如何操作此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
请您打开控制面板，在“卸载程序”中将所有能找到的Intel驱动程序卸载。
你好，现在蓝屏问题已经好了。但是还有问题就是长时间休眠唤醒后，中间会一直卡在锁屏界面几分钟，期间鼠标键盘都不可操作。我已经把Windows聚焦给关闭了，依然如此。所以想问下这个问题该如何解决呢此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
