Does anyone have any experience with using ThrottleStop to boost the performance for the Surface Pro 7? I've tried using the tool to optimize things but can't seem to get it working properly. I don't use it much on battery, though I'd like to have a profile that works for when on battery just in case so it doesn't crush it too badly. My goal is to have as high of performance as possible while plugged in. Thanks
-
Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
Surface Pro 7 i5 Optimizations
- Thread starter donjjones
- Start date
unclewebb
ThrottleStop & RealTemp Author
- Joined
- Jun 1, 2008
- Messages
- 8,068 (1.33/day)
Post some ThrottleStop screenshots so I can see your settings. Main window, FIVR and TPL windows.
Turn on the Log File option so I can see how your CPU is running.
Your CPU is locked. If it has a throttling problem, ThrottleStop might be able to help.
Turn on the Log File option so I can see how your CPU is running.
Your CPU is locked. If it has a throttling problem, ThrottleStop might be able to help.
Last edited:
unclewebb
ThrottleStop & RealTemp Author
- Joined
- Jun 1, 2008
- Messages
- 8,068 (1.33/day)
Your laptop barely has enough cooling to run the CPU at 25W. Having PL2 set to 61W is overkill.
In the TPL window I would clear the Disable Controls box. I would set PL1 to somewhere between 20W and 25W and I would set PL2 to 25W. I would also reduce the turbo time limit to about 8 seconds. The default 28 seconds is usually too much for laptops with poor cooling.
I am not sure how easy it is to open up your laptop for some maintenance. Blowing out the dust if this has never been done before would be a good thing to do.
The biggest problem your laptop has is it uses BD PROCHOT throttling. This drops the CPU speed down to just under 200 MHz which completely kills performance. This type of throttling is excessive. If it was my laptop, I would clear the BD PROCHOT box on the main screen of ThrottleStop.
Is this safe to do? Maybe, maybe not. I have no idea why your laptop is using BD PROCHOT throttling. It might be something like the temperature of the backside of the keyboard is getting hot and this is what triggers the CPU to crawl along like a slug. You will probably be OK with BD PROCHOT disabled but I cannot guarantee anything. It is up to you if you want to give this a try. I just think that any company, especially Microsoft, forcing their expensive laptops to run at only 200 MHz is a bad joke.
If you make any changes, look in the log file for BDPRO. Lowering the power limits might allow you to avoid BD PROCHOT throttling without having to use ThrottleStop to disable this.
In the TPL window I would clear the Disable Controls box. I would set PL1 to somewhere between 20W and 25W and I would set PL2 to 25W. I would also reduce the turbo time limit to about 8 seconds. The default 28 seconds is usually too much for laptops with poor cooling.
I am not sure how easy it is to open up your laptop for some maintenance. Blowing out the dust if this has never been done before would be a good thing to do.
The biggest problem your laptop has is it uses BD PROCHOT throttling. This drops the CPU speed down to just under 200 MHz which completely kills performance. This type of throttling is excessive. If it was my laptop, I would clear the BD PROCHOT box on the main screen of ThrottleStop.
Is this safe to do? Maybe, maybe not. I have no idea why your laptop is using BD PROCHOT throttling. It might be something like the temperature of the backside of the keyboard is getting hot and this is what triggers the CPU to crawl along like a slug. You will probably be OK with BD PROCHOT disabled but I cannot guarantee anything. It is up to you if you want to give this a try. I just think that any company, especially Microsoft, forcing their expensive laptops to run at only 200 MHz is a bad joke.
If you make any changes, look in the log file for BDPRO. Lowering the power limits might allow you to avoid BD PROCHOT throttling without having to use ThrottleStop to disable this.
Last edited: