Any suggestions?  Any chance of the 4.43 Beta BIOS fixing this?

It's probably worth mentioning I've seen other reports of the exact same error in the exact same situation.

Having the same exact issue... with that board and my spare Asrock X370 Killer. Hopefully a fix pops up somewhere. Hopefully someone will point us in the right direction.

MisterJ wrote: XavierMace, I have an X399, so am an observer on all these X370 and AB350 problems with the BIOS/UEFI updates.  It looks like to me that ASRock has turned loose a batch of bad UEFI updates.  So you have a choice to make:  go back to before the problems began or flash to the latest, maybe Beta, Bios and hope for the best.  Lots of users seem to be having good luck with the Beta. Concerning Drivers:  Get your chip set drivers here:  https://support.amd.com/en-us/download" rel="nofollow - https://support.amd.com/en-us/download Get other drivers from the manufacturer such as Intel and Realtek NOT from the from the ASRock DL page except in rare cases (eg, RAID) - they are almost always old.  Enjoy, John.

Unfortunately 4.40 is the oldest BIOS to support the new chips.  I'm also familiar with where/how to download drivers.  You'll note I mentioned twice already that I've tried multiple drivers.

I'll try the 4.43 tomorrow but I'm not going to hold my breath.  I'd love to know if yours BSOD's if you start using the wireless as I'm curious how consistent this issue is.

No problem. I'll give it a try and report back. Is there anything I should do to try to provoke it, like copying a batch of large files over the network?

For me, any sustained usage will do it.  Netflix, Steam, SMB file transfers.

Driver Provider: Intel

Driver Date: 10/01/2018

Driver Version: 19.51.11.2

There is a Minidump folder - I had to grant access to open it - but it's empty.

System is a 2400G on an ASRock AB350 Gaming-ITX/ac board with the 4.43beta BIOS installed. Everything else appears to be rock solid. I don't think it's a contributing issue, but I'll be running MemTest86 for several hours this afternoon to make sure the RAM checks out.

https://www.dropbox.com/s/ee0qff8awfmbxf8/022618-3687-01.zip%3cdl=0" rel="nofollow - Minidump Dropbox Link

Thanks for taking a look. I opened a ticket with ASRock after making the post earlier and included the same link, so hopefully that helps. MemTest86 showed no signs of RAM issues, as expected. In the interest of completeness, here are the drivers I installed:

https://support.amd.com/en-us/download/chipset%3cos=Windows%2010%20-%2064#" rel="nofollow - AMD Chipset Driver

https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-for-Ryzen-Desktop-Processors-with-Radeon-Vega-Graphics-Release-Notes.aspx" rel="nofollow - AMD Radeon Drivers for Desktop APU w/ Vega Graphics

https://downloadcenter.intel.com/download/27475/Wireless-Intel-PROSet-Wireless-Software-and-Drivers-for-Windows-10%3cproduct=94854" rel="nofollow - Intel Dual Band Wireless-AC 3168

https://downloadcenter.intel.com/download/25016/Ethernet-Intel-Network-Adapter-Driver-for-Windows-10%3cproduct=64403" rel="nofollow - Intel Ethernet I211-AT

https://downloadcenter.intel.com/download/27493/Wireless-Intel-Wireless-Bluetooth-for-Windows-10%3cproduct=94854" rel="nofollow - Intel Wireless Bluetooth

https://www.asrock.com/MB/AMD/Fatal1ty%20AB350%20Gaming-ITXac/index.asp#Download" rel="nofollow - Realtek Audio Driver from ASRock v.8067

Hope it helps, and I echo MisterJ's suggestion that others in this thread open a support ticket with ASRock to get this issue resolved. It's the one issue I'm having in an otherwise lovely new build.

Oops, I didn't realize that the forum breaks links. I obtained all of my drivers directly from AMD (chipset & Radeon) and Intel (ethernet, WiFi, & Bluetooth), with the exception of the Realtek audio drivers. Realtek's website was not very helpful, and I could not find drivers for the onboard audio there. I decided to use ASRock's drivers for audio.

I am currently at work, but I will posts screenshot of the window listing the chipset drivers when I get home about 10 hours from now. Thank you for your assistance!

I had the same BSOD issue when downloading Windows Updates over WiFi after my initial clean install, which was an outdated pre-1709 version of Windows 10. I had not yet installed any drivers at that point and was using the Windows 10 provided WiFi driver. Granted, that was with an outdated version of Windows 10, so it's not ideal, but I can say that I had the same issue with the Windows WiFi driver. It was at that point that I decided to start over with a clean install of the latest Windows 10 version, but the WiFi problem remained.

I will do the further testing as you suggest to help narrow down the issue and report back. Thanks again!

As requested:

Yes we have.  Everyone having issues is running Raven Ridge and it's the WiFi causing the problem.  I appreciate that you're trying to help, but you're now just having people try random things for giggles.  There's only two BIOS options for us.  4.40 and the 4.43 Beta, both of which have the same issue.  I've already started the RMA for my board, I'll replace it with a Gigabyte since WiFi actually works on theirs with Raven Ridge.

Is that indeed the case, meaning that if you were to use a Summit Ridge CPU the WiFi problem would not be present?

I don't think Raven Ridge is the problem in and of itself.  But Raven Ridge prevents us from using an older BIOS.  Since I didn't feel like playing musical chairs with CPU's, I opted to go the RMA route and get a board that doesn't seem to have this problem.  Which is a pity, as I generally prefer Asrock.

