How to reproduce for sure (it is happening fairly often):
1) Put the cursor like that
USE |Northwind;
Go;
so the highlight goes/crosses from one line to another.
2) Start commenting 20+ times then just start uncommenting (perhaps you need to reposition the cursor at some point in time), boom it goes! Btw, if you make the cursor positioned this way:
USE Northwind;
G|o
or perhaps anyways HE will bomb. I also go the parameter error by just uncommenting. So the key is to comment multiple times.
So, the other time I got the exit condition I allowed the VS debugger to take over the crash, the ending was:
The thread 'Win32 Thread' (0x27c) has exited with code -1073741811 (0xc000000d).
The thread 'Win32 Thread' (0x1400) has exited with code -1073741811 (0xc000000d).
The thread 'Win32 Thread' (0x49c) has exited with code -1073741811 (0xc000000d).
The thread 'Win32 Thread' (0x3d4) has exited with code -1073741811 (0xc000000d).
The thread 'Win32 Thread' (0x7e4) has exited with code -1073741811 (0xc000000d).
The thread 'Win32 Thread' (0x1714) has exited with code -1073741811 (0xc000000d).
The program '[5752] HippoEdit.exe: Native' has exited with code -1073741811 (0xc000000d).
Not sure if this is super helpful