Jump to content

kevindd99202

Registered User
  • Posts

    8
  • Joined

  • Last visited

Posts posted by kevindd99202

  1. Because that CPU/mobo/cooling combination apparently doesn't breach its TDP limits...even identical cpu models on the same system often behave slightly differently...

    Glad the mod worked for you! Looks like I'll have to make 2T mods public as they behave differently to automatic 2T mode...as if it is not enough time spend already to maintain all those mods... :P

    Ah, so this behavior is normal for a laptop?

  2. The CPU Turbos up to its TDP limit for a certain amount of time and then throttles, you can raise TDP limits in XTU or, if the cooling is sufficient, even avoid throttle all together. Some CPUs don't even reach thrir advertised maximum Turbo Speed without those manual adjustments.

    Saw it on Sager, haven't checked or seen stock Clevo versions yet...

    Understood, but what I'm wondering about is why does it not happen on my desktop with an i5-2500K CPU? That also has Turbo.

  3. I would say that's the regular temp or TDP throttle = to be expected

    Well, it isn't supposed to be throttling when having regular operations, right? My average temps are in the mid-50's. With my desktop computer, I can reach up to 90C and I don't get those event viewer errors?

  4. Prema, regarding the BIOS mod you gave me for my NP8130 I see some Warning events under event viewer with this message:

    The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 3 seconds since the last report.

    Is that normal?

  5. That is simply an invention "made by Sager", which we could never get out of peoples heads.

    One guy had flashed a Clevo BIOS on his Sager and when he asked Sager for an update they gave him a BIOS which was not compatible with the EC version (it would not have been compatible even if his system would have had the Sager version of the same EC).

    So he bricked his system, because of Sager's oversight, and Sager blamed him and started the "Sager's Cross-flash Myth".

    In case someone is uncertain about the compatibility of a certain BIOS with an EC, then we can just remove the "/SHUTDOWN %1 %2 %3 %4" commands from the ".bat" file and flash the latest EC and, without to shut the system down in between, the latest BIOS right after that.

    (On the HM series only the oldest EC is not compatible with the later BIOS revisions if I remember correctly)

    On the EM/ER/ET series on the other hand we can not downgrade to very old versions even if we flash BIOS & EC at the same time.

    (Just before moving to BIOS/EC 1.02.xx, so during the last few 1.00.xx versions, Clevo made some fundamental changes which cause a brick while trying to go back with regular updates) :untroubled:

    Does that mean that in my NP8130, I can flash a Clevo or Sager BIOS back and forth without any problems as long as my EC version is the latest?

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.