No I haven't, I really don't know how far I have to look to search for a working version, maybe no one?
I think it would be wiser to just implement dump features so crashes can be tracked in the same way FIFO tracks graphical glitches.
I opened a bug report
here
As with all issues, it could be great someone reproduced it, so we could say it's 100% a program bug.
That's not a PR, that's an issue report.
Sadly, since I don't even use Windows nor am a Dolphin developer, I cannot help you… and I can't reproduce this issue on my system. The wxWidgets error you saw is not really Dolphin code proper, which is why I personally don't think it's a Dolphin issue (because so far no one else could reproduce it).
(PS: you probably meant an issue on the bug tracker, not a PR. "PR" stands for pull request and is used for contributing code to the Dolphin project, to keep it simple.)
edit: oops. Didn't see your message before posting. Sorry.
I tested further, and it happens with a blank, configured by hand Dolphin (portable mode), that means, I didn't import any saves, savestates, cache, or settings. Turned off background processes and just loaded a game, ALT+F4 and then whatever I did triggered a crash dialog, whether it is loading another game, or exiting Dolphin all around. This behaviour is more frequent in some games like the Mario Galaxy's, and also if you savestate or do some Dolphin related tasks.
More people with the same issue reported the bug
here,
here, and probably
here.
Some research needs to be done on the developer side. Otherwise I hope to get the same issues on stable 5.0 so that would mean it's developer's fault.