MPG X870E CARBON WIFI Beta BIOS

Svet

Well-known member
Administrator
Joined
Nov 20, 2003
Messages
85,281
>>> 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 <<<

>>> E7E49AMSI.1A93 <<<
 
Last edited:
If neither the PCIE2 nor the M2_2 slot is occupied, your VGA should not run at x8 speed. However, if either or both of these slots are occupied, the switch activates and your VGA will operate at x8. If your VGA is running at x8 speed without anything installed in PCIE2 or M2_2, your motherboard may be faulty and should be considered for RMA. This issue should not occur, and I personally have never experienced it with my X870E Carbon WIFI.
If, for any reason, the SWTICH is activated, a standard CMOS clear should resolve the issue.
For a more thorough CMOS reset, first unplug the board from power, remove the battery, and short the on-board CMOS clear pins. Wait approximately 10 minutes, then reinstall the battery.
This process should restore the board to its original factory settings.
Avoiding references to mythical beings and overly literal expressions can help keep the post focused on the main issue and reduce the size .
...for someone that hates AI slop, you did a really good impersonation of AI summarization of my post that they were replying to... 😉
There's no need to short pins or pop the BIOS battery on the Carbon. The BIOS Clear/reset button in the back performs the same function (shorting the pins) much more conveniently, so far as I understand it from the documentation.
 
...for someone that hates AI slop, you did a really good impersonation of AI summarization of my post that they were replying to... 😉
There's no need to short pins or pop the BIOS battery on the Carbon. The BIOS Clear/reset button in the back performs the same function (shorting the pins) much more conveniently, so far as I understand it from the documentation.
AI Slop it is and I hate it , however, NO AI summarization of your post was necessary every word is mine and a well known fact I didn't even care to read through the litany you wrote just picked up glances here and there , that's for the other guy to read .
You are right, it does what you say with CMOS button until it doesn't and I'm talking out of experience, If you didn't do it then obviously you wouldn't know the difference , the explained option and method of hard reset bios is still available on board page 52 user manual JBAT1: Clear CMOS (Reset BIOS) Jumper ;) in case this doesn't help as a last resort and the switch keeps activated then his motherboard is a mythical POTATO like many others on this forum but that's more MSI's fault .
 
Last edited:
...for someone that hates AI slop, you did a really good impersonation of AI summarization of my post that they were replying to... 😉
There's no need to short pins or pop the BIOS battery on the Carbon. The BIOS Clear/reset button in the back performs the same function (shorting the pins) much more conveniently, so far as I understand it from the documentation.
AI Slop it is and I hate it , however, NO AI summarization of your post was necessary every word is mine and a well known fact I didn't even care to read through the litany you wrote just picked up glances here and there , that's for the other guy to read .
You are right, it does what you say with CMOS button until it doesn't and I'm talking out of experience, If you didn't do it then obviously you wouldn't know the difference , the explained option and method of hard reset bios is still available on board page 52 user manual JBAT1: Clear CMOS (Reset BIOS) Jumper ;) in case this doesn't help as a last resort and the switch keeps activated then his motherboard is a mythical POTATO like many others on this forum but that's more MSI's fault .

So i CMOS'd the thing, with the back button. i loaded defaults too, and still PCIe stuck at x8 like everything i tried before. didn't do the c-state thing tho. but iu tried all else you told me to try.

and i wrote that i noticed that my PC sometimes doesn't want to reboot, gotta correct that, since A95, every windows reboot button hit, gets the PC stuck, but not in mem training. the screen turns off, and i waited 5 minutes for any reaction and nothing. if the PC would be memory training, it would also get the screens out of standby, which doesn't happen. if the PC was off, hiting the power button would just boot the PC, but if i just press the power button, nothing happens, and i have to force shut off the PC on the front power button and then boot it out of stand by, with said button.

this didn't happen at all, before A95, same as the x8. and this booting issue is eerily similiar to the problems i had with my strix e-f 670 from ASUS, but that one was pretty sure, related to getting stuck in mem training, so this seems to also be a fully new and original problem too, cause with the ASUS, every reboot and every boot was a lottery, cause sometimes, it didn't happen. if i turn the carbon PC off now, it boots everytime. if i hit reboot, it gets stuck, every time.

