Having constant issues with MAG B550M Mortar

[antonin]

I've just completed a brand new build with MAG B550M Mortar and I'm having constant issues with the motherboard (many of these mirrored on reddit and other places). Would love to hear if anyone has any pointers on how to resolve these:

• the LAN controller stops responding and crashes. It either doesn't show up as a device altogether or it'll show up as working fine but "unplugged". Yes, I've tried multiple cables on different machines.

• USBs will stop working properly. Either they'll unplug all devices, or they'll misbehave. I stopped using LAN and started using a wifi adapter for the time being -- and it'll register as being plugged in but be unable to locate any network. This is a wifi adapter I've used every day and works on other machines

I've updated and installed all of the drivers available on the support page -- and eventually I also upgraded the BIOS to the newest version but none of it helped. The Dragon Center will straight up cause a blue screen, by the way.

The full build:
[list type=decimal]
[*]MSI MAG B550M MORTAR Micro ATX AM4 Motherboard
[*]AMD Ryzen 5 3600 3.6 GHz
[*]AMD Radeon RX 570
[*]Team T-FORCE VULCAN TUF Gaming Allian 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory
[*]Cooler Master MasterWatt 750 W 80+ Bronze Certified Semi-modular ATX Power Supply
[/list]

All benchmarks and tests pass for the GPU (even in a separate build), CPU, and RAM.

 

[Svet]

About the LAN issue,
have you tried using different router?

I've updated and installed all of the drivers available on the support page -- and eventually I also upgraded the BIOS to the newest version but none of it helped. The Dragon Center will straight up cause a blue screen, by the way.

Which BIOS version exactly? And Dragon Center version?
BSOD error code number is...?

 

[antonin]

Bios version: 7C94v118(Beta version) (had the LAN/USB issue with the non-beta version as well)
Dragon Center version: 2.0.54.0

I'm not sure how to retrieve the BSOD code (the dump fails to be created). The Event Viewer in Windows shows several events occur before the unexpected shutdown and before the dump failure. They're all "AppModel-Runtime" errors:

• 0x80073CFC: Cannot create the process for package 9426MICRO-STARINTENATION.DragonCenter_2.0.54.0_x64_kzh8wxbdkxb8p because an error was encounter while launching. [Launch Process]
• Deployment server integrity check of package 3489660990 failed with 9426MICRO-STARINTENATION.DragonCenter_2.0.54.0_x64_kzh8wxbdkxb8p
• App Integrity check failed with 3489660990 while checking 9426MICRO-STARINTENATION.DragonCenter_2.0.54.0_x64_kzh8wxbdkxb8p.
• Failed to terminate app with package 9426MICRO-STARINTENATION.DragonCenter_2.0.54.0_x64_kzh8wxbdkxb8p.

I'll also add that the machine sometimes gets stuck in a boot loop (after a BSOD or that LAN/USB dropping) and then it shows the motherboard screen asking if I want to use the boot menu, or get into the BIOS, and some other option. None of the options are selectable and the keyboard doesn't work (tested the keyboard on other machines and works fine).

I'm not as concerned about the BSOD (I can just not use DragonCenter), I"m more concerned about the LAN/USB issues

 

[antonin]

I don't have extra routers laying around. I've used this router without an issue with 5-6 different devices for months including PCs with other MSI boards.

 

[Svet]

Then try bypass the router and connect directly this computer to ISP.
Other than this is to try firmware update for the router, or changing LAN port or reset router settings to default.

I'm not sure how to retrieve the BSOD code (the dump fails to be created). The Event Viewer in Windows shows several events occur before the unexpected shutdown and before the dump failure. They're all "AppModel-Runtime" errors:

Scroll down more and look for Source as "BugCheck"

 

[antonin]

Then try bypass the router and connect directly this computer to ISP.
Other than this is to try firmware update for the router, or changing LAN port or reset router settings to default.



Scroll down more and look for Source as "BugCheck"

Ok, tried to directly connect after the network on the PC dropped (but worked for all my other devices), doesn't work. The cable is fine (tested it with the router and with my other computer). I tried using Windows diagnostic tools and the LAN controller gets disabled...and is unable to re-enable itself. I checked Event Viewer in case it had more info but it doesn't.

There's no "BugCheck" source. There's only the "volmgr" error which states that "dump file creation failed due to error during dump creation". I see the blue screen for half a second before i get a black screen and nothing else.

 

[jens.glathe]

Bios version: 7C94v118(Beta version) (had the LAN/USB issue with the non-beta version as well)

This beta BIOS is a b*tch. Had some really strange issues with it, reverted to 1.11 when it came out, seems to be more stable. Not issue-free, though. Mine are:
- after doing the weekly backup with macrium, then trying to mount a new CPU cooler (had to remove/refit the CPU), the BIOS says it has to revert to default settings. Strange, but sort of fair enough.
- as a result I lost my 2.5G cable connection (code 10). Also, an additional network card (Intel CT Desktop Adapter) fails to get it working. Had to revert to a USB GbE adapter (and some safemode digging). Not nice. And really annoying. I now have three ethernet adapters on this machine, and only one is working. All three have no issue at all on linux, same hardware, same BIOS.
- The USB2 ports are sort of fishy with some mice/keyboards. Switched these to USB3 to avoi.
- it was not the backup. Restored from backup (2 hours, sheeesh), same behaviour.
This doesn't really add trust to this M/B. I also have two other machines with MSI X570 (Unify and Tomahawk), both run flawlessly in contrast. And yes, I give them something to do Seems that another BIOS Update is in order. And it has something to do with the UEFI code.

 

[jens.glathe]

Okay, an update on the networking issues: hands off that strange PCI over 4G address space/ crypto setting. Linux actully doesn't seem to care, and Windows 10 appears to have an issue with it. Leave it off, and the network interfaces will be recognized and work again. Go figure.