![]() Throttle Reasons shows "EDP OTHER" in all three columns during the test. On the other tablet, both valued freely soared to $A_LOT GHz and 100% for C0%. 58 for the m5-6Y54: something like 20 seconds slower! This didn't make any sense at all.ĭuring the test, the CPU never boosted above 1.49 GHz, and C0% never raised above 52%. the Surface actually did WAY worse, taking 77 seconds to complete the benchmark vs. Initially, the Surface did a bit better, but then I noticed that the Surface had 8 cores at its disposal. I disabled the undervolt on both, set the Speed Shift EPP multiplier to the same value (tried with 84 and 128), disabled BD PROCHOT on the Surface, then ran the benchmark. I took out the ThrottleStop benchmark for a spin side-by-side with the older device. Now I'm left with a device that won't undervolt and is being severely choked. Attempting to edit the UEFI variables to disable CFG-Lock on a device that cannot be opened to reset the CMOS and is prone to bootloops is a tad risky, and that's assuming I could find the CFG-Lock variable in the stock Microsoft UEFI images to begin with - they might be using another method, possibly a "new" microcode revision. Tried looking into downgrading the UEFI by forcing a UEFI capsule update with an older UEFI capsule, but Microsoft has patched that hole by raising the minimum version that one could downgrade to, to a version newer than the prior publicly-available release. on a CPU that was never vulnerable to begin with!Īnd it's just begging for an undervolt: the CPU measures around 0.74 volts, a full 0.20 volts higher than the m5-6Y54! The fun-at-parties people at Microsoft decided to completely butcher the device by locking the 0圎2 MSR in order to patch Plundervolt. With the above, I thought, "looks like a repeat of the HP Elite x2 then! I'll open up ThrottleStop, then undervolt it, problem solved!"Īlas. Therefore, it's intuitive to assume that the fanless i5-1035G4 in here is an evolution of the Core m5-6Y54, an m5-1035G4 if you will.Īlso, both laptops used up exactly 7% in exactly 15 minutes of benchmark testing - nor does it do any better in daily usage, with both getting at 4-5h of battery life, except that one battery is 6 years old, and the other is hardly two years old. Notably, both CPUs list 1.10 GHz" in the CPUID string viewable in Task Manager, both share a base frequency of 1.50 GHz, also viewable in Task Manager, and both are fanless designs. the only time the CPU clock speed goes above 1.50 GHz is when playing a video - and when it does that, the animations become noticeably more fluid.This is in stark contrast to the old HP, which freely boosts up to 2.50 GHz and beyond when interacting with it, then dropping back to 1.10 - 1.50 GHz when idle. with normal (web + office) usage, the CPU NEVER clocks above 1.50 GHz, preferring to stay around the base clock of 1.10 GHz.Looking in Task Manager, I could notice two odd things: I then tried disabling the Intel Dynamic Tuning Service as suggested online, but to no avail. So, I downloaded the Surface Recovery Image and reimaged it back to factory fresh.Īt first, I reluctantly attributed that to the HiDPI "PixelSense" display of the Surface compared to the 1920x1200 of the HP Elite X2 - but that got quickly disproven when I set the Surface to a close resolution and the issue still persisted. It was painfully obvious ever since booting it for the first time that something was wrong: every Windows animation is choppy!Īt first, I put it down to Windows needing an OS reinstall, especially since it's arrived with a Windows copy preinstalled. I bought myself a secondhand Surface Pro 7, with a Core i5-1035G4, 8 GB of RAM, and a 128 GB NVMe SSD, in the hopes that it'll be both faster and more efficient than the venerable, but tired, Elite x2. I used to own an HP Elite x2 1012 G1 that I've asked you about earlier this year: since then, it has behaved itself, with your awesome advice! But pain of a poor battery, along with the ache to upgrade, the temptation of a faster tablet with more battery is hard to resist. This is the exact headache I've been dealing with for the last few months now. You try to dismiss that as delusions, but the incessant alarm sirens just keep getting louder and louder no, you've definitely gotten screwed, and things are undoubtedly, undeniably, visibly, obviously slow. truly sorry, planned a short post, ended up ranting :-(įew letdowns in the tech world beat that of thinking that you've upgraded, only for that gradual realization that things have become slower, not faster, to sink in.
0 Comments
Leave a Reply. |