Thanks, Martin. I'm gonna load it up and left my PC on all night long with RAM Test to see if there's any issue when I wake up tomorrow morning.
Good night.
So far so good. I haven't done anything too demanding over the past few hours on my computer as I'm still running Karhu RAM Test, but here you have another screenshot:
I will try the new beta as soon as I can and I'll report back my findings.
In the meantime, after disabling the GPU sensors for Navi21 in HWiNFO v6.42 Build 4360:
EDIT: By the way, I'm getting this upon launching the new beta. What was the recommendation in this case as I don't recall it?
Thanks!
I'm going to try that next. I've just disabled the GPU sensors (by pressing Del) and I'm going to give it a go! Hopefully, we'll find the root of the problem soon!
Thank you eveyone for your feedback.
Yes, 2702 is exhibiting the same issue. I went back as far as 2502 and the problem still persisted. Again, even with the RAM at 2133 and the IF at 1:1 for that frequency, the reboots are happening as long as I load HWiNFO. I have no idea why, which is why I opened this thread.
Martin, I enabled "Snapshot CPU Polling" last night and then I left my computer running Karhu RAM Test and went to sleep.
The computer was rebooted again, however, so that did not work.
It must have been triggered about 30 minutes into running RAM Test.
Any other suggestions?
Thanks!
I agree with you on what you're saying. I think that, ultimately and as you have just said, it could be a case where HWiNFO is triggering an inherent problem. However, if I upgrade the BIOS for my motherboard with most recent UEFI firmware, the problem is triggered even faster. Also, there was...
Hi Martin.
The only monitoring tool running in our case is HWiNFO. Let me add some specifics about my personal hardware/software setup:
Hardware (firmware):
Motherboard: ASUS Crosshair VIII Hero X570 (currently using BIOS 3003 with AGESA 1.1.8.0 - SMU 56.37.0 - although the problem persists...
Hello everyone:
A couple of users and myself have been suffering sudden reboots with our computers composed of Ryzen CPU systems (Ryzen 3000, but especially 5000) under different load conditions. The quickest way for us to trigger it, however, has been by using software designed to test RAM...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.