How To Fix Hyper-V Event Id 18590?

Question

Hello there!

I have been investigating a problem we been having with Hyper-V. Sometimes when launch a Windows Docker image, in Hyper-V isolation, I received the following error message.

Error response from daemon: hcs::CreateComputeSystem 290632f813f0320b8efd62a3a41595a4e697e2c4ff5d379ddc138cae642c53b1: The virtual machine or container exited unexpectedly.

Further investigation, I have found that the under the event viewer of source Hyper-V worker receives the follow error with id 18590.

'2bd0b553154a4f1b137891caf7651a73a2fa4f474687aab27296049ff2fdc056' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x7E, ErrorCode1: 0xFFFFFFFFC0000094, ErrorCode2: 0xFFFFF80432DF149F, ErrorCode3: 0xFFFFF88451CAA058, ErrorCode4: 0xFFFFF88451CA9870. PreOSId: 0. If the problem persists, contact Product Support for the guest operating system. (Virtual machine ID 0A36F061-FF1F-4B4D-B72F-AC34FB743B68) Guest message:

What is this error and how do I resolve it?

Answer 1

Hi Jordan St-Germain，

The error code 0x7E indicates that a system thread generated an exception that the error handler didn't catch. According to troubleshooting tips, you can check the System Log in Event Viewer in the VM for more error messages that might help identify the device or driver that is causing bug check 0x7E.

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled

Best Regards,

Ian Xue

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.