VirtualBox 5.2.18 - KM Exception Not Handled

[Leo52]

Nach der Installation von VitualBox 5.2.18 unter Windows 10 Pro 64-Bit generieren alle VMs (W10, W7, Vista, XP, 2000, NT) bereits nach wenigen Sekunden einen Bluescreen mit der Meldung "KM Exception Not Handled". Das Tool BluescreenView gibt als Ursache den VGA Boot Driver an. Dies lässt darauf schließen, dass das Extension Pack fehlerhaft ist und in dieser Form nicht zur Veröffentlichung geeignet ist!

Hier sollte umgehend eine funktionierende Lösung veröffentlicht werden!!!

[socratis]

After installing VitualBox 5.2.18 under Windows 10 Pro 64-bit, all VMs (W10, W7, Vista, XP, 2000, NT) generate a bluescreen with the message "KM Exception Not Handled" after a few seconds. The BluescreenView tool indicates the VGA boot driver as the cause. This suggests that the extension pack is faulty and not suitable for publication in this form!

A working solution should be published here immediately!

I'll reply in English. You can use DeepL translator or Google translator for help.

indicates the VGA boot driver as the cause. This suggests that the extension pack is faulty and not suitable for publication in this form!

You are a little bit confused. The ExtPack has absolutely nothing to do with the VGA:

• The Extension Pack (ExtPack) gets installed on the host and it has to match the VirtualBox version. It provides functionality such as USB2-3, Webcam, VRDP, PXE, PCI passthrough on Linux hosts, VDI Encryption. You have to download it and install it separately from the main VirtualBox program, due to its license.
• The Guest Additions (GAs) get installed on the guest and it would be good to match the VirtualBox version, for anything other than enhanced graphics support. It provides functionality such as shared folders, shared clipboard, drag and drop, pointer sharing (for PS/2 mice), enhanced graphics support. You do not have to download it separately from the main VirtualBox program, since it comes bundled with it.

A working solution should be published here immediately!

1) Nothing happens "immediately!", 2) there's nothing to publish, since it works for eveyone except you. So let's try to find out what's wrong with your setup.

Pick one VM that doesn't work. We're going to need to see a VM log from a complete VM run:

• Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.