Windows 10: Ryzen 3 2200G Black Display after driver update

I am extremely disappointed with this platform. There is most likely a driver error and I can't understand what it is.

My system is very simple:

Ryzen 3 2200G
400W PSU
8GB Corsair CMK8GX4M1A2666C16
Asus Prime A320M-K

The computer has been having random BSOD. Dump files indicated memory problem. I have tested memory, no problems.

Today changed memory as well from a working computer and trying to do clean install with Win10 Pro but every time the driver is updated (after chipset installation) the screen goes black once the computer restarts.

However basic Microsoft Driver seems to be working fine.

I have updated all Chipset driver, RAID installer driver and as soon as Windows loads the driver dated in July, the computer has black screen now.

I am using the HDMI connection to the monitor.

Don't know what to do, please advise.

:)

 

AMD Ryzen 2200G systems hang, usually no BSOD

Problem: Systems hard lock after anywhere from a few minutes of uptime to a couple of days. Image is frozen on screen and no mouse cursor is visible, pressing Ctrl+Shift+Win+B to reset graphics driver does nothing. Only one of the PCs has ever bluescreened
and it only did so one time, with error code 0x1000009f DRIVER_POWER_STATE_FAILURE for ntoskrnl.exe. I tried updating, downgrading, and reinstalling GPU, NIC, and sound drivers but no luck. Every other time the PCs don't bluescreen when they lock up and there
is nothing in the Event Viewer that is helpful.

Troubleshooting steps tried:

1. Updated AMD drivers from 18.5.1 to 18.7.1 and 18.8.1.
2. Clean installed both 18.8.1 and 18.5.1.
3. Installed Realtek LAN and audio drivers from ASRock.
4. Clean installed 17.7 AIO driver package from ASRock (listed as 17.40).
5. Updated BIOS from 4.70 to 4.90.
6. Reset BIOS.
7. Uninstalled August 2018 Windows 10 patches.
8. Switched to Balanced power plan instead of Ryzen Balanced.
9. Disabled USB suspending and PCIe ASPM
10. Switched to High performance, disabled ASPM & USB SS
11. Increased SOC voltage to 1.1 and RAM voltage to 1.3.
12. Removed AMD drivers, used Microsoft Basic Display Adapter.
13. Uninstalled Malwarebytes Premium 3.5.1
14. Started in Safe Mode w/ Networking
15. Repair install 1803.
16. Used only one RAM stick at 2133MHz.

Next steps:

1. Clean install 1803
2. Install 1709, delay 1803 update
3. RMA ASRock motherboards
4. Replaced ASRock motherboards
5. Replace AMD with Intel

Identical systems specs:

• AMD Ryzen 2200G CPU
• ASRock AB350M Pro4 Micro ATX Motherboard
• G.Skill Ripjaws V 8GB (4GBx2) 2666MHz DDR4 RAM
• Samsung 860 EVO 250GB SSD
• EVGA 450W Bronze PSU
• Fractal Design Core 1000 Micro ATX Case
• Windows 10 Pro x64 v1803

Other system specs:

• AMD Ryzen 2200G CPU
• Asus TUF B350M Plus Gaming Micro ATX Motherboard
• Corsair Vengeance LPX 8GB (4GBx2) 3000MHz DDR4 RAM
• Samsung 860 EVO 250GB SSD
• Corsair TX650M Gold PSU
• Fractal Design Node 804 Micro ATX Case
• Windows 10 Pro x64 v1803

Details:

I built four identical systems and one with different motherboard and RAM, all of them are having this problem to varying degrees of severity. The worst one locked up within 15 minutes, but the best one used to work for over a week without issues. I tried
doing a repair install on one of the systems, during the preparation period for the upgrade the system locked up at 16%. I was able to get it to complete to the point of restarting to do the majority of the install, but that locked up multiple times as well.

I've looked through the event log, and there is nothing between the systems that points to the source of the problem. There is no one thing that causes the systems to lockup, and there is no rime or reason to when they lockup. One of them did seem to lockup
every hour, but otherwise it happens at random.

I'm at my wits end; in over 15 years of troubleshooting and building PCs I have never had issues of this scope or inconsistency. I repair computers for a living, and I have never seen issues like this. I have a server based on AMD's Epyc 7351P and my main
desktop is based on the Ryzen 7 1700, and I haven't had issues anywhere close to this on those systems. At this point I'm seriously considering replacing the CPUs and motherboards with Intel equivalents. I've I'm willing to try any suggestions any one has,
no matter how much of a long shot they are or how stupid they seem.

Here's a link to the dump file, driver list, and system info: https://1drv.ms/f/s!AoFuBFiKuAH5uWqmul1JHUSusJ4S

 

Low-Power Variants of the Ryzen 5 2400G and Ryzen 3 2200G are on the Way

Over the last couple of days, motherboard manufacturers have been scrambling to release BIOS updates for their AM4 motherboards to accommodate the new Ryzen 3 2200G and Ryzen 5 2400G processors. From the information we gathered from ASRock's AM4 CPU support list, AMD is secretly preparing two more Ryzen "Raven Ridge" APUs. The unannounced models are the Ryzen 5 2400GE and Ryzen 3 2200GE. Judging from their technical specifications, the aforementioned processors are the low-power variants to the two models that were released today. The "GE" variants come with a lower 3.2 GHz base clock and 35W TDP. As of yet, AMD hasn't officially announced the pricing or release date.

 

ASRock AB350M Pro4 + Ryzen 3 2200G Virtualization Issue

I'm having a virtualization issue with an ASRock AB350M Pro4 motherboard (Ryzen 3 2200G). RAM tests fine.

I've activated virtualization in the BIOS (upgraded to 5.90) and have tried reinstalling and recovering Windows 10 Pro multiple times. Every time I've tried to install or use any feature related to virtualization my Windows install fails. I can boot into
safe-mode and the system then aborts and uninstalls the features. The issue is repeatable in both 1809 and 1903. It happens every time I try to install Windows Sandbox. It happens happens when I turn on 'Core isolation'. Same with Hyper-V.

This is the third AB350M Pro4 I've had issues with. I've RMAed 2x already. This newest one seems a more stable than the others, as long I don't use virtualization at all, but this seems to a totally bugged product. Anyone have any ideas what may be going
on? Is this a Windows issue or a hardware issue?