so if it was just the x8, i would feel obligated to believe that it wouldnt have to be the BIOS, but the fact that this BIOS version doesn't let me reboot trough windows, makes me feel like this has to be something with the BIOS having not installed properly, as an odity was, the more new BIOS i installed, the longer the process of loading into M-flash, and loading the BIOS from an external stick took. i mean that shouldn't happen i think, and i really noticed this odity also, with the first pre AGESA versions for 1.3.0.0 taking longer and longer, now that i realized that mid writinng my diseration of failure.

maybe this BIOS/AGESA version has some special kinks, which could be something in my set up which this particular BIOS doesn't like?!
those problems only appeared with A95 aside from the long BIOS install times, and i don't believe that it has anything to do with the widespread AM5 PCIe coldboot, degradation issue. my mouse quirks are also related to me making many tiny operations in quick succession and not on boot.

so, to not have to downgrade the BIOS, i'm gonna hope that we'll see a new version till close to the end of the month, and if that doesn't happen, i will downgrade it before my PC wizard comes to visit me, to install my new noctua front fans cause the stock ones in my case are infuriatingly loud at 600RPM already. and we'll also install that new monitoring tool from der8auer, where you can see if the 12V cables are all having the right power ditribution, and also gives you a warning noise if all the juice goes over too few "cables" which seems to causes the melting 12V cables, so that i can force shutdown the PC if i ever hear the trumpets of jensen, and his barely thought out choice of a new power cable connection which is, having issues, to put i mildly.

but as the AM5 plattform has also proven to me, with issues i read from every board manufacturer, when i searched for a replacment for the strix. MSI according to most forums i scouered trough, had the least issues.
my PC wizards GF, also has reboot issues on ther ASROCK board, sometimes, and only one particular BIOS version didn't cause that issue for her. and as said in one of my ealier messages, the problems on my ASUS board, is something which atleast 5 other ppl also experienced in the ASUS forum. or in short, call me beta tester, cause if we ain't doing it, AMD certainly won't pay ppl to beta test for them XD

downgrading is like a last resort i'm gonna try, even when it's gonna irk me very very much, to not know, what's up. or maybe i'll have to reboot too often and then going to downgrade cause the problem is gonna infuriate me enough, to do it "for science".
on ASUS, downgrading as much as i remember, necesitated to have the stick in that one particular slot, and you had to flash from the back, flash button, and i take it this also goes for MSI in case of downgrading, and my cable managment had, it's world already rocked now, and when i have to get the PC out of its nieche anyway when my friend comes, then i can optimize the whole USB set up then with nothing in the way, and i'll downgrade the day before he comes so that i can just pull out the cables willy nilly, as i will survive one night where some things may not be connected for a few hours.

and as for me not mentioning dragons, atleast you can be sure that i'm not AI, cause my attempts at condensing information, as an author, sadly fall flat on their nose, cause i just can't keep myself from trying to be atleast, mildly entertaining for the reader.

i'm going to update you as soon as i'm gonna make a decision. for now, i'm just gonna mope that my 5k PC, still doesn't, just work XD

and obviously thank you both, even if it didn't net tangible fruits, but your explanations atleast made me a bit more knowledgable, which is always a good thing.
 
So i CMOS'd the thing, with the back button. i loaded defaults too, and still PCIe stuck at x8 like everything i tried before. didn't do the c-state thing tho. but iu tried all else you told me to try.

and i wrote that i noticed that my PC sometimes doesn't want to reboot, gotta correct that, since A95, every windows reboot button hit, gets the PC stuck, but not in mem training. the screen turns off, and i waited 5 minutes for any reaction and nothing. if the PC would be memory training, it would also get the screens out of standby, which doesn't happen. if the PC was off, hiting the power button would just boot the PC, but if i just press the power button, nothing happens, and i have to force shut off the PC on the front power button and then boot it out of stand by, with said button.

this didn't happen at all, before A95, same as the x8. and this booting issue is eerily similiar to the problems i had with my strix e-f 670 from ASUS, but that one was pretty sure, related to getting stuck in mem training, so this seems to also be a fully new and original problem too, cause with the ASUS, every reboot and every boot was a lottery, cause sometimes, it didn't happen. if i turn the carbon PC off now, it boots everytime. if i hit reboot, it gets stuck, every time.

