MPG X870E CARBON WIFI Beta BIOS

Svet

Well-known member
Administrator
Joined
Nov 20, 2003
Messages
84,895
>>> E7E49AMSI.1A1E <<<

>>> E7E49AMSI.1A1H <<<

>>> E7E49AMSI.1A21 <<<

>>> E7E49AMSI.1A22 <<<

>>> E7E49AMSI.1A24 <<<

>>> E7E49AMSI.1A25 <<<

>>> E7E49AMSI.1A26 <<<

>>> E7E49AMSI.1A28 <<<

>>> E7E49AMSI.1A29 <<<

>>> E7E49AMSI.1A31 <<<

>>> E7E49AMSI.1A32 <<<

>>> E7E49AMSI.1A33 <<<

>>> E7E49AMSI.1A34 <<<

>>> E7E49AMSI.1A41 <<<

>>> E7E49AMSI.1A44 <<<

Notes:
  • * Unstable RAM OC
  • * Hang 0D when saving BIOS settings or doing M-Flash

>>> E7E49AMSI.1A62 <<<

>>> E7E49AMSI.1A65 <<<

>>> E7E49AMSI.1A66 <<<
 
Last edited by a moderator:
OMG, Can't disable motherboard leds with 7E49v1A7E BIOS.
Ps.: I removed the cables and reconnected them, the LEDs went out, wow.
 
Last edited:
Mine didn't start happening until A29 or so, then has been an issue on every version since then. Seems some people don't have the problem at all.
Cold starts and resume from long sleep brings it out, but restarting or putting it back to sleep and rining it out again fixes the issue.
Spread Spectrum enabled makes it happen much less often.
I started noticing it with A50, but only after I had it running for month or two. Like something else triggered this, not BIOS update.
It's not frequent (maybe every 10th boot) and restart always solves it, so it's just annoyance, not big problem. I did try enabling Spread spectrum, but that resulted in no boot. Probably would need to reduce some OC to make it work. Waiting for A7x to stop getting new minor versions every few days, then will try it.
 
I started noticing it with A50, but only after I had it running for month or two. Like something else triggered this, not BIOS update.
It's not frequent (maybe every 10th boot) and restart always solves it, so it's just annoyance, not big problem. I did try enabling Spread spectrum, but that resulted in no boot. Probably would need to reduce some OC to make it work. Waiting for A7x to stop getting new minor versions every few days, then will try it.
Yeah, it's definitely something "wearing" or settling in, but the BIOS update process seems to set it off on boards that are susceptible to it. I got mine the first month the board was released, and didn't need Spread Spectrum (but had pleeeeeennnnty of other problems) until A29 in January of last year.

Hard to believe I've been struggling with this board for over a year, but here we are.

Strange that Spread Spectrum didn't allow boot for you, it usually increases stability for a microscopic speed penalty.
 
I've owned the Carbon WiFi since December 2024. Recently, I upgraded to an RTX 5080 (no riser), and since then I've been experiencing frequent issues after booting, but only on a cold start.

Problem:
After booting, the system feels very sluggish/ slow and unstable. The cursor stutters heavily, sometimes there are even some artifacts. The system may calm down after a few seconds, but as soon as a window or an application is opened, the stuttering starts again. In some cases (usually when graphical artifacts are present), the system freezes or go black screen and then reboots itself. After a restart/reboot, the issue is always gone. There're no indications of the error in the event log.

Based on my observations, this might be related to PCIe 5.0. The previous GPU was an RTX 4080, which only supports PCIe 4.0. The RTX 5080 supports and runs on PCIe 5.0. I also tested forcing PCIe 4.0 in the BIOS, but without success. I experimented with various other settings as well (refresh rates, NVIDIA Control Panel settings, ErP on/off, single-monitor setup, HDMI vs. DisplayPort, etc.), but so far I haven't found a reliable solution. One thing that stands out is that the recovery count goes crazy whenever the issue occurs:

GPU Recovery.jpg

The recovery count isn't an error (according to Hwinfo-Martin), but rather a counter that reacts to PCIe interface switching when the GPU switches (for power-saving reasons). This is also easy to see when you open GPU-Z at the same time. I'll try the tip with FCH Spread Spectrum. Hopefully it's a (temporary) solution.
 
I've owned the Carbon WiFi since December 2024. Recently, I upgraded to an RTX 5080 (no riser), and since then I've been experiencing frequent issues after booting, but only on a cold start.

