If this feature is not locked by the bios, you can also try increasing these power limits in ThrottleStop.Īlways interesting to see this unique problem fully exposed.
If you are not getting the full 36.00 multiplier then you can try to increase the Turbo Power Limits in the bios. If you are bored, try running another test and snap a screen shot of IBT and ThrottleStop during the 9th test before it ends. When hyper threading is enabled, the GFlops drop about 10% so that explains some of the difference but there is still a significant difference between the Xeon and the 3570K. IBT / LinX / Linpack testing will show higher GFlops on CPUs that do not use hyper threading. The multiplier was steady at 45.00 when overclocked but I took the screen shot a few milliseconds after the benchmark had ended so you can see the multiplier and C0% load numbers starting to drop. RealTemp and ThrottleStop share a lot of the same code. The next version of RealTemp will let you disable BD PROCHOT. You are not the only person with this motherboard bug.
Better yet, download RealTemp because it does a lot better job of tracking your multiplier, especially when your CPU is lightly loaded.
You should update CPU-Z to the latest version. When you use ThrottleStop to disable BD PROCHOT, the last digit in 0x1FC changes to 0圎.Īnd now your CPU is allowed to use Turbo Boost in Windows too. That means all 4 of the above bits are set so when you boot up in Windows, BD PROCHOT is set, a bad sensor tells your CPU to throttle so the CPU throttles. The last digit in MSR 0x1FC when you are in Windows is 0xF. This OS has disabled the BD PROCHOT feature. That explains why the multiplier works correctly when you are in Linux. A bench or two and watching the multi should be able to confirm if you need to do this or not. On some locked CPUs, you might need to have at least C3 enabled in the bios in order to get full Turbo Boost.
With this problem, I do not think a future bios version will change anything unless this broken sensor is disabled.Įdit: Try doing some single threaded benchmarks like Super Pi Mod and keep a close eye on the multiplier that ThrottleStop reports while the bench is running. Glad to see your CPU running like it should.
Go to the second post in the Guide thread if you need an example of how to do that. You can also add ThrottleStop to your Start Up sequence by using the Task Scheduler. You can use ThrottleStop to disable BD PROCHOT and then automatically exit so you won't have to worry about this anymore. This will force ThrottleStop to exit 5 seconds after it starts. ThrottleStop has an INI option that is useful. Disabling this signal path simply prevents anything else from throttling the CPU. When you disable BD PROCHOT, your CPU will still slow down if it ever gets too hot and needs to. As soon as you uncheck BD PROCHOT in ThrottleStop, this tells the CPU to stop listening to this Processor Hot signal that is being sent to it.
It is likely that this sensor is not working correctly so it is constantly sending this signal to the CPU. This in theory would allow the voltage regulator to cool down and then after a while, it would stop sending this signal to the CPU so it could get back up to full speed. For example, if the voltage regulator was running too hot or drawing too many amps, it would send a signal to the CPU to tell the CPU to throttle back to its minimum speed.
This feature allows other sensors on the motherboard to send a throttling signal to the CPU. If you are still having problems, post some screen shots of ThrottleStop so I can see how you have it setup.īD PROCHOT stands for bi-directional processor hot. If that doesn't fix things, uncheck the BD PROCHOT option. Here's a guide if you need some help but it's a lot easier to just start the program and try clicking on a few options.Ĭlick on Set Multiplier and set that to Turbo and then click on the Turn On button. You can also use ThrottleStop to disable the BD PROCHOT signal if that is causing the problem. The other problem is that sometimes the board will send the CPU a BD PROCHOT signal which is basically something on the board telling the CPU that it is too hot so it forces the CPU into thermal throttle mode which locks the multi to 16. Give ThrottleStop a try to see if it can help you out. The bios might not have any idea what a Xeon E3-1240 is so it will set the CPU to a safe multiplier which is the minimum 16 multiplier.