On Sat, Aug 27, 2016 at 2:19 PM, Bob Hood <bhood2 at comcast.net> wrote: > > From what I can tell, it's not actually a crash. It appears to be an exit() > with a result of 1, so it's not going to be easy to track down. Break on ntdll!RtlExitUserProcess to print a stack trace.