GGTV-Jon
Willderborn can you post a picture of your CPU OC settings so I can try and match them. And are you still running with C States enabled?

Yeah sure, I'll post pics in a little bit.

OK, So I took your settings above an applied them to my 9800x and I was able to reproduce the same issue... however I am dont really think there is anything wrong. At first the only software that was picking up these rapid fluctuations in core clock was MSI Afterburner nothing else was showing them. At least not until I decreased the polling rate for HWInfo64 down to every 100ms and even than it was  hard to catch because the frequency in which it was occurring was so quick. In addition I also found that the load being applied to the CPU made a big difference in the rate at which the core clock changes would occur. I attached two screen shots that show this variation in frequency see notes below. 
 
Screen Shots: 
MSI Test One Prime95 - The data to the left of the RED line is the results of running Prime95 with a small data set. The data to the right of the RED line is the results of running Prime95 with a blend test. 
MSI Test Two OCCT - The data to the left of the RED line is the results of running OCCT with a small data set. The data to the right of the RED line is the results of running OCCT with a large data set. 
 
Ultimately I dont think that there is really anything wrong and this is normal I think that it just comes down to how MSI Afterburner is reading the data (polling rate and averaging). If your computer is crashing when those fluctuations I would chalk it up to your OC not being fully stable. Its also important to remember that your CPU is being fed a lot of different data even when you are running something like  Prime95 that used AVX other applications are still running that dont use AVX and the CPU still has to process those as well. 
 
 

willdearborn
Wow.. thank you for testing and your analysis. You are probably right in that nothing is wrong. My system no longer crashes even with the fluctuations after stabilizing my OC so I am inclined to agree. It's just strange that it only happens when overclocked. If I do the same test with no OC the clock speed stays steady. But it is good to know that it isn't a problem with my board.

I will test again today with everything set to auto and see what happens...

bcavnaugh
Still not seeing what the issue is here and why it is a an issue in the first place.
Also it has been recommended not to use Adaptive on the vCore and to use Override instead.
Why do you have the Mesh Ratio set to 35?

OP was concerned about the rapid fluctuations in CPU core frequency when running AVX loads and at the time was thinking that it was causing his system to be unstable. However it is no longer believed that this is an issue and represents normal operation of the CPU\Motherboard. Also looks like OP established that his OC was not stable and has corrected that as well.
 
This is basically resolved at this point... 
 

PC was blue screening when running Prime95. He had the CPU frequency set to 4.6GHz and and an AVX offset of 5 which should have resulted in a core frequency of 4.1GHz. However OP found that MSI Afterburner was showing that when running Prime95 that the CPU frequency was rapidly changing between 4.6GHz and 4.1GHz even though he was running Prime95 with AVX ON. His thinking was that these rapid changes in CPU frequency was resulting in the PC not being stable, but it appears that this is normal and the OC was just not a stable OC (which he has since corrected).  

willdearborn

bcavnaugh
Still not seeing what the issue is here and why it is a an issue in the first place.
Also it has been recommended not to use Adaptive on the vCore and to use Override instead.
Why do you have the Mesh Ratio set to 35?

If you dont understand what the issue is, why comment? You don't have to comment on every thread, the world will continue to spin whether you do or not. It has been explained multiple times by myself and others.

And the mesh ratio is set to 32 not 35. But have you not heard of overclocking the mesh?

And just because you want to use override instead of adaptive doesnt mean it's right for everyone. You say its recommended. By who? For what scenarios? Override keeps the voltage constant, while adaptive allows the voltage to scale back as needed. System is stable and uses less power.

Thanks for your help Jason. I guess my OCD will just have to live with the clock speed fluctuation now that I know its normal.

I do and I never read that you had posted you had a BSOD or was Unstable.
And I have been testing and trying your setting to see if any of my X299 Dark Motherboards would show the same.
If you look under Processor you will see the same difference in clocks listed under the Processor - Maximum turbo core clock
Port Royal 430.64 (DX12RT)
https://www.3dmark.com/compare/pr/92524/pr/91940/pr/91866/pr/91672/pr/91648/pr/91609/pr/91536/pr/91472/pr/91295/pr/91255/pr/91234/pr/91192
Time Spy Driver 430.64 (DX12)
https://www.3dmark.com/compare/spy/7189022/spy/7174802/spy/7173893/spy/7172903/spy/7168189/spy/7167597/spy/7166443/spy/7164977/spy/7163687/spy/7158797/spy/7158143/spy/7157270/spy/7156137
Fire Strike Driver 417.22 and 419.35 (DX11)
https://www.3dmark.com/compare/fs/19339923/fs/19324499/fs/19323782/fs/19322782/fs/19317481/fs/19316871/fs/19316105/fs/19314939/fs/19313619/fs/19308679/fs/19307786/fs/19307134/fs/19306258
3DMark 11 Driver 430.64 and 418.91 (DX11)
https://www.3dmark.com/compare/3dm11/13307911/3dm11/13304948/3dm11/13304842/3dm11/13304768/3dm11/13303415/3dm11/13303361/3dm11/13303260/3dm11/13303117/3dm11/13303008/3dm11/13301970/3dm11/13301843/3dm11/13301798/3dm11/13301711
3DMark Vantage Driver 417.71 (DX10)
https://www.3dmark.com/compare/3dmv/5763325/3dmv/5763015/3dmv/5763000/3dmv/5762986/3dmv/5762904/3dmv/5762903/3dmv/5762875/3dmv/5762855/3dmv/5762819/3dmv/5762682/3dmv/5762670/3dmv/5762664
3DMark06 (DX9)
 
