High CPU load
- Thread starter waleedov
- Start date
Please try this build and let me know if you still see such large delays: www.hwinfo.com/beta/hwi64_765_5254.zip
No 100% sure, but as far as I know I have seen those huge delays everytime after standby.
FYI - I never use sleep, standby, etc....
To add a detail... while I had previously thought this was linked to Suspend/Resume, today, with the 5250 BETA, I saw the "high CPU" issue after my display had timed out and turned off (10 minutes) - NO Suspend was needed.
When I woke it up again, there was the pegged logical core.
When I woke it up again, there was the pegged logical core.
OK, we seem to be mixing different issues for each of you.
Are you perhaps running some other monitoring tool too? Will restarting of HWiNFO bring the sensor to normal polling time?
This is clearly related to suspend/resume and I can see that right after resume HWiNFO properly restores access to the VRM sensor but something else later seems to disable it.
Are you perhaps running some other monitoring tool too? Will restarting of HWiNFO bring the sensor to normal polling time?
This might be something else and it will require checking which sensor takes so much time. It could also be the PresentMon sensor..
I am not sure why you are saying this - as soon as I run your current BETA (5250), I see the additional Renesas sensors - the ITE ones are still present.
And these Renesas sensor groups are where the huge amount of time is going, according to your "ms" column... this is why I posted today, when I saw someone else with a related mobo with the same symptoms as myself.
The fact that it may not require a Suspend/Resume to show up doesn't suggest to me that it is an unrelated problem.
And these Renesas sensor groups are where the huge amount of time is going, according to your "ms" column... this is why I posted today, when I saw someone else with a related mobo with the same symptoms as myself.
The fact that it may not require a Suspend/Resume to show up doesn't suggest to me that it is an unrelated problem.
I will need to see the HWiNFO Debug File from you too to check in detail what's going on there.
Looks like the VRMs became inaccessible again. Can you capture that in Debug File? Also create another Debug File from a new start of HWiNFO right after you closed it in such state.