Made some modification

1st now CAS 18 @ 3ghz 2x8GB - 18-18-38-18-1T :) give me extra bandwith was 19-19-43-19-1T before

i undervolt - 50 mV the uncore

TCC activation offset to 5

All these voltages was SRY WAS DOWNED by 50mV

now 1150 - 950 - 975 -1150 - 970 - 900 for the last (unstable if downed) and 1800 ohms (unstable not booting below this)






Then 5minutes run

63W then throttled back to 56W run 10 mins

DTS is good idea to be enabled (if disabled CPU main temp sensor will show always 28C), VCC for SA (System Agent) is always ~ 1V, I think there is no point to change it in laptop it will probably give placebo taste.
I could get stable 3000Mhz CL19 from my Kingston 2666Mhz CL19 with few clicks in BIOS :)

It's really hard to buy 3200MHz or higher SODIMM in my country, best compromise would be G.Skill 3000MHz CL16 (price/performance).
I'm very curious about flashing modded bios - if it will work (right away or with some driver fixes) it would be great info for me :)

BTW @saltinbank I found a way to control our Helios 300 fans manually to achieve real idle fan stop and quiet work mode for light loads ;)
It took me almost 3 days of thinking and testing - all those goods possible without editing BIOS/EC firmware or even using/modding PredatorSense.

It should work on Linux also if you disable SecureBoot (quite easy to do) and establish connection with your EC - which is not that hard (EC Probe from NBFC for example).

Performance under linux are prety good i do 4.49 ghz on one core and 4.1 on 6 cores and the app i used are not throttling ...
Under windows i will let at it is : game are non using more than 42W so i dont care it was for the pleasure of tweaking this laptop and see the guts it has :)

As I found it is not possible to exceed 56W barrier but at least you can able to set this 56W to any profile you want not only on turbo
And funny thing is that you don’t need unlock bios to do it you can change it in XTU directly
But interesting thing is that until you install PS you can set 56W in XTU! And only after installing PS you can do it, I suppose that during installation PS it sets some flag somewhere maybe in EC?

Zitat von saltinbank im Beitrag #166

---

All these voltages was SRY WAS DOWNED by 50mV

now 1150 - 950 - 975 -1150 - 970 - 900 for the last (unstable if downed) and 1800 ohms (unstable not booting below this)

---

I didn't saw anything special while activating Turbo mode, maybe there will be some registers, but after short while I didn't saw which one is responsible for activation.
All those laptop app comes with modified/special version of XTU app and services (also drivers), PredatorSense is no different.
I had HP Omen 17 (2019) same situation every change to CPU performance was done thanks to XTU service.

Zitat von saltinbank im Beitrag #169

---

Performance under linux are prety good i do 4.49 ghz on one core and 4.1 on 6 cores and the app i used are not throttling ...
Under windows i will let at it is : game are non using more than 42W so i dont care it was for the pleasure of tweaking this laptop and see the guts it has :)

---

@saltinbank PL2 state is short turboboost - totally not worth it.
If you mean PL1 it's still hard to push it for more than 128 seconds in Helios 300 (upper limit).

I think lowering SA voltages etc. will not gain you as much as might think - from power perspective it might be pointless.
From CPU perspective I found that ~ 70W is optimal power draw for all cores and threads at 100% load (4GHz) while beig factory UV-ed.
Without UV power draw will be significantly higher.

Zitat von mikolaj612 im Beitrag #172

---

I didn't saw anything special while activating Turbo mode, maybe there will be some registers, but after short while I didn't saw which one is responsible for activation.
All those laptop app comes with modified/special version of XTU app and services (also drivers), PredatorSense is no different.
I had HP Omen 17 (2019) same situation every change to CPU performance was done thanks to XTU service.

---

All those apps comming with XTU for few reasons :
- XTU profiles (easy to make - easy to set),
- proper and signed drivers,
- you couldn't mess anything (theretically).

ThrottleStop or even NBFC is using WinRing0 driver that could be rejected on some Windows 10 version due to memory integrity check (it needs to be disabled in Windows Defender/Secutiry Center).
According to my knowlegde and testing reading/writing EC regions on Linux will require SecureBoot to be disabled (you could do that when you set password in bios), if SB is enabled (by default) Linux won't let you in no matter how hard you will try.
On Windows is much easier to gain access via RW Everything for example.

Zitat von mikolaj612 im Beitrag #168

---

BTW @saltinbank I found a way to control our Helios 300 fans manually to achieve real idle fan stop and quiet work mode for light loads ;)
It took me almost 3 days of thinking and testing - all those goods possible without editing BIOS/EC firmware or even using/modding PredatorSense.

It should work on Linux also if you disable SecureBoot (quite easy to do) and establish connection with your EC - which is not that hard (EC Probe from NBFC for example).

---

My previous HP Omen 17 on performance mode got 90W for CPU (I had i5 9300H version).
At full power that i5 draw 50W of current and always provided me stable 4GHz boost no matter what I was doing.

@Hyppo
I found Windows 10 1903/09 or even newest 2004 (20H1) are kinda not optimized/bugged and won't let my CPU going to lower C states as it supose to do while idling.
This is the reason you see that kind of temps - they're not critical in any manner, but might be confusing for longer sessions.

Later this week I will try 1809 version which is often recognizable as best option for everyday usage.
As far as I remember I got my Helios 300 with 1809 preinstalled and I never saw such high current draw on idle and issues with going to deeper C states (like C6 or C7).
QuickCPU and ThrottleStop will easily inform you about current C state of your CPU.

For comparision - Xubuntu 1904 session (aprox. 2h on desktop, working with terminal and firefox) temp was ~ 45C for CPU most of the time.
So if there is an issue it must be hidden in Windows or drivers itself, especially when there is almost nothing launched/working in the backgound.

45C would be great temp while idle, even 50C will suit me well.

linux-intel-undervolt under linux let you set the TDP limits and undervolt on the fly ! without Psense

C state put it only in C1 mode ... forget (C2/3/4/5/6/7/8/9/10)
P-state are disabled for my part ...
And Cstate Motion/de-motion off

PLL 56/80W with - 170mv give me better performance in linux than windows btw

And Window 10 1803 idlling temps were 38/42C ... now they skyrocketed to 55/60C in 1903 ...