hi titus, thanks for providing a crash id - we have seen similar reports by other EMET users as well, apparently it's the SEHOP policy in the tool that causes these issues...

ok, and how can the problem be solved?

(thanks for your answer so far)

i am not familiar with the tool myself so i cannot give you proper instructions, but please try to play around with the sehop setting as indicated or else keep emet disabled. please also note, that over the long run microsoft will stop supporting that tool: https://technet.microsoft.com/en-us/security/jj653751