我更新了bios驱动后就开始蓝屏,蓝屏zip文件的下载链接:https://stucduteducn-my.sharepoint.com/:u:/g/personal/2020050843_stu_cdut_edu_cn/EcHlocIpQcdAqpko_WFbSLIBeaLPlRGMW7Tkxzh4aOGXHg?e=TIsG7M我该怎么办呢?请问。使用WinDBg日志代码:Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\Desktop\081922-10359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff804`09600000 PsLoadedModuleList = 0xfffff804`0a22a2b0
Debug session time: Fri Aug 19 22:25:26.349 2022 (UTC + 8:00)
System Uptime: 0 days 0:00:54.264
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:
fffff804`099f72e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbf03`5920f390=0000000000000124
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: ffff9c87a1adf028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: ffff9c87938c18fc
Arg4: ffff9c87939541a0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3217
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 16685
Key : Analysis.Init.CPU.mSec
Value: 1202
Key : Analysis.Init.Elapsed.mSec
Value: 2157083
Key : Analysis.Memory.CommitPeak.Mb
Value: 99
Key : Bugcheck.Code.DumpHeader
Value: 0x124
Key : Bugcheck.Code.Register
Value: 0x124
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 081922-10359-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 124
BUGCHECK_P1: 10
BUGCHECK_P2: ffff9c87a1adf028
BUGCHECK_P3: ffff9c87938c18fc
BUGCHECK_P4: ffff9c87939541a0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffbf03`5920f388 fffff804`09bb60dc : 00000000`00000124 00000000`00000010 ffff9c87`a1adf028 ffff9c87`938c18fc : nt!KeBugCheckEx
ffffbf03`5920f390 fffff804`09bb6c39 : ffff9c87`a2d95790 ffff9c87`a2d95790 ffff9c87`938c18d0 ffff9c87`a2f45168 : nt!WheaReportHwError+0x3ec
ffffbf03`5920f470 fffff804`09bb6d55 : 00000000`00000000 00000000`00000062 ffff9c87`a2d95790 00000000`00000000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
ffffbf03`5920f4a0 fffff804`0bc335d1 : 00000000`00000000 ffffbf03`5920f6c0 ffff9c87`939541a0 ffff9c87`939590ff : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffbf03`5920f500 fffff804`0bc2c830 : 00000000`00000000 ffff9c87`939541a0 ffff9c87`9603f1a0 00000000`00000000 : storport!StorpWheaReportError+0x9d
ffffbf03`5920f590 fffff804`0bc14a94 : fffff804`0bc59000 00000000`00000062 00000000`00000000 ffffbf03`5920f930 : storport!StorpMarkDeviceFailed+0x358
ffffbf03`5920f820 fffff804`0bbca2ed : 00000000`00000200 ffff9c87`93959020 00000000`00000000 00000000`00000000 : storport!StorPortNotification+0x17274
ffffbf03`5920f8f0 fffff804`0bbcd4c2 : ffff9c87`c1000002 00000000`00000000 ffff9c87`93959020 00000000`00000003 : stornvme!ControllerReset+0x1a1
ffffbf03`5920f970 fffff804`0bbcc43f : ffff9c87`93959020 ffff9c87`93954050 ffff9c87`a0c5f5d0 80000000`00002000 : stornvme!NVMeControllerReset+0x10a
ffffbf03`5920f9a0 fffff804`0bc29f31 : ffff9c87`a0c5f5d0 ffff9c87`93954050 ffff9c87`9398a080 ffff9c87`92e893a0 : stornvme!NVMeControllerAsyncResetWorker+0x3f
ffffbf03`5920f9d0 fffff804`09874825 : ffff9c87`a2a69310 ffff9c87`a2a69310 ffff9c87`93954050 fffff804`10205440 : storport!StorPortWorkItemRoutine+0x41
ffffbf03`5920fa00 fffff804`098b8655 : ffff9c87`a10af040 ffff9c87`a10af040 fffff804`098746f0 00000000`00000000 : nt!IopProcessWorkItem+0x135
ffffbf03`5920fa70 fffff804`09955995 : ffff9c87`a10af040 00000000`00000080 ffff9c87`92ec3080 000fa4ef`b59bbfff : nt!ExpWorkerThread+0x105
ffffbf03`5920fb10 fffff804`099fe938 : fffff804`035e5180 ffff9c87`a10af040 fffff804`09955940 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffbf03`5920fb60 00000000`00000000 : ffffbf03`59210000 ffffbf03`59209000 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
--------- 欢迎访问本站!。很抱歉,我无法访问该文件,建议分享到个人的OneDrive。
https://1drv.ms/u/s!As6QZrh-HtCgq1LWbjqJIjJ1kWeg?e=eeYeLq你好,这个是在个人云上的蓝屏文件的压缩包此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
感谢,大部分显示了英特尔的cpu硬件错误,建议参考上述的步骤,看下是否有改善。同时可能需要考虑硬件损坏。有一份显示了英伟达显卡相关的异常,可以更新完bios后覆盖安装一下英伟达显卡驱动。