VirtualBox

Opened 7 years ago

Last modified 7 years ago

#16832 new defect

When running any machine in VirtualBox 5.1.22 Windows bluescreens

Reported by: Allan Kjær Owned by:
Component: other Version: VirtualBox 5.1.22
Keywords: bluescreen, windows Cc:
Guest type: all Host type: Windows

Description

When I try and run a machine on VirtualBox Windows bluescreens and shuts down. I'm running Windows 10 Enterprise version 1703 build 15063.413.

Attachments (2)

VBox.log (28.0 KB ) - added by Allan Kjær 7 years ago.
Log
VBoxHardening.7z (30.8 KB ) - added by Allan Kjær 7 years ago.
VBoxHardening.log

Download all attachments as: .zip

Change History (7)

comment:1 by Frank Mehnert, 7 years ago

Please attach a VBox.log file of such a VM session.

in reply to:  1 comment:2 by Allan Kjær, 7 years ago

Replying to frank:

Please attach a VBox.log file of such a VM session.

Hi Frank,

Where do I find this log file?

by Allan Kjær, 7 years ago

Attachment: VBox.log added

Log

by Allan Kjær, 7 years ago

Attachment: VBoxHardening.7z added

VBoxHardening.log

comment:3 by Socratis, 7 years ago

Try do disable Hyper-V in your host.
Most probably a duplicate of #15780, #15984, #16013, #16675, #16801 or a combination of the above, which should be closed as duplicates at some point, most probably of #16801 since it seems to have the best description/workaround/suggestion.

in reply to:  3 ; comment:4 by Allan Kjær, 7 years ago

Replying to socratis:

Try do disable Hyper-V in your host.
Most probably a duplicate of #15780, #15984, #16013, #16675, #16801 or a combination of the above, which should be closed as duplicates at some point, most probably of #16801 since it seems to have the best description/workaround/suggestion.

I have already disabled all Hyper-V and other hypervisor software. Also all settings are enabled in BIOS. It worked before upgrading to Windows ver 1703.

in reply to:  4 comment:5 by Socratis, 7 years ago

Replying to techallan:

I have already disabled all Hyper-V and other hypervisor software.

  1. Please check again, do a cold reboot, and check again.
  2. Check if DeviceGuard or CredentialGuard are active.
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use