My CPU automatically goes to 100 percent load at startup. This issue is resolved for a short time if I change my power plan to a different plan. After a few days my CPU goes back to 100 percent on the new power plan, causing me to switch to a new plan I haven't used before.
This issue is causing me to duplicate a plan I haven't used before multiple times, so that I can switch to them as the previous plans I use get "infected" by the 100% CPU issue.
Basically this is what happens:
Use plan 1 until CPU hits 100% >>> Switch to plan 2.
Use Plan 2 >>> Duplicate plan 3 for future use since I haven't used it yet.
Plan 2 stuck at 100% CPU >>> Switch to plan 3 duplicate.
Use Plan 3 duplicate >>> Duplicate plan 3 again, to switch to later.
I have tried to go to the advanced power options for each of the plans to "Restore plan defaults" but that button is greyed out, even if I select the link "Change settings that are currently unavailable".
If anyone can help me it would be greatly appreciated.
Here is a Windows Performance Record for the CPU.
https://www.dropbox.com/s/71k0v7ircz7xydr/HYBRIDCLOVERPC.10-20-2015.11-46-01.etl?dl=0
Also, a screenshot of a few CPU monitoring methods while the trace was running.
This issue is causing me to duplicate a plan I haven't used before multiple times, so that I can switch to them as the previous plans I use get "infected" by the 100% CPU issue.
Basically this is what happens:
Use plan 1 until CPU hits 100% >>> Switch to plan 2.
Use Plan 2 >>> Duplicate plan 3 for future use since I haven't used it yet.
Plan 2 stuck at 100% CPU >>> Switch to plan 3 duplicate.
Use Plan 3 duplicate >>> Duplicate plan 3 again, to switch to later.
I have tried to go to the advanced power options for each of the plans to "Restore plan defaults" but that button is greyed out, even if I select the link "Change settings that are currently unavailable".
If anyone can help me it would be greatly appreciated.
Here is a Windows Performance Record for the CPU.
https://www.dropbox.com/s/71k0v7ircz7xydr/HYBRIDCLOVERPC.10-20-2015.11-46-01.etl?dl=0
Also, a screenshot of a few CPU monitoring methods while the trace was running.
