Verbum 6.9: Graphic driver crash still occurs
FYI I still see fairly regular driver crash/restarts with Windows 10, and Verbum 6.9. This has happened with multiple large Windows updates, about 4 updated NVIDIA drivers, and multiple versions of Verbum. It seems to always happen when I restore Verbum from the taskbar and start to do something - it can be bring a bible up, open library, relatively simple things. It will crash once, maybe twice within the first 30 seconds, and then not at all.
I use this Windows 10 laptop extensively, and Verbum is the only app that has crashed the graphics driver at all for a long time. I know this may be hard to find so I just wanted to let you know it is there. I have learned to live with it.
Comments
-
Bringing up default lectionary layout in 6.9
0 -
This happens to me multiple times a day (with ATI drivers) whenever Chrome opens a notification popup (with transparency). I don't think there's anything that we or Chrome can do about it; programs are just putting pixels on the screen and it's the graphics driver's job to handle that without crashing.
Hopefully Microsoft is collecting telemetry on this problem and sending it to NVIDIA so that they can include a fix in a future driver update. Unfortunately, my ATI video card appears to be so old it's no longer supported, so I don't know if it'll ever be fixed for me... (without buying new hardware).
0 -
I am practically computer illiterate, but could this issue be related to why videos and motion graphics in Proclaim stop working mid-presentation? Despite drivers and all updates being current? We have a NVIDIA card and it appears to be "crashing" at times as the motion graphics stop working and any slide we try to upload after that has jumbled pixels. I have it posted in another thread, but saw this, and enough words were similar, that I figured I'd ask if it could be the same root problem. Gotta love how in churches, those with no qualifications end up in the tech dept :-) Many other people are having this same motion graphics issue.
0 -
Thanks Bradley. I would love to see it fixed, it is distressing that this is the only app that has this problem and I run a lot of complex apps under Windows 10. I have no doubt that it's a driver problem, but under the premise that others have figured out how to avoid it, if it could be investigated I suspect Faithlife could figure out a way to avoid this problem too, it happens so much. I am close to ditching my Windows 10 Verbum and only using the Mac, it really happens a lot if you use the system every day.
0
