Contribute
Register

Asus X299 - Support

Status
Not open for further replies.
Overclocked/watercooled 5700XT is a beast for it's price.



Looks like the partner cards will be great (coming in September)

Also looks like it's like GCN and memory bandwidth starved just like Vega haha
 
Last edited:
Thank you, zzmadd!
So we still have to wait... maybe Asrock brins a newer BIOS, the one for the X299 Taichi XE is from 30.10.2018 (1.80), and I always check my builds also with the Taichi...
Someone told me the issue with the i9 9820X has been solved in Clover 5028.
Can you or anyone else test this out please?
I currently don't have the same CPU at hand.

Thanks a lot!
 
So, my odyssey seems to be over for the good!

As I said, I found a sealed 9980XE for 1500€ and these are the results:

2 cores @ 5GHz / 4 cores @ @4.7GHZ / 18 cores @ 4,4GHZ / AVX Offsets 5-6 / AutoVoltage / 360 AiO Push/Pull

I don't think there's any power to squeeze more, do you guys??

View attachment 417006View attachment 417007
IS MacOS AVX aware?
On Intel Core certainly not.
All frequencies drop by the amount specified whenever you set any number in AVX fields.
 
IS MacOS AVX aware?
On Intel Core certainly not.
All frequencies drop by the amount specified whenever you set any number in AVX fields.

I don't know if macOS uses AVX instruction but, since CineBench and GeekBench do, I prefer to offset them (I know how it works) just in case any other app would use AVX.
 
IS MacOS AVX aware?
On Intel Core certainly not.
All frequencies drop by the amount specified whenever you set any number in AVX fields.

From my many tests, DaVinci Resolve on MacOS uses AVX during decode of RED Helium footage. iTunes also seems to use AVX, not sure why. I may be wrong and misunderstanding how AVX calls work, but without AVX offsets I can boot fine until I try iTunes or playing RED footage DaVinci Resolve. Other things trigger KP without AVX offset, but those ones are repeatable.
 
AVX is heavily used in pro apps like Cinema 4D. macOS does use AVX, but I can't pinpoint exactly how much. Apple hooks into Intel features all the time since it's the only CPU macOS works with officially, ie iGPU/QuickSync was heavily used by native Apple apps like FCPX, but I think now they moved away from it and hook into Metal which can then hook into Intel iGPU or AMD Compute Units.

Run CineBench R15 or a full version of C4D and render a heavy scene and you will see it push AVX really hard.

My current OC settings are:
x44 on All Cores
-5 AVX on both
CPU Input Voltage is set to Auto
XMP is on (GSkill 3200MHz 128GB)
Under 80c (usually 79c on full load)
Throttle is set to 84c per Intel TJunction for 9980XE. It never reaches that even on extreme full load.

All works well, zero crashes, no errors, slowdowns etc. Before when I had AVX to default -0/-0 (or the one from KGPs original guide) it was a tad unstable and I noticed microstutters sometimes. And the CPU was being pushed too far with OC on. Now it's a really good balance.

It would be interesting if anyone was curious enough to look at the iMac Pro or future Mac Pro firmware dumps to see what exactly Apple does with AVX or any other Intel hooks. I think this would make Hackintoshes more perfect and stable if we figure that out.
 
Last edited:
From my many tests, DaVinci Resolve on MacOS uses AVX during decode of RED Helium footage. iTunes also seems to use AVX, not sure why. I may be wrong and misunderstanding how AVX calls work, but without AVX offsets I can boot fine until I try iTunes or playing RED footage DaVinci Resolve. Other things trigger KP without AVX offset, but those ones are repeatable.
You can see in Intel Power Gadget what are the frequencies.
If you have a 4.5Ghz frequency in the bios and then an AVX offset of -3 and then run MacOS and the max frequency you measure is 4.2Ghz THEN AVX doesn't work. Meaning MacOS will run all of its operations at 4.2Ghz.
At that point it's equal to lower the frequencies to 4.2Ghz having AVX se to 0.
 
AVX is heavily used in pro apps like Cinema 4D. macOS does use AVX, but I can't pinpoint exactly how much. Apple hooks into Intel features all the time since it's the only CPU macOS works with officially, ie iGPU/QuickSync was heavily used by native Apple apps like FCPX, but I think now they moved away from it and hook into Metal which can then hook into Intel iGPU or AMD Compute Units.

Run CineBench R15 or a full version of C4D and render a heavy scene and you will see it push AVX really hard.

My current OC settings are:
x44 on All Cores
-5 AVX on both
CPU Input Voltage is set to Auto
XMP is on (GSkill 3200MHz 128GB)
Under 80c (usually 79c on full load)
Throttle is set to 84c per Intel TJunction for 9980XE. It never reaches that even on extreme full load.

All works well, zero crashes, no errors, slowdowns etc. Before when I had AVX to default -0/-0 (or the one from KGPs original guide) it was a tad unstable and I noticed microstutters sometimes. And the CPU was being pushed too far with OC on. Now it's a really good balance.

It would be interesting if anyone was curious enough to look at the iMac Pro or future Mac Pro firmware dumps to see what exactly Apple does with AVX or any other Intel hooks. I think this would make Hackintoshes more perfect and stable if we figure that out.
It's not unstable because you use AVX BUT because when you use AVX MacOS always runs any app at any time with such negative offset. If you drop the frequencies by such offset and set AVX to zero than it's the same.
if the system in the two scenarios behaves differently is just because of random better tuned voltages that are auto-adjusted by the bios. But that's random, you can have AVX to zero and lower frequencies and set a proper voltage yourself.

AVX doesn't work in MacOS. It's like dropping frequencies of the cores as it intervenes for all apps all the time and not only on those using the instruction set.
 
It's not unstable because you use AVX BUT because when you use AVX MacOS always runs any app at any time with such negative offset. If you drop the frequencies by such offset and set AVX to zero than it's the same.
if the system in the two scenarios behaves differently is just because of random better tuned voltages that are auto-adjusted by the bios. But that's random, you can have AVX to zero and lower frequencies and set a proper voltage yourself.

AVX doesn't work in MacOS. It's like dropping frequencies of the cores as it intervenes for all apps all the time and not only on those using the instruction set.

I have checked frequencies multiple times and I saw system properly clocks the CPU correctly. In generale usage (SSE instructions) max frequencies spike to 5GHz as tuned in the BIOS and in Cinebench (AVX intensive) it operates according to offsets. I suppose the same behavior occurs in any app according to the instructions in use.
 
Status
Not open for further replies.
Back
Top