problem with MSI MEG X570 Unify after BIOS update

grens156502dd

New member
Joined
Jan 20, 2022
Messages
16
Board: MSI MEG X570 Unify
BIOS: currect with problem 7C35vAC1 and before 7C35vAB NO problems with 7C35vAB3
VGA: XFX Radeon RX 5600 XT Thicc III Ultra,
PSU: be quiet! Straight Power 11 (750W)
CPU: AMD Ryzen 7 3800X
MEM: 4x 8GB Patriot Viper 4 Blackout (DDR4-3200 CL16-18-18-36) with active XPM profil
HDD/SSD: 1x Samsung 970 EVO Plus SSD (500GB) on M.2 Slot 1 (other M.2 Slots are unused and empty); 1x Samsung 870 EVO SSD (2TB) and 3 other Samsung HDDs
COOLER: be quiet! Dark Rock Pro 4
OS: Windows 10 64bit Professional (Build 19044.1499) installed on Samsung 970 EVO Plus SSD

Issue/Problem:
In the past, I used since released the BIOS beta version 7C35vAB3 without any issues. Then I updated to BIOS final version 7C35vAB0, this version is no longer available on MSI website and I don't know why, and got the first issues with the board.
The update from 7C35vAB3 to 7C35vAB0 works fine, like all other BIOS update before, and I have done the manual configuration of my settings I used 7C35vAB3. One day later I boot my computer and got only a black screen with a white non-flashing cursor and nothing more happens. I shut down the computer with power button (pushing till PC got off) and start it again. This time everything works fine, and I got the POST and the OS boots without any issue. Next day I boot my computer again but this time I got directly a BIOS screen with the message that something with BIOS doesn't work, and I have to flash the BIOS again. So I flashed 7C35vAB0 again over current 7C35vAB0 and done the configuration of all the settings again and the computer boots without any issues. Some days later I got again the issue with a black screen with the white non-flashing cursor. I have done CMOS, loading default settings in BIOS but nothing changed this behavior and got one day later the same issue.
After I saw that the final version 7C35vAB0 was taken off the website, I went back to beta version 7C35vAB3 and everything works fine again without any issues.

Yesterday I saw that the new BIOS beta version 7C35vAC1 was released, and I have done the update from beta version 7C35vAB3 to BIOS beta version 7C35vAC1. Directly after the update and first load of the BIOS, to do the configuration, I have done CMOS to be on save side and load also default settings and reboot. Then I have done the manual configuration of my settings, I used without any issue on 7C35vAB3, and boot the OS without any issue. I can shut down the computer and boot again without any issue, also after powercut of 30 minutes or longer, but I have with 7C35vAC1 the issue, that a reboot doesn't work.
If I choose on Win10 to reboot the computer goes off but doesn't go in POST. Mouse, keyboard and monitor goes off, but the board stays on (LEDs and fans) and nothing else happens. I have tested it several times with the same result, if I choose reboot on WIn10. In the event log from Win10 is nothing to find like Win10 doesn't shut down correctly or something else like this. I don't check on all tries the debug code on the board but at one try I saw the code 95 and at another try the 25.

After switching back to 7C35vAB3, with same settings, everything works fine again.

What can be the reason of this issues with BIOS final version 7C35vAB0 and the beta version 7C35vAC1?

best regard,
GrenSo
 
Last edited:

Alan J T

🙈 🙉🐝 🤬😈
Global Moderator
Joined
Sep 11, 2020
Messages
7,874
Board: MSI MEG X570 Unify
BIOS: currect with problem 7C35vAC1 and before 7C35vAB NO problems with 7C35vAB3
VGA: XFX Radeon RX 5600 XT Thicc III Ultra,
PSU: be quiet! Straight Power 11 (750W)
CPU: AMD Ryzen 7 3800X
MEM: 4x 8GB Patriot Viper 4 Blackout (DDR4-3200 CL16-18-18-36) with active XPM profil
HDD/SSD: 1x Samsung 970 EVO Plus SSD (500GB) on M.2 Slot 1 (other M.2 Slots are unused and empty); 1x Samsung 870 EVO SSD (2TB) and 3 other Samsung HDDs
COOLER: be quiet! Dark Rock Pro 4
OS: Windows 10 64bit Professional (Build 19044.1499) installed on Samsung 970 EVO Plus SSD