so if it was just the x8, i would feel obligated to believe that it wouldnt have to be the BIOS, but the fact that this BIOS version doesn't let me reboot trough windows, makes me feel like this has to be something with the BIOS having not installed properly, as an odity was, the more new BIOS i installed, the longer the process of loading into M-flash, and loading the BIOS from an external stick took. i mean that shouldn't happen i think, and i really noticed this odity also, with the first pre AGESA versions for 1.3.0.0 taking longer and longer, now that i realized that mid writinng my diseration of failure.

maybe this BIOS/AGESA version has some special kinks, which could be something in my set up which this particular BIOS doesn't like?!
those problems only appeared with A95 aside from the long BIOS install times, and i don't believe that it has anything to do with the widespread AM5 PCIe coldboot, degradation issue. my mouse quirks are also related to me making many tiny operations in quick succession and not on boot.

so, to not have to downgrade the BIOS, i'm gonna hope that we'll see a new version till close to the end of the month, and if that doesn't happen, i will downgrade it before my PC wizard comes to visit me, to install my new noctua front fans cause the stock ones in my case are infuriatingly loud at 600RPM already. and we'll also install that new monitoring tool from der8auer, where you can see if the 12V cables are all having the right power ditribution, and also gives you a warning noise if all the juice goes over too few "cables" which seems to causes the melting 12V cables, so that i can force shutdown the PC if i ever hear the trumpets of jensen, and his barely thought out choice of a new power cable connection which is, having issues, to put i mildly.

but as the AM5 plattform has also proven to me, with issues i read from every board manufacturer, when i searched for a replacment for the strix. MSI according to most forums i scouered trough, had the least issues.
my PC wizards GF, also has reboot issues on ther ASROCK board, sometimes, and only one particular BIOS version didn't cause that issue for her. and as said in one of my ealier messages, the problems on my ASUS board, is something which atleast 5 other ppl also experienced in the ASUS forum. or in short, call me beta tester, cause if we ain't doing it, AMD certainly won't pay ppl to beta test for them XD

downgrading is like a last resort i'm gonna try, even when it's gonna irk me very very much, to not know, what's up. or maybe i'll have to reboot too often and then going to downgrade cause the problem is gonna infuriate me enough, to do it "for science".
on ASUS, downgrading as much as i remember, necesitated to have the stick in that one particular slot, and you had to flash from the back, flash button, and i take it this also goes for MSI in case of downgrading, and my cable managment had, it's world already rocked now, and when i have to get the PC out of its nieche anyway when my friend comes, then i can optimize the whole USB set up then with nothing in the way, and i'll downgrade the day before he comes so that i can just pull out the cables willy nilly, as i will survive one night where some things may not be connected for a few hours.

and as for me not mentioning dragons, atleast you can be sure that i'm not AI, cause my attempts at condensing information, as an author, sadly fall flat on their nose, cause i just can't keep myself from trying to be atleast, mildly entertaining for the reader.

i'm going to update you as soon as i'm gonna make a decision. for now, i'm just gonna mope that my 5k PC, still doesn't, just work XD

and obviously thank you both, even if it didn't net tangible fruits, but your explanations atleast made me a bit more knowledgable, which is always a good thing.
You should be able to revert to an older BIOS, as there is a BIOS recovery procedure involving a USB stick and a dedicated USB port if you can't get it flashed normal way. However, having the lane stuck at 8 even after a CMOS clear isn’t promising. Good Luck !
 
Guys, should i be afraid? this wasn't intended in any way, im not joking.
As for info im on the BIOS 7E49v1A95.
CPU: Ryzen 9 9950X3D
And my PC has allways been and is still stable in performance and crashes.

My CPU Frequency literaly looks like its missfiring, its going from 5.4 to IDK what numbers are even those.
1775670805770.png
 
So i CMOS'd the thing, with the back button. i loaded defaults too, and still PCIe stuck at x8 like everything i tried before. didn't do the c-state thing tho. but iu tried all else you told me to try.

and i wrote that i noticed that my PC sometimes doesn't want to reboot, gotta correct that, since A95, every windows reboot button hit, gets the PC stuck, but not in mem training. the screen turns off, and i waited 5 minutes for any reaction and nothing. if the PC would be memory training, it would also get the screens out of standby, which doesn't happen. if the PC was off, hiting the power button would just boot the PC, but if i just press the power button, nothing happens, and i have to force shut off the PC on the front power button and then boot it out of stand by, with said button.

