win11蓝屏,大佬能帮忙分析下我这是cpu还是内存寄了吗
本帖最后由 zxw11211 于 2023-3-6 23:17 编辑玩FF7,大表哥2大概10分钟左右就会蓝屏,用windbg分析结果如下
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: 0000000000000000, Machine Check Exception
Arg2: ffffd209e670a028, Address of the nt!_WHEA_ERROR_RECORD structure.
Arg3: 00000000bc800800, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000060c0859, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** 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: hal!_WHEA_MEMORY_ERROR_SECTION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: hal!_WHEA_MEMORY_ERROR_SECTION ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key: Analysis.CPU.mSec
Value: 2828
Key: Analysis.DebugAnalysisManager
Value: Create
Key: Analysis.Elapsed.mSec
Value: 455931
Key: Analysis.IO.Other.Mb
Value: 7
Key: Analysis.IO.Read.Mb
Value: 0
Key: Analysis.IO.Write.Mb
Value: 12
Key: Analysis.Init.CPU.mSec
Value: 171
Key: Analysis.Init.Elapsed.mSec
Value: 18651
Key: Analysis.Memory.CommitPeak.Mb
Value: 154
Key: Bugcheck.Code.DumpHeader
Value: 0x124
Key: Bugcheck.Code.Register
Value: 0x124
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:030623-12140-01.dmp
BUGCHECK_CODE:124
BUGCHECK_P1: 0
BUGCHECK_P2: ffffd209e670a028
BUGCHECK_P3: bc800800
BUGCHECK_P4: 60c0859
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT:1
PROCESS_NAME:RDR2.exe
STACK_TEXT:
ffffbf01`7dc80938 fffff807`0daf43bb : 00000000`00000124 00000000`00000000 ffffd209`e670a028 00000000`bc800800 : nt!KeBugCheckEx
ffffbf01`7dc80940 fffff807`0f0b10c0 : 00000000`00000000 ffffbf01`7dc80a19 ffffd209`e670a028 ffffd209`de5fe7a0 : nt!HalBugCheckSystem+0xeb
ffffbf01`7dc80980 fffff807`0dbfe73f : 00000000`00000000 ffffbf01`7dc80a19 ffffd209`e670a028 00000000`00000000 : PSHED!PshedBugCheckSystem+0x10
ffffbf01`7dc809b0 fffff807`0daf5dea : ffffd209`e6738910 ffffd209`e6738910 ffffd209`de5fe7f0 fffff807`0d9bf71a : nt!WheaReportHwError+0x38f
ffffbf01`7dc80a80 fffff807`0daf6235 : 00000000`0000000d ffffd209`00000000 00000000`00000000 00000000`00000000 : nt!HalpMcaReportError+0xb2
ffffbf01`7dc80bf0 fffff807`0daf60d4 : ffffd209`de4b09c0 00000000`00000000 ffffbf01`7dc80e00 00000000`00000000 : nt!HalpMceHandlerCore+0x12d
ffffbf01`7dc80c50 fffff807`0daf5566 : ffffd209`de4b09c0 ffffbf01`7dc80ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffbf01`7dc80c90 fffff807`0daf7cfb : ffffd209`de4b09c0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0x96
ffffbf01`7dc80cc0 fffff807`0db5aa79 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x3b
ffffbf01`7dc80cf0 fffff807`0da3aa3e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffbf01`7dc80d20 fffff807`0da3a653 : 00000000`00000000 00000000`00000000 0000023f`c5cc0000 ffffbf01`7dc80ef0 : nt!KxMcheckAbort+0x7e
ffffbf01`7dc80e60 00007ff6`540c0da3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x2d3
000000fe`8a0ff838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`540c0da3
MODULE_NAME: AuthenticAMD
IMAGE_NAME:AuthenticAMD.sys
STACK_COMMAND:.cxr; .ecxr ; kb
FAILURE_BUCKET_ID:0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
OS_VERSION:10.0.22621.1
BUILDLAB_STR:ni_release
OSPLATFORM_TYPE:x64
几个蓝屏dump分析结果都是这个0x124_0_AuthenticAMD_MEMORY__UNKNOWN_FATAL_IMAGE_AuthenticAMD.sys
5800X+MSI B550M edge wifi,主板驱动是微星官方提供的最新版5.01.29.2026
晚上睡前准备跑个memtest86测下内存
先把显卡和bios升级到最新试试吧 memtest86不用跑了
有人一样的错误,跑不出什么 我之前WHEA_UNCORRECTABLE_ERROR 是换硬盘解决的,不过我那几次根本抓不到内存转储文件 laotoutou 发表于 2023-3-6 23:24
先把显卡和bios升级到最新试试吧
我发现倒是有个最新的测试版bios,难道这次是AMD驱动整大活儿? 升级了刚刚出来的测试版bios了,玩了半小时FF7,目前没有蓝屏,看来八成又是AMD主板驱动整了大活儿
明天继续测试看看
1。CPU加电压,内存加电压。2。电源换个好的,振华海韵。
页:
[1]