quaintwolf
New Member
I am facing the same issue with Gigabyte b650 aorus elite axJust show them.this thread haha it's not just x3d chips either looks like all 7000 series and also not just Asus motherboards
I am facing the same issue with Gigabyte b650 aorus elite axJust show them.this thread haha it's not just x3d chips either looks like all 7000 series and also not just Asus motherboards
I am facing the same issue with Gigabyte b650 aorus elite ax
I just built a new 7950X3D system for 2 weeks and run fine without a glitch (normal use, no gaming just productivity with PBO enabled, no process lasso). Today this problem happened to me after i use process lasso for CPU affinity + cryptomining program. *sometimes i use mining software for benchmarking but without process lasso, this scary stuff never happened.
Tried to replicate it and record hwinfo log + process lasso setting. Btw, my hashrate going up by 9% after i apply the process lasso setting
SS + log attached
Thanks Martin! Can you perhaps confirm by now if it's a software or hardware issue?Patience please. We're discussing this internally... such things need time to reach the right channels, etc...
More than 24h later and numerous games played I think I have a decent idea of what the problem is. I tried running the same games where I got that error but this time without the built in AMD overlay for fps power gpu usage etc. No errors whatsoever. So it might be the case that the latest versions of hwinfo doesn't play well with the latest versions of AMD's software [probably the same issue on nvidia].99.99% that it's a "software" (or better firmware/software) issue.
as someone who's worked with martin and gave him the debug files i can tell you overlays aren't the issue. I did extensive testing with amd's driver only and even windows basic driver and still got the crazy misreads of 2.4v on vsoc. I have vsoc locked at 1.2 so it's not going anywhere. I haven't paid attention yet to see if i still get it.More than 24h later and numerous games played I think I have a decent idea of what the problem is. I tried running the same games where I got that error but this time without the built in AMD overlay for fps power gpu usage etc. No errors whatsoever. So it might be the case that the latest versions of hwinfo doesn't play well with the latest versions of AMD's software [probably the same issue on nvidia].
For those having issues just make sure to not activate or disable any other info display software [in my case it was AMD's built in overlay for the GPU] and see if the problem repeats. Having disabled that I had zero errors.