MMM
Results 1 to 25 of 861

Thread: Ryzen - Return of the Jedi

Threaded View

  1. #11
    Xtreme Member
    Join Date
    Sep 2008
    Location
    Eastern Tennessee (from Minnesota)
    Posts
    241

    Question

    Anyone happen to know which of these three are what I'd need to input into the BIOS?



    The situation is as follows...
    • I'm running Prime95 with the Max Temps stress test setting to test 3.7GHz set by Ryzen Master (note: just opening K17TK [latest beta v0.9.1.10] seemed to have confused Windows somehow, as it instantly behaved as if I had applied something and set multi to 35X with VID of 1.275V [as per AIDA's CPU Tweakings page], despite K17TK showing the VID was still at 1.350V)
    • Initially everything was indeed appearing to be running in "OC Mode". AIDA said VID was 1.2750 which clearly was wrong. HWiNFO shows the VID as a static 1.300V. The VDDCR_CPU was at 1.337V (which I know is what mine displays in OC mode). The VCore I think was like 1.375V.
    • My first voltage change (since I wasn't sure what exactly was going on and I knew that 1.3V would be sufficient for 3.7GHz) was changing the VID to 1.30000V, which dropped the HWiNFO VDDCR_CPU to ~1.28V and VCore to 1.320V. From there I adjusted it down in roughly 0.01V steps.
    • The window on the upper left is K17TK, which I'm using the adjust the voltage since it has no overhead like Ryzen Master (and I wasn't working with benchmarks). Important to note, is that K17TK's applied VID IS in fact reflected by Ryzen Master, thus both display the 1.2750V as in the screenshot.
    • The voltage it's operating at is stable, not jumping around any, at all VIDs I've used.
    • Prime95 has been continually running all during my voltage level changes. I set the new voltage as soon as the last worker thread finishes Test 1, and I let it pass two tests (the Test 2 that it has started when I apply voltage, and then the following Test 1 with its "Self-test" pass).



    I know the voltages are applying because they lower in HWiNFO, as well as the temps drop a couple C each volt change.

    Currently it's passed about 6 more since I further lowered it to 1.26250V (1.194V VDDCR_CPU [1.189V VRM], 1.232V VCore), so I'm pretty happy with that as it lowered the core temp by 8 to 10C over the original voltage, and the TOTAL Power has dropped about 27W (Package dropped ~14W).

    I'd just love to know what I'm really looking at, so I can apply this in the BIOS. Takes forever to reboot, enter, change, boot Windows, see what it's at, then repeat the cycle another X number of times just to get it to where it is now! lol

    Update: I'll assume that this means it's a case of massive VDroop?

    UPDATE 2: Alright, so I dunno what was up with the VID/Voltage reporting that day, but the only one that was correct seemed to be the VDDCR_CPU of ~1.19V. I set the BIOS voltage to 1.25V first and it was way off. I set it to 1.20V and it was basically perfect, though was strangely drooping just a bit too much (I presume because BIOS was set to Auto and 1.35V, but CPU only requested 1.2V). Nevertheless, the seemed to be the lower limit of the stable voltage for 3.7GHz anyhow, and that additional smidgeon of droop was enough to cause instability, which I'm trying to combat with LLC on the CPU. Mode 3 was actually worse, and so I decided to just try Mode 1 instead. Might be more than needed, but it keeps it at a perfect 1.2V unloaded AND loaded, which is impressive. I'll probably set it to Mode 2 later today.
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	Which one...png 
Views:	1408 
Size:	53.2 KB 
ID:	132369   Click image for larger version. 

Name:	So its VDroop....png 
Views:	298 
Size:	48.8 KB 
ID:	132370  
    Last edited by Formula350; 07-01-2017 at 05:19 AM. Reason: Update

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •