Yearly1845
joined 1 year ago
I have this same bug on the same platform! It was infuriating to track down. I was able to get around this by disabling c-states in the bios. I've heard that updating your aesga firmware also helps, but I can not confirm that.