toggle quoted messageShow quoted text
Have you tried turning off the “Use accessibility driver for screen capture” option in the JAWS settings? If this doesn’t help, the next step would be to contact Microsoft’s accessibility support and ask them to analyze the minidump files that are created when the system crashes. If I remember correctly, they’re in c:\windows\minidump
From: email@example.com <firstname.lastname@example.org> On Behalf Of Max
I am using Intel HD Graphics 4600 display driver.
When I remove JAWS completely from my system, this BSOD does not occur anymore.
I have found users of other applications experiencing the same thing (https://www.bleepingcomputer.com/forums/t/654578/bsod-triggered-exclusively-by-faststone-image-viewer/)
I am wondering if this has been reported before here and if not what possible workarounds there might be?