DX11 Backend Error on Dolphin Exit

arthur117 · (This post was last modified: 06-02-2011, 10:33 PM by arthur117.)

Whenever I Exit Dolphin (not a game, but the Emulator itself, it hangs and Windows gives me the default "Dolphin.exe has stopped responding and needs to be terminated. You can check online if there is a solution for this problem". This only happens when I've been using the DX11 Backend (not with DX9 or OpenGL), and I've included the corresponding snippet from exceptioninfo.txt below:

Code:
Unhandled Exception

  Code: 0xC0000005

Call stack info: 

     D3DUtil.h(61) : DX11::SharedPtr<ID3D11GeometryShader>::~SharedPtr

     Dolphin!0x01063DE8 : `eh vector destructor iterator'

     Dolphin!0x00E8EDD3 : DX11::TextureCache::TCacheEntry::Save

     crt0dat.c(567) : doexit

     crt0dat.c(393) : exit

     crt0.c(284) : __tmainCRTStartup

     kernel32!0x75D7D0E9 : BaseThreadInitThunk

Unhandled Exception

  Code: 0xC0000005

Call stack info: 

     D3DUtil.h(61) : DX11::SharedPtr<ID3D11GeometryShader>::~SharedPtr

     ehvecdtr.cpp(140) : __ArrayUnwind

     Dolphin!0x01063E1C : `eh vector destructor iterator'

     Dolphin!0x01062CB6 : __NLG_Return2

     Dolphin!0x010833B0 : _local_unwind4

     Dolphin!0x0108347B : @_EH4_LocalUnwind@16

     Dolphin!0x0107495A : _except_handler4

     ntdll!0x77045DA9 : RtlRaiseStatus

I've already updated my video drivers and got the latest DirectX package. Tried different revisions including 7574, 7571, 7570. (currently using R7519 SSL4.1 from Lectrode), but same Error everywhere. Using DX9 or OpenGL won't produce this error.

EDIT: Forgot to include my Specs...

Win Vista x86 Ultimate
2GB RAM DDR2
Intel Core 2 Duo E8400 @ 3150MHz
ATI Radeon HD 5770

Is this a Dolphin/DX11 problem, or do I need to change some setting?

**neobrain** · 06-02-2011, 10:58 PM #2

As far as we can't tell this problem only appears on D3D 11.0 hardware... Neither I nor the author of the code which is responsible for this error own such though, so it's hard to fix..

arthur117 · 06-03-2011, 01:46 AM #3

(06-02-2011, 10:58 PM)NeoBrain Wrote: As far as we can't tell this problem only appears on D3D 11.0 hardware... Neither I nor the author of the code which is responsible for this error own such though, so it's hard to fix..

Mmm... 'kay. Was just wondering, since it doesn't bother me much. Thankfully it doesn't crash mid-game (At least, not as far as I can remember). I check for new revisions regularly, so when the problem stops manifesting (or starts messing up my games by crashing) I'll report back here... Any info I might add that could be useful? Besides the exceptioninfo.txt snippets, I mean...

**neobrain** · 06-03-2011, 03:43 AM #4

If there was any useful information you could give us for this problem, you probably would've debugged and identified the issue meanwhile anyway ;P