Problem:
After booting, the system feels very sluggish/ slow and unstable. The cursor stutters heavily, sometimes there are even some artifacts. The system may calm down after a few seconds, but as soon as a window or an application is opened, the stuttering starts again. In some cases (usually when graphical artifacts are present), the system freezes or go black screen and then reboots itself. After a restart/reboot, the issue is always gone. There're no indications of the error in the event log.

Based on my observations, this might be related to PCIe 5.0. The previous GPU was an RTX 4080, which only supports PCIe 4.0. The RTX 5080 supports and runs on PCIe 5.0. I also tested forcing PCIe 4.0 in the BIOS, but without success. I experimented with various other settings as well (refresh rates, NVIDIA Control Panel settings, ErP on/off, single-monitor setup, HDMI vs. DisplayPort, etc.), but so far I haven't found a reliable solution. One thing that stands out is that the recovery count goes crazy whenever the issue occurs:

View attachment 208847

The recovery count isn't an error (according to Hwinfo-Martin), but rather a counter that reacts to PCIe interface switching when the GPU switches (for power-saving reasons). This is also easy to see when you open GPU-Z at the same time. I'll try the tip with FCH Spread Spectrum. Hopefully it's a (temporary) solution.
I have the same GPU and it works fine for me. Try disabling the iGPU in your BIOS; that might solve the problem. If it doesn't, your card might have a hardware issue, so it's worth reaching out to the manufacturer for a warranty claim.
 
I've owned the Carbon WiFi since December 2024. Recently, I upgraded to an RTX 5080 (no riser), and since then I've been experiencing frequent issues after booting, but only on a cold start.

Problem:
After booting, the system feels very sluggish/ slow and unstable. The cursor stutters heavily, sometimes there are even some artifacts. The system may calm down after a few seconds, but as soon as a window or an application is opened, the stuttering starts again. In some cases (usually when graphical artifacts are present), the system freezes or go black screen and then reboots itself. After a restart/reboot, the issue is always gone. There're no indications of the error in the event log.

Based on my observations, this might be related to PCIe 5.0. The previous GPU was an RTX 4080, which only supports PCIe 4.0. The RTX 5080 supports and runs on PCIe 5.0. I also tested forcing PCIe 4.0 in the BIOS, but without success. I experimented with various other settings as well (refresh rates, NVIDIA Control Panel settings, ErP on/off, single-monitor setup, HDMI vs. DisplayPort, etc.), but so far I haven't found a reliable solution. One thing that stands out is that the recovery count goes crazy whenever the issue occurs:

View attachment 208847

The recovery count isn't an error (according to Hwinfo-Martin), but rather a counter that reacts to PCIe interface switching when the GPU switches (for power-saving reasons). This is also easy to see when you open GPU-Z at the same time. I'll try the tip with FCH Spread Spectrum. Hopefully it's a (temporary) solution.
This is the same problem several of us are having. Over time (and BIOS updates?) it appears to happen more often. ENABLING FCH Spread Spectrum in your BIOS will likely fix it (AUTO is disabled, I believe), for most of the time. You'll still get the occasional dips in PCIe lane speed, but putting your PC in sleep and then resuming will get it set back to 5.0, as will a reboot. It happens so infrequently that I forget about it, but if there's any hiccups in mouse movement at all after sleep, I'll check in GPUz.

The problem really hits when it gets stuck at 2.0 or 2.1, and will likely crash shortly after if you put any load on the graphics driver.

Someday, MSI will hopefully fix this and get the PCIe to resume at 5.0 properly every boot/resume.

FFCH Spread Spectrum does put a very tiny penalty in your processing as it will shift frequency around a bit, but it's more like... 0.001%. Not noticable in gaming or most uses.
 
This is the same problem several of us are having. Over time (and BIOS updates?) it appears to happen more often. ENABLING FCH Spread Spectrum in your BIOS will likely fix it (AUTO is disabled, I believe), for most of the time. You'll still get the occasional dips in PCIe lane speed, but putting your PC in sleep and then resuming will get it set back to 5.0, as will a reboot. It happens so infrequently that I forget about it, but if there's any hiccups in mouse movement at all after sleep, I'll check in GPUz.

The problem really hits when it gets stuck at 2.0 or 2.1, and will likely crash shortly after if you put any load on the graphics driver.

Someday, MSI will hopefully fix this and get the PCIe to resume at 5.0 properly every boot/resume.

FFCH Spread Spectrum does put a very tiny penalty in your processing as it will shift frequency around a bit, but it's more like... 0.001%. Not noticable in gaming or most uses.
All I can say is that since I bought this board, I’ve never experienced any lane degradation at any level cold boot, restart, gaming or otherwise. Either there are some boards with a weird defect on it effecting the lanes under some circumstances, or there’s some special connection between MSI motherboards and MSI VGA. But one I know for sure no BIOS update will ever fix it. Every time I check GPUZ lanes are fixed on 16x5.0
 
