bios update for hp omen 17t cb-0000 F35 ?

did anyone update to bios F35 ? just want to make sure before I update that it doesnt lock the undervolting ability ? thanks

 

It doesn't, it's good. But be careful with the new version of OCC, now OGH. There are some instances where it will revert to a 45W PL1 and 28 sec tau that Throttlestop can't override. You can disable the OmenCAP service to prevent this, but then OGH will run somewhat crippled. I regret having not kept the last version of OCC. Don't use the new undervolting feature, the automatic will intentionally crash your system leading to some ssd errors that need fixing, and it undervolts the core and cache together which is sloppy. The new lighting hub is a CPU hog. I played with this stuff for a week before getting rid of it, meaning disabling lighting hub, xtuservice, and Omen CAP. This is a throttlestop machine.

I can only speak for the 9th gen.

 

I have the 9th gen that bios lists support for windows 10 20h2 im afraid i will be missing some features if I dont update

 

Hi!

I'm facing the same problems. Currently OGH is fighting with Throttlestop changing my UV and PLs even if I turn off the UV feature, sometimes it sets itself to 'custom' with -0.125mv in both core and cache, while my custom UV with TS is -0.250 cpu and -0.125 cache.

In all honesty I would remove completely OGH, but I noticed that If you don't have it installed, the laptop will use the 'default' profile, meaning the CPU will be limited to PL1 of 45w and the GPU (in my case an rtx 2070 mq) to 80w instead of 90w.

Is there a way to control the fans, power limits for both cpu and gpu without using this crap of software?

 

Yes, someone helped me with that it's in the owner's lounge thread I believe, using Notebook Fan Control. I still keep OGH functional though, the Max fan is just easier.
OGH installs Intel XTU underneath itself (that's the Omen SDK, or part of it) that runs the undervolting and some of the parameters. Disabling the XTU service prevents this interference. However the OGH buttons will still switch around the turbo limits (mine never leaves Performance which is 90/90, or used to be when it was OCC) but Throttlestop overrides it. With it disabled, the undervolting tab will complain that it needs the component installed.
Someone else noted the annoying activity spikes every 30 seconds that jump the CPU temps while idle. That seems to be OmenCAP. Disabling that service smoothes out the temp/power curves at idle but OGH will then moan with a popup box that it's broken. All the useful functions still work though. OGH will error box upon start but still functions.
I discovered this after all the updates while benchmarking, it was only running 90W for 28 sec and dropping down to 45. So HP either changed what the buttons do (due to temp complaints I'm sure), or it's a bug where if it hits thermal limit it reverts in a hard manner, or they've implemented a switch where it PL1 drops with the standard timer IF the GPU is active. I haven't tested this but it's possible I had Edge open while benchmarking, which raises my GPU frequency from idle.

 

There aren't any new features that are that exciting. I tried the undervolting and quickly went back to using Throttlestop. Lighting Hub is in the Microsoft Store by itself, you can try it by itself without trashing OCC. I wish I had kept the final version of OCC but oh well. There's probably no way to go back to it, other than a system image I made back in November.

 

nice, so disabling the XTU service and omenCAP might help. One can only wish to have an open source laptop command center

 

I actually got an interview from a PR company about OCC, HP reached out to me a few months after having bought the machine. I thought it was totally bizarre to be interested in customer reaction to the software and not the laptop itself (which was very problematic out of the box but I kept), but they were extremely interested in online features of OCC we use, what we wanted to see, how did I feel about this and that streaming/gaming hub/social whatever. I, of course, stressed my disgust with packaging the critical, proprietary utilities needed to fully use the machine with all this other stuff, but apparently no one listened. I think some MBA at HP is thinking "why can't we turn buying a gaming laptop in to using a gaming laptop as a service!" Probably got a promotion.
I have the selectable telemetry turned off but there are still several HP services that I haven't disabled yet, like touchpointanalytics, etc. Not to change the subject of this thread but I'd be interested in hearing more about the more privacy minded people than me have to say about the issue.
I much prefer how MSI did this stuff, Dragon Gaming Center just controlled the machine quite nicely, that was it. No endless updates changing the functionality, other than adding a little more fan control.
Of course ideally all this stuff could be done in BIOS requiring no software whatsoever, and a hot key for max fan.
I also made clear that the next Omen 17 should absolutely not be a MaxQ or they will lose my interest. The entire appeal of this machine is that it's competitive with $4K MSIs and Alienwares, while being a somewhat compact, affordable alternative. And HP includes features like Thunderbolt and makes things like a 4K screen affordable.

 

Well I just sent them a feedback email when the OGH asked me if it "missed the mark" and told them that we need more features present in Throttlestop like separate voltage offsets for cpu core and cpu cache.

And yes, I agree with you, a command center should only include knobs and levers to control the damn laptop. But sadly we've been for several years with this hardware as a service trend.

Regarding all those services installed by the SDK I'm honestly afraid to stop at least XTU service because it completely screws up or used to when I tried, the Intel Optane memory management.

If you have (in my case I have an H10 optane SSD) and you disable the XTU service it will try to rebuild the whole optane memory, because I quote from other users that I read months ago 'it uses the CPU cycles to determine which processes should be cached'

And it was true, after I disabled that service, the CPU would ramp up to 100% for several minutes, rebuilding the cache, then a few minutes of idling, again doing the same stuff in an endless loop.

It was a complete mess for me, so considering that I'm between a rock and a hard place (OGH v/s TS) i'm quite screwed.

I've been a laptop user for a decade, I really love them, but my next PC will be a desktop. We don't own the laptops, the manufacturer does.

 

Me too. I have an ultrabook for travel that's great, but can accept its limitations. The fact that Intel is making laptop chips that need 90W to hit their all core turbo is just unmanageable, and the manufacturers simply go with this combined heatpipe system and let thermal throttling handle it.
BTW one of the first things I did was swap out the H10. Nothing but problems.

 

I think (it's been a week doing this) I found a simple trick to make Throttlestop win the battle with OGH over the control of the undervolt

when OGH updates through the Microsoft store it turns on the UV feature, and overrides my custom UV in TS. That's when I found that some weird UV value was applied like -0.125 mv or 0 mv using "default" for both cpu and cache offsets

If I disable the fast boot with powercfg -h off, and let the system boot a fresh start, the UV applied with TS will prevail. and the feature in OGH will remain off.

I still check from time to time in OGH to see if it's OFF, and so far I'm quite sure it has updated (new layout in system vitals since last week and new version number)