NIV84 crashing Logos 5
Comments
I have been using Logos 5 without any problems (Dell Studio XPS, Win 7, i7, 8gig RAM). In the last week the NIV84 exclusively crashes the application. "Logos Bible Software 5 has stopped working." Is there a way I can reinstall NIV84 or is there a better suggestion? Many thanks.
By all means, turn on logging as suggested above so we can see just what is happening.
Before hiding/unhiding, there is something else we can try, if the NIV84 is your preferred (1st prioritized) Bible: Set another Bible as your prioritized Bible, restart Logos and type update resources in the Logos command bar. If the NIV84 isn't your preferred Bible, or this didn't work for you try the next step.
To "reinstall" the NIV84, first make sure it's not your preferred Bible (just choose another as your preferred, or prioritize another as first in the list). Then 'hide' it, following the directions here: http://wiki.logos.com/Hiding_Books and restart Logos.
After confirming that the NIV84 is no longer in your Library (CTRL-L opens the Library), unhide it from your settings pane (right click, select unhide) and restart Logos again. This will download a new copy of the NIV84.
NOTE: sometimes hiding doesn't remove the resource from your library. If that happens to you, report back.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
Thanks so much for your help.
NIV84 is my preferred Bible. I tried setting to a different Bible and updating resources but this one didn't work. I haven't hidden the file as yet; I thought I would uplad the log files first.
Thanks.
This appears to be a crash inside WPF when it is trying to draw a bitmap to the screen. I've never seen error 0x88982F04 before, but it means WINCODEC_ERR_WRONGSTATE and (according to various forum posts) seems to indicate that the WIC imaging library isn't being used correctly, which is unfortunately out of our control.
I'm trying to guess why this might suddenly be happening, and am wondering if you have been using a custom highlighting style with an image off your hard disk? If you have, that may be causing the problem.
To test this, we could try opening the NIV to a chapter that doesn't have any highlights. In the command box at the top of the program, enter "open niv to gen 1:1" and press Enter. (Of course, if you were recently working in Genesis, use "open niv to lev 1:1" or some other chapter.)
If that doesn't crash, the problem may indeed be with a particular highlight. To try to fix it, open the Notes document that contains your highlights for the NIV. Find the most-recently-added highlights, and use the highlight style control (the coloured box to the left of the note) to change the custom highlighting style it uses to something without an image, e.g., yellow highlighter or Highlight with note color. Then open the NIV to that location and see if the crashing has stopped.
If the problem is highlighting, was it created on this computer, or synced from another computer?
This appears to be a crash inside WPF when it is trying to draw a bitmap to the screen. I've never seen error 0x88982F04 before, but it means WINCODEC_ERR_WRONGSTATE and (according to various forum posts) seems to indicate that the WIC imaging library isn't being used correctly, which is unfortunately out of our control.
Finally, an interesting bug for you to research, Bradley. 
Donnie
Hi Bradley,
I think you have touched on the problem here. I have opened to Leviticus 2 and have no highlites there and Logos 5 has not crashed. I also access NIV84 from my iPhone (Logos App) but only use it for reading, not for mark ups etc.
How do I access NIV highlights through a notes page? I have highlighted the NIV using the imaged highlighters (not straight edged) directly in my NIV - they're all through the whole Bible. I have a notes doc for every book with hundreds of notes in each but there are no references to highlighted text. How do I access that?
Interestingly enough, I just selected some text to highlight in Lev 2 and went to Tools > Highlighting and Logos 5 crashed before opening the panel.
Jared
Interestingly enough, I just selected some text to highlight in Lev 2 and went to Tools > Highlighting and Logos 5 crashed before opening the panel.
Unfortunately, this sounds very bad: it's likely that is WPF crashing when trying to display the built-in image-based highlighting styles. We're not able to reproduce this crash, but we may be able to add a workaround for the WPF/WIC bug. Ultimately, it seems likely that something in Windows itself is not functioning correctly and needs to be repaired; however, there aren't (AFAIK) tools supported by Microsoft that can repair WIC or WPF.
Follow these steps and up load logs. http://wiki.logos.com/Diagnostic_Logging
Mission: To serve God as He desires.