MPG X870E CARBON WIFI Beta BIOS

Svet

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

>>> E7E49AMSI.1A99 <<<
 
Last edited by a moderator:
While my Titanium 7200 works nicely with 6400/2200 and no BSOD or errors during a 30-minute run of AIDA stress test CPU+FPU or OCCT, I can't get it to work on 8000 at all. Sometimes it will go into Windows, but a restart or shutdown and power on ends up with a black screen and a distinctive memory not recognized beep. I have the buzzer on my board.
Hah, I couldn't get my actual Titanium 8000 to work properly at XMP, though again, that was with a pretty early BIOS. It would boot and LOOK stable, but almost instantly fail testing any time I put stress on the FPU/memory. Rolling it back to 7200 was stable, but the latency cost was too high running it at that level.
 
Realtek PCIE Network Drivers 10.73.815.2024

A4 is definitely the most stable bios. :biggthumbsup:
10.73 were some rough drivers that caused stuttering in a LOT of builds - to the point we were recommending folks roll back to 10.72 or get the 10.74 directly from Realtek. Though it looks like MSI has finally updated the drivers on the support page to 10.74 as well.

Even if they weren't using the network card and were just using wireless, the 10.73 drivers were causing game stuttering. Maybe they've managed to fix that with the newer BIOSes, but since they've posted it to the official support page, no reason not to upgrade. Might also grab the newer Audio drivers if you haven't yet as well, since those are all going through the USB controller.
 
They've made absolutely massive improvements in memory stability between 1A1 and 1A4. I would definitely upgrade.
Many of the BIOS upgrades have had trouble POSTing after the upgrade, make sure to do a BIOS RESET flash after you've upgraded and it's rebooted. Also, some of the BIOS updates in the meantime have an absolutely brutal memory training time, upwards of 7 minutes. After the upgrade, wait for it to restart and give it some time to make sure the BIOS update has finished, then shut down and do a full 20 second BIOS reset by holding the button on the back of the motherboard with the power supply switched off. This has solved a lot of BIOS upgrade problems for me with this board, specifically.
If you get to code 15, that's training the RAM. Give it 10 minutes before giving up. It may take a while, then turn on Memory Context Restore in the BIOS once you get in.
With memory that tight of timing, it may take even longer to train, or may not do so at all at XMP settings - the IMC on these 9800x3ds seems to be very finicky. You may need to manually tune the RAM to run it outside of JDEC.
As for the EOL - I've heard g.skill has had a significantly difficult time binning those chips in enough quantity to meet demand and may be dropping the CL26 memory production for the time being, and once the supply runs out, there won't be any more for a while.
Firstly, thank you so much for the extensive reply.

I have upgraded to 1A4… on the first try… did not clear CMOS.. re-did the RAM and CPU overclock, even went -10 over -5 curve all cores… Seems to have really juiced my frame rate in star citizen. I haven't gone below 100FPS hanging around 130-161fps…. Which is insane at 5k2k. I did notice I am now hitting 5.4 ~ instead of 5.5 ghz max. X10 scalar 200mhz, must have been a glitch on the old 1A1?

I hope its a availability problem with the CL26 and not something else, Reason for going to CL26 over CL30 was to bolster the 1% and 0.1% lows on FPS in silly games like StarCitizen. ( all sorts of stuff on forums about how 9800X3d wont benefit from CL25 over CL30 )
 
Just throwing this out as a suggestion if anyone from MSI is reading this and since we're barrelling through BIOS updates anyway; Would it be an idea to label the two "Onboard LAN Controller" appropriately? Which one is the 2.5GbE and which one is the 5GbE, right now they just have an identical name;

2.jpg
 
Those are some good numbers, but Cinebench isn't really a stability test, it's a raw performance test. Good way to warm up the CPU and see your temperature curves for sure. What scalar are you running with (if you manually set it)?

If you can run AIDA64 Burn-in with CPU, FPU, cache, and System Memory all being tested for 15-20m, you've probably got your settings stable enough for 99% of any gaming or workload. If not, I'd dial the CO back by 5 or so. Playing with the curve shaper can also help stabilize a system at higher load, but @vic123159d02e5 is more knowledgeable on that than I am.

Looking at your ZenTimings screenshot and Aida64 numbers, you might be able to cut your latency significantly by lowering your tRFC to 500 and raising your tREFI to 50000, just for some easy settings. Even the EXPO/XMP timings on those two settings are generally WAY looser than they need to be, particularly since those are Hynix A-die so far as I'm aware. You're not running the CPU in Hypervisor mode (according to your AIDA screenshot) so you should be getting ~60ns timings. thought with the IMC on the 9950x3d there might be differences from the 9800x3d that I'm not aware of. Guess I better learn fast since I have a 9950x3d coming Friday...

Thanks for the advice! I went ahead and ran the AIDA System Stability test for 25 minutes, and everything went smoothly!
I think the system is more stable now. :beerchug:
 

Attachments

  • stabilitytest.png
    stabilitytest.png
    120.3 KB · Views: 98
what are you doing for the OC besides CO - All Core -25?
Are you using PBO - Scalar X10 / BCO+ 200mhz... looks like your messing with the multiplier ?
I did these settings:
CO All Cores -30
PBO Limits= Mobo, Scalar x10, and Boost Clock O. +200 Mhz
 

Attachments

  • Screenshot 2025-05-28 223233.png
    Screenshot 2025-05-28 223233.png
    798.2 KB · Views: 101
