Hi,
I came across an interesting situation. A few of my co-workers ran the code I wrote against an .iiq file (https://mega.nz/#!I4hTFCrQ!hKbRHNQXwy0HxOv3xqBHS47TgvkOL90Ffhc2kX8ICwc). On 2 different computers, they get a warning from windows that their display driver crashed and then repaired itself. It doesn't seem like it's causing the program to crash in any way, but it does cause a conversion call to MagickImage.ToBitmap() to fail and return a black image.
Some initial searches on the internet seems to indicate that it may be tying up too much resource / slowing down the display frame buffer, so Windows is restarting the display driver. Is that something that you've seen? And what would be a good way to mitigate this type of error?
Message from windows event log:
I came across an interesting situation. A few of my co-workers ran the code I wrote against an .iiq file (https://mega.nz/#!I4hTFCrQ!hKbRHNQXwy0HxOv3xqBHS47TgvkOL90Ffhc2kX8ICwc). On 2 different computers, they get a warning from windows that their display driver crashed and then repaired itself. It doesn't seem like it's causing the program to crash in any way, but it does cause a conversion call to MagickImage.ToBitmap() to fail and return a black image.
Some initial searches on the internet seems to indicate that it may be tying up too much resource / slowing down the display frame buffer, so Windows is restarting the display driver. Is that something that you've seen? And what would be a good way to mitigate this type of error?
Message from windows event log:
Display driver nvlddmkm stopped responding and has successfully recovered. Event ID 4101