What can cause AMD build errors with integrated graphics?

Question

Iron

For the first time in my life, I'm doing a simple, cheap assembly on AMD with integrated graphics (config at the end).

Some kind of "assembly from hell" turned out. I assembled more than a dozen computers, there were never any problems (except for the first one, back in pre-ATX times, where the power button in the case turned out to be inoperative). It's just a jamb on a jamb - first constant BSOD's due to WIFI network card (originally TP-LINK) - literally 5 minutes of network activity, and a skiff; After replacing with ASUS, the problem disappeared. But there were problems with the graphics. Under win10 there were BSODs with atkimpag.sys error, randomly, without load, just by themselves. For experiment set win11. We installed AMD firewood using the standard AMD utility - it downloaded the firewood for the chipset, etc., and for the integrated VEGA 3 graphics. ok. But in games (old and simple, CIV6 and Stalker COP) crashes very quickly with the error "AMD software detected a driver response timeout". After that, the video adapter is turned off by Windows.

There is no overclocking, everything is by default. There is no overheating. Furmark, corona benchmark, Prime95 work without problems, SMART disk is normal.

What I tried:
- replacement of firewood - tested all the firewood available on the site, both the latest version and the latest stable ones, and several previous versions; between installations, the previous firewood was demolished by the regular AMD utility amd driver cleaner; moreover, they tried different firewood both under w10 and under w11.
- replacing the processor with a second of the same model
- memtest memory check (long)
- replacing the memory with a completely different one, instead of 2 * 8 they put 1 * 32 from another manufacturer with different parameters
- the behavior is the same on the original UEFI version and on the last update

I smoked out all the forums, where, of course, at best they offer to rearrange the firewood to those under which it will not fall, at worst - to put some blasphemous driverpack (well, yes, of course).

What to do? In fact, only the mother remained untested, and the SSD did not change, although in theory it should not affect (although, of course, anything can happen). Does the community have any ideas?

Configuration:
MB ASUS TUF B450M-PRO GAMING
CPU YD30GEC6M2OFH AMD Athlon™ PRO 300GE
CPU cooler Wraith Prism
RAM PVB416G320C6K
SSD Team Group T253X2001T0C101
CASE Be quiet! PURE BASE 500
WIFI PCE-AC58BT
PSU EVGA 600 BQ [110-BQ-0600-K2]

Answer 1

I have a Ryzen 5 3400G Vega 11 video core.
Win 10 regularly crashed BSODs in a blue screen.
It seemed that there was some kind of conflict between the hardware, and in the tests everything worked stably BUT when I started watching the movie "online" with a resolution of 1080 after 5 s. flew out.
I just changed the Win 10 distribution and it worked.
Unfortunately, I have not found the reason for this behavior. I think that there is a question about some specific driver that is part of the OS distribution kit and which, as it were, is not present everywhere. Or this driver is included in some kind of update. The stable Win 10 distribution was up to March 21 with updates.

Answer 2

The name PRO GAMING kagba directly hints at the fact that by default there will be some kind of game with regular overclocking.
I would try to switch to manual mode and turn off all kinds of regular dynamic processor / memory overclocking and set the processor and memory parameters manually, according to the specs.
Well, of course, do not install a regular utility, which, after launch, begins to apply the devil knows what overclocking profiles are intelligent.
With normal processors, it can and vice versa be good, but a deshmanian percent can panic because of profiles that no one thought to check on it.
I did not see in the text, is the bios fresh?

Answer 3

SSD lies ... but the mother, given that the built-in, is quite real .... I hope the RAM is not AMDshnaya?)
Here, on Asus TUF motherboards, they complain about the 3rd time in a month ...
How funny - try disabling uefi and secure boot, and put Windows on the MBR)