I've converted the latest intel microcode (revision 0x3d, with the meltdown/spectre patches) into a header form, suitable for compilation. Anyone willing to recompile a driver and get protection can get it here - https://raw.githubusercontent.com/dur-randir/306f2-ucode/master/0x3d.dat
Maybe because of I set uncore to max in it, not sure.
Have you tried Throttlestop? If it also doesn't work - you're stuck with experimenting with different BIOS options, as those msrs are completely undocumented by Intel.
Too much undervolt for your silicon) Here's a version without vcore...
As an alternative, you can try to enable ThrottleStop's PowerCut feature on a clean system (without any efi's loaded). If it also doesn't work than it's something to do with the BIOS.
No, with "error:vccin" you have everything as usual (and those 50mV are correctly accounted for). You'll see what happens if you get it working)
You can write to msr 0x620, say, 0x2323. On any one core - it propagates to all other. This sets uncore frequency limits to 35-35. It's successfully...
That's the core msr trickery failing( I can think of two possibilities:
- you've set a vccin override in bios that sets up a lock afterwards - try setting it to auto if you have such option
- you've done only a soft reset - try to shutdown and then load this driver to start from a clean cpu state
Can you try the following two EFI drivers? There's two modifications of the original V3_2 EFI with some additional msr hackery. I've compiled both v39 and uCode-less versions (I run v39 version on my system). They include 50mV vcore undervolting which is stable for me but may be unstable on your...
And if you place the following content into the local.txt file in the prime95 folder, would you be able to hit more that x34 multiplier?
CpuSupportsAVX2=0
CpuSupportsAVX=0
PS: impressive chip, I've persuaded myself only for double 2683's)
Can you run mprime (prime95) torture test with small ffts and then check frequency? I find it the most CPU demanding benchmark, far more demanding than linpack/renderers.
Supermicros are unlockable, though they require a manual BIOS editing. The only problem with them is that the BIOS lacks any...
@Ionstream ,
>this is a SuperMicro board
MMTool won't work with it. I've successfully modded X10DRi-T by an algorithm described at the beginning of this thread, when you manually modify 2 bytes of the microcode signature so it is no longer recognized as 306F2. There're four f2 06 03 00...
Cinebench R15:
No uCode ~3650
39 uCode ~3860
This is achieved with no BCLK overclocking and far from optimal memory configuration (2ch one cpu and 3ch another). So for a baseline I've made a run without any overclocking and no ucode loaded (I was too lazy to prepare a separate image) and got...
Hi @Welsper, thanks for your dual-xeon version, but I highly suspect some race conditions/other bugs in it. I'm able to hit stable 29x on a single socket with the original V3, but results vary from run to run with your V3_2 (from 25x mult on all cores to global freeze upon microcode update). So...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.