this didn't happen at all, before A95, same as the x8. and this booting issue is eerily similiar to the problems i had with my strix e-f 670 from ASUS, but that one was pretty sure, related to getting stuck in mem training, so this seems to also be a fully new and original problem too, cause with the ASUS, every reboot and every boot was a lottery, cause sometimes, it didn't happen. if i turn the carbon PC off now, it boots everytime. if i hit reboot, it gets stuck, every time.

so if it was just the x8, i would feel obligated to believe that it wouldnt have to be the BIOS, but the fact that this BIOS version doesn't let me reboot trough windows, makes me feel like this has to be something with the BIOS having not installed properly, as an odity was, the more new BIOS i installed, the longer the process of loading into M-flash, and loading the BIOS from an external stick took. i mean that shouldn't happen i think, and i really noticed this odity also, with the first pre AGESA versions for 1.3.0.0 taking longer and longer, now that i realized that mid writinng my diseration of failure.

maybe this BIOS/AGESA version has some special kinks, which could be something in my set up which this particular BIOS doesn't like?!
those problems only appeared with A95 aside from the long BIOS install times, and i don't believe that it has anything to do with the widespread AM5 PCIe coldboot, degradation issue. my mouse quirks are also related to me making many tiny operations in quick succession and not on boot.

so, to not have to downgrade the BIOS, i'm gonna hope that we'll see a new version till close to the end of the month, and if that doesn't happen, i will downgrade it before my PC wizard comes to visit me, to install my new noctua front fans cause the stock ones in my case are infuriatingly loud at 600RPM already. and we'll also install that new monitoring tool from der8auer, where you can see if the 12V cables are all having the right power ditribution, and also gives you a warning noise if all the juice goes over too few "cables" which seems to causes the melting 12V cables, so that i can force shutdown the PC if i ever hear the trumpets of jensen, and his barely thought out choice of a new power cable connection which is, having issues, to put i mildly.

but as the AM5 plattform has also proven to me, with issues i read from every board manufacturer, when i searched for a replacment for the strix. MSI according to most forums i scouered trough, had the least issues.
my PC wizards GF, also has reboot issues on ther ASROCK board, sometimes, and only one particular BIOS version didn't cause that issue for her. and as said in one of my ealier messages, the problems on my ASUS board, is something which atleast 5 other ppl also experienced in the ASUS forum. or in short, call me beta tester, cause if we ain't doing it, AMD certainly won't pay ppl to beta test for them XD

downgrading is like a last resort i'm gonna try, even when it's gonna irk me very very much, to not know, what's up. or maybe i'll have to reboot too often and then going to downgrade cause the problem is gonna infuriate me enough, to do it "for science".
on ASUS, downgrading as much as i remember, necesitated to have the stick in that one particular slot, and you had to flash from the back, flash button, and i take it this also goes for MSI in case of downgrading, and my cable managment had, it's world already rocked now, and when i have to get the PC out of its nieche anyway when my friend comes, then i can optimize the whole USB set up then with nothing in the way, and i'll downgrade the day before he comes so that i can just pull out the cables willy nilly, as i will survive one night where some things may not be connected for a few hours.

and as for me not mentioning dragons, atleast you can be sure that i'm not AI, cause my attempts at condensing information, as an author, sadly fall flat on their nose, cause i just can't keep myself from trying to be atleast, mildly entertaining for the reader.

i'm going to update you as soon as i'm gonna make a decision. for now, i'm just gonna mope that my 5k PC, still doesn't, just work XD

and obviously thank you both, even if it didn't net tangible fruits, but your explanations atleast made me a bit more knowledgable, which is always a good thing.

Yeah, this is pretty weird. That it doesn't happen on previous BIOS versions really makes me think it isn't hardware failure in general. The only other thing I can think of aside from the hardware just not being able to handle something new in the BIOS (and that would also be VERY weird) is if your CPU isn't mounted with not-quite-even pressure, and something new in the BIOS isn't detecting part of the PCIe channels, some sensitivity in the detection is suddenly more sensitive. I've seen that cause memory channel detection issues, and though I've never heard of that for PCIe channels, maybe it's possible. I haven't heard of any others having this same problem, but maybe nobody on A95 has noticed yet... When your hardware pal arrives, maybe have them make sure there's no dust or something triggering M2_2 or PCI_E2 to make it think they're populated, even though they don't have anything actually plugged in there.
 
Guys, should i be afraid? this wasn't intended in any way, im not joking.
As for info im on the BIOS 7E49v1A95.
CPU: Ryzen 9 9950X3D
And my PC has allways been and is still stable in performance and crashes.

