Logos was running in the background when it crashed by itself.
3252.Logos4Crash.txt
6472.Logos4Error.log
David Lee: Logos was running in the background when it crashed by itself. 3252.Logos4Crash.txt 6472.Logos4Error.log
These logs don't tell us very much. We'll need more logs.
Please enable logging by carefully following all the instructions in the link below: http://wiki.logos.com/Diagnostic_Logging
Then run Logos and see if you can repeat the issue that caused the crash. Make sure to post all the log and txt files here for review.
Here are the Wiki instructions for how to upload logs. http://wiki.logos.com/Uploading_Logs
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
This appears to be an error in WPF itself (there is no Logos code in the call stack).
Searching for the error message turns up an (unresolved) post on our forums, and only one other person on the Internet asking about this (http://stackoverflow.com/questions/5471021/nullreferenceexception-in-validateinputdevices). It appears to be an exceedingly rare crash with no known solution.
I looked into the code that's causing the crash, and it appears to be a race condition in WPF. Additionally, this code has been changed in .NET 4, so the bug should be fixed when we upgrade Logos 4 to use .NET 4. Until then, there are no known workarounds.