Question Ryzen Random crashes in windows 10 at idle. Seems to be very common out there

[GeezerMan]

I have been working on a ongoing problem with a new Asus x370 pro board. Every few days while in windows 10, it crashes to the UEFI . This happens at idle.
Looking on google, it seems to be a very common problem for a number of brands of boards for the past two years .
I am now trying the disable Global C-State Control in the UEFI..

Some other fixes and comments include:

Power supply cannot handle the lower power draw when CPU goes into power saving, so get a new power supply.
disable C6 states
use the high performance mode in windows 10
in the UEFI, set power supply idle to Typical Current Idle, I tried this and it did not fix the issue
disable global c state control in the UEFI

There was a post two years ago in another forum by an Aussie lab that uses several of the x370 pro baords, and all of them were crashing at idle.
The fix for them was to Disable Global C-State Control in the UEFI, which I am now trying

Asus x370 pro board, with latest bios update
ryzen 5 2600
crucial 3200 ram, but set at JEDEC default

 

[lopri]

Interesting. I have not experienced it first hand, but it sounds plausible enough. I will keep an eye on it.

 

[William Gaatjes]

I have an ASROCK B350M with a ryzen 5 2600. Never experienced any crash. But to be honest. When i am done with the computer, i turn it off(with the exception of leaving it on because of virus scanning or building something or downloading a game). So it is never longer running than about 24 hours or so with me. Although there is quite a lot of idle time in between in those 24 hours. But yeah, best powersavings happen when a computer is turned off when not needed.
With a fast PCIex4 SSD , the boot time is fast enough that leaving a pc on to be able to start quicker is no longer justifiable.



When i read here and there, it seems the ASUS X370 boards are not the best to have.

 

[piasabird]

This might have something to do with hibernation and low power states that some CPU's can have. Might be some settings you can change. Using a newer BIOS might help also. This could also be caused by spyware, firmware, or virus activity. I dont see this on my Gigabyte Intel Motherboards. Sometimes Win 10 does a version update and it breaks software or apps that previously worked just fine.

 

[GeezerMan]

this describes it well

https://forums.anandtech.com/thread...-freeze-problems-with-1st-gen-ryzens.2562813/

https://www.google.com/search?q=ryz...7j0j69i60l2.5064j0j8&sourceid=chrome&ie=UTF-8

https://forum.level1techs.com/t/psa-testing-for-and-solving-random-freezes-on-ryzen/133239/21

 

[kschendel]

I had a hard freeze at idle issue with a 2700X on an X470 Taichi running linux, and disabling Global C States fixed it. (I also have processor.max_cstates set to 1 on the boot command line; I don't know if both bits of voodoo are necessary, and I don't especially care to experiment as this is a work machine.)

 

[EXCellR8]

OP are there any new chipset drivers available for the board? AMD posted X370 drivers at the end of last month however I would consider them to be generic.

 

[GeezerMan]

all drivers and bios are up to date. I am now trying the disable Global C-State Control in the UEFI .
this has been a issue for many people going back 2 years.

My crashes are always at idle, and very sporadic, sometimes every 3-5 days , with the PC running 24/7

after reading a lot about the issue, I would say it's probably the low power states.

Now, why should we have to disable these helpful power saving modes? is it a windows issue, bad motherboard design, an AMD coding problem?

 

[GeezerMan]

looks like the disabling of the global c state control in the UEFI has fixed it for me.

what do you guys think? AMD said awhile back, it was the power supplies not being able to go to such low voltages in the C states causing the issues..

or, is it a design problem with the boards?

 

[VirtualLarry]

I had to do the same thing with a Gigabyte Brix unit, disable Global C-States. I had issues with Linux Mint crashing on it (Bay Trail bug), and that basically fixed it, but that "fix" alone, basically shut off all of the boost/turbo states of the CPU, so it was crawling at the lowest-speed setting. I guess forcing a C-state of 1 as mentioned above might have fixed that too.

I think that issue was eventually fixed, either with a kernel update, or a BIOS revision.