VirtualBox crash on each Restore Saved state (atio6axx.dll)

[toyo]

Hello,

So I have this Win 7 x86 guest on a Win 7 x64 host. The CPU is a E7200 (no hardware acceleration), 4 GB RAM, Asus P5Q, AMD HD 4850 512 RAM (Catalyst 11.9, 2D+3D acceleration, 256 RAM allocated), Virtualbox+ extension pack, latest build (4.1.4.r7291). If the VM is saved and I try to start it, VM will crash just after making it to the Desktop, with an error like the one below:

Code: Select all

Faulting application name: VirtualBox.exe, version: 4.1.4.0, time stamp: 0x4e89c9d4
Faulting module name: atio6axx.dll, version: 6.14.10.11079, time stamp: 0x4e690283
Exception code: 0xc0000005
Fault offset: 0x000000000042888b
Faulting process id: 0xc98
Faulting application start time: 0x01cc8ae52531ed37
Faulting application path: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
Faulting module path: C:\Windows\system32\atio6axx.dll
Report Id: 66602a75-f6d8-11e0-8de4-0022156a981d

[BillG]

Have you tried deleting the saved state (the orange downward arrow next to the green start arrow) and rebooting from scratch?

[Sasquatch]

The problem is some ati file, which is responsible for your video card. Update the drivers and see if that helps, or downgrade to an older version. If that doesn't help, then the only solution is to not use saved state, unfortunately. It seems something is causing a problem in the 3D capabilities of VB.

[toyo]

There's only the Saved state which is affected.

I think that Catalyst 11.7, 11.8 and 11.9 (the latest) are affected. Downgrading is not an option, it messes up more important things. This is a new OS installation, that has installed 11.9 directly above the Microsoft driver, and it still crashes. Also affected are the 2-3 VB builds.

Are there any chances this is going to get fixed in a new build? Or is the reponsibility standing solely with the AMD developers?

[BillG]

I would not expect any changes in VirtualBox. It us up to the adapter supplier to make changes to the driver. If the VirtualBox code works with other drivers and other products, it's pretty clear where the problem lies.

[toyo]

With all due respect, this is a simple way to look at it. I know enough about coding to not dismiss any possibilities.

I will, however, report a bug to AMD Catalyst team, although if my luck is only with them, my position is very poor... Will post back any meaningful responses/resolutions.