https://bugs.winehq.org/show_bug.cgi?id=39141
--- Comment #2 from Armin Altorffer aapmak@gmail.com --- After installing Linux kernel 3.19.8.ckt5-low latency-x64, I ran a lengthy stress test; simply running a Windows demoscene demo on loop, using Wine. To see if the problem would resurface; so far, it has not.
Suggesting indeed that kernel 4.0 and up (all kernels from 4.0 and up have demonstrated this phenomenon for me) are different in some way that causes Wine to seize the machine up completely. Still, that seems odd still; since most of the very low ASM > C changes in the kernel since 4.0 are not in user space and I would imagine Wine operating purely in user space.