Vista Host and BSOD

lowebb · Post by **lowebb** » 8. Jan 2009, 12:06

Hi all,

I am getting frequent BSOD since starting to use Virtual Box with a virtual Ubuntu installation. It is quite stable as long as I do nothing at all on the Windows host. If I however open 2 Bit tornado sessions on the Vista host along with running the Ubuntu Virtual machine I will get the BSOD. The error given can however vary.

I dont think I should as I've plenty on memory. Has anyone else seen this or can point me ways of optimising VirtualBox to avoid this. As a side point, if anything I want to INCREASE the memory available to the virtual machine but currently cannot do this.

My setup
Host: Vista Home Premium
CPU: Intel Core2Duo 2.4G
Memory: 4G

Virtual Machine:
OP: Ubuntu 8.10
Memory: 512M

Post by **vbox4me2** » 8. Jan 2009, 12:54

Still need the BSOD messages, could be anything.

lowebb · Post by **lowebb** » 8. Jan 2009, 13:04

Yeah, I'll begin tracking them and respond here. Thanks

bwcook0 · Post by **bwcook0** » 8. Jan 2009, 16:39

Although in Vista there is no blue screen (that I have seen) I am getting applcation crashes from virtualbox on a Vista host. Here are the details captured from 3 crashes. Thanks...

Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 0.0.0.0
Application Timestamp: 4948c7be
Fault Module Name: VBoxDD.DLL
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4948c7d4
Exception Code: c0000005
Exception Offset: 0000000000094d0e
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 8c9f
Additional Information 2: bf41559ad511f402c9c41886543ac22f
Additional Information 3: e3d5
Additional Information 4: bbdf8a07d286842c772747e3cd237940

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 0.0.0.0
Application Timestamp: 4948c7be
Fault Module Name: ole32.dll
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 4791ad88
Exception Code: c0000005
Exception Offset: 0000000000015740
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Information 1: cba3
Additional Information 2: 3189a2b8ba03a7e3a12db47c79412962
Additional Information 3: 4893
Additional Information 4: 307225dd93873338a090f71dbc61166f

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

Problem signature:
Problem Event Name: APPCRASH
Application Name: VirtualBox.exe
Application Version: 0.0.0.0
Application Timestamp: 4948c7be
Fault Module Name: VBoxDD.DLL
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4948c7d4
Exception Code: c0000005
Exception Offset: 0000000000094d03
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 8c9f
Additional Information 2: bf41559ad511f402c9c41886543ac22f
Additional Information 3: fc4f
Additional Information 4: 8d808071a6b4b1c6a9a9c3ac10259cec

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

Post by **vbox4me2** » 8. Jan 2009, 16:51

VB Version? try 2.06, the latest version has a few quirks.

bwcook0 · Post by **bwcook0** » 8. Jan 2009, 19:20

2.1.0. I thought that after I upgraded that I could not use the disk images with 2.0.6 anymore?

Post by **Sasquatch** » 8. Jan 2009, 20:59

bwcook0 wrote:2.1.0. I thought that after I upgraded that I could not use the disk images with 2.0.6 anymore?

You have to edit the xml files, or restore them from the backup that was created when you ran 2.1.0 for the first time. After that, you can use your VMs again.

d34th · Post by **d34th** » 9. Jan 2009, 01:22

In My Experience I Had A Virus And Wiped My PC Before It didn't work and after wipe it did. so umm yea

lowebb · Post by **lowebb** » 11. Jan 2009, 14:12

vbox4me2 wrote:Still need the BSOD messages, could be anything.

So over the past couple of days I've had 3 BSOD, twice with the error

DRIVER_IRQL_NOT_LESS_OR_EQUAL

and once with

BAD_POOL_HEADER

Any ideas? (I'm using the latest Virtual Box 2.1.0 BTW and am reluctant to go back a version)

sirsquishy · Post by **sirsquishy** » 16. Jan 2009, 22:29

I have been getting the same ERRORS and I can reproduce it every time.

Open up a VB, that is using VT, doesnt have to be a 64bit Image...

Now, open a Com session using Putty on Com 1 or 2 ( 3-7 are not affected)

Issue a reboot to the Com device (In my case, a 3com NBX) right as soon as the Device does a Boot post, your vista box will BSOD with 1 of 3 errors

IRQ not equal to
Paged in non Paged area
'Somthing' writing to Read only memory

The error returned is Different EVERYTIME, but its always one of the 3 errors.

Ive done this with 32bit Vista as the Host, 64bit XP, 32bit XP, 32bit Vista, and 64bit 2003 as the guest. Everytime this happens.

On Vmware, no problems.

Its a virtual box issue.

Running 2.1.0 VB
Vista32bit Sp1.

Pottsie · Post by **Pottsie** » 27. Jan 2009, 10:25

G'day,

Bumping this up, because I've got the same issue (32-bit XP SP3 Host running 32-bit XP SP3 VM) and both 2.1.0 and 2.1.2 are giving me BSOD with Driver Irq less than or not equal to (Or to that effect) whenever the VM starts up.

Any ideas?

Cheers,

Pottsie