locked
W10 1903 in VM hanging with System Process using 100% of CPU RRS feed

  • Question

  • I'm copy/pasting this from the regular MS forums as suggested by a moderator.  I view this as more of a host OS issue than a Hyper-V issue personally, but defer to the experts.

    So, it's taken me a while to track down exactly what process was causing this.  I've attached the first evidence I've found as to what process is causing this problem.

    This is a virtual Windows 10 Pro 1903 installation on a Server Datacenter 2016 Hyper-V host.  Around 3 months ago (not sure exactly, but certainly not long after we approved the update to 1903) this system began not checking in to WSUS and when I would look into the issue, Hyper-V manager would report the VM was using about 12% of the processor, which translates into 100% in the virtual environment.  Requests to remote in would time out, and connecting through Hyper-V Manager would show the lock screen, but it was unable to proceed through logon.  The only way to get it to respond is to reset the virtual machine, after which it starts up normally.  However, it could freeze again in as little as 15 minutes, or it could take over a day, without any discernible pattern.

    This system is used to host the only Java installation we have on campus, which it needs to access HVAC controls for our campus, as well as monitor some of our wireless access points.  Other than the browser, and Java, there is no additional software (except for that which I've downloaded for troubleshooting since the beginning of this issue).  The system had been working fine for over a year with only regular updates being done.  As it's a VM, there's no physical hardware for which drivers could be out of date.

    Since the time between system startup and hang appear to be somewhat random, it's not usually possible to notice when it hangs.  In the case of the screenshot attached, it froze after I left, but before the problem VM's lock screen came on.  I left screen sharing software running in the hopes of catching it in the act and finally succeeded.  This freeze apparently happened 7 minutes after I walked away from my desk today.

    Any suggestions for this one?  Certainly it's possible to just reinstall from scratch, but if a solution exists, I'd rather find that than just keep nuking and paving the VM every time it decides to try to turn into a space heater.

    Best wishes,

    Roy

    Since it's not a verified account, the screenshot is available at this post:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/w10-1903-in-vm-hanging-with-system-process-using/0c30370e-823a-41f1-bdfc-37c685ee001b?tm=1572380956433

    Thursday, October 31, 2019 1:00 PM

All replies

  • Sorry, but if you need help with Hyper-V, this isn't the forum, this one's for Virtual Server 2005.

    The Hyper-V server forum is here: https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverhyperv&filter=alllanguages

    Basic help ideas before you repost:

    Have you tried increasing the number of vCPUs to the VM?  One to two, etc?

    Are you licensed correctly?  With a remotely accessed Win10 VM like you've got, you need additional licensing beyond the basic Windows 10 license.  I've heard rumors that Microsoft is starting to enforce this.

    If you do need to post in the Hyper-V forum, can you include your host info, CPUs, RAM, disk subsystem, etc.  Also, include the VM details, generation, RAM, vCPUs assigned, etc.  Are there other VMs on the host?

    Friday, November 1, 2019 5:23 PM
  • Thanks for the suggestions.

    Thursday, November 7, 2019 2:17 PM