I believe both #795196 and #798755 are the same problem, and I have encountered it too; I've reported it upstream at https://pcsxr.codeplex.com/workitem/12230 . It appears to be that kernel 4.1.0 changed how it lays out the address space, triggering a latent bug in the JIT code-generator for x86-64; see the upstream bugreport for more details.
