Hello ROG'ers, long time no talk.
🙂 Been having a weird problem lately, was wondering if anybody else has seen this: For some reason, kb3000850 ("November 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2"), which was recently re-released on April 23, 2015, causes the system to ignore Additional Turbo Voltage. I think the update might be messing with MEI's sense of the cpu's c-states? With the offending Windows Update rollup installed, the system applies Offset vcore (by itself) to achieve stable voltage, but the system will NOT apply any "Additional Turbo Voltage" (from the CPU Power Settings menu).
i.e
before the update: VID 1.27 + Offset .025 + Additional Turbo Voltage .05 = ~1.34v @ x46
since the update: VID 1.27 + Offset .025 (Additional Turbo Voltage .05) = ~1.29v @ x46
for stability since: VID 1.27 + Offset .07 + Additionaly Turbo Voltage .00 = ~1.34v @ x46
In other words, the outcome is the same with or without Additional Turbo Voltage because the system simply doesn't do Additional Turbo Voltage anymore. (*note, I'm recounting these figures from memory as I'm not at my pc right now... they may not be 100% exact, but you get the idea)
It seems logical that the problem would be Windows' *REPORTING* of the voltage rather than the actual voltage itself, but it does to be somehow actually BLOCKING Additional Turbo Voltage from being applied as the system BSODs if I run Cinebench or Realbench, whereas at my known stable voltage (~1.344v) using ONLY vcore Offset it's rock solid stable as it has been for years. Notably, XTU still shows Turbo enabled and functioning AND shows the Additional Turbo Amount set per my bios/uefi instructions even though the Additional Turbo Voltage is not being applied. Perplexing. Temperature readings seem to be messed up, too, it reports ~10 C less than expected (though I can't be sure if maybe that's accurate because of the borked voltage)
Also, earlier this week I installed Windows 10 preview, and even with a clean install with nothing else installed, the exact same problem. Natively, Windows 10 seems to cause the system to either not apply or not recognize Additional Turbo Voltage.
I'm perplexed by the idea of Windows changing BIOS hardware control; and also curious that I haven't heard of anybody else experiencing this. The only thing I can think of is that Offset vcore + Additional Turbo Voltage + c-states & EIST enabled is an uncommon setup? Offset vcore with c-states disabled seems to be the most common setup, but I prefer to have mine tuned as tightly as possible. It's been rock-solid stable for almost 2 years... but it would seem maybe the outdated drivers need an update?
tl:dr: it seems that something Microsoft did in the last couple of months is messing with Asus's drivers mobo drivers and/or hardware? Has anybody else seen or reported this? Raja? I know X79 is old news now, but can we expect any Black Edition driver or bios updates in the wake of Windows 10? It seems they will be necessary.
Asus RIVBE • i7 4930K @ 4.7ghz • 8gb Corsair Dominator Platinum 2133 CL8
2xSLI EVGA GTX 770 SC • Creative X-Fi Titanium • 2x 840 SSD + 1TB Seagate Hybrid
EVGA Supernova 1300W• Asus VG278H & nVidia 3d Vision
Phanteks Enthoo Primo w/ custom watercooling:
XSPC Raystorm (cpu & gpu), XSPC Photon 170, Swiftech D5 vario
Alphacool Monsta 360mm +6x NB e-loop, XT45 360mm +6x Corsair SP120