I had problems listening to music. A lot of hissing from the speakers. Sold the old assembly and took a new board immediately rolling a4. Does anyone have problems with rtl 4080 and hissing? I want to understand whether to do rma or bios problems. On the previous assembly with the same 870 carbon this did not happen. I listen to music in apple music
 
I had problems listening to music. A lot of hissing from the speakers. Sold the old assembly and took a new board immediately rolling a4. Does anyone have problems with rtl 4080 and hissing? I want to understand whether to do rma or bios problems. On the previous assembly with the same 870 carbon this did not happen. I listen to music in apple music
On A1 NOV, I was getting hissing audio randomly 1 / 20 boots, rebooting fixed it. Now fresh on A40 today, 6 reboots no hissing audio
 
На A1 NOV я получал шипящий звук случайным образом 1 / 20 загрузки, перезагрузка исправила это. Сейчас свежий на A40 сегодня, 6 перезагрузок нет шипящего звука
Before a40 I never had problems on the previous same board. Looks like I need to do rma
@Svet Maybe you've heard from someone else about this problem?
P.S
Of course I reinstalled the chipset drivers, uad and nvidia. The only thing I can do is ask the guy I sold the old PC to update to a4 to see if he has any problems. There were never any problems with hissing on that board. This is not analog interference, but hissing from something.
It looks like there are problems with the codec on the board. But I don't want to do rma because the window is already over and I'll have to wait a long time
 
Last edited:
Firstly, thank you so much for the extensive reply.

I have upgraded to 1A4… on the first try… did not clear CMOS.. re-did the RAM and CPU overclock, even went -10 over -5 curve all cores… Seems to have really juiced my frame rate in star citizen. I haven't gone below 100FPS hanging around 130-161fps…. Which is insane at 5k2k. I did notice I am now hitting 5.4 ~ instead of 5.5 ghz max. X10 scalar 200mhz, must have been a glitch on the old 1A1?

I hope its a availability problem with the CL26 and not something else, Reason for going to CL26 over CL30 was to bolster the 1% and 0.1% lows on FPS in silly games like StarCitizen. ( all sorts of stuff on forums about how 9800X3d wont benefit from CL25 over CL30 )
Glad to hear! There were definitely some glitches in the 1A1 release, so really nice to hear that you've seen performance and stability improvements. That being said, it's still a good idea to flush out any old configs in the BIOS by doing a full reset (or at least "load bios defaults", save, and restart), whenever you do a BIOS flash. They may have fixed that in the meantime so it does a reset during flash, do you remember if you were prompted when you restarted after the flash that the BIOS has been reset (something like: Hit F1 to load defaults, etc)? I haven't upgraded to A4 yet, that'll be this weekend with the 9950x3d install...
And yeah, that's definitely about the only reason to go with lower CL right now, the lower latency helps a tiny bit with your 1% and .1% lows. It's a lot of money to spend but sometimes those nanoseconds mean all the difference. :-)
Star Citizen has taken so long to get to a playable state that I've kind of moved on from space sims. I'm an original kickstarter backer because of Chris Roberts' name, but really haven't kept up on it despite all of the great looking visuals and cinematics for Squadron 42.
 
Before a40 I never had problems on the previous same board. Looks like I need to do rma
@Svet Maybe you've heard from someone else about this problem?
P.S
Of course I reinstalled the chipset drivers, uad and nvidia. The only thing I can do is ask the guy I sold the old PC to update to a4 to see if he has any problems. There were never any problems with hissing on that board. This is not analog interference, but hissing from something.
It looks like there are problems with the codec on the board. But I don't want to do rma because the window is already over and I'll have to wait a long time
When you updated the UAD, did you grab the newest audio and network drivers on the carbon wifi support page, April 7 (for audio) and May 9 (for network)? I haven't had any audio issues since then. Just a thought. Since it's going through the USB system with a lot of other stuff there's plenty of opportunity to get interfered with.
 
Glad to hear! There were definitely some glitches in the 1A1 release, so really nice to hear that you've seen performance and stability improvements. That being said, it's still a good idea to flush out any old configs in the BIOS by doing a full reset (or at least "load bios defaults", save, and restart), whenever you do a BIOS flash. They may have fixed that in the meantime so it does a reset during flash, do you remember if you were prompted when you restarted after the flash that the BIOS has been reset (something like: Hit F1 to load defaults, etc)? I haven't upgraded to A4 yet, that'll be this weekend with the 9950x3d install...
And yeah, that's definitely about the only reason to go with lower CL right now, the lower latency helps a tiny bit with your 1% and .1% lows. It's a lot of money to spend but sometimes those nanoseconds mean all the difference. :-)
Star Citizen has taken so long to get to a playable state that I've kind of moved on from space sims. I'm an original kickstarter backer because of Chris Roberts' name, but really haven't kept up on it despite all of the great looking visuals and cinematics for Squadron 42.
The last patch and upcoming one have been bangers. 600 player servers, captial ships are flying around. Sub cap destroyer coming out later this year. At 5k2k it’s super playable. Comes down to bugs… which going back 1 - 3 - 5 -7 years. It’s inching its way
 
Just throwing this out as a suggestion if anyone from MSI is reading this and since we're barrelling through BIOS updates anyway; Would it be an idea to label the two "Onboard LAN Controller" appropriately? Which one is the 2.5GbE and which one is the 5GbE, right now they just have an identical name;

View attachment 202466
The upper port is 2.5G, while the lower port on the board is 5G. This is consistent with the BIOS, where the upper controller is 2.5G and the lower one is 5 G. I agree that labeling these ports would make quick identification easier. .
 
Back
Top