%1.%2: %3 was opened by File ID successfully the first time but not the second time. No recovery operation was tried on file %4. This is an internal error.
was configured with an internal network number of %3. This network number conflicts with one of the attached networks. The ...
was faulted because the guest executed an intercepting instruction not supported by Hyper-V instruction emulation. If the ...
was faulted with general protection exception, due to insufficient memory on the host while emulating an instruction for ...
was faulted with general protection exception, due to unexpected error occurred on the host while emulating an instruction ...
was opened by File ID successfully the first time but not the second time. No recovery operation was tried on file %4. This ...
was powered off because a TLB page size mismatch error occurred on a virtual processor. If the problem persists, contact ...
was reset because an uncorrected memory error occured at physical address %1, which was used by this virtual machine. (Virtual ...
was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, ...
was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. This error might have ...