If you can’t help me to find message with V4 bclk bootstrap method
Thank you
http://www.overclock.net/t/1591590/xeon-hacking-and-overclocking-x79-x99-beyond-x58/1500#post_26425768 said:Would someone with dual or more sockets and CPU's run a small program for me under the UEFI shell?
Thanks.
Edit: The free time I had over the weekend to provide up to 8 socket V3 voltage control from the BIOS with an FFS addon has gone now so no need for anyone to reply to this anymore.
Well they do cheat really because the power management is never initialized which means no power readings, DTS temperature readings, idle C-States other than CC1, no AVX and they cannot use later ucodes. Also this type of bclk overclocking is different from v3 and v4 as it is not linked to PCIe clock. Might be able to do something with an i5-8400 but for Haswell and Broadwell it's a no go, only the straps are an option.Non-K Skylake Overclocking
but they do not cheat TDP nor delete ucode.
Interesting. Looks like the driver is working but something else limits cpu speed under load.
Interesting. Looks like the driver is working but something else limits cpu speed under load.
But that does not mean anything. Thats can be microcode or fused code inside the cpu.
this is my asus z10 bios for c state :
![]()
i dont know what option i change..?
I am using blck right now "overclock" my V4's. It's not worth it on xeons, at least for me. I can push it as high as 103mhz and anything higher will cause system instability. As stated, it changes everything, pcie, memory, etc. It's an issue with these system as ecc memory usually aren't stable at higher than rated speed.bclk changes everything, core ring memory...
if bclk straps works, with TDP cheat and voltage offset, we almost get one multicore unlocking high-end CPU, like 7980xe and 7940x.
wow
It is sure that overclocking bclk without locking pcie speed to 100mhz is meaningless.I am using blck right now "overclock" my V4's. It's not worth it on xeons, at least for me. I can push it as high as 103mhz and anything higher will cause system instability. As stated, it changes everything, pcie, memory, etc. It's an issue with these system as ecc memory usually aren't stable at higher than rated speed.
So, to go back. This is wrong; Power Technology should be set to Custom.
Under CPU P State Control:
Show us what's available under CPU HWPM State Control...
- Package C State limit to C0/C1 state
- CPU C3 Report to Enabled
- CPU C6 Report to Disabled
Thanks saved me as mmtool had disappeared from the interwebs. Still to do the deed on EP2C612 with 2x e5-2696 v3. Nervous as hell here! Wondering if it is worth it for 20-25% increase in performance...😱..apart from pure awesomeness of course!Hey, I made a pack with all the tools necessary 😉 UBU, UEFI SHELL, V3 driver, microcodes, etc and instructions =)
-Modded Bios 3402 for Asus X99 deluxe included-
http://www80.zippyshare.com/v/U179LJHE/file.html
I've used that method on PC with two CPU: BIOS modificaton + V3.EFI + win + microcode_27
Config: ASRock EP2C612 WS + 2xE5-2686v3.
And have got an interesting result: the first CPU is unlocked and the second one is not.
(That "asymmetrical" system works stable after C3/C6 states were disabled in BIOS.)
As I understand that's happened because V3.EFI has updated MSR registers only on the first CPU - where it was executed.
But how can I run necessary MSR update on both CPU ?
Is this still an issue?
Great thanks for heads up..was about to use the original v3.efi.The original v3.efi one cpu only, for dual cpu systems you can use C_payne's dual drivers
https://peine-braun.net/public_files/XEON_V3_BIOS_MODS/EFI-Drivers/dual CPU/
Uhhm, any idea which one I'm supposed to use? Go from 0 to 120. Starting to become a pretty long there thread here, is the post about it towards the back? Thanks for the help! 🙂Great thanks for heads up..was about to use the original v3.efi.
Roger that, would like to know as well before committing...At least it is confirmed for EP2C612 WS, however needs more data regarding the everyday usage - stability, temps and so on.
Safest method is "load" command in efi shell but i think C_payne drivers has a problem with load command. So, you can use bcfg driver add 0 ..... command.
Always start from "0"
ffs and driver injecting last thing you should do. When everything works perfect you can inject ffs version into your bios image.
You can use or try the original v3.efi but your second cpu will stuck in to non turbo stock speed. V3.efi not recommended for dual systems.
Thanks anyway, struggling though it! Happy modding! Nice avatar btw 😉ffs files are injectable versions of the efi drivers.
I know 82 page too much but all information about modding inside it. I read it all more than 3-4 times.
arne I have same board dual chips use v3x2_50_39_vcc still the best but disables all power monitoring so good cooling required I'm watercooled