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.

Latitude E6400 Owner's Lounge, Part 2

Discussion in 'Dell Latitude, Vostro, and Precision' started by Commander Wolf, Oct 6, 2009.

Thread Status:
Not open for further replies.
  1. John Ratsey

    John Ratsey Moderately inquisitive Super Moderator

    Reputations:
    7,197
    Messages:
    28,839
    Likes Received:
    2,157
    Trophy Points:
    581
    It's possible that Windows 10 doesn't let RMClock work properly - those temperatures are very low if being read correctly. What does HWiNFO > Sensors show?

    I don't know how well ThrottleStop works with older hardware but it would be work trying it.

    John
     
  2. slander

    slander Notebook Guru

    Reputations:
    0
    Messages:
    66
    Likes Received:
    1
    Trophy Points:
    16
    Thanks John.

    RMClock (and TaskManager>Performance) and HWiNFO show different readings for Temps; ~5C more in the latter. Screenshot:
    [​IMG]

    I have also enabled SuperLFM (multiplier 6.0x) in RMClock and for my 'Power Saving' profile, it is the only active multiplier. Here, RMClock (and TaskManager) shows the cores dropping down to ~800Mhz, but HWiNFO shows ~1600Mhz. Screenshot:
    [​IMG]
    Aren't they using the same sensors? Why the different readings? I would assume RMClock is correct because the readings are approximately the same as those in Task Manager... yes?

    Finally, in HWiNFO > SMART... why does the 'Drive Warning' sensor show Yes? What exactly is the warning about? Is my drive about to fail?

    PS: I've tired ThrottleStop; I prefer RMClock. I'll try the former again if I am not able to satisfactorily continue with RMClock.
     
  3. unclewebb

    unclewebb ThrottleStop Author

    Reputations:
    7,805
    Messages:
    6,411
    Likes Received:
    6,706
    Trophy Points:
    681
    @slander - I do not think that RM Clock can fix Chipset Clock Modulation throttling. The other problem with RM Clock is that it does not support 45nm CPUs that use half multipliers. The P8400 has a default multiplier of 8.5 but it also uses an IDA multiplier of 9.0 so this multiplier limitation might not be a problem for you.

    Some monitoring software does not correctly detect when these CPUs are using SLFM mode. Some monitoring software reports that the multiplier is decreasing when inside the CPU, it is actually the Front Side Bus MHz that drops in half. Some monitoring software does not report anything when the CPU enters SLFM mode. ThrottleStop should report this correctly.

    If you want to stick with RM Clock that is OK but you might have to run it along side ThrottleStop to get rid of the throttling issue. If you want to do this, do not use the ThrottleStop Set Multiplier or voltage adjustment features. Leave that to RM Clock.

    A slow CPU used to be a great way to save power until the low power C States were developed. Holding a CPU to a low speed will reduce performance but it might not reduce power consumption as much as you think. A fast CPU that can get work done quickly which allows the CPU cores to spend a bigger percentage of time in the low power C States.

    http://www.cs.berkeley.edu/~krioukov/realityCheck.pdf
     
    Last edited: Apr 28, 2016
    John Ratsey likes this.
  4. CuterKiller

    CuterKiller Notebook Enthusiast

    Reputations:
    0
    Messages:
    36
    Likes Received:
    0
    Trophy Points:
    15
    Last edited: Aug 7, 2016
Loading...
Thread Status:
Not open for further replies.

Share This Page