FACILITY_USERMODE_VIRTUALIZATION: the user mode virtualization subsystem.
The source of the error code is the user mode virtualization subsystem.[1][2]
0xC0370001: The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370002: The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370003: The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370004: No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370005: The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370006: The partition name of the virtualization infrastructure driver exceeds the maximum.[2]0xC0370007: The message queue name of the virtualization infrastructure driver exceeds the maximum.[2]0xC0370008: Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists.[2]0xC0370009: The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC037000A: The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC037000B: A message queue with the same name already exists for the virtualization infrastructure driver.[2]0xC037000C: The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC037000D: The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed.[2]0xC037000E: Cannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC037000F: The non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration.[2]0xC0370010: The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology.[2]0xC0370011: The memory block for the virtualization infrastructure driver is already associated with a message queue.[2]0xC0370012: The handle is not a valid memory block handle for the virtualization infrastructure driver.[2]0xC0370013: The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370014: The handle is not a valid message queue handle for the virtualization infrastructure driver.[2]0xC0370015: The handle is not a valid page range handle for the virtualization infrastructure driver.[2]0xC0370016: Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block.[2]0xC0370017: The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370018: The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver.[2]0xC0370019: Notifications cannot be created on the memory block because it is use.[2]0xC037001A: The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC037001B: Cannot add a virtual processor to the partition because the maximum has been reached.[2]0xC037001C: Cannot stop the virtual processor immediately because of a pending intercept.[2]0xC037001D: Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC037001E: The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC037001F: This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370020: Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370021: The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370022: The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370023: Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370024: The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370025: Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370026: Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.[2]0xC0370027: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine.[2]0xC0370028: Cannot restore this virtual machine because an item read from the saved state data is not recognized. Delete the saved state data and then try to start the virtual machine.[2]0xC0370029: Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine.[2]0xC037002A: The specified VTL does not have the permission to access the resource.[2]0xC0370100: The compute system unexpectedly terminated while starting.[2]0xC0370101: The operating system of the container does not match the operating system of the host.[2]0xC0370102: A Virtual Machine could not be started because Hyper-V is not installed.[2]0xC0370103: The call to start an asynchronous operation succeeded and the operation is performed in the background.[2]0xC0370104: The supported number of notification callbacks has been exceeded.[2]0xC0370105: The requested compute system operation is not valid in the current state.[2]0xC0370106: The compute system exited unexpectedly.[2]0xC0370107: The compute system was forcefully terminated.[2]0xC0370108: A connection could not be established with the Virtual Machine hosting the Container.[2]0xC0370109: The operation timed out because a response was not received from the Virtual Machine hosting the Container.[2]0xC037010A: The connection with the Virtual Machine hosting the container was closed.[2]0xC037010B: An unknown internal message was received by the Hyper-V Compute Service.[2]0xC037010C: The communication protocol version between the Hyper-V Host and Guest Compute Services is not supported.[2]0xC037010D: The JSON document is invalid.[2]0xC037010E: A Compute System with the specified identifier does not exist.[2]0xC037010F: A Compute System with the specified identifier already exists.[2]0xC0370110: The Compute System with the specified identifier did already stop.[2]0xC0370200: A virtual switch with the given name was not found.[2]0x80370001: A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration.[2]
Sources
- https://msdn.microsoft.com/en-us/library/cc231198.aspx
- winerror.h from Windows SDK 10.0.14393.0