I am not going to try and debug your problem, you have not even given all your system specs, especially the PSU.
I would have told you if you would have ask instead of jumping on the defensive and claiming it is all sensationalism for no reason. I said on the first post that i not longer have the 1700 so why do you think im trying to diagnose MY system? Im trying to find out what could be the root case of this and C-states is what im trying right now.
----
In case anyone wonders, my system was:
-Ryzen 7 1700
-Gigabyte AB350-Gaming with F23 Bios (Agesa 1.0.0.4)
-4x8GB DDR4-3200 Corsair LPX
-MSI RX580 Gaming X
-EVGA 650GQ
Here is the last time i had my 1700 last Saturday, i ran a Cinebench R20
And i had this random idle freezes, it happened like once a day since december-january, altrought in some days did not happen.
Now i have:
-Ryzen 3 2200G
-Gigabyte AB350-Gaming with F23 Bios (Agesa 1.0.0.4) (the exact same motherboard)
-4x8GB DDR4-3200 Corsair LPX
-MSI RX580 Gaming X
-EVGA 650GQ
No freezes for a few days until i got to get rid of the RX580 and 16GB of ram on wednesday. Now i have the 2200g, the same motherboard and PSU, it is still running fine with no freezes but is not longer the same.
The 2 system that im waiting to get here for support are:
-Ryzen 1200
-Gigabyte A320-S2H
-1x8GB DDR4-2400 Crucial
-Zotac GTX1050 2GB
-XFX 400W
And
-Ryzen 5 1400
-Gigabyte AB350-DS3H
-2x8GB DDR4-2400 Crucial
-RX570 4GB (i think it is Gigabyte, not sure)
-TT Smart 650W
Both reporting the same issue that i was having.
Y
A Windows problem is unlikely due to Ryzen having sold very well, hence a buggy OS - CPU interaction would affect lots of users at once. It would also likely leave a diagnostic trace, bluescreen or event log.
If you want to further investigate this, the first step is to try disabling C state support in BIOS.
i will next week on the two systems im looking into.
I said that about Windows Power Management because i saw people investigating lower Ryzen performance on Windows due to recent updates, that is likely to be caused by something wrong in handling C-States.