Mirh, either you do not have much experience with DRM in general or are intentionally assuming I don't know what I'm talking about, fair enough. I'm a software developer with experience on the system side and a gamer for decades with an interest in how DRM works. I suggested a possible investigation route for this issue based on the symptoms, not the root cause per se. Steam DRM is a joke but individual releases can attach their own custom DRM on top of it (including Securom etc which have trigger-based checking in more recent versions) which may cause such issues. Various software configurations and interactions including those by the video drivers provided by the manufacturer themselves (as can be seen in known issues in release notes) can cause BSODs due to a variety of in-game events, a kernel panic can be triggered by any hardware operation the OS deems "unsafe" and the chain leading to said crash can be tough to pinpoint. If the issue is repeatable and no other game has it on the same system and the issue happens to other different systems over time there has to be a link between how the issue was fixed and the cause of the crash.
And no, it is not sense when after proof that was asked for is provided,the requirements are suddenly changed. Once proof is provided, the reasonable course of action would have been to use the talk pages to probe but more importantly before reverting anything with a "Nonsense, his system is broken" on the first edit, a simple search would have shown this issue predates the report and bears investigating. It is not my intention to escalate but withholding a fix from people who might need them on a whim isn't right.