Check out:OzzyFrank wrote:*****... was hoping this "fix" would do the trick, but still ends up as Aborted. I really hope Sun fix this problem in later versions, as it is extremely annoying.
http://www.virtualbox.org/ticket/4020#comment:21
Looks like if your Aborted problem is being caused by the failed assertion, it should be fixed now, but you need to wait for version 3.0.8 to come out OR you need to download and build the current source now. If that's not it, you need to post your logs to that bug ticket and ticket #5042 so that they can see I'm not the only one with this problem (and hopefully logs from a setup other than mine might also reveal more about the bug).
And I think what Perryg wrote might be partially true-- this is related to Windows, but if the virtual machine is doing its job acting like a real machine, whatever DMA access is going on the VM should handle it properly when closing itself out, so it's probably more like a confluence of bugs rather than a purely "Windows-thing" or purely a "VirtualBox -thing". Afterall, VirtualBox doesn't care what Windows or any other OS inside is doing, it's a sandbox, it's only Aborted if it itself fails to do something like save state or if the virtual hardware crashes. Windows may be misbehaving, but if VirtualBox is affected by something in the sandbox, then it is misbehaving too. Other guest OSes behave well, so the bug is rarely seen with those platforms. So, I would not, however, agree that shut down aborts are hard to find: I think at last count my own setup was at 22 "Aborted"s out of 24 attempted shutdowns.