MSI MEG UNIFY - CPU Failure Light 5900x

Kaelsin · 10 Nov 2020 at 09:41

Joxeon said:
I'd try with just 2 sticks for now or try downclocking to run at 3000~3200 and see if that helps as a temporary measure until the bios fixes, which bios are you on btw?.

I flashed to the latest version (7C35vA7) before installing the CPU.

mickyflinn · 10 Nov 2020 at 10:19

Kaelsin said:
I flashed to the latest version (7C35vA7) before installing the CPU.

It mite be worth trying the previous bios 7C35vA6 which I believe supports ryzen 5000.

https://www.msi.com/Motherboard/support/MEG-X570-UNIFY

Kaelsin · 10 Nov 2020 at 11:40

mickyflinn said:
It mite be worth trying the previous bios 7C35vA6 which I believe supports ryzen 5000.

https://www.msi.com/Motherboard/support/MEG-X570-UNIFY

I've dropped down to version 7C35vA6.

Fingers crossed that this fixes the issues!

I had a couple of Windows Start Menu lock-ups last night but decided to leave the PC on overnight and was greeted by a black screen this morning.

The ram model number is: CMW32GX4M4D3600C18

SonicSW20 · 10 Nov 2020 at 11:44

Load optimized defaults, reboot, back to BIOS and go through and check that you definitely have no OC enabled, XMP is off so RAM is running at the default 2666MHz, see if its now stable.

mickyflinn · 10 Nov 2020 at 11:46

Kaelsin said:
I've dropped down to version 7C35vA6.

Fingers crossed that this fixes the issues!

I had a couple of Windows Start Menu lock-ups last night but decided to leave the PC on overnight and was greeted by a black screen this morning.

The ram model number is: CMW32GX4M4D3600C18

Was Sleep mode and hibernation turned off In windows ?

Kaelsin · 10 Nov 2020 at 11:59

mickyflinn said:
Was Sleep mode and hibernation turned off In windows ?

Yep, I set going to sleep to 'Never' and also turned off the HDD going to sleep.

I forgot to mention this morning, I needed to clear the CMOS to get it to boot past the 07 code and back to Windows.

This has obviously dropped the XMP (default profile 1) setting and the RAM is back to 2133 MHz.

turbot1984 · 10 Nov 2020 at 12:05

Kaelsin said:
That would be my luck. I'm running CORSAIR VENGEANCE RGB PRO 32GB (4x8) DDR4 3600 (PC4-28800) C18 at the moment.

Exactly same RAM here on Z490 Meg Unify, issues with XMP, sorted by upping volts to 1.40v, no issues since. Good luck.

mickyflinn · 10 Nov 2020 at 12:05

@Kaelsin mite be worth downloading and running memtestand Test the ram at diffrent speeds.

turbot1984 · 10 Nov 2020 at 12:09

Got to add, MSI Meg has been a real pain to get working properly after previous Asus ROG which was spot on from day one!

Kaelsin · 10 Nov 2020 at 12:22

mickyflinn said:
@Kaelsin mite be worth downloading and running memtestand Test the ram at diffrent speeds.

I'll download MEMTEST and give it a go different speeds.

turbot1984 said:
Got to add, MSI Meg has been a real pain to get working properly after previous Asus ROG which was spot on from day one!

It really does seem to be pain

Appreciate all the help so far!

mickyflinn · 10 Nov 2020 at 12:26

Kaelsin said:
I'll download MEMTEST and give it a go different speeds.

It really does seem to be pain

Appreciate all the help so far!

Run memtest from start-up not in windows

Kaelsin · 10 Nov 2020 at 14:07

I've kicked off the first test with the memory defaults in the bios:

Kaelsin · 10 Nov 2020 at 15:03

Quick update:

So, the first test passed with no issues.

I then decided I would try the default 1 XMP profile first (3600Mhz). I selected it in the BIOS, saved and when it rebooted it failed to POST.

The DRAM light was lit up on the motherboard with the debug code 0d.

I then reset the CMOS (back to 2133Mhz), and it posted fine.

Tried to set it to the default 1 XMP profile again and it failed to POST again.

turbot1984 · 10 Nov 2020 at 15:42

Kaelsin said:
Quick update:

So, the first test passed with no issues.

I then decided I would try the default 1 XMP profile first (3600Mhz). I selected it in the BIOS, saved and when it rebooted it failed to POST.

The DRAM light was lit up on the motherboard with the debug code 0d.

I then reset the CMOS (back to 2133Mhz), and it posted fine.

Tried to set it to the default 1 XMP profile again and it failed to POST again.

Mine did the same. Try :
XMP OFF
Manually set RAM @ 3600mhz (3700 also worked)
Change RAM voltage to 1.40v
Everything else Auto

mickyflinn · 10 Nov 2020 at 15:45

You can set the timings manually why don't you try 3200mhz 18-19-19-39 at 1.35 v

Kaelsin · 10 Nov 2020 at 16:10

turbot1984 said:
Mine did the same. Try :
XMP OFF
Manually set RAM @ 3600mhz (3700 also worked)
Change RAM voltage to 1.40v
Everything else Auto

Just tried this:

Unfortunately, I got the same result with it refusing to POST.

mickyflinn said:
You can set the timings manually why don't you try 3200mhz 18-19-19-39 at 1.35 v

I'll try this shortly!

mickyflinn · 10 Nov 2020 at 16:12

Kaelsin said:
Just tried this:

Unfortunately, I got the same result with it refusing to POST.

I'll try this shortly!

If it fails go up to 1.4 v

turbot1984 · 10 Nov 2020 at 16:35

Kaelsin said:
Just tried this:

Unfortunately, I got the same result with it refusing to POST.

I'll try this shortly!

Are all your RAM sticks exactly same serial number? I have had mixed ones in same box before.

hardyxd · 10 Nov 2020 at 20:53

SAME ISSUE X570 UNIFY. when XMP enabled it doesn't boot.

have 32gb crucial c16 3600mhz

tried on V6 and v7 bios.
tried with 1 stick in running XMP enabled - no post
tried with the other stick alone

Just set to 3200mhz. gona try up the voltage now, like you say

edit: got it working on 3800 , 1900 FLK c16. gona try 4000 / 2000 tomorrow

hardyxd · 11 Nov 2020 at 07:39

Ok so if i set the voltage to 1.4 and 3600 or xmp present 1 or 2 after a bios reset I get ERROR NO POST

workaround. downrank your memory frequency. i used 3200 and set voltage to 1.4
rebooted. seems it wants the extra power before upping the frequency.
set frequency back up to 3800 and reboots fine 1900FLK 1:1 stable.

seems like a bios issue hopefully MSI will fix it soon. Does that work for you guys who are also having this issue?