August 2, 20196 yr I have a 6 core i5 8400 with the last 4 assigned to my Windows 10 VM. The VM doesn't have a dedicated video card. I access it strictly through RDP. Today I noticed that when I'm not interactive with the VM a single core is pegged. It moves around occasionally but is always pegged. If I log in "local" using the VNC connection it calms down but CPU activity still seems higher than it used to be. If I remote in via RDP it settles down the same as using the VNC connection. As soon as RDP disconnects a single core is again pegged. Since this seems to be something new I'm unsure what could be causing it. As soon as it goes non-interactive (disconnect from RDP) Windows seems to peg a single core. I don't now how to determine what's causing it. unraid-diagnostics-20190802-2014.zip
August 3, 20196 yr Author I also just noticed that this prevents power saving on my CPU from working and actually ends up causing my CPU to always be at the turbo speed of 3.8Ghz on all cores. Normal speed for my i5 8400 is 2.8Ghz.
August 4, 20196 yr Author Ok, apparently this problem has to do with the newer WDDM remote display driver used in Windows 10. You can use Group Policy Editor to disable the WDDM driver and force it to use the older XDDM driver and it works as it should. There are lots of people having issues with this even on bare iron. DWM.EXE High CPU (One Core) On Target System after Remote Desktop Disconnect on Windows 10 x64 1903 (Fully Patched)
Archived
This topic is now archived and is closed to further replies.