Blue screen of death

Page 1 of 1 (4 items)
This post has 3 Replies | 0 Followers

Posts 3578
steve clark | Forum Activity | Posted: Thu, Nov 12 2009 10:25 AM

Got the dreaded blue screen of death (DOS screen when system crashes) while zooming in on a map in Biblical Places. Don't know if i can reproduce it (not that i would want to) but thought reporting it here might be useful.

QLinks, Bibl2, LLR, Macros
Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1

Posts 25284
Forum MVP
Dave Hooton | Forum Activity | Replied: Thu, Nov 12 2009 4:14 PM

Steve, try to reproduce whist logging --> start L4 whilst holding Ctrl key and sign-in as normal. If it happens again wait about 60 seconds for logging to complete before closing L4. Log files are in \My documents\Logos Log Files. Zip them and attach to your next post or send them to support@logos.com

Dave
===

Windows 10 & Android 8

Posts 3578
steve clark | Forum Activity | Replied: Thu, Nov 12 2009 4:23 PM

Thanks for the tip. It was even worse than i reported. L4 would crash everytime i tried to start it. I ended up calling Logos support. They got me going again.

They have me using the CTL logging.

As for waiting 60 sec after blue screen...the blue screen means that windows has failed and it is the DOS screen which restarts windows. So closing L4 is not an option.

But i am logging for the next several days or a week in case this happens again. If it does i will be sending them the new log file.

Thanks for the tip

 

QLinks, Bibl2, LLR, Macros
Dell Insp 17-5748, i5, 1.7 GHz, 8G RAM, win 8.1

Posts 8138
LogosEmployee
Bradley Grainger (Faithlife) | Forum Activity | Replied: Thu, Nov 12 2009 10:43 PM

steveclark:

Got the dreaded blue screen of death (DOS screen when system crashes) while zooming in on a map in Biblical Places. Don't know if i can reproduce it (not that i would want to) but thought reporting it here might be useful.

On a modern OS, it's basically impossible for a "user mode" application (like Logos 4) to directly cause a blue screen; instead, it's almost always caused by device drivers, a hardware fault, or the OS itself. It's likely that Logos 4 is doing something that's exposing a bug in your video card drivers (especially because you say you were doing something graphically intensive). I'd recommend checking your video card manufacturer's site (or Windows Update, but they're usually a few versions behind) for updated drivers.

Page 1 of 1 (4 items) | RSS