Issue/Problem:
In the past, I used since released the BIOS beta version 7C35vAB3 without any issues. Then I updated to BIOS final version 7C35vAB0, this version is no longer available on MSI website and I don't know why, and got the first issues with the board.
The update from 7C35vAB3 to 7C35vAB0 works fine, like all other BIOS update before, and I have done the manual configuration of my settings I used 7C35vAB3. One day later I boot my computer and got only a black screen with a white non-flashing cursor and nothing more happens. I shut down the computer with power button (pushing like PC got off) and start it again. This time everything works fine, and I got the POST and the OS boots without any issue. Next day I boot my computer again but this time I got directly a BIOS screen with the message that something with BIOS doesn't work, and I have to flash BIOS again. So I flash 7C35vAB0 and done the configuration of the settings and the computer boots without any issues. Some days later I got again the issue with a black screen with the white non-flashing cursor. I have done CMOS, loading default settings in BIOS but nothing changed this behavior and got one day later the same issue.
After I saw that the final version 7C35vAB0 was taken off the website from MSI I went back to beta version 7C35vAB3 and everything works fine again without any issues.

Yesterday I saw that the new BIOS beta version 7C35vAC1 was released, and I have done the update from beta version 7C35vAB3 to BIOS beta version 7C35vAC1. Directly after the update and first load of the BIOS, to do the configuration, I have done CMOS to be on save side and load also default settings and reboot. Then I have done the manual configuration of my settings, I used without any issue on 7C35vAB3, and boot the OS without any issue. I can shut down the computer and boot again without any issue, also after powercut of 30 minutes or longer, but I have with 7C35vAC1 the issue, that a reboot doesn't work.
If I choose on Win10 to reboot the computer goes off but doesn't go in POST. Mouse, keyboard and monitor goes off, but the board stays on (LEDs and fans) and nothing else happens. I have tested it several times with the same result, if I choose reboot on WIn10. I don't check on all tries the debug code on the board but at one try I saw the code 95 and at another try the 25.

After switching back to 7C35vAB3, with same settings, everything works fine again.

What can be the reason of this issues with BIOS final version 7C35vAB0 and the beta version 7C35vAC1?

best regard,
GrenSo
There seems to be a Problem with 1.2.0.5 for some users can you please roll back to BIOS 7C35vAA AGESA 1.2.0.3b

And see if this will fix your problems.
 

grens156502dd

New member
Joined
Jan 20, 2022
Messages
16
There seems to be a Problem with 1.2.0.5 for some users can you please roll back to BIOS 7C35vAA AGESA 1.2.0.3b

And see if this will fix your problems.
I can have a try, but I'm really sure, that the BIOS version 7C35vAA will work like the BIOS version 7C35vAB3 too, because the 7C35vAB3 use ComboAM4PIV2 1.2.0.3c. And with the BIOS version 7C35vAB3 I do not have any issues.
But you can be right, because BIOS versions 7C35vAB and 7C35vAC1 switched to ComboAm4v2PI 1.2.0.5, like you can see in the attachments with the official change logs from MSI.
 

Attachments

grens156502dd

New member
Joined
Jan 20, 2022
Messages
16
BTW it can't be the solution to stay on the old BIOS version AB3 with 1.2.0.3c or AA with 1.2.0.3b if MSI provide a newer version with 1.2.0.5.

Now, I wrote directly to the support of MSI and described the issues I have with BIOS versions AB0 and AC1.
 

Alan J T

🙈 🙉🐝 🤬😈
Global Moderator
Joined
Sep 11, 2020
Messages
7,874
BTW it can't be the solution to stay on the old BIOS version AB3 with 1.2.0.3c or AA with 1.2.0.3b if MSI provide a newer version with 1.2.0.5.

Now, I wrote directly to the support of MSI and described the issues I have with BIOS versions AB0 and AC1.
it is only affecting very few people so far about 5 or 6 have reported a problem Reverting BIOS is only a temporary fix till New Bios is released.
 

grens156502dd

New member
Joined
Jan 20, 2022
Messages
16
After contact with global support from MSI, it seems that in my case can be the XMP profile of my memory the root cause. But I can't say anything more precise yet and will now, if I have the time, do some tests over the weekend.
 

Alan J T