My CPU Frequency literaly looks like its missfiring, its going from 5.4 to IDK what numbers are even those.
View attachment 210637
This looks more like something wrong with Windows itself in how it displays. You can download Sysinternals Process Explorer or HWInfo, or get a professional program like Process Lasso to check those frequencies with separate functions from Windows' own.
 
This looks more like something wrong with Windows itself in how it displays. You can download Sysinternals Process Explorer or HWInfo, or get a professional program like Process Lasso to check those frequencies with separate functions from Windows' own.
Ill check it out, I'll try to replicate the issue tomorrow and check with hwinfo or amd soft.
 
Update: MSI accepted my x870e Carbon board into their RMA service facility 2 days ago being I sent it in to address the pcie bug. Return date ETA is the 14th. Will keep everyone posted on how it goes.

On a side note, the Asus board I'm now running has had 0 issues since day 1 of installation. Again, only thing different is the motherboard. Same CPU, Memory, power supply, nvme drives etc.. and it all just works.
 
Update: MSI accepted my x870e Carbon board into their RMA service facility 2 days ago being I sent it in to address the pcie bug. Return date ETA is the 14th. Will keep everyone posted on how it goes.

On a side note, the Asus board I'm now running has had 0 issues since day 1 of installation. Again, only thing different is the motherboard. Same CPU, Memory, power supply, nvme drives etc.. and it all just works.
Good luck! And good for the ASUS board. For me, since everything works great without any issues, I really have no reason to change, although I’m annoyed at MSI for other reasons in this case. But if I start experiencing any issues with my Carbon, even just a twitch, it’s going straight to the garbage bin.
 
On a side note, the Asus board I'm now running has had 0 issues since day 1 of installation. Again, only thing different is the motherboard. Same CPU, Memory, power supply, nvme drives etc.. and it all just works.
I’ve also switched to the X870E Dark Hero. I reinstalled Windows right away, using the latest drivers and BIOS. Right now, I’m still working on setting up programs, testing settings, etc.
The bus clock is set to 99.8 MHz by default for me (HWinfo). I assume it works the same way as with GB, where Spread Spectrum on Auto means it’s enabled.

PCIe speed has been stable on every boot so far (2.5 GT/s – 32.0 GT/s). What I’ve noticed compared to the Carbon:

- The Dark Hero takes significantly longer to boot up and initialize devices. It's still totally fine, but maybe that was exactly the problem with Carbon (initialization too fast). That would at least explain why every reboot/ warm start never caused any issues.

- I've two monitors connected to the 5080. With the Carbon, the OLED always flickered very slightly in dark areas at first few minutes (gaming was always fine). With the Dark Hero, I don’t see any flickering.
 
I’ve also switched to the X870E Dark Hero. I reinstalled Windows right away, using the latest drivers and BIOS. Right now, I’m still working on setting up programs, testing settings, etc.
The bus clock is set to 99.8 MHz by default for me (HWinfo). I assume it works the same way as with GB, where Spread Spectrum on Auto means it’s enabled.

PCIe speed has been stable on every boot so far (2.5 GT/s – 32.0 GT/s). What I’ve noticed compared to the Carbon:

- The Dark Hero takes significantly longer to boot up and initialize devices. It's still totally fine, but maybe that was exactly the problem with Carbon (initialization too fast). That would at least explain why every reboot/ warm start never caused any issues.

- I've two monitors connected to the 5080. With the Carbon, the OLED always flickered very slightly in dark areas at first few minutes (gaming was always fine). With the Dark Hero, I don’t see any flickering.
The "significantly longer boot," especially during the first phase when you power on the PC, might be due to memory training that happens every time you start the system. Carbon has an option to memorize the last good training, which it can keep up to about 30 days if I'm not mistaking, making it seem like it boots faster. The Dark Hero also has an enhanced and larger 64mb BIOS compared to Carbon, which might also be part of the reason. 5080 flickering has nothing to do with motherboard its HW impossible to influence anything on the 5080 flickering wise or any other VGA that's VGA onboard components responsible for. If you said the onboard VGA on the the HERO has no flickering while the onboard on the Carbon has, I would say it may be possible due to HDMI components and circuits embedded on the motherboard. It is also possible to be is more on the OLED monitor side then VGA or Motherboard.
 
