F5F Stay Refreshed Hardware Desktop MSI MPG B550 Gaming Plus shows odd actions following a BIOS update.

MSI MPG B550 Gaming Plus shows odd actions following a BIOS update.

MSI MPG B550 Gaming Plus shows odd actions following a BIOS update.

Pages (2): 1 2 Next
S
SofiSmile
Junior Member
14
05-09-2020, 04:34 PM
#1
Hi there, I hope you can assist me. Here are some details about my system: Mainboard is MSI MPG B550 Gaming Plus, BIOS version is 1.B0, CPU is Ryzen 7 3700X, RAM is G.Skill DIMM 32 GB DDR4-3000, GPU is KFA2 RTX 2070. I recently updated the BIOS a few days ago after the previous version was 7C56v16 from May 14, 2021. The update was done via USB stick and everything worked fine until now. Now I’m facing an issue: the computer won’t boot at first. When I press the power button, all fans spin and lights come on, but it doesn’t reach the BIOS screen. The CPU LED stays white constantly. After a few seconds of pressing the power button again, the computer turns off, then comes back on when I press it once more. In short, it needs two attempts to boot, every time it was off. Before the BIOS update, I didn’t have any similar problems. Greetings from Germany, Natsu.
S
SofiSmile
05-09-2020, 04:34 PM #1

Hi there, I hope you can assist me. Here are some details about my system: Mainboard is MSI MPG B550 Gaming Plus, BIOS version is 1.B0, CPU is Ryzen 7 3700X, RAM is G.Skill DIMM 32 GB DDR4-3000, GPU is KFA2 RTX 2070. I recently updated the BIOS a few days ago after the previous version was 7C56v16 from May 14, 2021. The update was done via USB stick and everything worked fine until now. Now I’m facing an issue: the computer won’t boot at first. When I press the power button, all fans spin and lights come on, but it doesn’t reach the BIOS screen. The CPU LED stays white constantly. After a few seconds of pressing the power button again, the computer turns off, then comes back on when I press it once more. In short, it needs two attempts to boot, every time it was off. Before the BIOS update, I didn’t have any similar problems. Greetings from Germany, Natsu.

R
Ralkage
Junior Member
46
05-10-2020, 01:11 PM
#2
The update to fTPM might be the issue, possibly affecting RAM compatibility, Secure Boot settings, or other factors. It could also be unrelated to BIOS changes. Are your RAM modules correctly installed in the right slots? Would the problem persist without XMP support?
R
Ralkage
05-10-2020, 01:11 PM #2

The update to fTPM might be the issue, possibly affecting RAM compatibility, Secure Boot settings, or other factors. It could also be unrelated to BIOS changes. Are your RAM modules correctly installed in the right slots? Would the problem persist without XMP support?

S
SkyAtom777
Junior Member
12
05-15-2020, 12:55 PM
#3
Thanks for your quick reply. I already disabled Secure Boot since I had it off earlier. RAM is placed in the correct slots with XMP enabled or disabled not affecting the issue. I’ll investigate the TPM next. After rebooting the system, the problem persists. *Update* It appears the RAM setting is the root cause now. I had manually set it to 3000Mhz in BIOS, which prevented changes from XMP being applied. After switching to Auto with XMP off, the issue reappears when I change it back to manual 3000Mhz. Before the BIOS update, everything worked smoothly with XMP enabled at 3000Mhz. Updated March 14, 2023 by natsu411
S
SkyAtom777
05-15-2020, 12:55 PM #3

Thanks for your quick reply. I already disabled Secure Boot since I had it off earlier. RAM is placed in the correct slots with XMP enabled or disabled not affecting the issue. I’ll investigate the TPM next. After rebooting the system, the problem persists. *Update* It appears the RAM setting is the root cause now. I had manually set it to 3000Mhz in BIOS, which prevented changes from XMP being applied. After switching to Auto with XMP off, the issue reappears when I change it back to manual 3000Mhz. Before the BIOS update, everything worked smoothly with XMP enabled at 3000Mhz. Updated March 14, 2023 by natsu411

Z
Zosiapx
Member
61
05-20-2020, 12:43 AM
#4
Run MemTest86 using XMP settings to check each RAM stick. This helps pinpoint any faulty units. The latest AGESA version enhances compatibility and improves detection of problematic RAM.
Z
Zosiapx
05-20-2020, 12:43 AM #4

