And wow, apparently I had hair once
![](http://emoji.tapatalk-cdn.com/emoji6.png)
I switched back and forth a couple of times. At the point of the arrow, I started a screen saver that always blew one core to close to 100%. The rest is just idling. The fan kicks in after about 3 mins of idling, which it never did before..mk79 wrote:Use Task Manager instead of Resource Monitor, go to CPU tab and active "Show kernel times" under "View" I guess.
Hair is vastly overratedAnd wow, apparently I had hair once
Hm ok, no idea. Obviously QPC didn't change in the last year, so something else must have. I did expect much more kernel time (the red line), which usually hints at a hardware problem. Does this happen without anything loaded in SMSQ/E as well?pjw wrote:I switched back and forth a couple of times. At the point of the arrow, I started a screen saver that always blew one core to close to 100%. The rest is just idling. The fan kicks in after about 3 mins of idling, which it never did before..
Ahem. I should have tested more thoroughly before rending my cloak and pouring ashes on my head in publicmk79 wrote:Hm ok, no idea. Obviously QPC didn't change in the last year, so something else must have. I did expect much more kernel time (the red line), which usually hints at a hardware problem. Does this happen without anything loaded in SMSQ/E as well?pjw wrote:I switched back and forth a couple of times. At the point of the arrow, I started a screen saver that always blew one core to close to 100%. The rest is just idling. The fan kicks in after about 3 mins of idling, which it never did before..
Thats hard to tell, isnt it? I was more concerned with Spectre and Meltdown, as I recently found out that they were discovered about the time my machine started playing up, although the info only hit the public sphere recently. Its not the exploits that are the problem so much as the cure which, Im told, could significantly affect performance on older CPUs. This may still be the problem here (I know virtually nothing about these things, and thats how I like to keep it). But I think your suggestion to open up and give her a good blowout is a good one, and thats what I intend to do.Dave wrote:Definitely time to open up that laptop. Also, is it mining cryptocurrency without your informed consent?
That is still strange, QPC doesn't consume even 1% of CPU when idling here on my machine. You could download Process Explorer, right click QPC and hit "Properties". Then go to the "threads" tab and see which thread consumes the QPC.pjw wrote:Ahem. I should have tested more thoroughly before rending my cloak and pouring ashes on my head in publicWithout anything loaded the fan doesnt come on after three minutes (or ten for that matter) The CPU strain is still nearly 100% on one of the cores - in fact with the tools I have available I cant tell the difference between a loaded and an empty system.
To be frank, I no longer remember what was "normal" behaviour; I only started reacting to the noise. I do remember that my "Matrix" screen saver maxed out the one core, leading to this sort of reacket - even when QPC2 was running in the background. Which is why I abandoned it as a screen saver and just sometimes use it as an aid to meditation.. (Only joking).mk79 wrote:That is still strange, QPC doesn't consume even 1% of CPU when idling here on my machine. You could download Process Explorer, right click QPC and hit "Properties". Then go to the "threads" tab and see which thread consumes the QPC.pjw wrote:Ahem. I should have tested more thoroughly before rending my cloak and pouring ashes on my head in publicWithout anything loaded the fan doesnt come on after three minutes (or ten for that matter) The CPU strain is still nearly 100% on one of the cores - in fact with the tools I have available I cant tell the difference between a loaded and an empty system.