• HomeBoards
  • RulesRules
  • HelpHelp
  • WikiWiki
  • Donate

Author Topic: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage  (Read 3651 times)

bitersnake (OP)

  • Posts: 244
Okay so many people seem to have had this issue with their GPD win and @Maniac 's solution for turning of the intel thermal processes in the BIOS have worked for some and have, unfortunately, not worked for others.

I recently started experiencing crashes on Grid Autosport which I was playing off of a flash disk and after a couple of days of searching on the internet, I tried all kinds of solutions by configuring the game and changing display settings etc, none of which worked until this solution came up on some forum:

http://boards.dingoonity.org/gpd-windows-devices/grid-autosport-crash-on-gpd-win/

I had previously managed to diagnose through xperf that the high system SPU  usage was due to the touchscreen driver
(see here- http://boards.dingoonity.org/gpd-windows-devices/post-hibernate-cpu-usage-any-reliable-fix/) but wasn't sure of what my next step should be.

Anyway, cutting to the chase, here's what you need to do:
Go to the task manager-> services-> open services-> Touch Keyboard and Handwriting Panel Service-> Stop (or preferably, disable) this service et voi-f**king-la!

CPU usage will stay put at 0-1 % (could be little higher based on how many processes you've got going on your device) even after resuming from sleep/ hibernate.

I hope this helps fix the issue for some people- as we learnt from other possible solutions, the causes for high system CPU can be many but this is definitely one fix.

Cheers!

EDIT- I shoudl point out that with this service disable you'll lose access to on-screen keyboard-- didn't matter sh*t to me but just putting it out there.
« Last Edit: April 02, 2017, 09:05:39 pm by bitersnake »

SmashMan4

  • Posts: 33
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #1 on: April 03, 2017, 05:26:04 am »
Sadly this didn't work for me. :(

Faust

  • Posts: 542
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #2 on: April 03, 2017, 08:41:45 am »
Neither for me

bitersnake (OP)

  • Posts: 244
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #3 on: April 03, 2017, 09:02:14 am »
Ahhh sorry. Did you guys also turn off dptf in bios? I realised that i needed to have dptf off AND disable the touch keyboard. Perhaps you could try again. Hope it helps

Faust

  • Posts: 542
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #4 on: April 03, 2017, 09:44:35 am »
Unfortunately it still doesn't work.
« Last Edit: April 03, 2017, 09:47:52 am by Faust »

Maniac

  • Posts: 422
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #5 on: April 03, 2017, 12:31:33 pm »
SmashMan4/Faust, disabling DPTF in the bios didn't fix the hibernate issue for you?

You can try diagnosing why it's happening to you using these instructions:
https://www.reddit.com/r/gpdwin/comments/5ymg5v/30_cpu_usage_after_hibernation_fixed/det78wc/

Faust

  • Posts: 542
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #6 on: April 03, 2017, 01:09:52 pm »
Thanks, I check and come back to give more information!

SmashMan4

  • Posts: 33
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #7 on: April 03, 2017, 05:26:23 pm »
SmashMan4/Faust, disabling DPTF in the bios didn't fix the hibernate issue for you?

You can try diagnosing why it's happening to you using these instructions:
https://www.reddit.com/r/gpdwin/comments/5ymg5v/30_cpu_usage_after_hibernation_fixed/det78wc/

Disabling DPTF made mine hot, but still did not fix it. I ran xperf and it said that wdf01000.sys is the culprit.

Maniac

  • Posts: 422
Re: [SOLVED] Potential fix for post-hibernate/sleep high system CPU usage
« Reply #8 on: April 04, 2017, 12:12:03 pm »
Disabling DPTF made mine hot, but still did not fix it. I ran xperf and it said that wdf01000.sys is the culprit.

The culprit is calling or being called by wdf01000.sys, but it's not wdf01000.sys - that's the Windows Driver Foundation. Any other sys files in the tree that wdf01000.sys is in?