A320M Pro 4 no post after reboot

I've given up and got a replacement coming from Amazon, hopefully its not a fundamental problem with the A320M Pro4

mjinglis wrote: Hi, Im having problems with my ASRock A320M Pro4,  In general the system works fine, however frequently on reboot from Windows the system sits with a blank screen and no post. Whilst up it is fine and stable, however on a windows update restart etc it will just sit on blank screen, monitor is not powered up so im assuming the graphics card is not running. There are no motherboard beeps and Windows thinks it has shutdown the system as far as i can tell. Im running the latest BIOS and have tried a CMOS reset but it still happens. Anyone have any suggestions?  im running : Windows 10 Creators ASRock A320 Pro4 Ryzen 3 2200 8GB Crucial DDR4 2400 1050 GTX Graphics Card

are you able to hard reset the machine and boot and this only occurs on softboots such as the windows restart, i had the same issue on the b350 pro4 as well. I also believe this occurred on an ASrock extreme 4 board (which I sold), initially thinking my 290x was defective up until the new ryzen build and same issues persist despite no existing hardware was used. The only workaround is to use stock settings, nothing else. The only thing I configured was my raid array, if i changed ram timings or cpu freq, warmboots would fail to post and there seems to be no remedy.

I highgly doubt i would ever touch another ASrock board at this point, same goes for MSI as their build quality is mega awful and bios chips become corrupted after a few years of usage. Think ill be going to gigabyte from now on.


Edited by Solace50 - 23 Apr 2018 at 3:39pm

The C states are implemented in the AGESA code by AMD, not many people understand that almost all the UEFI settings that have to do with the Chipset/Memory/CPU/GPU/SATA/M.2 are in the AGESA code, SMU code and SouthBridge code provided by AMD, things like Fans, Leds, LAN/WLAN are indeed managed by ASRock, as well as the UEFI layout and layout options provided, some vendors unlock all options from the firmware provided by AMD, some dont, but vendors cant add features that are not available already in the firmware provided by AMD, but in essence they are all linked to the firmware provided by AMD, the only bugs that can occur are in the underlying implementation, as in how ASRock assembles the final UEFI code for the specific motherboard configuration.

Edited by cristy6100 - 24 Apr 2018 at 1:38am

The C-States are not the cause of the issues here, its almost all the time the memory that causes the problems for cold boots. The C states are used to manged all adaptive voltage/frequency for the CPU/GPU, they are beneficial for power consumption reduction and less wear on the silicone and transistor by adjusting both voltage and frequency, we are at 12/14nm the transistor are very sensitive, constant high voltage and frequency will degrade them 100' of times faster than older CPU's using 32-45-65nm fab processes. Long gone are the days of pusing a Fixed frequency and voltage in the CPU, people need to understand and adjust to this.

Edited by cristy6100 - 24 Apr 2018 at 1:57am

Be aware that low end boards use less PCB layers and lower quality traces, that can affect the memory performance, I am using the Fatal1ty X370 ITX/ac and had also her sister the AB350 ITX/ac

Edited by cristy6100 - 24 Apr 2018 at 2:07am