• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Xiaomi notebook pro 8550U (TM1701) voltage offset not applying, wrong readings

Joined
May 31, 2016
Messages
12 (0.00/day)
Processor 12700KF x49-x52
Motherboard Asus PRIME Z690-P D4
Cooling NZXT Kraken 360
Memory B-die 4x16GB 3400CL16 tuned
Video Card(s) Gigabyte RTX 4070 Gaming OC
Storage Samsung 2TB 980 Pro + more
Display(s) XV275U 1440p 170Hz mini LED + 2 more
Case NZXT H6
Audio Device(s) SMSL SU-8 -> Drop 789 -> Audeze LCD-2C/AKG K7XX, Presonus Eris E5 XT
Power Supply Corsair RM850x
Mouse Lamzu Thorn, X-raypad Aqua Control Plus Wave 3XL
Keyboard Keychron V10
Benchmark Scores https://www.3dmark.com/spy/43578324 https://www.3dmark.com/sn/4858
I'm stumped, I can't figure out why my voltage offset fails to apply. All sort of wrong readings. Win11 home, virtualization is disabled, memory integrity is disabled. Changing powerlimits works fine. Tried a handful of Throttlestop versions between 8.6 and 9.6. I'm 100% sure I had this working with a -100mv undervolt before I reinstalled a fresh windows, but I can't figure out how I got it working before. I have not updated BIOS in between, still on the same old 0300. Any thoughts?
 

Attachments

  • Screenshot 2024-11-14 094503.png
    Screenshot 2024-11-14 094503.png
    800.7 KB · Views: 51
... turns out VBS is still running. Why are you running?
 

Attachments

  • Screenshot 2024-11-14 163739.png
    Screenshot 2024-11-14 163739.png
    69.2 KB · Views: 41
  • Screenshot 2024-11-14 163808.png
    Screenshot 2024-11-14 163808.png
    87.7 KB · Views: 39
  • Screenshot 2024-11-14 163901.png
    Screenshot 2024-11-14 163901.png
    100.5 KB · Views: 42
  • Screenshot 2024-11-14 163927.png
    Screenshot 2024-11-14 163927.png
    140.4 KB · Views: 41
... Why was the solution turning memory integrity back on, and then turning it back off again. Thanks windows, very microsoft of you. Leaving this for posterity.
 
Back
Top