Opened 15 years ago
Closed 9 years ago
#6643 closed defect (obsolete)
LoseThos guest VM BSoDs Windows 7 host
Reported by: | Dan | Owned by: | |
---|---|---|---|
Component: | host support | Version: | VirtualBox 3.1.6 |
Keywords: | LoseThos 64-bit | Cc: | |
Guest type: | other | Host type: | Windows |
Description (last modified by )
I get a bluescreen on the host while booting this in a VM.
VBox 3.1.6r59338 64-bit. Windows 7 Professional 64-bit host
Event Log dump of BSoD events and VirtualBox config are attached.
(<EventData> in the event logs seems to refer to the BSOD itself (30 == STOP 0x0000001E))
CD was attached after first boot (which ended at the "FATAL: No bootable media" error) then rebooted. System BSoDs after a few seconds and a few console lines from LoseThos boot process.
Attachments (8)
Change History (14)
by , 15 years ago
Attachment: | No Hard Drive.xml added |
---|
comment:1 by , 15 years ago
I also get a BSoD on the most recent version of VirtualBox (v3.2.4) and Windows 7 x64 (Home Professional).
comment:3 by , 15 years ago
Can't reproduce here. The VBox.log file of the session would be helpful as well (don't wait for the crash; just briefly start it).
comment:4 by , 14 years ago
I tried to trigger the BSoD again to get a fresh log with 3.2.8. However, the log file was empty. :(
However I am getting a different error on the BSoD from before so I am attaching a new minidump from today. Log file is from older 5/4/10 BSoD.
Crash seems to happen in ntfs.sys+c898, called from ntoskrnl.exe+6fb69, called from VMMR0.r0+1c94f (addresses from 3.2.8 64-bit Windows).
comment:5 by , 14 years ago
Looks like the log file was there, I guess filesystem corruption was reporting a 0 byte size incorrectly? Windows fixed it while I wasn't looking, attached.
comment:6 by , 9 years ago
Description: | modified (diff) |
---|---|
Resolution: | → obsolete |
Status: | new → closed |
Virtual Machine config