This is the same problem several of us are having. Over time (and BIOS updates?) it appears to happen more often. ENABLING FCH Spread Spectrum in your BIOS will likely fix it (AUTO is disabled, I believe), for most of the time. You'll still get the occasional dips in PCIe lane speed, but putting your PC in sleep and then resuming will get it set back to 5.0, as will a reboot. It happens so infrequently that I forget about it, but if there's any hiccups in mouse movement at all after sleep, I'll check in GPUz.

The problem really hits when it gets stuck at 2.0 or 2.1, and will likely crash shortly after if you put any load on the graphics driver.

Someday, MSI will hopefully fix this and get the PCIe to resume at 5.0 properly every boot/resume.

FFCH Spread Spectrum does put a very tiny penalty in your processing as it will shift frequency around a bit, but it's more like... 0.001%. Not noticable in gaming or most uses.
Out of curiosity, do you have Windows Fast Startup / Hybrid Shutdown enabled or disabled?
 
All I can say is that since I bought this board, I’ve never experienced any lane degradation at any level cold boot, restart, gaming or otherwise. Either there are some boards with a weird defect on it effecting the lanes under some circumstances, or there’s some special connection between MSI motherboards and MSI VGA. But one I know for sure no BIOS update will ever fix it. Every time I check GPUZ lanes are fixed on 16x5.0
Yup, never happened to me either until about 3 months in, late January 2025, when A29 was released. That's when I needed to start enabling Spread Spectrum to prevent this from happening, most of the time.
I would not be at all surprised to find it's some minor defect, or a cheap-out on the early boards' ICs. There was initially word that a couple of other vendors (ASUS, Gigabyte) that had a similar problem but had fixed it in their BIOS. Unknown if that's true or not.
Out of curiosity, do you have Windows Fast Startup / Hybrid Shutdown enabled or disabled?
This is a good question. I don't believe I have Fast Startup or Hybrid Shutdown enabled. When I get a few minutes, I'll check for that. I haven't changed it on this system that I can remember, but it has been a hell of a year...
 
Based on my observations, this might be related to PCIe 5.0. The previous GPU was an RTX 4080, which only supports PCIe 4.0. The RTX 5080 supports and runs on PCIe 5.0.
I don't think it's related to PCIe 5.0, as I'm having exactly the same problem on my 4090. On rare occasions after boot, it works as 3.0 instead of 4.0.

Out of curiosity, do you have Windows Fast Startup / Hybrid Shutdown enabled or disabled?
Interesting idea... I've now disabled Fast Startup, will see after few weeks if it helped.
 
Try disabling the iGPU in your BIOS
It's disabled from day one.

If it doesn't, your card might have a hardware issue, so it's worth reaching out to the manufacturer for a warranty claim.
I don't think that makes sense. I have over 150 hours of game time on the 5080. This error only occurs during a cold start (but not always), and after a restart, everything runs smoothly. Therefore, it's very likely that the GPU can be ruled out. In German HWL-Forum are several users who have exactly the same problem with exactly the same image errors (post). It's noticeable that this always occurs with MSI motherboards.

So far, I'm very satisfied with the Carbon Wifi. This is the first time I've had such problems. Hopefully, MSI will resolve the issue.


Interesting idea... I've now disabled Fast Startup, will see after few weeks if it helped.
I tried disabling fast start. It didn't work. I've now installed the latest chipset driver and activated FCH Spread Spectrum. The 2-3 starts after setting it up were normal so far. Hope it stays that way.
 
Since you already have hwinfo, check the 12VHPWR Voltage reading under the gpu tab. Just to rule out it's not some bad stuff going on with the connector. What the exact value should be varies a bit, but I think it's ~12v-12.3v, google a bit on it. Check if it stays about the same during idle, load and so on.
 
Since you already have hwinfo, check the 12VHPWR Voltage reading under the gpu tab. Just to rule out it's not some bad stuff going on with the connector. What the exact value should be varies a bit, but I think it's ~12v-12.3v, google a bit on it. Check if it stays about the same during idle, load and so on.
Looks completely normal in all logs. Whether gaming or idle/office load, the 12VHPWR always shows 12.1xx V. As mentioned, gaming load runs without any problems, as long as the cold start boots correctly.
 
Some people have replaced their motherboard with one from another brand and the problem disappeared, so it's not a hardware defect since it works 99% of the time with Spread Spectrum. And it's not just the X870 chipset that's affected by MSI.
 