For me the choice was between the ASRock and Gigabyte ITX boards, too, with the Asus ones being non-starters for Raven Ridge APUs. I chose ASRock because of the better VRM cooling and because the layout of the headers better suited my case. I don't use the WiFi (but that's no excuse for it not working) but I'm disappointed that there's no USB 3.1 Gen 2 - though that appears to be common to all ASRock B350 boards. There may be exceptions but I don't know of them.

Patience is a hard thing, but luckily this isn't my primary machine.

The BIOS seems to be the only reasonable option.  The Gigabyte board is using a nearly identical WiFi setup.  Intel PCIe M.2 module, they're just using the older 3165 instead of the 3168.  But both are extremely common modules.  If there was an issue with the Intel or Microsoft drivers or the cards themselves, you'd be hearing about it else where.

I prefer the layout of the headers on the Asrock too as well as having a brand preference for Asrock.  But not enough to sit around hoping for a quick BIOS update.  Without WiFi the board is useless for me.  The Gigabyte board is cheaper and has USB 3.1 Gen 2 as well as functioning WiFi.

You can turn it off in the BIOS or you can disable it in Windows.

I sure hope so. I haven't heard back on my ticket with ASrock yet. Using a USB wifi adapter until we have an update.

I have the same problem as everyone else in this thread.  BSOD with the AB350 gaming itx/ac with a ryzen 5 2400g, likely caused by the wifi.  I've tried bios v4.43 updates, wifi driver updates, memory testing, prime95 testing, everything.  I even bought a brand new board, hoping that the replacement board would not have this problem.  Well, it is a problem.  

Do they even acknowledge they have a problem here?!  This is really frustrating... 

There is a simple work-round to get you up and running: use the cabled Ethernet. It works so much better than WiFi ever will.

Use the latest drivers directly from intel, not the outdated ones on the ASRock's motherboard download support site:

https://downloadcenter.intel.com/product/72252/Intel-PROSet-Wireless-Software" rel="nofollow - https://downloadcenter.intel.com/product/72252/Intel-PROSet-Wireless-Software

Confirm what?

No. I can't confirm that. It seems it might be slightly better for some people and there's one report of stability with one particular Windows version used with one particular driver version but in general people are still unhappy with it.

For me, the new bios help but the problem is still there.  I can usually get away with watching a little youtube also.   

Try something that will stress data transfers over wifi, like downloading large files for a few hours.  If that doesn't work, I would try going back to 4.4 to see if you can recreate the problem then.  Many of us still have the problem in 4.5.

I have two boards that I bought from newegg.com that both have the issue.  I haven't returned either of them yet.  If ASRock truly cannot recreate the problem and is willing to reimburse me for the purchase and pay for shipping, I can send you my one of mine.  

No. Until the bridge BIOS has been installed you don't have the option of installing 4.40 or later even if they are present on your USB stick.

Dear XavierMace,

Greetings, this is ASRock TSD.

Regarding your question, we had already fixed on BIOS L4.51A

Please download BIOS from below link and then update it to verify again. 

http://www.asrock.com/MB/AMD/Fatal1ty%20AB350%20Gaming-ITXac/index.asp#BIOS" rel="nofollow - http://www.asrock.com/MB/AMD/Fatal1ty%20AB350%20Gaming-ITXac/index.asp#BIOS

How to Update:

http://www.asrock.com/support/BIOSIG.asp%3Fcat=BIOS8" rel="nofollow - http://www.asrock.com/support/BIOSIG.asp?cat=BIOS8

Thanks!

All the best,

ASRock TSD

I'll be updating once I get home; will post after I do it!

I have an AB350 ITX board with the Ryzen 2400G APU.

Try this:

Did you install the Radeon driver after the AMD chipset driver? Get both from AMD, rather than ASRock.

Thanks, I tried it. Given that it went from working (mostly w/o wifi) to not even powering anything beyond the fans after the bios update; I suspect the update killed it. I also tried putting in AMD's bootkit processor they sent me, nothing.... when I took the old one out it was cool, so no power, board is dead.

I was trying to, but honestly I was getting confused by their installation files.  

The file from the chipset driver's page is called: amd-chipset-drivers_18.10_feb.exe

The file from the video driver's page is called: rv-win10-64bit-whql-radeon-software-17.40.3701-feb12.exe

There appears to be numerous drivers in both installation packages, and many of them overlap but not all of them.  If I install the chipset drivers first (v18.10), and then I try to install the video drivers (v17.40), I get an error saying the later version is already installed.  I don't understand this...I didn't install the video package yet, and I believe there are drivers in there that aren't installed yet.  

Then, to complicate the matter, there is a different installation package called: radeon-software-adrenalin-18.2.3-minimalsetup-180222_web.exe

I figure that I might be able to use this somehow to get around this issue, but that isn't exactly clear either.  

What I think I ended up doing was uninstalling all them, and putting 17.4 in first, and then putting 18.10 in on top of that.  But I suppose this is installing the video drivers before the chipset drivers?

What did you do, and how did you get around this issue?

Once those are installed, order is not that critical. This is because the chipset drivers facilitate the correct identification of components and help prevent conflicts. 

Just to be clear, you are not using the onboard wifi, you are using a dedicated wifi adapter, correct?  Why not just use the onboard wifi?  

I don't know if the recent ab350 itx/ac motherboard wifi issue was a problem for ALL wifi devices, or just the onboard wifi.  It's possible that ASRock didn't anticipate people using other wifi devices when they came out with the wifi fix in 4.51.  

Or it could be that there is some kind of conflict between the two cards.  I would try using the onboard wifi and the dedicated wifi independently. Try disabling the onboard wifi and only using the dedicated card.  Verify the onboard wifi works without the wifi card installed. This would at least give you some more information.