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.

    Disabled BD PROCHOT and CPU Temp Increase?

    Discussion in 'ASUS Gaming Notebook Forum' started by Spiritus777, Apr 7, 2012.

  1. Spiritus777

    Spiritus777 Notebook Enthusiast

    Reputations:
    0
    Messages:
    39
    Likes Received:
    0
    Trophy Points:
    15
    When I disabled my BD PROCHOT on my G53SW, I noticed that the CPU temps are reaching high 60's C to 70's C just from surfing the web. It went back to high 40's C once I re enabled BD PROCHOT. Can you guys share your experience with disabling BD PROCHOT and it's affect on CPU temp? I'm using Core Temp 1.0 widget to monitor my CPU temp.
     
  2. moral hazard

    moral hazard Notebook Nobel Laureate

    Reputations:
    2,779
    Messages:
    7,957
    Likes Received:
    87
    Trophy Points:
    216
    When you disable that, you disable or reduce some CPU throttling, which is good for performance, but you get more heat.
     
  3. steelblueskies

    steelblueskies Notebook Geek

    Reputations:
    15
    Messages:
    95
    Likes Received:
    0
    Trophy Points:
    15
    few days late but .. well .. o_O

    disabling a throttle cpu because this other component is too hot signal, which unfortunately also tends to trigger erroneously, *SHOULD NOT* be causing a jump of 20 to 30 degrees C while just browsing the web. practically speaking running the same test on the same hardware there is ZERO net temp difference between action taken with the msr fo prochot disabled or enabled.

    my guess is you are using throttlestop to enable/disable it, and turning throttlestop on, which in turn is throwing you into a custom power management state.

    disabling it only requires running ts then exiting, not turning anything on, or clicking anything in the program, or leaving it open.