Something interesting. It seems that it only happens to the diablo client running in ISBoxer/InnerSpace. Testing for 3rd time, will update. Maybe something with resolutions or another setting is causing d3 to crash there.
Updated some windows settings that ISboxer recommended so we'll see what...