Question (Solved) Unexpected crash in windows after updating bios and gpu drivers

[Taptan]

I have b450 tomahawk , r5 2600 , rx 580. For more than 1 year it was working fine , ram were on xmp . Started having issues when i updated bios to 7C02v17 version (before, i was using 7C02v12 bios) and updated my gpu drivers to adrenalin 2020. After doing the updates i started to experience a crash were my system would: freeze ,my monitor would turn off and lose signal, my keyboard rgb would turn off, ez cpu debug light would light up and i would have to force restart my computer. My motherboard still posts successfully. The crash is not occuring for the past 3 days now , so its very hard to tell if it fixed itself or that i am not giving it its reason to crash on me.

The crash occured: when i exited full screen, when i launched chrome, when i was playing games, even when i was just at desktop with no programs running just after booting up.

Tried a lot of things to find the main cause: updated to latest bios version , cleared cmos, reinstalled gpu and chipset drivers, tried older gpu drivers, ran stock clocks/voltages on my gpu, stock r5 2600 voltages/clocks , ran ram memory tests, checked if windows was corrupted, disabled xmp, monitored my motherboard cpu gpu temperatures and they all were safe.Also ran cpu, ram, gpu stress tests but they all were able to run 10+ minutes

Eventviewer says it was unexpected shutdown.That might just mean that it registered reset button when i pressed it but not that it crashed.

Can it be gpu drivers issue if my cpu ez debug light lights up when i crash?

I am thinking of downgrading to atleast v13 which has 1.0.0.6 agesa , while v17 has 0.0.7.2. Flashing with bios mflash would not work because of amd limitations in downgrading.

Currently msi support has sent me afu firmware update utility so that i could try to downgrade my bios withing windows. The bios file i want to flash is the correct one and i get a warning message that rom file information does not match system bios. Can it be because i am downgrading from v17 to v13 and the difference between agesa codes?

I need help in finding what is causing this weird behavior for this windows freeze into cpu debug light ,and what can i do more.

 

[VirtualLarry]

I've always heard that, if you don't have a 3000-series Ryzen CPU, then keep your BIOS/UEFI at AGESA 1.0.0.6 (PinnaclePI?), and DON'T Upgrade to ComboPI-1.0.0.4 patch B. (*Unless, of course, you have a Matisse CPU.)

Also, AMD has been (slowly?) wringing bugs out of their new "Adrenaline 2020" drivers. I've got an RX 5700 in my rig as my primary/display card, and they seem to be increasing stability. I was having some crashes and black-screen events (usually they recover after a few seconds).

You could go back to 19.12.1 or something, just to test.

 

[Taptan]

Update. I was able to downgrade back to v13 version which is on 1.0.0.6 agesa code with the afuwinx64 firmware, just had to type F option and it flashed the bios successfully. Been running the downgrade with xmp on and no issues so far. The main problem was the bios agesa version (0.0.7.2) as i have predicted.