Last edited:
The Dark Hero also has an enhanced and larger 64mb BIOS compared to Carbon
Afaik, the 64MB BIOS chip is only for network drivers, or perhaps support for more CPUs (in future), etc. Right now, it’s more or less just marketing for the new X870E boards, cuz otherwise they offer almost no real value compared to "old" X870E boards.

5080 flickering has nothing to do with motherboard
It definitely does. Other users (HWL forum) and I can prove it. It's no surprise when the recovery count goes crazy (as described here) and the GPU can't work properly. Just a comparison of two different systems, both running X870(E) MSI Boards with RTX 5000 and 9000X3D CPU:

Display issues related to the cold boot-/PCIe-bug with X870 Tomahawk + 5070Ti (all hardware brand new, only Expo, rest stock):
GPU01.jpg

Display issues with my Carbon Wifi and new 5080:
1776023152596.png

Very similar error pattern. After a restart, everything always worked perfectly. This is definitely a motherboard issue related to the PCIe initialization of the hardware and not a GPU issue. If it were a GPU issue, there would also be problems after a reboot and/or under heavy load. However, these issues occurred ONLY from a cold boot.


If you said the onboard VGA on the the HERO has no flickering while the onboard on the Carbon has, I would say it may be possible due to HDMI components and circuits embedded on the motherboard. It is also possible to be is more on the OLED monitor side then VGA or Motherboard.
I really hoped that the MSI motherboard wasn't the cause of the problems. I tried different DP cables, I tried different HDMI cables, I tried using just one monitor (and a new one), I tested different refresh rates on both monitors, I tried several old and new BIOS versions, hundreds of BIOS settings, and so on and so forth. Absolutely nothing helped in the end.

The user on the HWL forum was smart. He saved a lot of time and just got a different (Asus) motherboard. With exactly the same hardware and exactly the same settings (only Expo, everything else stock), he had no GPU issues, display artifacts, etc. For a long time, I hoped that MSI would fix the problem, but it seems they’ll never do it, or maybe they just can’t (hardware related). Just a “small” selection, all of which have the same cause:

MSI forum (en) - X870E Godlike stutter/ very slow
MSI forum (en) - Carbon Wifi Beta BIOS (this thread)
MSI forum (en) - X870 Tomahawk Cold Boot Issues
MSI forum (en) - X670E ACE PCIe stuck issue
MSI forum (en) - X670E Tomahawk PCIe stuck issue
MSI forum (ger) - B850 Tomahawk massive latency issue
MSI forum (ger) - B650 Tomahawk cold start problem
IgorsLab - News about the BIOS update to address this issue
Hardwareluxx (ger) - PCIe and latency issues on MSI boards

and there are just as many Reddit posts on the topic.

