MSI B650 Tomahawk yellow dram led when restarting pc

Joined
Nov 29, 2024
Messages
20
this is a old problem never fixed, if restart windows 11 the pc will not start and yellow led dram is on
if you turn on pc normally it will start with no yellow dram led
msi fix this annoying problem
 
What's your DRAM model?
Is it listed on AVL?
 
What's your DRAM model?
Is it listed on AVL?
yes, these CTCWD532G6000HC30DC01
 
never tried only one dram, the problem is on the memory training of dram at the restart, is a bios problem im sure, other users have the same exact problem
Testing each RAM individually is a mandatory step to see if one of the DIMMs is playing a role in the problem. When testing put the DIMM in the slot furthest away from the CPU.
 
My b650I has/had the same behavior with a 7700x
My fix was to increase SOC voltage to 1.3v with "amd overclocking" option or decrease ddr speed to 5600 or worse.
Can you test it and report back?

I had a thread on here about to, someone mentioned some ryzen cpu memory controllers are weaker then others but if they still work at ddr5 jedec speeds like 4800 speed AMD doesnt have to replace it.
see thread:
 
My b650I has/had the same behavior with a 7700x
My fix was to increase SOC voltage to 1.3v with "amd overclocking" option or decrease ddr speed to 5600 or worse.
Can you test it and report back?

I had a thread on here about to, someone mentioned some ryzen cpu memory controllers are weaker then others but if they still work at ddr5 jedec speeds like 4800 speed AMD doesnt have to replace it.
see thread:
interesting, there is some risk doing the increase SOC voltage to 1.3v?
 
I have the same sort of issues. Contantly hangs on restart and you get a boot LED forever but if I turn the PC off and boot from cold start it works. Honestly I will never be buying another MSI board again. When it is in Windows I don't have any issues for stabilty but trying to get it BIOS trained and after any changes even such as accepting a simple USB boot disk takes way too long. Often so long my monitor gives up waiting and switches off. I never had this problem with either Gigabyte or Asus boards in the past. MSI is a nightmare. Never again.
 
I have the same sort of issues. Contantly hangs on restart and you get a boot LED forever but if I turn the PC off and boot from cold start it works. Honestly I will never be buying another MSI board again. When it is in Windows I don't have any issues for stabilty but trying to get it BIOS trained and after any changes even such as accepting a simple USB boot disk takes way too long. Often so long my monitor gives up waiting and switches off. I never had this problem with either Gigabyte or Asus boards in the past. MSI is a nightmare. Never again.
agree but i don't understand why they don't fix this with a bios update, they made so much bios update in these months for this motherboard and problem not solved yet!
 
agree but i don't understand why they don't fix this with a bios update, they made so much bios update in these months for this motherboard and problem not solved yet!
Totally agree - there is no excuse for these issues not being fixed properly in a BIOS update long ago. I went to the BIOS support page and note that they are still running three consecutive "Beta" versions of the BIOS since my last update (mine is the B650M Mortar and close relation of the Tomahawk). That suggests to me they don't know what they are doing if they can't even produce a certified BIOS since last July - I certainly am not going to risk using any Beta versions and risk a potentially bricked board in a beta BIOS update process. I can't understand why tech reviewers don't slap MSI around a hell of a lot more because these pages are filled with customers with stuck led lights and other BIOS issues. My board was so finicky with RAM that I couldn't get a new graphics card to work with the board and actually RMA'd the card thinking it was the issue. Nope it was just the board not booting with the card and the RAM combination - it was perfectly happy with an older card though and the same RAM config which threw me off trying to troubleshoot the damn thing. I will definitely not be buying another MSI board whilst their quality control, time to fix speeds and customer focus is so poor. You expect a motherboard to just work out of the box with modern components and not be a nightmare issue-ridden problem - especially with the prices you have to pay. It is not like they are $ 100 budget boards. They have lost me as a future customer and MSI well deserves it's reputation for having the slowest and finickiest BIOS to train out of all the big name manufacturers. Even the simplest boot from the BIOS with a USB disk (as I said earlier) seems to cause it long deliberations (WTF is it thinking about - it just has to hand off to the USB drive ?) - if other manufacturers don't have these issues then there is no excuse for MSI to have them.
 
