Thanks Damon. I have identified what went wrong here. Cheers
Hello,
I am marking this topic as resolved for tracking purposes, as we have not heard from you in a few days. If this issue persists, feel free to respond to this thread. For any new issues, please create a new Answerhub topic.
Have a great day
I have now noticed this in the log window shortly after editor startup: “LogCrashTracker: Crashtracker disabled due to settings.”
I am unable to find a switch of some kind in the editor or project settings window.
Could this be the culprit?
The 4.10 logs show the same entry, But the crash reporter shows.
Are you using a source build? If not, you can try downloading and building the engine from source, and then building the Crash Reporter project separately, which is located inside the Visual Studio solution.
Exactly the same issue with 4.12 I get crashed all the time and no reporter ever popped up. It all worked in preview versions.
Hey StMalk,
Are you using a source build?
I have the same issue (4.12.5). No crash reporter and no information in the log other than “Fatal Error” when I click the Play-Button in the engine. I’m feeling like doing nothing else than git reseting/reverting/recompiling 80% of my worktime until my code somehow starts working again.
I tried all the suggestions mentioned in the comments above but I am still unable to get any information out of unreal engine why it stops working and crashes. (UE 4.12.5, Windows 10).
Are you using a source build?
If you are using a build from the launcher, ensure that you have debugging symbols installed. You can check this by going to the Library tab, clicking the arrow next to the engine version you are using (4.12.5 in your case), clicking the options button, and then ensuring that the Debugging Symbols checkbox is checked.
Yes I have the debugging symbols installed. I posted a separate question on this topic here: Crash Reporter not showing up - what to do - Programming & Scripting - Epic Developer Community Forums
(So this can be considered a duplicate)
@ryan20fun hi! have you solved this problem? I’m having exactly the same problem with UE 4.12.5 from launcher.
I made a post in answerhub too where an epic staff member tried to help me, but it seems that he’s out of ideas because I’ve didn’t receive any new reply.
For me is a pain because having the crash reporter with the call stack, cpp file and line number was great for debugging my code.
For me it’s absolutely clear that it’s a bug/incompatibility and it’s great to know that I’m not alone.
PD: are you using intel skylake by any chance?
Unfortunetly not, The log’s say that it has caught the exception.
I have been meaning to do some debugging to find out why the window is not shown, But other things have taken priority.
The only difference for me really is that I have double check if the editor icon is still on the task bar to see if it crashed.
Ok, that disproves my theory about the incompatibility with z170 chipset 
One thing that I’ve noticed is that, even with debug symbols installed, all that I get logged on crash is “fatal error”, no call stack :S. Maybe it’s a problem with the engine itself and not with the crash reporter.
Anyway this means that I cannot debug my code, well… I can, but it’s a pain!
[2016.08.04-18.51.48:415][833]LogWindows:Error: === Critical error: ===
Fatal error!
Do you have windows 10?
I am using a AMD FX 8120, But those high end I7’s look good (But that will have to wait)
I have found minidumps either in the project directory or the appdata one, So you could start there if need be.
One thing I want to do sometime(when I make time) is to copy the engine into a VM and see what happens when a exception is raised.
I have Win8.
I see some minidums in sub folders in “/Saved/Logs/”.
I have not tried loading them into VS yet.
I’d recommend following up with the post linked below for more information regarding this issue: