Tracked down to a bug in MSVCR120.DLL, the ball is in Microsoft's camp. On the user side, the workaround is to update to Win7 SP1. On our side, the workaround is to detect FMA3 and if not present, disable it manually via _set_FMA3_enable(0) because Microsoft's are too incompetent to do it themselves.
I'm not going to work on that, fwiw.
Win7 RTM support ended last April. Dolphin not running is the least of their problems. It also affects Vista, but how many Haswell/PD users are using that.
I've got a (controversal) workaround in
https://github.com/BhaaLseN/dolphin/tree/fma3-workaround that may fix the issue, but I don't have any affected hardware/OS configuration, so I cannot try this out. If anyone does their own builds, please give it a try:
(from scratch)
Code:
git clone -b fma3-workaround git@github.com:BhaaLseN/dolphin.git
(if you have a working clone already)
Code:
git remote add bhaalsen git@github.com:BhaaLseN/dolphin.git
git fetch bhaalsen
git checkout bhaalsen/fma3-workaround
Keep in mind that only the windows build for 64-bit is concerned, so build for x64.