Further to my previous comment I am frustrated also by the fact that if we can't get into BIOS before the RAM training is done (as it is now) then we risk having to start from scratch - pull the RAM and pull the CMOS battery. Not a big deal on a test bench but it certainly is when all in a case and your GPU is on an mATX board blocking the battery and the reset pins and you cant get at the CMOS battery without also pulling the GPU. So make a mistake in a BIOS setting and the motherboard won't boot, won't respond to DEL keypresses and you are essentially locked out of BIOS until you do the big teardown reset. SO I asked ChatGPT why it isn't possible (and desirable) for there to to be a small (say 4K) of RAM set aside on the board to read keypresses BEFORE the memory training starts. In that case you could change BIOS settings to default before the memory training caused the issues we and many others are experiencing. Here is my suggestion - MSI should be able to easily adopt it and save us all a load of grief. I don't know if ChatGPT has got it perfectly as I envisaged it but it should be enough to get MSI started !!:rolleyes:

# **1. Tiny on-board buffer**
* Reserve **~4KB of EC (Embedded Controller) RAM** or a small area in SPI flash.
* Purpose: store a minimal pre-boot routine and a small keyboard input buffer.
* Requirements: fast enough to detect keypresses before main DDR5 memory is trained.

# **2. EC Pre-Boot Routine**
On power-on:
1. **EC takes control immediately** (before CPU starts memory training).
2. Initialize only the **keyboard interface** and minimal display (or just rely on LEDs).
3. Check for keypresses (DEL/F2/etc.) for a fixed window (e.g., first 2–3 seconds).

# **3. Decision Logic**
* **If key is pressed:**
* EC signals the CPU/BIOS to jump directly into BIOS setup.
* Skip DDR5 training completely for now.
* BIOS can load defaults or safe JEDEC memory settings.
* **If key is not pressed:**
* EC releases control.
* Normal CPU boot proceeds, memory training runs as usual.

# **4. Minimal Safe BIOS Stack**
* When jumping to BIOS, use **EC memory as temporary stack** until DDR5 is initialized.
* Once DDR5 memory training completes or safe default JEDEC speeds are loaded:
* Switch BIOS execution to main RAM.
* All normal BIOS features become available.

# **5. Advantages**
1. **Never locked out of BIOS** — even if RAM settings were previously fatal.
2. **Works with any number of DIMMs** — no need to remove sticks or reset CMOS.
3. **Zero dependency on CPU being able to train memory first.**
4. **Backward-compatible** for normal users — routine only runs if key is pressed.

# **6. Implementation Notes for Manufacturers**
* EC firmware update — minimal code (~2–4KB).
* Keyboard scanning routine — already exists in EC, just needs a pre-boot hook.
* BIOS handoff — existing architecture already supports conditional boot paths; just add a “skip DDR5 training if safe mode requested” flag.
* Could be integrated into a BIOS update — no hardware change needed.
 
At both. Please report the issue with MSI. When they see multiple reports to them it may help to decide to address the issue. From what I gathered reports directly to MSI sound louder than issues being reported at the forums.
 
At both. Please report the issue with MSI. When they see multiple reports to them it may help to decide to address the issue. From what I gathered reports directly to MSI sound louder than issues being reported at the forums.
Appreciate that Eric but MSI need to understand and respond to customers' issues and watching their user forums is the obvious and most economical way to do that (for MSI) as well as their received formal support requests. I don't have time to mess about trying to communicate with non-English first language speakers - I have had interactions with support before and it was a pain in the butt. It isn't just the two of us complaining either - there are reports all over these forums and the internet generally about MSI boot issues. As DJSolidsnake8 has already stated in his first comment, these issues have been going on for absolutely ages so I cannot believe MSI is not aware of them. They either don't care or they can't fix them - which is it ? They have already lost one future customer (Me) as a direct result of the "Motherboard Anxiety Syndrome" I experience whenever dealing with the MSI BIOS. I never had that problem with ASUS nor Gigabyte whose boards I have used in the past. It seems MSI just can't get to grips with DDR5 Ram. The new user motherboard experience out of the box is woeful.
 
Last edited:
@djsolidsnake8158e02e3 What BIOS version do you have installed?

I was looking into a topic with a very similar problem. There could be multiple reasons why it happens. One of them is running hardware monitor tools like f.e. HWInfo which has been solved BIOS update.
actually im on latest 7D75v1P5(Beta version) but every single versions i tried before have the same problem
msi need to fix this
 
Back
Top