🙈 🙉🐝 🤬😈
Global Moderator
Joined
Sep 11, 2020
Messages
7,874
After contact with global support from MSI, it seems that in my case can be the XMP profile of my memory the root cause. But I can't say anything more precise yet and will now, if I have the time, do some tests over the weekend.
Humm to be honest I reckon if your XMP profile worked OK with the previous bios then AMD or MSI got something wrong in 1.2.0.5 and it seems to be with Four dims or 32GB and over.
Your running same ram speed and clocks as I am and I had a hell of a time gettin mine to post with 4x16GB sticks. on 1.2.0.5 but once I got it to post and set XMP it has been good.
Got my mem voltage set at 1.360v and this is the rest
1643370758711.png
 
Last edited:

Alan J T

🙈 🙉🐝 🤬😈
Global Moderator
Joined
Sep 11, 2020
Messages
7,874
After contact with global support from MSI, it seems that in my case can be the XMP profile of my memory the root cause. But I can't say anything more precise yet and will now, if I have the time, do some tests over the weekend.
Hi can you supply a screenshot of the sticker on your Memory please you can blackout the last 6 digit on serial if you want to it should look a bit like this
Make sure to reply to this post please so I know you have left a message
mem sticker.jpg
 

Alan J T

🙈 🙉🐝 🤬😈
Global Moderator
Joined
Sep 11, 2020
Messages
7,874
Hi guys, I have the same problem, did you manage to solve it?
Can you also supply more detail >>Posting Guide<<
Hi can you supply a screenshot of the sticker on your Memory please you can blackout the last 6 digit on serial if you want to it should look a bit like this
Make sure to reply to this post please so I know you have left a message
mem sticker.jpg
 

grens156502dd

New member
Joined
Jan 20, 2022
Messages
16
Hi can you supply a screenshot of the sticker on your Memory please you can blackout the last 6 digit on serial if you want to it should look a bit like this
Make sure to reply to this post please so I know you have left a message
View attachment 156312
I don't think this will help, because I tried many things the last week end and gave up and will stay at the moment on the BIOS beta version AB3.

First of all, the computer starts without any issues with active XMP profile in cold start/boot. It needs just a little bit longer than usual but he starts. I think one hour or later when I used the computer I tried a reboot and had the first issue. Win10 normally shut down (what I saw in event log from Windows too) but doesn’t boot again. Monitor and all other things, like mouse and keyboard stay off but all fans stay on and control LEDs from graphic card (PCIe slot 1) and raid controller (PCIe slot 5) stay on. In this case I had the debug code 94 on the mainboard. I shut off the computer with the power button and he starts without any issues. (no entry in event log from Windows about the failed reboot)

Next I tried a shut down and then a restarting. The shutdown from Win10 works well and also the computer goes off. No fan and no LEDs stay on. At the try of the new restart/boot I get three different events.
  1. 1. Boot works well. I think in 10% of the tries
  2. 2. Computer stay off and Win10 doesn’t boot. I had in this case just a black monitor and mouse and keyboard stay off too and the VGA-LED on the mainboard was on and I got the debug code 02 on the mainboard. I think in 30% until 40% of the tries.
  3. 3. Computer stay off and Win10 doesn’t boot. In this case and the Boot-LED on the mainboard was on and I got the debug code 02 too on the mainboard but I got immediately screen of the BIOS settings. I think in 50% until 60% of the tries.
Then I test each single RAM module in RAM slot A2 with active XMP profile but got the same result, until I loaded the default settings and configure all settings in BIOS again instead of XMP. Only without active XMP the computer was able to boot. Also if I tried to configured the XMP settings manually I had the same negative result. But I cannot tell if I really setup all settings I need to get exactly the same like XMP have configured. I also tested all 4 RAM modules with MemTest but I didn’t got any errors.

At this point I flashed back to BIOS beta version AB3, because I thought something might be defective, with minimum BIOS settings (UEFI, TMP and Secure Boot) and the computer and Windows starts without any issues again. I configured all my standard settings in BIOS manually again, with XMP profile too and the computer boots again without any issues.

So, I think there must be an issues with AGESA ComboAM4v2PI 1.2.0.5 from AMD or the way how it is implemented in the BIOS beta version AC1 and AA0 too (I had with his one the same issues) because with AGESA ComboAM4v2PI 1.2.0.3b and with AGESA ComboAM4v2PI 1.2.0.3c everything works fine and without any issues.

Attached you can find the report of the memory from AIDA64 with all information about my memory.
 

Attachments

laurence1211

Well-known member
PRIVATE E-2
Joined
Jun 28, 2020
Messages
1,826
I don't think this will help, because I tried many things the last week end and gave up and will stay at the moment on the BIOS beta version AB3.

