Throughout the day and into the early evening when it looks like you are not using your computer, the multiplier is OK.
When you put a load on the CPU, it drops to a steady 40 so that all looks fine. On the other hand, I have no idea how you had ThrottleStop setup during your 13 hour session, I have no idea if you made any changes to ThrottleStop or to your Windows power plan, or what exactly you were doing at any point during that log.Įarly on, the CPU multiplier is spending most of its time in the 40 to 42 range which is what it should be doing. I usually have to beg people to see some data. On the one hand, you should be commended for uploading 13 hours of log file data. Sometimes they might get it right but often times they miss and get it wrong. Most other apps are throwing darts at a moving dart board. ThrottleStop uses high performance timers within the CPU and is able to report a very accurate average multiplier when this is going on.
As soon as a second or third or fourth core becomes active, the multiplier immediately drops from 42 to 40. The full 4200 MHz will not be seen during this test because there are always hundreds of Windows background tasks running that are waking up additional cores on a regular basis. With Intel Turbo Boost and C3 or C6 enabled, you should see lots of evidence of your CPU going beyond 4000 MHz. You can copy and paste log file data to or attach a log file to your next post. The problem with some monitoring software is they are waking up inactive cores and then showing something like 800 MHz which is not accurate. Those cores are dormant at 0 MHz and 0 volts. Inactive cores that are in one of the C states like C3 or C6 are not using any multiplier. The active cores are all physically locked to the same multiplier. For your Intel CPU, at any moment in time, all active cores are using the exact same multiplier.
0 kommentar(er)
