03-19-2012 03:36 PM - edited 03-19-2012 03:36 PM
I have a factory fresh X1 with Windows 7, and have the Power/Display options in Windows set to No Screen Saver, and turn off the display after 10 minutes whether plugged in or on battery. Without fail, after about 20 minutes of being idle, my CPU shoots up to around 90 or higher%. I can't tell what the offending process is because the second I move the mouse and the screen returns, the CPU drops back to 0-5%. I can confirm that my CPU was high because of my Windows Sidebar gadget which shows the high utilization in graph form. I can usually tell when the problem starts as my fan cranks up to cool the laptop. Unfortunately, each time I move the mouse and the screen comes back, the problem vanishes. Any ideas on what to look for?
Solved! Go to Solution.
03-20-2012 02:48 PM
I have the same issue on my X1, I have all the latest drivers and BIOS, and I know that it is not software related as it has done this to me on Windows 7, fresh installs of Windows 8 Developer Preview, and Consumer Preview. I haven't looked at the processor usage per se, but I can hear the fan accelerating and Core Temp sometimes indicates the temperature going as high as 80C and as soon as I move the mouse, it drops back down slowly to 45-50C. I usually only leave my laptop in idle when listening to music while doing other things, which is when these things have occured.
05-21-2012 04:07 PM
OK - I know this is an old topic, but I finally figured out what was causing my CPU spikes. It turns out the offending process was "mscorsvw.exe", which compiles .NET assemblies in the background while my computer is idle: http://blogs.msdn.com/b/davidnotario/archive/2005/
Running the command "ngen.exe executequeueditems" cleared up the problem.
11-30-2013 04:16 AM - edited 11-30-2013 04:21 AM
I am still having this issue and this command does not exist in my system. The page linked to, actually, says this does not apply to the current .NET version anymore.
However I found the NGEN services on Computer Management, and proceeded to disable them. Now I only have to wait and see if the CPU goes wild on idle again or not.
Is there ANY system monitor that logs to a file every X interval, so I can check what the hell is happening when the monitor is off?