Bug:Biblical places crashes

I am running Beta5. Whenever I open Biblical places, it crashes after about 30 seconds or so. Initially the problem was discovered when I opened Biblical places from PG, but the same thing happens when I open Biblical places from a blank screen. After about 30 seconds, I get a message saying the Logos had to close and the program crashes.

System Specs

3480.Logos4.log

Find more posts tagged with

Comments

Bradley Grainger (Logos)

This is a crash in WPF that's possibly caused by your video drivers. (Unfortunately, the log doesn't provide much more information than that.)

Rosie Perera

https://community.logos.com/discussion/comment/82171#Comment_82171

Bradley, I wonder if the Error earlier up in the log before the crash ("Error ResourceRichTextUtility Couldn't load color_green.jpg from LLS:RCL: No imaging component suitable to complete this operation was found") has anything to do with setting up the scenario where the crash could occur?

I'd hate to leave someone with a crash where they can't use some feature of Logos because "it's WPF's fault; nothing we can do for you." Why might this be happening to him and not to other people? Any suggestions about how he might try to work around it or how he could narrow down what about his configuration is causing it? Or ways that you might be able to reproduce it on a configuration on one of the Logos development machines?

Ken, could you try some things that might help: Update your video drivers. Make sure you've got the latest updates for Windows. Try it with only one monitor. Does it still crash? Maybe Bradley has some other ideas...

Ken Guenther

https://community.logos.com/discussion/comment/82189#Comment_82189

Thanks Rosie. I have recently updated my video driver. I have the latest update for Windows. But when I reverted to only using my laptop screen rather than multiple screens, the program stopped crashing. So the problem is due to using multiple screens. I tried viewing Logos only on the laptop screen while still keeping the other screen active, but it still crashed.

Rosie Perera

https://community.logos.com/discussion/comment/82193#Comment_82193

Ken, that's useful information. Perhaps others who have dual monitors could try this out? I'm sure it would have been noticed by now if it were a really common thing as plenty of other users have dual monitors. I don't so I can't try it here.

Have you noticed any crashes at any other times in other applications, or only when doing Biblical places in Logos?

Ken Guenther

https://community.logos.com/discussion/comment/82195#Comment_82195

The second monitor is relatively new - only a little more than a week. But this is the first time that I have noticed any problems, and the first crash that I have had in Logos 4.

Ken Guenther

https://community.logos.com/discussion/comment/82198#Comment_82198

After playing with different options a while longer, I have been able to keep Biblical places from crashing while still using multiple monitors by 1) reducing the color depth to 16 bit on the 22 inch monitor OR 2) disabling desktop composition (Vista Aero) on the compatibility tab for the Logos shortcut. Either of these options prevents the program from crashing.

Rosie Perera

https://community.logos.com/discussion/comment/82230#Comment_82230

After playing with different options a while longer, I have been able to keep Biblical places from crashing while still using multiple monitors by 1) reducing the color depth to 16 bit on the 22 inch monitor OR 2) disabling desktop composition (Vista Aero) on the compatibility tab for the Logos shortcut. Either of these options prevents the program from crashing.

That's more helpful info in debugging what's causing this problem. I hope Bradley will visit this thread again and give some further thoughts. It's too bad for you to have to run with your color depth at only 16, or with Vista Aero disabled. But at least you've got a workaround for now to let you continue working. My understanding is that a new version of WPF is due out in March or something, which might fix some bugs that Logos users have been experiencing. But not knowing exactly what this bug is makes one wonder whether it has been reported to them so they can fix it, if indeed it is their bug. Hard-core WPF clients like Logos should be the ones reporting the bugs to Microosft, so I hope they can get enough info from what you've given to be able to report the bug to Microsoft.

Douglas Stolberg

https://community.logos.com/discussion/comment/82285#Comment_82285

I have suddenly started having these same problems, whenever I open one of the Biblical xxx tools it crashes within a short period of time. I haven't had this problem on this machine at all until tonight. I pursued the adapter drivers issue by going to Dell and downloading/installing the current drivers and found out I had a newer one installed than the Dell site. I rolled back to what was on Dell. It made no difference. This is very frustrating. Any help? Here are the crash logs.

4505.Logos4crashFiles.zip

Mark

Melissa Snyder

https://community.logos.com/discussion/comment/116091#Comment_116091

I have suddenly started having these same problems, whenever I open one of the Biblical xxx tools it crashes within a short period of time. I haven't had this problem on this machine at all until tonight. I pursued the adapter drivers issue by going to Dell and downloading/installing the current drivers and found out I had a newer one installed than the Dell site. I rolled back to what was on Dell. It made no difference. This is very frustrating. Any help? Here are the crash logs.

4505.Logos4crashFiles.zip

Mark

The crash log indicates that the error was on the render thread. This error indicates a problem with the video driver, and has been resolved in the past by updating to a new version, or rolling back to a previous version. If the problem started recently, it most likely can be attributed to a specific event, such as a Windows Update. If a new Microsoft video driver was installed, that could have been the cause. I'm surprised that installing the Dell driver wouldn't have fixed this issue. You may need to remove the display adapter in Device Manager, then reinstall using the latest Dell driver.

Since you have 4.0b SR-1, it's best to post in the main Logos 4 forum, rather than the PC Beta forum, or call Technical Support for assistance, if possible.