cancel
Showing results for 
Search instead for 
Did you mean: 

Processors

buildorbust
Adept II

Re: 5950x, agesa 1.1.0.0 patch C, Machine Check Exception, Bus/Interconnect Error, Cache Hierarchy E

minidump file

https://drive.google.com/file/d/1L8alcMCjbr6t2lzB316vABp1Xn2dAnhe/view?usp=sharing 


Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112820-13453-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 (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff803`23200000 PsLoadedModuleList = 0xfffff803`23e2a310
Debug session time: Sat Nov 28 02:47:48.458 2020 (UTC - 8:00)
System Uptime: 0 days 0:09:16.055
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
12: 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
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffc08c05544028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000001010135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

fffff80323e0f340: Unable to get Flags value from nt!KdVersionBlock
fffff80323e0f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
*** ***
*** ***
*** 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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************
fffff80323e0f340: Unable to get Flags value from nt!KdVersionBlock
*************************************************************************
*** ***
*** ***
*** 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_PROCESSOR_GENERIC_ERROR_SECTION ***
*** ***
*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-96HSJQP

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 28

Key : Analysis.Memory.CommitPeak.Mb
Value: 82

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc08c05544028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dota2.exe

STACK_TEXT:
ffffd100`be9d7938 fffff803`236b333a : 00000000`00000124 00000000`00000000 ffffc08c`05544028 00000000`bc000800 : nt!KeBugCheckEx
ffffd100`be9d7940 fffff803`1f6d15b0 : 00000000`00000000 ffffc08c`05544028 ffffc08c`02af7200 ffffc08c`05544028 : nt!HalBugCheckSystem+0xca
ffffd100`be9d7980 fffff803`237b4e3e : 00000000`00000000 ffffd100`be9d7a29 ffffc08c`05544028 ffffc08c`02af7200 : PSHED!PshedBugCheckSystem+0x10
ffffd100`be9d79b0 fffff803`236b4c61 : ffffc08c`0c797900 ffffc08c`0c797900 ffffc08c`02af7250 ffffc08c`02af7200 : nt!WheaReportHwError+0x46e
ffffd100`be9d7a90 fffff803`236b4fd3 : 00000000`0000000c ffffc08c`02af7250 ffffc08c`02af7200 00000000`0000000c : nt!HalpMcaReportError+0xb1
ffffd100`be9d7c00 fffff803`236b4eb0 : ffffc08c`00f048a0 00000000`00000000 ffffd100`be9d7e00 00000000`00000000 : nt!HalpMceHandlerCore+0xef
ffffd100`be9d7c50 fffff803`236b43f5 : ffffc08c`00f048a0 ffffd100`be9d7ef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0
ffffd100`be9d7c90 fffff803`236b6bb5 : ffffc08c`00f048a0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9
ffffd100`be9d7cc0 fffff803`2370c2b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35
ffffd100`be9d7cf0 fffff803`236036fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9
ffffd100`be9d7d20 fffff803`236033b7 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KxMcheckAbort+0x7a
ffffd100`be9d7e60 00007ffc`95be99f9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277
0000004f`0317b370 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`95be99f9


MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR__UNKNOWN

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {92068ce4-dacf-c0d2-ac6c-91e2b9ac5b67}

Followup: MachineOwner
---------

 

0 Likes
elstaci
MVP

Re: 5950x, agesa 1.1.0.0 patch C, Machine Check Exception, Bus/Interconnect Error, Cache Hierarchy E

I recently purchased a new Asus Motherboard and it has two latest BIOS.

Non-BETA BIOS has Patch B

BETA BIOS has Patch C.

I asked Asus Tech about the difference between Non-BETA and BETA BIOS and  he mentioned the Patches are different.

Possibly Patch C might be for the new AMD Processors but at least at Asus it is still considered to be BETA BIOS.

EDIT: Went to your Motherboad BIOS download page and the latest is a BETA BIOS which i would avoid installing:

7C84v151(Beta version)

MSI Latest Non-BETA includes Patch C in it.

0 Likes
buildorbust
Adept II

Re: 5950x, agesa 1.1.0.0 patch C, Machine Check Exception, Bus/Interconnect Error, Cache Hierarchy E

7C84v151 - bsod

7C84v14 - bsod

7C84v13 - bsod

0 Likes
deepcuts
Adept II

Re: 5950x, agesa 1.1.0.0 patch C, Machine Check Exception, Bus/Interconnect Error, Cache Hierarchy E

Same issue on a Gigabyte Aorus X570 Xtreme
Upgraded from 3950X to 5950X = from stable to constant reboots in seconds.
Stock settings with defaults loaded and memory at 2133 Mhz
The only setting that "fixes" constant reboots and BSODS is to disable Core Performance Boots, which locks the CPU at 3.4 Ghz.
Replaced everything but CPU and motherboard.
Opened a ticket with AMD. So far no reply. Not even the email with "A separate email containing your service request reference number will follow."
I hope this is a BIOS issue, but at the same time, there are other users with the same board and without this issue.

0 Likes
Amiles
Journeyman III

Re: 5950x, agesa 1.1.0.0 patch C, Machine Check Exception, Bus/Interconnect Error, Cache Hierarchy E

Hello! I just finished a build with a 5950x, and was curious if you ever found out what exactly was causing this problem.  I seem to be having the same issue on an ASUS motherboard.  If you sent it in to get a replacement, did the replacement have the same issues? Thanks!

0 Likes
deepcuts
Adept II

Re: 5950x, agesa 1.1.0.0 patch C, Machine Check Exception, Bus/Interconnect Error, Cache Hierarchy E

I have bought another 5950X and returned the 1st defective 5950X.
The replacement CPU fixed my problems.
AMD has some serious QQ problems.

0 Likes