And no luck trying to get help from Adobe. They are absolutely useless. This post has been going for 4 months and the only thing they can do is blame the graphic card haha what a joke. I'm going to have to disagree. First of all many of the people hitting this problem are not using Adobe products; they are running video games or other graphics-intensive activities. Second, I'm a software engineer. An application should never be able to crash a PC because an application cannot directly touch the bare metal. Even old software that used pointers, such as the C and C++ I wrote in, in the first 25 years of my career, in a modern operating system is only using those pointers in a sandbox managed by the system's memory management, and if a pointer steps outside the sandbox (say a pointer of all 0's or all F's, or just random bits like 00216ACCF103DE1) it's the application, not the PC that crashes. It's very hard to crash a PC from an application without taking advantage of a bug in the OS or driver. Applications access all the resources of the PC - memory, storage, hardware devices, etc, through various software layers supplied by either the operating system or the device makers (e.g., drivers). And THAT's where the problem is. Device drivers operate in kernel mode, which is to say without the system protections that application software has, so there's nothing between them and bare metal. So device drivers are notorious for crashing PC's. And graphics card device drivers are the worst because the GPU makers turn out so many, so fast and with so many updates that they never thoroughly test them. On top of that they push everything to the bleeding edge of performance envelopes because we're all salivating for the hottest benchmark numbers. Since this crash always involves nvlddmkm.sys it has to be NVidia's fault. And indeed, NVidia seems to be aware of it based on their bulletins . . . Find Answers | NVIDIA ... but ultimately the crash involves their driver so it's up to them to fix it.
... View more