VirtualBox crash

Discussions related to using VirtualBox on Windows hosts.
Post Reply
tnewhook
Posts: 1
Joined: 18. Oct 2012, 17:38

VirtualBox crash

Post by tnewhook »

For the last several times I've run virtualBox, the client crashes within a few minutes.The error is: "A critical error has occurred while running the virtual machine, and the machine execution has been stopped" I have no idea what to look for in the log file, but I'm hoping someone here will have an idea. The nearest I can guess is that it's a memory error, but I really have no clue. Thanks for the help.

here's the relevant info:
virtualBox 4.2.0
host: win7
guest: ubuntu 12
The log file is available at: pastebin. mozilla. org / 1869959
Y E T I
Posts: 161
Joined: 9. Aug 2010, 01:47
Primary OS: Other
VBox Version: OSE self-compiled
Guest OSses: ?
Location: H i m a l a y a s
Contact:

Re: VirtualBox crash

Post by Y E T I »

attach the log file here
XTNdc
Posts: 1
Joined: 18. Oct 2012, 19:53
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: Linux, Win XP

Re: VirtualBox crash

Post by XTNdc »

I have also encountered errors in Virtual Box causing it to crash (2X).
I was running CLC Genomics workbench 5.5.1 on a BioLinux 6.0 (based on Ubuntu 10.04), and I was downloading the human genome BLAST database (build 37 - 6097MB)
I use VBox 4.1.22 on a Win7 Pro (64bit)
My machine specs:
Dell Precision T7500, 0M1GJ6 motherboard, Intel Xeon L5640 (2.27GHz) 4core (X2) with 48GB RAM

This was the error generated (Windows) upon crash, I also attached two logs from VBox that might be informative on the machine state during the crash.

Code: Select all

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	VirtualBox.exe
  Application Version:	4.1.22.0
  Application Timestamp:	504a1524
  Fault Module Name:	VBoxDD.DLL
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	504a1528
  Exception Code:	c0000005
  Exception Offset:	00000000000d6030
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	7b6f
  Additional Information 2:	7b6f0b6d4b0c873594e1f01bfad064f2
  Additional Information 3:	9a34
  Additional Information 4:	9a345e816c390bc3aee23c4a048258dc
...
Biolinux-2012-10-18-16-15-01.log
(61.78 KiB) Downloaded 12 times
Biolinux-2012-10-18-13-43-46.log
(59.25 KiB) Downloaded 10 times

ADDITIONAL:
I also had a BSOD crash on my host machine a few days ago which seems to have been caused by VBox.
Here is the error report from that incident

Code: Select all

A problem has been detected and Windows has been shut down to prevent damage
to your computer.

The problem seems to be caused by the following file: VBoxDrv.sys

DRIVER_POWER_STATE_FAILURE

If this is the first time you've seen this stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.

Technical Information:

*** STOP: 0x0000009f (0x0000000000000003, 0xfffffa8025870060, 0xfffff80000b9c518, 
0xfffffa8082d77750)

*** VBoxDrv.sys - Address 0xfffff880043a50af base at 0xfffff880043a0000 DateStamp 
0x504a14c8
Post Reply