I have carefully reviewed the crash dump files you sent me. These are my findings:
- None of the threads of the process are in ViEmu.dll or show any ViEmu.dll call in the thread's call stack
- What seems like the 'main' UI thread is somewhere in nview.dll, which is an nvidia driver DLL
- This thread seems to have arrived into nview.dll somehow from CreateWindowEx()
- Inspecting the stack of the thread seems to show that the CreateWindowEx() call was trying to create a VsTipWindow, and nview.dll gets called for some reason (seems reasonable if it is a 'SAVEBITS' window such as a tooltip window)
Although the information is not definitive, as a crash dump file doesn't have all the info, it seems there is some interaction with NVidia's drivers. Could you try turning graphics acceleration off in Windows? A second possibility, although less clear-cut, would be to upgrade the video drivers.
As to my interpretation of how ViEmu 2.0 could trigger this, the VS integration in 2.0 is so different that it's pretty possible that the sequence of window update and creation events could be very different, and could involve a buggy codepath in the drivers.
Of course, it is entirely possible that ViEmu is causing this 'freezes' directly, but the crash dump files I reviewed seem to point into an entirely different direction.
Please let me know anything else that you come up with. If there are other crashes, it would be good to collect crash dump files so that I can review them and let you know whether it looks like the same problem.