Just FYI, there are a lot of comments on Reddit about your ASRock MOBO & CPU combination suffering from high CPU failure rates:
https://www.reddit.com/r/ASRock/comments/1kodcsa/another_dead_9800x3d_b850m_steel_legend_wifi/
2 Likes
I know about that issue, it’s why I keep my BIOS Version as up to date as possible. I just saw that I have an ‘old’ version 3.50 installed, and there is a ‘new’ 3.50 online.
Guess I’ll install that one today, once I get home.
Too bad I didn’t know it when I bought the mainboard, but I’m not switching now, as long as it works.
I’ll reset to default, update, load defaults in BIOS once I’m home.
That is too vague for me to act upon. Any tipps, where I find which settings to set how?
As mentioned above, the hangup persists even if nothing but power and monitors are connected, even without the internal front-IO USBs.
Thanks. Thats concrete help. After updating BIOS and loading defaults I’ll try it with disabled IOMMU. But maybe the update already fixes things.
My PC also takes quite some time to boot when I previously did not unplug my external seagateUSB HDD. I noticed simply unplugging it reduces the time significantly. Most of my inxi’s posted in this forum since I enabled hibernate are when it is plugged in.
A web search will return quite a few different recommendations.
For best results use search terms such as:
- very slow boot ASRock “B850M” Steel Legend WiFi Arch Linux
- very long boot time “asrock b850m steel legend wifi” Arch Linux
- slow boot “asrock motherboard” Linux
- bios settings to correct slow boot “asrock motherboard” Linux
Some search result examples:
Long boot time after changes in BIOS depending on RAM size result from enable Memory Context Restore - memory training (minutes, details see manual), Long boot time without touching BIOS: check “Memory Context Restore” setting, for BIOS up to 3.20 in “OC Tweaker”, for BIOS 3.25 in Advanced → AMD CBS → DDR Options → DDR Memory Features.
Disable “Instant Boot”
If you have “Instant Boot” enabled, it can cause issues.
Disable it from the main ASRock Instant Boot menu by selecting “Disable Instant Boot” and applying the changes.
disable the Compatibility Support Module (CSM)
- EXPO enabled at 6000 CL30 using Silicon Power RAM. (SK Hynix, I forget which die)
- PBO has never been enabled. I hear so many horror stories I’m concerned to turn it on. I’d go for undervolting more than overclocking with it
Perform a hard reset:
Turn off the computer completely.
Remove all devices connected to pc except for Keyboard, Mouse, Monitor.
Disconnect the power cord.
Press and hold the power button for 30 seconds to drain any residual power.
Reattach power cord and try booting again
Perform thorough testing on your RAM, check the storage drive’s health as well.
Search around and you’ll find lots of bios setting suggestions.
4 Likes
I remember when I was shopping for a overclocker’s inexpensive mobo 13 yrs ago, I had considered Asrock because it was cheaper than other brands offering greater features and more diversity. I came across posts in overclocker forums that faulted Asrock alot (RAM issues, BIOS flashing errors, and general boot failures). An example I remember was this (ASRock P67 Extreme4 Gen3 Error HELP | Overclock.net). I think from then unitl now Asrock has had a challenge when it comes to mobos. For that reason I went with Asus which helped me get higher overclocks than Gigabyte did. The Asus board is what I use to date still very reliable even with overclocks.
Every brand will have its issues, I’m currently typing this from a computer with a Asrock X570 Taichi Razer board and ive put it through hell and back and it just keeps asking for more.
Also having worked in the PC hardware industry - not just your mom and pops pc shop, but a actual PC company that made industrial equipment. We went through and used every brand as the application fit.
Also FYI, Asrock came from ASUS
That’s the reason I’m asking what @nepti meant. There are so many options and opinions flying around, and if I change the wrong settings, I’ll get another reply like:
Wow, I see you marked my suggestion for boot parameters below as the solution:
I’m rather stunned to be honest, because not one post online that I read contained those suggestions. The advantage of being older is that problems from 15 years ago often tend to repeat themselves and what was old becomes new again.
If you want to use virtualization technologies you likely won’t want to disable iommu. There are a pair of different parameters that may work for you if you need to use VM’s. I don’t recall them off the top of my head, but I can post them for you after I get home and get a chance to check my old notes.
Anyways, I’m glad that suggestion helped. Proves once again that persistence pays off. Good for you for sticking with it. 
Edited to add further info:
You can try the amd_iommu=on iommu=pt boot parameters together if you want to retain the option to use virtualization technologies.
You will need to use this method if you want to run a Virtual Machine.
When using the amd_iommu=on iommu=pt boot parameters together it is best to leave iommu enabled in the bios.
Alternately, you can use the iommu=soft boot parameter if you have no need for virtualization technologies.
When using the iommu=soft boot parameter it is best to leave the iommu option disabled in the bios.
2 Likes
I had to delete the last post on this thread as it was flagged for inappropriate comments. As this thread has been solved, this thread has run its course and will now be put to bed.
To the new user whose post I had to remove; in the future please keep your comments on topic, and never post personal attacks other forum members. Posts such as your last, are not welcome on the Garuda forum. Please do not repeat this behavior.
8 Likes