ASRock.com Homepage
Forum Home Forum Home > Technical Support > AMD Motherboards
  New Posts New Posts RSS Feed - AB350 Gaming-ITX/ac issue
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

AB350 Gaming-ITX/ac issue

 Post Reply Post Reply Page  12>
Author
Message Reverse Sort Order
Raephen View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Mar 2018
Location: The NL
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote Raephen Quote  Post ReplyReply Direct Link To This Post Topic: AB350 Gaming-ITX/ac issue
    Posted: 12 Mar 2018 at 8:14pm
Originally posted by cubebucket cubebucket wrote:

 I'm having similar issues with the display drivers. I'll try to do what you did...

I hope my messing about with my new system can be of help to you. Keep us posted!
Back to Top
Xaltar View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 16 May 2015
Location: Europe
Status: Offline
Points: 24713
Post Options Post Options   Thanks (0) Thanks(0)   Quote Xaltar Quote  Post ReplyReply Direct Link To This Post Posted: 12 Mar 2018 at 5:05pm
There was a recent BIOS update that fixed an issue with Wifi enabled boards. It is possible the 2 issues were related (wifi causing conflicts).

Either way, glad to see you have it up and running, enjoy your new build Thumbs Up
Back to Top
cubebucket View Drop Down
Newbie
Newbie


Joined: 06 Mar 2018
Status: Offline
Points: 50
Post Options Post Options   Thanks (0) Thanks(0)   Quote cubebucket Quote  Post ReplyReply Direct Link To This Post Posted: 12 Mar 2018 at 5:00pm
Originally posted by Raephen Raephen wrote:

[URL=][/URL]I am happy to report: my issue has been fixed!

While I can't put my finger on what exactly did the trick, I'll list the 3 consecutive? steps I took.

First off, I flashed my UEFI to v4.50.?

Secondly, I cloned my OS drive from the Plextor M6e in it's m.2->PCIe adapter to my Crucial MX300 in the native m.2 slot. Rebooted and set the boot order to load from the MX300 (and removed the M6e from the boot order completely) to test it. Succes, so I powered down and removed the Plextor from the system.

