VirtualBox

Opened 14 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 Frank Mehnert)

http://www.losethos.com/

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)

No Hard Drive.xml (3.7 KB ) - added by Dan 14 years ago.
Virtual Machine config
050410-40872-01.dmp (268.0 KB ) - added by Dan 14 years ago.
Minidump
050410-40872-01.eventlog.txt (1.0 KB ) - added by Dan 14 years ago.
Event log to go with dump
050110-18189-01.dmp (268.0 KB ) - added by Dan 14 years ago.
Minidump
050110-18189-01.eventlog.txt (1.0 KB ) - added by Dan 14 years ago.
Event log to go with dump
080610-34460-01.dmp (268.0 KB ) - added by Dan 14 years ago.
Another BSoD minidump
VBox.log.1 (43.5 KB ) - added by Dan 14 years ago.
VBox log for 5/4/10 BSoD.
VBox.log (44.9 KB ) - added by Dan 14 years ago.
VBox log for 8/6/10 BSoD

Download all attachments as: .zip

Change History (14)

by Dan, 14 years ago

Attachment: No Hard Drive.xml added

Virtual Machine config

by Dan, 14 years ago

Attachment: 050410-40872-01.dmp added

Minidump

by Dan, 14 years ago

Event log to go with dump

by Dan, 14 years ago

Attachment: 050110-18189-01.dmp added

Minidump

by Dan, 14 years ago

Event log to go with dump

comment:1 by Mikael Lyngvig, 14 years ago

I also get a BSoD on the most recent version of VirtualBox (v3.2.4) and Windows 7 x64 (Home Professional).

comment:2 by Sander van Leeuwen, 14 years ago

Please attach a minidump.

comment:3 by Sander van Leeuwen, 14 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 Dan, 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).

by Dan, 14 years ago

Attachment: 080610-34460-01.dmp added

Another BSoD minidump

by Dan, 14 years ago

Attachment: VBox.log.1 added

VBox log for 5/4/10 BSoD.

by Dan, 14 years ago

Attachment: VBox.log added

VBox log for 8/6/10 BSoD

comment:5 by Dan, 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 Frank Mehnert, 9 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use