The ThrottleStop Guide

Discussion in 'Hardware Components and Aftermarket Upgrades' started by unclewebb, Nov 7, 2010.

  1. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    9,007
    Messages:
    10,837
    Likes Received:
    8,140
    Trophy Points:
    931
    Maybe there's a defect in the board or the BIOS itself. Generate a battery report from Windows using this guide https://www.windowscentral.com/generate-battery-report-windows-10

    powercfg /batteryreport /output "C:\battery_report.html"
     
  2. Kocane

    Kocane Notebook Deity

    Reputations:
    395
    Messages:
    1,623
    Likes Received:
    15
    Trophy Points:
    56
    I'll give it a go when I'm home. Right now the M2 SSD resides in my work laptop (which had working c-states before) and c-states stopped working again. That's two laptops (same generation etc) with the problem. I don't have any other M2 SSD to test with (2242mm isn't too common) so I can't test if it's the port on the laptop or the M2 itself. It's just odd that I can't install new Windows and have working c-states on either laptop. I tried Windows 8.1 yesterday and I had working C3 state when power saver profile was selected, but not C6 or C7. When I installed Intel RST driver that stopped working all together.

    What an awful experience this is, Jesus... and it's even a CPU that's meant to be powersaving.
     
    Vasudev likes this.
  3. keshavmot2

    keshavmot2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    12
    Trophy Points:
    6
    I keep getting the error "Could not open WinRing0.dll" on the latest Insider build (16273). It was working before I updated to this latest build today. Is anyone else experiencing this?
    Thanks!
     
  4. unclewebb

    unclewebb ThrottleStop Author

    Reputations:
    7,244
    Messages:
    6,040
    Likes Received:
    5,585
    Trophy Points:
    681
    Maybe Microsoft has finally pulled the plug on ThrottleStop. This has always been a possibility. :(
    Thanks for the info. I will be avoiding that build until I hear more.
     
    duttyend and HagsterZx like this.
  5. keshavmot2

    keshavmot2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    12
    Trophy Points:
    6
    Is there any testing I might be able to help with?
     
  6. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    9,007
    Messages:
    10,837
    Likes Received:
    8,140
    Trophy Points:
    931
    Have you tried in compatibility mode using W7/8.1?
     
  7. keshavmot2

    keshavmot2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    12
    Trophy Points:
    6
    Just tried it, but same error :( As soon as I rolled back to 16257, it works fine again, so it is the new build I think.
     
    duttyend likes this.
  8. Vasudev

    Vasudev Notebook Nobel Laureate

    Reputations:
    9,007
    Messages:
    10,837
    Likes Received:
    8,140
    Trophy Points:
    931
    Did you notice anything about VC++ 6 or something being removed in the changelog?
     
    duttyend likes this.
  9. plee82

    plee82 Notebook Evangelist

    Reputations:
    95
    Messages:
    507
    Likes Received:
    361
    Trophy Points:
    76
    Welp, MS is killing it. I guess they want you to use XTU.
     
  10. keshavmot2

    keshavmot2 Notebook Enthusiast

    Reputations:
    0
    Messages:
    18
    Likes Received:
    12
    Trophy Points:
    6
Loading...

Share This Page