X870 Tomahawk Cold Boot Issues - How many of us are there?

jonjon12315c602ec

New member
Joined
Oct 4, 2025
Messages
4
I've posted before about this issue in other threads and other subreddits, and from what I can gather this is specifically a problem only on MSI X870/X870e boards when paired with an X3D processor.

Basically, when the system has been shut down for some time, on start up the sound lags, the screen becomes laggy/jittery and 50% of the time the system crashes if you don't restart. From checking various threads it seems that it's an issue that was introduced in a BIOS revision where the main PCIe slot is forced to work at x1 speed. This happens at completely random times, it can be fine for days and then happen twice in a row.

I did so much troubleshooting before realizing it was a BIOS problem, I changed GPU, PSU, M.2 drives and upgraded from a 7800X3D to a 9800X3D along the way with the issue persisting. I've tried different BIOS configurations, and a fresh windows install didn't help either.

Before realizing it was a BIOS problem I contacted MSI and told them about the issue, where they offered an RMA which I didn't take, as I was worried the problem would just persist on another board. MSI are now trying to say it's either a GPU problem, or suggesting it may be due to having an M.2 occupying the M.2_1 slot which makes no sense whatsoever, nothing should share bandwidth with the main PCIe1 slot as far as I'm aware.

I'm trying to tell MSI that it's clearly a BIOS issue and they need to look into a firmware update rather than an RMA, but they seem to be skirting around accepting this or even entertaining the idea.

Here are some other threads I quickly found detailing the same or similar issue;




And my personal experience;


If you have experienced this, and can tell me what the last stable BIOS was, I can feed this back to MSI and push for a fix. I also suggest you log a ticket too, the more eyes we have in it the better the chances for a fix are.
 
You should try enabling FCH Spread Spectrum since people mentioned it fixes the problem.
+1 to this.

I have had 4 successful days now since enabling FCH spread spectrum in BIOS. As mentioned in this thread I also turned off PSPP Policy. Not sure if the latter has an effect, but anyway it works as intended now.
However I don't see it as a long term solution, something is clearly wrong when the computer can't perform on default settings.
 
After dealing with this for like a month straight, i returned my x870 and just got a x870e and havent had a problem since. must have been the board
My rebuild computer seems to have come with the x870e in place of the x870 as well. And all is fine like 15 reboots in. The bug hasn't happened yet.

Spread Spectrum is set to auto. So it's not like they set it up to not fail as often, either. Unless on that board 'auto' means 'on'.
I'll keep you posted.
 
Last edited:
The motherboard in this rebuild computer is a MSI X870E GAMING PLUS WIFI (MS-7E70) on the latest bios for it.
(previous motherboard was a MSI MAG X870 TOMAHAWK WIFI)

Just to test I turned FCH Spread Spectrum from 'auto' to 'off'. And it's had plenty of reboots.
The system seems stable, so far.
 
I have this board as well and just got it returned from RMA (1/10). It booted up fine and ran at pcie x 16 5.0 fine. They said they found "r30 cpu1 internal code msi" and repaired something but upon booting up the computer today (1/11) the issue occurred again and I got a video scheduler screen. I understand this could be due to the graphics card but I sent in my msi card to them for repair as well before the board thinking it was the issue and it wasn't. They found nothing wrong with the graphics card. I replaced every part in my computer (literally) and the mother board was the last thing.

After a few restarts the computer runs and games fine so I dont know whats going on. It seems they are denying the issue and its getting incredibly frustrating. Even calling them, I have some neck beard chomping on food in my ear barely helping me. What is going on with this company and how did they come so highly recommended? Everyone was recommending their parts when I started my build.
 
Again, this issue is related to AGESA 1.2.0.3, the issue is also visible in other motherboards with chipsets x670e/670 also.
 
Last edited:
I have been using a Tomahawk x670e motherboard since July 2023, never had this issue until I flashed it with a BIOS based on AGESA 1.2.0.3. Older BIOS based had other problems but not this one.
 
I need to make a correction to my first post in this thread about the motherboard in the pre-build I initially bought, but can't edit that post anymore I think.

My prebuild computer was supposed to have a MSI X870 GAMING PLUS WIFI motherboard installed, according to the website, so I put that in my post. But in hindsight the actual motherboard delivered with the computer was a MSI MAG X870 TOMAHAWK WIFI. This was the type of board causing the crashes. Even when they tried to fix it with the another one of the same type board it kept crashing.

They rebuild me a replacement computer with a MSI X870E GAMING PLUS WIFI (MS-7E70) motherboard instead. And this is stable.
 
Someone said that connected ARGB-connector of your computer case to the motherboard causing problem with PCI Express version changing, can somebody with that problem check it? Cause I don't have this problem with my 4070ti
 
Someone said that connected ARGB-connector of your computer case to the motherboard causing problem with PCI Express version changing, can somebody with that problem check it? Cause I don't have this problem with my 4070ti
Can you clarify? I currently have the following case and am using the little argb card that came with it but am using the mother board for argb control.

DIYPC Vanguard-F1-BK -Black Dual USB3.0 and Type C Tempered Glass ATX Full Tower Gaming Computer Case w/ 4 x ARGB PWM ...

My board is currently with MSI for its second RMA. Is it confirmed that these cards can be the issue? I don't see how.
 
Can you clarify? I currently have the following case and am using the little argb card that came with it but am using the mother board for argb control.

DIYPC Vanguard-F1-BK -Black Dual USB3.0 and Type C Tempered Glass ATX Full Tower Gaming Computer Case w/ 4 x ARGB PWM ...

My board is currently with MSI for its second RMA. Is it confirmed that these cards can be the issue? I don't see how.
Well, we need a person to try this. I found a comment about this on local market, so that's all I can tell you. Maybe someone here will test unplugging ARGB from JRainbow on MB and check if it helps.
 
Well, we need a person to try this. I found a comment about this on local market, so that's all I can tell you. Maybe someone here will test unplugging ARGB from JRainbow on MB and check if it helps.
Well hopefully but I don't see how it could affect it especially if it was just one guy and I assume plenty of people use argb hubs with their mb. I would try but the fans that came with the case require the hub. I cant daisy chain them to the mother board.
 
I have this problem too and I found out this thread after I searched for possible solution. So I am also on X870 Tomahawk WiFi with RTX 50 series GPU, and I have tried everything that's been written but the problem persists.

What is the solution to this?
 
I have this problem too and I found out this thread after I searched for possible solution. So I am also on X870 Tomahawk WiFi with RTX 50 series GPU, and I have tried everything that's been written but the problem persists.

What is the solution to this?
Out of curiosity, did you try the argb hubs thing the guy said above? Im still waiting for my 2nd RMA to come back so I cant try it. In regards to the issue, it seems to be a very wide spread thing and I don't understand why MSI is ignoring it. I even got in an argument with one of their cs staff about it.
 
Also having cold boot issues with my X870E Gaming plus WIFI , Very slow boot (even the windows loading circle freezes and starts) once in windows I have no WIFI/BT adapter and no front USB, and they don't even show in device manager. shut down and restart fixes it until the next cold boot.

My first ever MSI motherboard and probably my last, will go back to ASUS next time as i did the last 15 years.
 
Back
Top