First of all, the computer starts without any issues with active XMP profile in cold start/boot. It needs just a little bit longer than usual but he starts. I think one hour or later when I used the computer I tried a reboot and had the first issue. Win10 normally shut down (what I saw in event log from Windows too) but doesn’t boot again. Monitor and all other things, like mouse and keyboard stay off but all fans stay on and control LEDs from graphic card (PCIe slot 1) and raid controller (PCIe slot 5) stay on. In this case I had the debug code 94 on the mainboard. I shut off the computer with the power button and he starts without any issues. (no entry in event log from Windows about the failed reboot)

Next I tried a shut down and then a restarting. The shutdown from Win10 works well and also the computer goes off. No fan and no LEDs stay on. At the try of the new restart/boot I get three different events.
  1. 1. Boot works well. I think in 10% of the tries
  2. 2. Computer stay off and Win10 doesn’t boot. I had in this case just a black monitor and mouse and keyboard stay off too and the VGA-LED on the mainboard was on and I got the debug code 02 on the mainboard. I think in 30% until 40% of the tries.
  3. 3. Computer stay off and Win10 doesn’t boot. In this case and the Boot-LED on the mainboard was on and I got the debug code 02 too on the mainboard but I got immediately screen of the BIOS settings. I think in 50% until 60% of the tries.
Then I test each single RAM module in RAM slot A2 with active XMP profile but got the same result, until I loaded the default settings and configure all settings in BIOS again instead of XMP. Only without active XMP the computer was able to boot. Also if I tried to configured the XMP settings manually I had the same negative result. But I cannot tell if I really setup all settings I need to get exactly the same like XMP have configured. I also tested all 4 RAM modules with MemTest but I didn’t got any errors.

At this point I flashed back to BIOS beta version AB3, because I thought something might be defective, with minimum BIOS settings (UEFI, TMP and Secure Boot) and the computer and Windows starts without any issues again. I configured all my standard settings in BIOS manually again, with XMP profile too and the computer boots again without any issues.

So, I think there must be an issues with AGESA ComboAM4v2PI 1.2.0.5 from AMD or the way how it is implemented in the BIOS beta version AC1 and AA0 too (I had with his one the same issues) because with AGESA ComboAM4v2PI 1.2.0.3b and with AGESA ComboAM4v2PI 1.2.0.3c everything works fine and without any issues.

Attached you can find the report of the memory from AIDA64 with all information about my memory.
That report does not give them all the information they need, hence the request for a picture of the identification sticker. Also the report is in German lol.
 

Alan J T

🙈 🙉🐝 🤬😈
Global Moderator
Joined
Sep 11, 2020
Messages
7,874
I can provide it tomorrow.
They need it for something, report is Good has some info but no part or model numbers listed and was what they asked me to get. Will include it with rest of the info I have been collecting.
 

grens156502dd

New member
Joined
Jan 20, 2022
Messages
16
They need it for something, report is Good has some info but no part or model numbers listed and was what they asked me to get. Will include it with rest of the info I have been collecting.
What do you mean with "they"? I thought this is a forum by users for users, as it says in your signature. Or are you an employee of MSI or at least have direct contact with the engineers of MSI?

Like I wrote, I can provide it this evening (German time).
 

Alan J T

🙈 🙉🐝 🤬😈
Global Moderator
Joined
Sep 11, 2020
Messages
7,874
What do you mean with "they"? I thought this is a forum by users for users, as it says in your signature. Or are you an employee of MSI or at least have direct contact with the engineers of MSI?

Like I wrote, I can provide it this evening (German time).
I only got made A Moderator this year and no I dont know of any MSI staff, I just leave a message for Forum Admin if I notice a pattern forming.
 
Last edited:

grens156502dd

New member
Joined
Jan 20, 2022
Messages
16
I only got made A Moderator this year and no I dont know of any MSI staff, I just leave a message for Forum Admin if I notice a pattern forming.
Attached you will find two Reports, one short report of the memory and a complete report (both in English) from AIDA64, a picture from one of the RAM modules and screenshots from CPUz.
I deleted or exchanged with XXXX in the AIDA64 reports things like IP and MAC address, user names, serial numbers and other privat things.

RAM_module.jpg


CPUz.jpg


I hope this will help and are enough usefull information at the moment.
 

Attachments

Top