My Error 32 and Not 35 
 

 
You say its recommended. By who? TiN_EE if I recall.
But I will pull out and not bother you any longer.
Good luck with your troubleshooting.
 
 

willdearborn

bcavnaugh
Still not seeing what the issue is here and why it is a an issue in the first place.
Also it has been recommended not to use Adaptive on the vCore and to use Override instead.
Why do you have the Mesh Ratio set to 35?

If you dont understand what the issue is, why comment? You don't have to comment on every thread, the world will continue to spin whether you do or not. It has been explained multiple times by myself and others.

And the mesh ratio is set to 32 not 35. But have you not heard of overclocking the mesh?

And just because you want to use override instead of adaptive doesnt mean it's right for everyone. You say its recommended. By who? For what scenarios? Override keeps the voltage constant, while adaptive allows the voltage to scale back as needed. System is stable and uses less power.

Thanks for your help Jason. I guess my OCD will just have to live with the clock speed fluctuation now that I know its normal.

Not to take your thread over, but are you having this same issue? I have tried a clean install of windows, to going back to 1.07 bios to 1.17? I think the 9800X handles clocks a bit different to sky lake and evga maybe did not update the firmware correctly ?
https://forums.evga.com/X299-Dark-owners-please-check-in-m2951266.aspx

35 mesh frequency! Is it too high?
And you can reduce the frequency of the processor to 8-10 on AVX3.

dmann304
On the 2 avx options 2, 3, which one is the one that causes most heat under load? i hear one of these 2
settings isn't reall useful in games or Handbrake, so if it does effect the package temp, or mesh, memory?
I would easily get 5ghz on my CPU, if the avx sets weren't pushing heat at this thing.

In the BIOS for the X299 Dark AVX2 is referring to AVX & AVX2 instructions sets and AVX3 is referring to AVX-512 instruction sets. As far as heat goes AVX-512 will produce the most heat by far, however it is also used the least. For reference as far as I know there are no AMD CPU's that support AVX-512 instructions and in the consumer lineup X299 is the only thing from Intel that supports it. AVX and AVX2 instruction sets are used in some games, but not very many. Handbrake, specifically H.264 encoding uses AVX2 and AVX-512 instructions. There are other applications that use AVX/AVX2/AVX-512, but Google for those. With an ambient cooling solution your have almost no chance of running AVX-512 at 5.00 Ghz (stable), the heat would just be off the charts...
 
One thing to keep in mind is that applications like Handbrake that use AVX2/AVX-512 instructions will not load all of your CPU cores with AVX instructions at the same time. If you watch clock frequencies (assuming an offset has been configured) you will see that only some of the CPU cores will be processing AVX instructions at any given time. On top of that the cores that are used for AVX will 'randomly change' throughout the duration of usage... This of course is assuming that the application in question has implemented the usage of AVX instructions correctly. All of this to say the 'real world' AVX loads that you see will be nothing like what you see in a stress test. Also worth noting that Handbrakes implementation of AVX2/AVX-512 instructions was done with the direct help of Intel, another words its implemented correctly. 

dmann304
So, sounds like the avx 2 option would be the one to not sorry so much about as heat goes, and avx 3 is the one that puts out the heat?
I do gaming a a sorted blender runs, and Handbrake occasionally.  So can i just bring down avx 3 to stock speeds of the CPU? and get 5ghz?

Both AVX2 and AVX3 put out more heat than non-AVX, AVX3 does it more than AVX2. Whole purpose of AVX offsets is to bring execution under control so yes, you should be able to figure out what offsets you will need to run non-AVX at some OC frequency and AVX2/AVX3 at safer one. When I was figuring out my offsets I did it in following way: I picked multiplier for non-AVX I knew I will be happy with (stable and temperatures under control). Then I set offset for AVX2 to some value, fired up workload that uses AVX2, monitored temperatures and throttling and adjusted accordingly until I knew I could run that workload at that frequency non-stop. Then repeated same for AVX3.

357832
I'm not sure if this is an old thread or not, but I have the x299 ftw k which has the same bios as the dark. I had the same problem and it would constantly switch between 5.0 and 4.7 extremely fast in games. I just turned AVX off and set my voltage to over-ride. Be careful with over-ride because whenever you set it to 1.3 the actual voltage will be higher like 1.317, which might be what it's supposed to do I dont know.

Thread is old but questions from dmann are receent.
 
IMO fluctuations are not a problem, they are signs of CPU behaving exactly how it is supposed to behave: Executing at one frequency when executing non-AVX instructions, changing to lower (by an offset) frequency when executing AVX instructions.