New
#31
Yes, that's why it's not enabled by default. The performance penalty is considerable.
Anyway, I think you should consider the possibility that yours is a hardware-level issue. This latest crash is verifier catching NTOSKRNL (the OS kernel) supposedly corrupting its own memory management structures. When you see things like that in a verifier crash, it is frequently caused by hardware.
Mismatched memory? Too-ambitious manually configured timings? Over-clocked? Under-cooled? Plain broken? Any of those are just some of the possible hardware causes.