I don't think it is all hardware I think it is something to do with the bios setups take me for example I never had the problem and even with I use 64 bios it always works and it just started happen on the new biois go back to 64 and even think works.i think that msi has a lot of issues with making bios files standard that is why we get some many problem in different versions.
 
It's disabled from day one.


I don't think that makes sense. I have over 150 hours of game time on the 5080. This error only occurs during a cold start (but not always), and after a restart, everything runs smoothly. Therefore, it's very likely that the GPU can be ruled out. In German HWL-Forum are several users who have exactly the same problem with exactly the same image errors (post). It's noticeable that this always occurs with MSI motherboards.

So far, I'm very satisfied with the Carbon Wifi. This is the first time I've had such problems. Hopefully, MSI will resolve the issue.



I tried disabling fast start. It didn't work. I've now installed the latest chipset driver and activated FCH Spread Spectrum. The 2-3 starts after setting it up were normal so far. Hope it stays that way.
Keep GPUz installed and check it regularly - you might see some 4.0's in there that you might not notice otherwise, but it largely does take care of the problem with FCH Spread Spectrum enabled. If you notice it acting up, put your computer in suspend for a sec, then resume and you should be good.

Seems to happen whenever the computer is asleep or shut down completely for more than an hour or so and things "cool off".
 
I've owned the Carbon WiFi since December 2024. Recently, I upgraded to an RTX 5080 (no riser), and since then I've been experiencing frequent issues after booting, but only on a cold start.

Problem:
After booting, the system feels very sluggish/ slow and unstable. The cursor stutters heavily, sometimes there are even some artifacts. The system may calm down after a few seconds, but as soon as a window or an application is opened, the stuttering starts again. In some cases (usually when graphical artifacts are present), the system freezes or go black screen and then reboots itself. After a restart/reboot, the issue is always gone. There're no indications of the error in the event log.

Based on my observations, this might be related to PCIe 5.0. The previous GPU was an RTX 4080, which only supports PCIe 4.0. The RTX 5080 supports and runs on PCIe 5.0. I also tested forcing PCIe 4.0 in the BIOS, but without success. I experimented with various other settings as well (refresh rates, NVIDIA Control Panel settings, ErP on/off, single-monitor setup, HDMI vs. DisplayPort, etc.), but so far I haven't found a reliable solution. One thing that stands out is that the recovery count goes crazy whenever the issue occurs:

View attachment 208847

The recovery count isn't an error (according to Hwinfo-Martin), but rather a counter that reacts to PCIe interface switching when the GPU switches (for power-saving reasons). This is also easy to see when you open GPU-Z at the same time. I'll try the tip with FCH Spread Spectrum. Hopefully it's a (temporary) solution.
Hi there,
I have the exact same motherboard (MSI X870E Carbon WiFi) and CPU (9800X3D), and I’ve been looking into your issue. Since you mentioned this only happens on a cold start and involves "recovery counts" (PCIe errors), there are a few things that stand out.

First, I noticed your Curve Optimizer is at -38. While the 9800X3D is efficient, -38 is quite aggressive. Cold start issues are often linked to "low-load instability." When the system is cold and idling at the desktop, a high negative CO offset can cause the voltage to drop too low for the CPU's internal PCIe controller to maintain a stable link with the Gen5 GPU. I would suggest testing with CO at Stock or -20 just to rule out CPU instability affecting the PCIe lanes.

Regarding the PCIe 5.0 link, here are a few other things you might want to try:
  1. Disable "Power Management Mode" in NVIDIA Control Panel: Set it to "Prefer Maximum Performance" to see if the stuttering stops. Sometimes the aggressive power saving on Gen5 cards causes link drops during idle.
  2. Disable "Fast Boot" in Windows: Since you mentioned it only happens on a cold start, Windows Fast Startup (which is a hibernation hybrid) might be loading a corrupted driver state. A "Restart" clears this, which explains why the issue disappears after a reboot.
  3. Update to the latest AGESA BIOS: MSI recently released BIOS updates specifically targeting PCIe 5.0 compatibility and RTX 50-series stability.
  4. Check "C-States" in BIOS: Try disabling Global C-States. If the stuttering stops, it confirms the issue is related to the CPU dropping voltage too low during low-load scenarios, affecting the PCIe bus.
Your "recovery count" going crazy is a clear sign of PCIe Signal Integrity issues. If forcing Gen4 didn't work, it might actually be the CPU's SOC voltage or the CO offset being too low to drive the high-speed bus stably.

Hope this helps you narrow it down!
 
Back
Top