Problems OC i7-5930K

jmig wrote: I am a casual overclocker.  By that I mean, I read online how to OC and then use the builtin features to OC. I do not try to go extreme. I want a goo solid stable platform.

Stable means not particularly using the ez oc way out to oc it.

jmig wrote: Is there a way to get the speed to 4.2 to 4.5 GHz?

Again, study the Haswell-E OC'ing Guides of which there are many. Study, test(not copy) the steps on your system, and learn along the way while doing so. But as each system is very different don't simply copy someones settings to yours and expect it to be stable. Odds are it won't be.

Thank you Parsec and Wardog,

jmig wrote: Thank you Parsec and Wardog, "You'll get some increase in FPS with a CPU over clock, but how much do you actually get going from stock clocks to ~4.075GHz? How much of an increase do you want or expect from a higher OC?"  There is no accurate answer for this question. There are far to many variables within the settings of PD3 (Flight sim program) that affect its FPS. The biggest hits are AI aircraft, weather (Clouds), and the additional monitor views. So, the general rule is that you OC as much as you can to get the best frame rate as possible.  I would like to have a fairly stable 30 fps. Right now, I am getting 25-8 fps depending on the complexity of the scene. Below 15 fps you start to lost the fluidity of flight control. "Why do you have the BCLK set to 127.4MHz? What is the purpose of that? " This is a result of Intel's Extreme Tuning program.  This program set the settings that I posted.  It has been the only attempt to remain steady and allow me to boot into Windows.  The internal ASROCK BIOS OC settings and the F-Tuning settings have always resulted in failure to boot, with one exception that got the system to 4.0 GHz. I have been trying to raise the Vcore voltage. I had it set to 1.21 vDC. That still wouldn't allow me to boot. I could go higher. Wardog,  I understand you comments. However, when a manufacturer be it chip or motherboard puts out a simple OCing program, people who do not have a strong desire to learn the ins and outs of OCing will try and use it to achieve what are thought to be average results. The 4.5GHz number came for a couple of OC sites that overclocked the i7-5960 CPU. They stated that the i7-5930 could go a little higher. I settled on a compromise of 4.2GHz just to be safe. Parsec, thank you for the comment on the clr CMOIS button. However, because it is covered by the second GPU, I have found the A_B switch to be easier to reach.   John

Your board also has a CLR CMOS button on the board's IO panel, which is visible on the back of your PC case. That was what I wrote about in my last post.

This button is between the PS2 keyboard input, and the two blue USB 3.0 ports. It's a very small black button, and is labeled CLR CMOS. You can use a pencil eraser to push it in, or the plastic tube from a can of the compressed gas used to clean dust off PCs. Your finger nail should work too. Be sure to turn off and unplug your power supply before pressing that button.

Next about the Intel IXTU utility. The ONLY time or way that IXTU sets ANY TYPE of changes to ANY of the options available in its screens, is if the user changes them, or it takes the current UEFI option settings for the CPU and memory, from the UEFI of course.

IXTU does NOT have any kind of built in or predefined over clocking settings or profiles.

I've used Intel's IXTU for years, and I have an ASRock X99 mother board with a CPU I've over clocked, both with Haswell-E and Broadwell-E processors. So I know how it works. IXTU does not automatically over clock any processor simply by running IXTU. It does not change any of its option setting by itself.

But I can tell you what actually happened, that you are confused about.

When you run IXTU, it displays the current UEFI/BIOS option settings. The first time you ran IXTU, on the upper right side of the IXTU display you saw the System Default and Proposed values, which caused you to think IXTU over clocked your processor. The settings you saw in IXTU were already set in your board's UEFI/BIOS. That is all there is to that. Unless of course you set them yourself. You apparently applied those settings in IXTU, which are being applied automatically by IXTU every time you start the PC.

When you run IXTU, it remains running, and when you shutdown and then start the PC again, IXTU will be running in the background. You can find in the the Taskbar "Show hidden Icons" list, on the far right of the Task Bar, next to the networking icon. IXTU is applying an OC that was apparently set in the UEFI/BIOS at one time.

The 127MHz BCLK setting must be from your memory OC (DDR4 at 2666 is a memory OC, all Haswell-E HEDT processors have a maximum specified memory speed of 2133), as using that memory "strap" (normally 125MHz) was one method of over clocking early models of DDR4 memory on X99 platforms, the first one to use DDR4.

Your PC won't boot with the 127MHz BCLK, but will actually run in Windows with that BCLK. I have seen that happen in the past, without going into the details explaining why.

The 127MHz BCLK that must have come from your memory, makes it difficult for you to OC. I'd like you to check what the BCLK is in your UEFI/BIOS, when the memory speed is 2666. Are you using the XMP profile?

The best way to OC any CPU, is to set the memory speed to its stock speed, which is 2133 (BCLK = 100MHz). Then OC the CPU using the core ratio multipliers, VCore, and Load Line Calibration settings. Once you have a stable CPU OC, then you can OC your memory. But if the XMP profile changes the BCLK to 127MHz, that will affect the CPU OC. I would like to know if your memory's XMP profile is the source of the 127MHz BCLK.

Yes you should increase the VCore as one way to stabilize an OC.

I understand the reasons for a higher FPS rate. I'm simply saying is a high CPU OC really going to produce a 10+ FPS increase. I you are only at 30FPS now, your current video cards in SLI are not cutting it at all, and your quest for higher FPS rates via a CPU OC is not the ultimate answer.