And the third step was to reinstall the chipset-drivers for good measure (+reboot after that) and Google how to boot into safe mode under Windows 10 (last time I've ever had to use safe mode was under W7, so a while back...). In safe mode, I ran DDU, which removed the Microsoft default display drivers and blocked their reinstallation on reboot (a nifty trick, that, and one of the major factors in the solution of my issue, I feel), and on reboot, made a system-restore-point for good measure and installed the AMD display-drivers again.

Needless to say, certain muscles in my body clenched during the installation, but the display came back on and I was so relieved :D

On a side note: is it normal to have an extreme Vcore like 1.45v by default? I can't remember what the 1600X in my gaming system rocked by default, but I know it can handle 3.8GHz at 1.325v.
So I decided to undervolt my 2200G, too, using the AMD CBS by -0.100mv.
If I had more fine grained control instead of steps of 0.050mv at a time, I'm confident I could lower it even more.?
I used CBS, because the Asrock option in the UEFI didn't seem to do a thing - I set my target max-clocks and Vcore (3000 and 1.325ish) and nothing changed.

Oh well, all in all, I'm very happy with the board and chip -- a major up-grade from my Kabini based Athlon 5350 I was using before :D


I'm having similar issues with the display drivers. I'll try to do what you did...
Asrock fatal1ty AB350I wifi mini itx - ryzen 3 2200g - 8GB DDR 4 ballistix sport 2666mhz (BLS8G4D26BFSC) - adata 120gb SSD 580 - 550w Gold plus - thermaltake core V1 - Windows 10 home - Bios 4.51a
Back to Top
Raephen View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Mar 2018
Location: The NL
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote Raephen Quote  Post ReplyReply Direct Link To This Post Posted: 11 Mar 2018 at 7:03pm
I am happy to report: my issue has been fixed!

While I can't put my finger on what exactly did the trick, I'll list the 3 consecutive  steps I took.

First off, I flashed my UEFI to v4.50. 

Secondly, I cloned my OS drive from the Plextor M6e in it's m.2->PCIe adapter to my Crucial MX300 in the native m.2 slot. Rebooted and set the boot order to load from the MX300 (and removed the M6e from the boot order completely) to test it. Succes, so I powered down and removed the Plextor from the system.

And the third step was to reinstall the chipset-drivers for good measure (+reboot after that) and Google how to boot into safe mode under Windows 10 (last time I've ever had to use safe mode was under W7, so a while back...). In safe mode, I ran DDU, which removed the Microsoft default display drivers and blocked their reinstallation on reboot (a nifty trick, that, and one of the major factors in the solution of my issue, I feel), and on reboot, made a system-restore-point for good measure and installed the AMD display-drivers again.

Needless to say, certain muscles in my body clenched during the installation, but the display came back on and I was so relieved :D

On a side note: is it normal to have an extreme Vcore like 1.45v by default? I can't remember what the 1600X in my gaming system rocked by default, but I know it can handle 3.8GHz at 1.325v.
So I decided to undervolt my 2200G, too, using the AMD CBS by -0.100mv.
If I had more fine grained control instead of steps of 0.050mv at a time, I'm confident I could lower it even more. 
I used CBS, because the Asrock option in the UEFI didn't seem to do a thing - I set my target max-clocks and Vcore (3000 and 1.325ish) and nothing changed.

Oh well, all in all, I'm very happy with the board and chip -- a major up-grade from my Kabini based Athlon 5350 I was using before :D
Back to Top
Raephen View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Mar 2018
Location: The NL
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote Raephen Quote  Post ReplyReply Direct Link To This Post Posted: 09 Mar 2018 at 12:43am
Aye, Wardog, I saw the new bios earlier today.

It's on my bucket-list for this weekend, before safe-mode + DDU.
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 08 Mar 2018 at 11:51pm
NEW AM4 BIOSes as of March 8 2018 for WiFi Issues
http://forum.asrock.com/forum_posts.asp?TID=7986&PID=47140

OP, Can I suggest you upflash, regardless.
Back to Top
Raephen View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Mar 2018
Location: The NL
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote Raephen Quote  Post ReplyReply Direct Link To This Post Posted: 08 Mar 2018 at 4:40pm
Originally posted by stree stree wrote:

Have you installed latest chipset drivers and Radeon graphics driver? ( in that order)

Yep. At least: have tried to. And always get the distorted display output the moment the display drivers are installing. Maybe DDU can be of some help this weekend.
Back to Top
Raephen View Drop Down
Newbie
Newbie
Avatar

Joined: 07 Mar 2018
Location: The NL
Status: Offline
Points: 8
Post Options Post Options   Thanks (0) Thanks(0)   Quote Raephen Quote  Post ReplyReply Direct Link To This Post Posted: 08 Mar 2018 at 4:36pm
Originally posted by Xaltar Xaltar wrote:

It sounds driver related but with Ryzen, that isn't always assured. 

I would try DDU under safe mode as you mentioned then install the driver version AMD recommends for the APU. From what I have seen with reviews on the R3 and R5 APUs this is not an uncommon issue. Many reviewers complained about how difficult it is to get these APUs working properly. 

As for the M.2 slot issue, it may have something to do with Ryzen APUs not having as many PCIe lanes as regular Ryzen CPUs, the M.2 slots are usually designed to utilize spare PCIe lanes so as not to take away from the x16 slots. If the APU has less PCIe lanes then it is quite likely that the M.2 slot is trying to use lanes the CPU does not possess. 

Thank you for your reply.

The M.2 issue was BIOS/EFI related: 4.40 didn't see it - 4.43 does. I'll try DDU this weekend when I've got a bit more time to fiddle with my system as it is functional, right now, just far from optimal as a HTPC without display drivers.
Back to Top
JohnM View Drop Down
Groupie
Groupie
Avatar

Joined: 20 Feb 2018
Location: UK
Status: Offline
Points: 267
Post Options Post Options   Thanks (0) Thanks(0)   Quote JohnM Quote  Post ReplyReply Direct Link To This Post Posted: 08 Mar 2018 at 12:41am
Originally posted by cubebucket cubebucket wrote:

I'm getting sick of this ryzen related issues :( ...I hope everything will be sorted out and solved soon. I don't wanna switch to intel or MSI or any other solution :(

That doesn't help and sounds like a rant. If you describe your problem then someone might be able to help you.
ASRock Fatal1ty AB350 ITX P4.90, AMD Ryzen 5 2400G, 2x8GB Corsair CMK16GX4M2A2666C16, 250GB Samsung 960EVO, 500GB Samsung 850EVO, 4TB WD Blue, Windows 10 Pro 64, Corsair SF450, Cooler Master Elite 110
Back to Top
cubebucket View Drop Down
Newbie
Newbie


Joined: 06 Mar 2018
Status: Offline
Points: 50
Post Options Post Options   Thanks (0) Thanks(0)   Quote cubebucket Quote  Post ReplyReply Direct Link To This Post Posted: 07 Mar 2018 at 10:39pm
I'm getting sick of this ryzen related issues :( ...I hope everything will be sorted out and solved soon. I don't wanna switch to intel or MSI or any other solution :(
Back to Top
 Post Reply Post Reply Page  12>
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.156 seconds.