The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    11800H stuck in C2, can't access higher C-states

    Discussion in 'Hardware Components and Aftermarket Upgrades' started by kylezo, Dec 15, 2021.

  1. kylezo

    kylezo Notebook Geek

    Reputations:
    0
    Messages:
    91
    Likes Received:
    2
    Trophy Points:
    16
    Hello, maybe I'm reading the interface wrong, but I seem to be unable to access deeper cstates on my system (Eluktronics MAX-15 i7-11800H) and as a result I'm seeing very high idle Core VID and power usage.

    HWiNFO64 does show c7 residency, and the Core C States table in TS shows 90%+ in C7, but the package C States table is always 0 in every category except C2 (this is where I'm unsure of how to interpret the GUI readings).

    I have read a bit about AHCI Drivers etc preventing core parking, but I'm not sure which drivers I should be looking at if I need that kind of a solution. Maybe it's a BIOS issue?

    I did un-hide some processor power state management options in the windows power profile through the registry, but changing those values doesn't seem to have had any effect. I've included a screenshot of my TS window while my system is at idle (task manager shows system idle at 99%, there's not much going on in this system, very clean setup.)

    Thanks for any help or tips on reducing idle voltage/power consumption.

    [​IMG]
     
  2. tilleroftheearth

    tilleroftheearth Wisdom listens quietly...

    Reputations:
    5,398
    Messages:
    12,692
    Likes Received:
    2,717
    Trophy Points:
    631
    Why isn't this in the ThrottleStop thread?
     
  3. kylezo

    kylezo Notebook Geek

    Reputations:
    0
    Messages:
    91
    Likes Received:
    2
    Trophy Points:
    16

    Because this isn't related to throttlestop? I included a screenshot of it's c state readouts to be helpful. I could have just as easily included a screenshot of XTU voltage graphs or HWiNFO64 graphs. I can cross post it if that would please you. Of course, if you have any input on the topic rather than the post location, that'd be even more helpful.
     
  4. 4W4K3

    4W4K3 Notebook Evangelist

    Reputations:
    73
    Messages:
    452
    Likes Received:
    208
    Trophy Points:
    56
    In the past when I have had similar C-state issues and the idle wattage went up, I reset CMOS and BIOS to Factory Defaults and the cores began parking normally again. I then made all my BIOS edits again and the problem never reappeared. Firmware bug maybe?

    I use ParkControl software to force the PC to act right, along with ThrottleStop of course.
     
  5. kylezo

    kylezo Notebook Geek

    Reputations:
    0
    Messages:
    91
    Likes Received:
    2
    Trophy Points:
    16
    Thanks, I'll check out ParkControl. I reset the BIOS using the CMOS and it actually resulted in resetting my factory undervolt from Eluktronics, and now I have to have them flash the BIOS over teamviewer to restore it. In the meantime I've been using XTU to undervolt but it's not ideal. They told me that soon they'll be releasing a new Tiger Lake specific BIOS revision after the holiday rush that should have a lot more unlocked features. For now, it's pretty sparse. My old GS63 has a much more robust BIOS.
     
  6. Samot

    Samot Notebook Evangelist

    Reputations:
    224
    Messages:
    610
    Likes Received:
    334
    Trophy Points:
    76
    Are you connected to an external display? If so, disconnect it.
     
  7. kylezo

    kylezo Notebook Geek

    Reputations:
    0
    Messages:
    91
    Likes Received:
    2
    Trophy Points:
    16
    Hey, saw you in the other thread and replied there. Btw, I did try running with no display plugged in and it made no difference, which rules that out.