Blue Screen Of Death in Win2003

[plunkers]

I have only recently started using VirtualBox. I have two host systems, a Windows XP box and a Fedora Box.

I recently upgraded to 2.1.0 and have begun getting BSOD's. I am uncertain if it is related to the upgrade due to my short period using the technology.

I am however certain that it is VirtualBox creating the BSOD as it points to a VirtualBox system file when it fails.

Anyone have any ideas on how to resolve this issue?

2003 server event log report attached. (domain removed)



The reason supplied by user [DOMAIN]\Administrator for the last unexpected shutdown of this computer is: System Failure: Stop error
Reason Code: 0x805000f
Bug ID: not known error
Bugcheck String: 0x00000019 (0x00000020, 0x88f53000, 0x88f53120, 0x0a240000)
Comment: 0x00000019 (0x00000020, 0x88f53000, 0x88f53120, 0x0a240000)

[Quimby]

I'm getting BSODs since 2.1 upgrade, too. Seems to be this problem in my case: http://www.virtualbox.org/ticket/2832

Happens mostly after shutdown of a VM, the GUI freezes and after a couple of Seconds of 100% CPU Usage on one core -> BAD_POOL_HEADER Bluescreen.
System was running fine with VBox 2.0.X for several months.

[plunkers]

Is it expected they will patch this? Any time frame of the fix?

[chsh]

I wonder if it's related to the new Host Interface features, because after switching to NAT I was able to run fine for several hours (no bluescreens) when before I could get them in no more than 20 minutes depending on use.

Sometimes even just having other things up and running and the VBox in the background was sufficient to see the bluescreen.

[Sasquatch]

Is it expected they will patch this? Any time frame of the fix?

If you read the ticket, you will see that Sander responds with a thank you and they are tracking it down. Should be fixed in the next release, as it's quite a show stopper.