The "significantly longer boot," especially during the first phase when you power on the PC, might be due to memory training that happens every time you start the system.
Significantly longer” is a bit misleading (from me). BIOS/ Boot time in task-manager says 16.4 sec. On my carbon it was 18.2 sec, but this it what windows measure. It's not the time from pressing PWR button to windows. I haven't measured it, but I'd guess that the Dark Hero does take 5 to 10 seconds longer than my Carbon. The initialization phase before the logo appears on the screen takes longer on the Asus. This is probably why it's more stable and reliable. (I'm talking about a cold boot and a reboot, not first boot.)

Edit, I measured it. It takes 24 seconds from pressing the power button to booting up in windows on the Dark Hero. The Carbon took about 20 seconds.
 
Last edited:
Ill check it out, I'll try to replicate the issue tomorrow and check with hwinfo or amd soft.
Soo i forgot about it, and today i noticed the issue is happening again without having done anything strange, antivirus on, secure boot, everything normal.

Also, i checked AMD soft, and there everything seems allright.
 

Attachments

  • 17760297588027681129690848322927.jpg
    17760297588027681129690848322927.jpg
    1.7 MB · Views: 37
  • 17760299814615945016597481654566.jpg
    17760299814615945016597481654566.jpg
    1.9 MB · Views: 32
Afaik, the 64MB BIOS chip is only for network drivers, or perhaps support for more CPUs (in future), etc. Right now, it’s more or less just marketing for the new X870E boards, cuz otherwise they offer almost no real value compared to "old" X870E boards.


It definitely does. Other users (HWL forum) and I can prove it. It's no surprise when the recovery count goes crazy (as described here) and the GPU can't work properly. Just a comparison of two different systems, both running X870(E) MSI Boards with RTX 5000 and 9000X3D CPU:

Display issues related to the cold boot-/PCIe-bug with X870 Tomahawk + 5070Ti (all hardware brand new, only Expo, rest stock):
View attachment 210704

Display issues with my Carbon Wifi and new 5080:
View attachment 210705

Very similar error pattern. After a restart, everything always worked perfectly. This is definitely a motherboard issue related to the PCIe initialization of the hardware and not a GPU issue. If it were a GPU issue, there would also be problems after a reboot and/or under heavy load. However, these issues occurred ONLY from a cold boot.



I really hoped that the MSI motherboard wasn't the cause of the problems. I tried different DP cables, I tried different HDMI cables, I tried using just one monitor (and a new one), I tested different refresh rates on both monitors, I tried several old and new BIOS versions, hundreds of BIOS settings, and so on and so forth. Absolutely nothing helped in the end.

The user on the HWL forum was smart. He saved a lot of time and just got a different (Asus) motherboard. With exactly the same hardware and exactly the same settings (only Expo, everything else stock), he had no GPU issues, display artifacts, etc. For a long time, I hoped that MSI would fix the problem, but it seems they’ll never do it, or maybe they just can’t (hardware related). Just a “small” selection, all of which have the same cause:

MSI forum (en) - X870E Godlike stutter/ very slow
MSI forum (en) - Carbon Wifi Beta BIOS (this thread)
MSI forum (en) - X870 Tomahawk Cold Boot Issues
MSI forum (en) - X670E ACE PCIe stuck issue
MSI forum (en) - X670E Tomahawk PCIe stuck issue
MSI forum (ger) - B850 Tomahawk massive latency issue
MSI forum (ger) - B650 Tomahawk cold start problem
IgorsLab - News about the BIOS update to address this issue
Hardwareluxx (ger) - PCIe and latency issues on MSI boards

and there are just as many Reddit posts on the topic.


Significantly longer” is a bit misleading (from me). BIOS/ Boot time in task-manager says 16.4 sec. On my carbon it was 18.2 sec, but this it what windows measure. It's not the time from pressing PWR button to windows. I haven't measured it, but I'd guess that the Dark Hero does take 5 to 10 seconds longer than my Carbon. The initialization phase before the logo appears on the screen takes longer on the Asus. This is probably why it's more stable and reliable. (I'm talking about a cold boot and a reboot, not first boot.)
Just wondering, have you connected the additional PCIe power support? I’ve always had mine plugged in and have never experienced any issues like that.
5090 liquid SOC on Alienware QD Oled AW3423DW
Screenshot 2026-04-13 092650.png
 
With an 8-pin PCIe power connector.


but many other people have. Not the graphics errors, but the whole situation with MSI motherboards and the PCIe/cold boot issue.
Simply put, it seems that MSI’s hardware quality has totally declined. They clearly don’t care about quality control, often refusing RMAs, which means they have no material to learn from or troubleshoot. Maybe they don’t even have dedicated professionals, relying instead on some third-party services for QC. It feels like these so-called “wise managers” have run MSI into the ground compared to what it once was. Unfortunately, MSI isn’t alone ASUS and most others follow the same concept: sell at high prices, refuse RMAs, blame customers for everything, and push out junk without facing proper legal repercussions.
Everything feels like a lottery these days, you might end up doing great with no problems at all, or you might end up like so many others facing never-ending issues.
 
I have not plugged additional pci power connector, and my system working perfectly well.
With my 4080, I didn't use the PCIe power connector either, and everything worked perfectly. The problems only started when I switched to the 5080 (PCIe 5.0). To find the cause, I tried everything (as I said, different cables, monitors, BIOS versions, BIOS settings, etc.). The PCIe power connector was one of the first things I tried. It makes no difference whether it's connected or not.

I am restarting my PC once a month after 30 days of uptime, no crashes, bluscreens etc.
Then be happy that your carbon is working properly. Many people (as mentioned in the links), including some here in this thread and myself, aren’t so lucky. It’s also questionable how many people actually check their PCIe speed regularly (I always have HWinfo running). You won’t be able to notice a performance difference between PCIe 4.0 (16 GT/s) and PCIe 5.0 (32 GT/s) right away. It's also hard to tell the difference between X8 and X16 in everyday use. But the point is, I expect a motherboard that works properly and doesn't throttle down to PCIe 4.0 or slower.
 
Back
Top