• 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.

i7-9750H issues after reinstalling Windows and replacing RAM

dan335am

New Member
Joined
Jan 10, 2023
Messages
7 (0.01/day)
Hey @unclewebb , can you help me please?

I reinstalled Windows today, due to the replacement of a new SSD in RAM.

The config is the one you advised me, but in Throttlestop, turbo ratio limits shows some strange numbers, also it is not possible to change the voltage to the default value

HP Pavilion Gaming 15 dk0090ur
New SSD Samsung 1TB M.2 NVme
RAM Hikvision DDR4 32GB 3200Mhz
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    63.3 KB · Views: 64
  • Screenshot_2.png
    Screenshot_2.png
    63.7 KB · Views: 69
  • Screenshot_3.png
    Screenshot_3.png
    19.5 KB · Views: 65
  • Screenshot_4.png
    Screenshot_4.png
    50.3 KB · Views: 62
  • 2023-01-17.txt
    2023-01-17.txt
    229.9 KB · Views: 59
Solution
turbo ratio limits shows some strange numbers
You have to disable Windows 11 Virtualization Based Security if you want ThrottleStop to have full access to the CPU. The weird looking values in the Turbo column in the FIVR window and the 0.3799 voltage numbers in the monitoring table happen when VBS is left enabled.


After VBS including core isolation memory integrity are disabled, reboot, and delete the ThrottleStop.INI configuration file.

Post some updated screenshots.
turbo ratio limits shows some strange numbers
You have to disable Windows 11 Virtualization Based Security if you want ThrottleStop to have full access to the CPU. The weird looking values in the Turbo column in the FIVR window and the 0.3799 voltage numbers in the monitoring table happen when VBS is left enabled.


After VBS including core isolation memory integrity are disabled, reboot, and delete the ThrottleStop.INI configuration file.

Post some updated screenshots.
 
Solution
Back
Top