Run MemTest86 using XMP settings to check each RAM stick. This helps pinpoint any faulty units. The latest AGESA version enhances compatibility and improves detection of problematic RAM.

I
209
05-25-2020, 08:58 PM
#5
I believe I discovered the problem. At the time of building the computer, I purchased two 16GB RAM kits, and when I opened CPU-Z, I noticed they were identical except for different DRAM types.
I
IninhaGamer_BR
05-25-2020, 08:58 PM #5

I believe I discovered the problem. At the time of building the computer, I purchased two 16GB RAM kits, and when I opened CPU-Z, I noticed they were identical except for different DRAM types.

G
Gustavgurra03
Posting Freak
815
05-27-2020, 05:24 AM
#6
And now I can share the answer to your issues. At least you can attempt a few solutions. First, verify your results with PassMark RamMon. Because the RAM configuration is different and you have two channels with two slots each. Don't stick to AABB; try ABAB if it's unstable, then switch to BABA. The less powerful RAM should be placed in the main slots.
G
Gustavgurra03
05-27-2020, 05:24 AM #6

And now I can share the answer to your issues. At least you can attempt a few solutions. First, verify your results with PassMark RamMon. Because the RAM configuration is different and you have two channels with two slots each. Don't stick to AABB; try ABAB if it's unstable, then switch to BABA. The less powerful RAM should be placed in the main slots.

T
Tarasgames
Member
52
05-27-2020, 08:30 AM
#7
I used the information you provided and followed your instructions. The issue seems to be related to Revision versus revision 2, and I adjusted accordingly. After some changes, the system started booting again with the SK Hynix models in the slots. Thank you for your guidance!
T
Tarasgames
05-27-2020, 08:30 AM #7

I used the information you provided and followed your instructions. The issue seems to be related to Revision versus revision 2, and I adjusted accordingly. After some changes, the system started booting again with the SK Hynix models in the slots. Thank you for your guidance!

F
fruitypie121
Member
64
05-31-2020, 10:56 PM
#8
They shouldn’t fail so quickly. Have you attempted to reset the CMOS? Changing the order of the RAM should have included a BIOS reset. Apologies, I missed that step.
F
fruitypie121
05-31-2020, 10:56 PM #8

They shouldn’t fail so quickly. Have you attempted to reset the CMOS? Changing the order of the RAM should have included a BIOS reset. Apologies, I missed that step.

C
chaoscrafter1
Member
120
06-01-2020, 04:42 AM
#9
I handled it after each change with the sticks. However, it doesn't boot with the Samsung ones—not when using both and not even when I use just one stick. The fans and lights stay on, but the CPU LED stays white and nothing else happens. It feels like the same issue before, but the power cycle and restart don’t seem to resolve it. It’s strange that this only occurs after an update. Maybe trying an older BIOS from the weekend or the Beta version would help. It could be a bug I’m not sure about.
C
chaoscrafter1
06-01-2020, 04:42 AM #9

I handled it after each change with the sticks. However, it doesn't boot with the Samsung ones—not when using both and not even when I use just one stick. The fans and lights stay on, but the CPU LED stays white and nothing else happens. It feels like the same issue before, but the power cycle and restart don’t seem to resolve it. It’s strange that this only occurs after an update. Maybe trying an older BIOS from the weekend or the Beta version would help. It could be a bug I’m not sure about.

J
81
06-01-2020, 06:13 AM
#10
AGESA 1207 performed well with compatibility, surpassing AGESA 1208. However, the newest version is worth testing. Does the alternative RAM fit any slots? Could you attempt the Samsung RAM in a different setup? Also, RAM typically comes with extended guarantees—usually five years, ten years, or even lifetime, depending on the manufacturer.
J
jamesmader1993
06-01-2020, 06:13 AM #10

AGESA 1207 performed well with compatibility, surpassing AGESA 1208. However, the newest version is worth testing. Does the alternative RAM fit any slots? Could you attempt the Samsung RAM in a different setup? Also, RAM typically comes with extended guarantees—usually five years, ten years, or even lifetime, depending on the manufacturer.

Pages (2): 1 2 Next