Contribute
Register

nⓩxtMac Pro - i9-9900k - Gigabyte Aorus z390 Pro - macOS Mojave - Sapphire Vega 64 Reference

Status
Not open for further replies.
Hell yeah man! Congratulations on the new hack!

I will be working on overclocking today once home. I think I will only push to 5.0 on it. Maybe 4.9. Would you mind sharing the settings you used for each of these.
 
I will be working on overclocking today once home. I think I will only push to 5.0 on it. Maybe 4.9. Would you mind sharing the settings you used for each of these.

I skipped 4.9, to be honest. Since the chip can turbo to 5GHz, 5 is theoretically possible on all cores with minimal steps. Follow my guide on the first page, just use a multiplier of 50 instead of 51. Vcore will likely be stable at 1.25, potentially even less. I’d start at 1.21 and go up by .01 incrementally.

I’m currently using a multiplier of 48, and a turbo on 6/8 of 52, and 51 on the last two. Vcore of 1.35. So my base clock is 4.8GHz, with a mixed turbo of 5.2GHz and 5.1GHz. I did this to improve thermals, so I could keep my voltage and temps down, but still turbo up when necessary. My h100i v2 is great, but past 1.35 VCore, it REALLY struggles to keep the i9 under control. Just remember to set your Watt settings to something obnoxious like 1k-4K so the TDP doesn’t inhibit the chip.

I may experiment with doing a 2/4/2 turbo, of 5.3, 5.2, and 5.1. It’s gonna depend on if I can squeeze the voltage though. I’m not really willing to go much higher. 1.4v tends to put me in the 90’s when under load, which is out of my comfort zone.

I did grab a set of the Corsair 120ML fans, so I have a push/pull combo on the rad now, which keeps acoustics down and thermals by a few degrees when under load.

 
Last edited:
Hey ! I've bought the same CPU/mobo, and I'll probably need your advice once Santa/Amazon has delivered the packages! This build is going to rock my world.

I was up and going fully in about a 2 hour time frame. This was taking out old board and putting everything back in. Very easy the second time around as I understand the whole picture now. Hopefully between the two of us was can keep you from pulling out your hair.

I skipped 4.9, to be honest. Since the chip can turbo to 5GHz, 5 is theoretically possible on all cores with minimal steps. Follow my guide on the first page, just use a multiplier of 50 instead of 51. Vcore will likely be stable at 1.25, potentially even less. I’d start at 1.21 and go up by .01 incrementally.

I’m currently using a multiplier of 48, and a turbo on 6/8 of 52, and 51 on the last two. Vcore of 1.35. So my base clock is 4.8GHz, with a mixed turbo of 5.2GHz and 5.1GHz. I did this to improve thermals, so I could keep my voltage and temps down, but still turbo up when necessary. My h100i v2 is great, but past 1.35 VCore, it REALLY struggles to keep the i9 under control. Just remember to set your Watt settings to something obnoxious like 1k-4K so the TDP doesn’t inhibit the chip.

I may experiment with doing a 2/4/2 turbo, of 5.3, 5.2, and 5.1. It’s gonna depend on if I can squeeze the voltage though. I’m not really willing to go much higher. 1.4v tends to put me in the 90’s when under load, which is out of my comfort zone.

I did grab a set of the Corsair 120ML fans, so I have a push/pull combo on the rad now, which keeps acoustics down and thermals by a few degrees when under load.


Running around 80-84 degrees at 5.0GHZ. Tempting to try going on up. I might just leave it. No crashes or anything. Rendered several videos in FCPX and went smooth. Now then Dual Vega 64's? BTW I will have airdrop and handoff working tomorrow.
 
I was up and going fully in about a 2 hour time frame. This was taking out old board and putting everything back in. Very easy the second time around as I understand the whole picture now. Hopefully between the two of us was can keep you from pulling out your hair.



Running around 80-84 degrees at 5.0GHZ. Tempting to try going on up. I might just leave it. No crashes or anything. Rendered several videos in FCPX and went smooth. Now then Dual Vega 64's? BTW I will have airdrop and handoff working tomorrow.

If you're already in the 80's I wouldn't really recommend goin any further up. What is your CPU cooler?
 
99% sure that’s just the big brother to my h100i v2, no? Interesting that your 5GHz temps are so high. What did your Vcore end up at? Always a good idea to find a stable vcore, then try to dial it as far back as possible without compromising stability. More voltage equals more heat, more heat equals less headroom.

Ill have to pull that this evening when I get home. Ran into another issue with benchmarking. Running Valley Test always crashes. Heaven and Luxmark GFXbench and Geekbench all work fine. Valley crashes right after it starts the test page goes for about 5-10 seconds and closes back to main screen. Not a big deal but it drives me crazy when something doesnt work.
 

Attachments

  • Geekbench CPU.png
    Geekbench CPU.png
    2.2 MB · Views: 207
  • Geekbench Metal.png
    Geekbench Metal.png
    1.8 MB · Views: 185
  • Geekbench OpenCL.png
    Geekbench OpenCL.png
    1.9 MB · Views: 164
  • GFXBench.png
    GFXBench.png
    303.8 KB · Views: 153
  • Heaven.png
    Heaven.png
    3.6 MB · Views: 167
  • Luxmark.png
    Luxmark.png
    2.8 MB · Views: 154
  • Blackmagic.png
    Blackmagic.png
    2.5 MB · Views: 148
Last edited:
Ill have to pull that this evening when I get home. Ran into another issue with benchmarking. Running Valley Test always crashes. Heaven and Luxmark GFXbench and Geekbench all work fine. Valley crashes right after it starts the test page goes for about 5-10 seconds and closes back to main screen. Not a big deal but it drives me crazy when something doesnt work.

Are you using AVX offset at all? macOS doesn't seem to respond particularly well to AVX offset adjustments. It simply downclocks by the offset, and AVX instruction based benches tend to crash immediately (Prime95 is a good example). I'm not sure if Valley uses AVX or not, just a thought.
 
Are you using AVX offset at all? macOS doesn't seem to respond particularly well to AVX offset adjustments. It simply downclocks by the offset, and AVX instruction based benches tend to crash immediately (Prime95 is a good example). I'm not sure if Valley uses AVX or not, just a thought.
I honestly dont know on that. Where is that at?

Valley worked fine with the old system. So I know its a setting. I used a Asus board last time. Also heaven works fine. I assumed they share the same engine.

I’ve been looking. It could be the memory Xmp being turned on(No turned off and still doing it). I doubt it as it was turned on in previous build. Just a pain trying to get one thing working.

Ok it has something to do with the intel graphics on the chip. I cannot get it to properly use both intel and vega.
 
Last edited:
Status
Not open for further replies.
Back
Top