about the microcode

[freecableguy]

about the microcode

[freecableguy]

It is important that you only remove the Haswell-E (v3) microcode revision patch updates in the BIOS. Leave all microcode revision patch updates for Broadwell-E (v4) intact. Make a new BIOS and flash via SPI to replace the faulted BIOS.

Windows 10 is now at Haswell-E microcode revision level 0x43 as of build 2004. Take ownership of and rename "mcupdate_GenuineIntel.dll" found in \Windows\System32 folder to prevent auto-microcode patching in Windows.

Download the VMWare tool: https://labs.vmware.com/flings/vmware-cpu-microcode-update-driver
Download microcode: version 0x27 & 0x39 microcode for Haswell-E (0x306F2) in VMWare driver / Linux compatible format: https://1drv.ms/u/s!Ag6oE4SOsCmDhFnET3uw9wHeV4EA

Install VMWare driver: use 0x27 microcode for best performance; 0x39 driver for "better" stability. Copy the file 0x27.dat (or 0x39) to the same folder as the VMWare utility and rename it to 'microcode.dat'.

Download and copy these files to the same folder:
'microcode_amd.bin'
'microcode_amd_fam15h.bin'

Execute 'install.bat' as admin and reboot.
Check microcode revision level with HWiNFO.

[freecableguy]

Re-opening for visibility.

HOW TO: Properly Modify BIOS for All-Core Turbo work-around
https://forums.anandtech.com/threads/what-controls-turbo-core-in-xeons.2496647/page-43#post-39001892

[carson512]

Thanks for the Windows 10 autoload problem sloved.
Now I use the bios with 'cpu306F2_plat6F_ver0000001D_2014-04-15' microcode.
Can't Do the All-core turbo..
So change to 0x27 microcode or must remove the 306F2 microcode?

[freecableguy]

All embedded microcode patches for CPUID 306F2 (leave all other microcode, for example 406F1, as-is) must be removed from the BIOS to be flashed.
Entering UEFI setup there should be no microcode patch loaded (some boards will indicate this in properties listing for CPU).
New microcode to be applied at OS load using VMWare tool (or do nothing and let OS manage microcode patch level).

[carson512]

Thanks.Will check for remove microcode.

[peylight]

@carson512 Can you contact to me?

[freecableguy]

How can I help?

[carson512]

recently solved the bios problem.In HWinfo show none uCU.

Use EFI Shellx64 or other suitable UEFI shell to set automatic load (and execution) of v3x4.efi during system boot. Use cmd ' bcfg driver add 0 fs1:\EFI\Boot\v3x4.efi "V3 Full Turbo" ' where 'fs1:\EFI\Boot\v3x4.efi'

but use this way seem not funtion.Still x26 ratio...How to check the problem...

so i try add E5-50.ffs to the bios file. the ratio chang to x30 but can't lock.(maybe the TDP?)
system have two 6 Cores 12 Threads CPUs.So it have 12Cores 24 Threads.
but windows 10 use HWinf or CINEBENCH just found 10Cores 19 Threads.

[freecableguy]

Be sure to Enable C3 and Disable C6 in BIOS.
C6 is borked for Haswell-E (errata) and was never corrected... C3 enabled sets the bit to allow for "opportunistic" clock increases.

Recommend CPU Package limit C0/C1, C1E Enabled, and check Turbo Boost Enabled in CPU power configuration.

If BIST (CPU feature configuration) is enabled, Disable.

Injecting .EFI -> .FFS into BIOS for flash only works for single-CPU boards.
You indicated you're using a pair of 6-core Xeons and so this method is off the table for you.

Locate the .EFI driver file on an UEFI-accessible partition and add to driver load chain using the 'bcfg' (boot configuration) command above. Check that the item added to BIOS is set to Enabled.

Load a uCode at Windows boot using the VMWare tool previously linked: I use 0x27.
Running un-patched uCode is bound to cause problems.

[ahzay]

Hi, commenting much later but there has been recent development. There is a russian tool called S3TurboTool which allows for generating a DXE driver along with the SVID/FIVR hack which is added into the bios using UEFITool. The process is detailed here: https://github.com/Koshak1013/HuananzhiX99_BIOS_mods and I've attached a translated screenshot of the tool.

However me and other users on overclockers.ru seem to still be hitting the TDP limitation despite the SVID bug exploit. How can that be? Are you able to maintain all-core turbo for extended amounts of time with your driver? for example my 2x2680V3 only stay at 3.3GHz for about a minute before throttling down to 2.8GHz despite thermals being low. Undervolting seems to make the boost last a little longer but TDP limits are reached nonetheless.