I'm having this same issue with a Linux Mint 17 guest on a Win 7 host...
Running VB 4.3.18 r96516 with 4.3.18 guest additions.
If 3D acceleration is enabled, shutdown of guest always results in "aborted" status with an error dialog on the host titled "VirtualBox.exe - Application Error" - The instruction at 0x<varying 8 digit hex address> referenced memory at 0x00000010. The memory could not be written. Click OK to terminate the program
Display adapter is an ATI R9 270 with the latest catalyst drivers (v14.9)....
Please advise if there are any details that might be useful.
Note: VBoxSVC log has nothing pertinent
In the VBox.log, there are a few errors that might be pertinent, and here's a sample from the startup:
00:00:01.301632 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: rc=VERR_LDRVI_UNSUPPORTED_ARCH fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\System32\aticfx64.dll: WinVerifyTrust failed with hrc=CERT_E_CHAINING on '\Device\HarddiskVolume2\Windows\System32\aticfx64.dll'
00:00:01.301670 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\aticfx64.dll': rcNt=0xc0000190
00:00:01.379040 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_UNSUPPORTED_ARCH fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=1 \Device\HarddiskVolume2\Windows\System32\aticfx64.dll
00:00:01.379067 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\aticfx64.dll': rcNt=0xc0000190
Similar messages occur periodically throughout, and the log ends with:
00:05:07.772653 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_NOT_SIGNED fImage=1 fProtect=0x0 fAccess=0x0 cErrorHits=32768 \Device\HarddiskVolume2\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH64.dll
00:05:07.772692 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH64.dll': rcNt=0xc0000190
Scott
edit: 11/24
4.3.20 behaves the same as 4.3.18 did, which isn't much of a surprise, as this issue wasn't mentioned in the changelog...
2nd edit: 11/25
It turns out I didn't actually have the Catalyst 14.9 drivers installed after all, and once I installed them, the problem is resolved! Sorry for the false alarm
