cancel
Showing results for 
Search instead for 
Did you mean: 

General Discussions

lzap
Journeyman III

Re: Ryzen Instability MCE bea0000000000108? What do do next?

Experienced the same error, there was no load on my system, I had just Google Chrome up doing some emails, going to disable C6 in BIOS and see, got certified DDR4 modules at 2400MHz with two memtest passes without any error. My CPU is by the way already RMAed one, batch week 31 and it does not suffer from the GCC compilation bug anymore. Jeez this return to AMD after many years with Intel is painful for me, really painful.

Any other hints?

0 Likes
hifigraz
Elite

Re: Ryzen Instability MCE bea0000000000108? What do do next?

Hi lzap,

Yes a really painful expierience ... I'm missing a stable system since March .

But with CStates disabled in Bios my system is stable, but obviously more powerhungry.

KR

Robert

0 Likes
lzap
Journeyman III

Re: Ryzen Instability MCE bea0000000000108? What do do next?

Thanks hifigraz, well I was unable to find this option in my ASUS B350 BIOS, can anyone help me finding it? I was searching for "Advanced C-State Handling => Disable" but could not find this. All I was able to find was "Global C-State Control" which is set to Auto and can be Enabled or Disabled.

How much of a difference in consumption this is?

0 Likes
lzap
Journeyman III

Re: Ryzen Instability MCE bea0000000000108? What do do next?

Oh no, second one today. In the morning my PC just restarted, this one I had hard freeze. Computer was idling, I had one libvirt VM up tho (idle too).

I have set Global C-State Control to Disabled now. Let's see. This is a disaster. Ryzen launch is a disaster for Linux users.

0 Likes
royfall
Journeyman III

Re: Ryzen Instability MCE bea0000000000108? What do do next?

Hi, I'm also having this MCE error. I have a Ryzen 7 1700 and an ASRock Taichi X370 with the latest BIOS (3.20).

0 Likes
bsp2020
Elite

Re: Ryzen Instability MCE bea0000000000108? What do do next?

Is there a consensus on the cause of this problem? I had 1800X that had segfault problem and random reboot/hang issue. I had the CPU replaced through RMA process and am using the new replaced CPU. It does not have segfault problem any more. But I'm still experiencing random reboot/hang. I thought getting a known good CPU (I assume that the replacement CPU is more rigorously tested) would resolve both problems. I've heard some people blaming the motherboard. So, I was wondering if there is any consensus here.

0 Likes
hardcoregames_
Big Boss

Re: Ryzen Instability MCE bea0000000000108? What do do next?

depending on the motherboard, some seem to need a bios update to get ahead of problems with memory etc

0 Likes
dimyself
Journeyman III

Re: Ryzen Instability MCE bea0000000000108? What do do next?

I just now received this same error for the 1st time (i think) since owning the taichi and 1700. Never OC'ed. Everything is default in bios except for virtual machine setting is enabled. I'm using Arch linux. I have had random reboots in the past, but its been few and I don't remember seeing this error before. I just updated to latest bios about 1 week ago using the auto DHCP updater in the bios. So perhaps there's a newer update now that may address this?

Here's the error I got:

Oct 11 20:24:52 arch-pc kernel: CPU: Physical Processor ID: 0

Oct 11 20:24:52 arch-pc kernel: CPU: Processor Core ID: 0

Oct 11 20:24:52 arch-pc kernel: mce: CPU supports 23 MCE banks

Oct 11 20:24:52 arch-pc kernel: LVT offset 1 assigned for vector 0xf9

Oct 11 20:24:52 arch-pc kernel: LVT offset 2 assigned for vector 0xf4

Oct 11 20:24:52 arch-pc kernel: Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 512

Oct 11 20:24:52 arch-pc kernel: Last level dTLB entries: 4KB 1536, 2MB 1536, 4MB 768, 1GB 0

Oct 11 20:24:52 arch-pc kernel: Freeing SMP alternatives memory: 24K

Oct 11 20:24:52 arch-pc kernel: smpboot: Max logical packages: 2

Oct 11 20:24:52 arch-pc kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1

Oct 11 20:24:52 arch-pc kernel: smpboot: CPU0: AMD Ryzen 7 1700 Eight-Core Processor (family: 0x17, model: 0x1, stepping: 0x1)

Oct 11 20:24:52 arch-pc kernel: Performance Events: Fam17h core perfctr, AMD PMU driver.

Oct 11 20:24:52 arch-pc kernel: ... version:                0

Oct 11 20:24:52 arch-pc kernel: ... bit width:              48

Oct 11 20:24:52 arch-pc kernel: ... generic registers:      6

Oct 11 20:24:52 arch-pc kernel: ... value mask:             0000ffffffffffff

Oct 11 20:24:52 arch-pc kernel: ... max period:             00007fffffffffff

Oct 11 20:24:52 arch-pc kernel: ... fixed-purpose events:   0

Oct 11 20:24:52 arch-pc kernel: ... event mask:             000000000000003f

Oct 11 20:24:52 arch-pc kernel: Hierarchical SRCU implementation.

Oct 11 20:24:52 arch-pc kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.

Oct 11 20:24:52 arch-pc kernel: smp: Bringing up secondary CPUs ...

Oct 11 20:24:52 arch-pc kernel: x86: Booting SMP configuration:

Oct 11 20:24:52 arch-pc kernel: .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6

Oct 11 20:24:52 arch-pc kernel: mce: [Hardware Error]: Machine check events logged

Oct 11 20:24:52 arch-pc kernel: mce: [Hardware Error]: CPU 6: Machine Check: 0 Bank 5: bea0000000000108

Oct 11 20:24:52 arch-pc kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffa00b5ac8 MISC d012000101000000 SYND 4d000000 IPID 500b000000000

Oct 11 20:24:52 arch-pc kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1507771487 SOCKET 0 APIC 6 microcode 8001129

Oct 11 20:24:52 arch-pc kernel:   #7  #8  #9 #10 #11 #12 #13 #14 #15

Oct 11 20:24:52 arch-pc kernel: smp: Brought up 1 node, 16 CPUs

Oct 11 20:24:52 arch-pc kernel: smpboot: Total of 16 processors activated (95726.37 BogoMIPS)

thanks

0 Likes
hifigraz
Elite

Re: Ryzen Instability MCE bea0000000000108? What do do next?

Hi,

I've tried two Mainboards (asus prime b350 and gigabyte x370 gaming 5) two sets of ram meanwhile the third CPU (the 4th is on it's way) two GPU's and two PSUs. of course always newest available kernel (Arch linux), of course the newest available BIOS, but the problem still persists. Disabling P-State Managing in Bios is the only workaround. Of course your system will then acquire more electrical power, but at least it is sort of usable.

0 Likes
evgenyk
Adept I

Re: Ryzen Instability MCE bea0000000000108? What do do next?

the problem still occurs on the latest BIOS. AMD confirmed RMA but has been keeping radio silence since recently even after my email about the status.

The latest instant crash

oct 15 18:00:03 ryzen kernel: mce: [Hardware Error]: CPU 10: Machine Check: 0 Bank 5: bea0000000000108

oct 15 18:00:03 ryzen kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8667af7a MISC d012000101000000 SYND 4d000000 IPID 500b000000000

oct 15 18:00:03 ryzen kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1508090382 SOCKET 0 APIC a microcode 8001129

0 Likes