VirtualBox

Opened 12 years ago

Closed 8 years ago

#10474 closed defect (obsolete)

Windows 7 Ultimate x64 Crashing Under VirutalBox 4.1.12

Reported by: Stewart Berman Owned by:
Component: other Version: VirtualBox 4.1.12
Keywords: BugCheck Cc:
Guest type: Windows Host type: Windows

Description

Host: Windows 7 Ultimate x64 with all important patches VirtualBox 4.1.12 Guest: Windows 7 Ultimate x64 with all important patches

I stayed on VirtualBox 3.0.10 for a long time because all of my VMs were stable under it. (I tried 3.0.12 but the VMs kept crashing.)

I upgraded to 4.1.12 and my VMs crash when left running. I have attached the log files that cover the period of the latest crash and an analysis of the MEMORY.DMP file that windows produces.

Attachments (7)

VBoxSVC.log (1.8 KB ) - added by Stewart Berman 12 years ago.
VBoxSVC.log.1 (3.8 KB ) - added by Stewart Berman 12 years ago.
MEMORY.DMP.txt (17.8 KB ) - added by Stewart Berman 12 years ago.
VBox.log.3 (92.7 KB ) - added by Stewart Berman 12 years ago.
Correct log file
MEMORY_20120424.DMP.txt (17.6 KB ) - added by Stewart Berman 12 years ago.
VBox-20120424.log (60.0 KB ) - added by Stewart Berman 12 years ago.
Log to go with memory dump
BlueScreenView_20120427.txt (23.7 KB ) - added by Stewart Berman 12 years ago.
Analysis of the minidumps from BlueScreenView

Download all attachments as: .zip

Change History (11)

by Stewart Berman, 12 years ago

Attachment: VBoxSVC.log added

by Stewart Berman, 12 years ago

Attachment: VBoxSVC.log.1 added

by Stewart Berman, 12 years ago

Attachment: MEMORY.DMP.txt added

comment:1 by Frank Mehnert, 12 years ago

There must be a VBox.log file for that VM. You attached the wrong logfiles, please use the GUI (Machine / Show Log File...) to find the correct logfile.

by Stewart Berman, 12 years ago

Attachment: VBox.log.3 added

Correct log file

by Stewart Berman, 12 years ago

Attachment: MEMORY_20120424.DMP.txt added

by Stewart Berman, 12 years ago

Attachment: VBox-20120424.log added

Log to go with memory dump

by Stewart Berman, 12 years ago

Attachment: BlueScreenView_20120427.txt added

Analysis of the minidumps from BlueScreenView

comment:2 by Stewart Berman, 12 years ago

Tried installing 4.1.16. Same problem. 052812-16765-01.dmp 5/28/2012 12:36:36 AM MEMORY_MANAGEMENT 0x0000001a 0000000000041287 0000000000000000 0000000000000000 0000000000000000 atapi.sys atapi.sys+183a x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\052812-16765-01.dmp 1 15 7601 268,472

comment:3 by Stewart Berman, 12 years ago

Correction: The VB release they are stable under should have been 3.2.10 not 3.0.10.

Additional information: The VMs are running on a single host and the VB GUI is used with them. The machines are idle and the GUI is minimized when the crashes occur.

comment:4 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use