Blue Screen of Death errors after most recent Storyline update

Apr 09, 2020

I started getting a lot of Blue Screen of Death errors after the most recent Storyline update (4/7/20). IT has worked on my computer but I am still getting the errors and seemingly only when I am working in Storyline. 

 

Is anyone else experiencing this? 

7 Replies
Vincent Scoma

Hi Chrissie,

Thank you for letting us know! 

Does this error appear only when working in Storyline? What is the error message you are receiving? 

It may help to try a repair of Storyline to see if that clears the issue. This guide will help walk you through that process: 

If the issue continues, I would like our Support Engineers to take a closer look. You can connect with them at any time by clicking here

Erin S

I have actually had this issue too! I couldn't pin point when it started, but I've uninstalled and reinstalled over the months.. What i've noticed today is that it seems to be related to publishing courses to the LMS. At least, I've gotten the blue screen at least 6 times today and all I've been doing on the PC is publishing storyline files. (I only ever use Storyline on the PC, so I can't pin it to another program.)

Katie Riggio

Hi there, Erin!

I'm sorry to hear this. We're here to help!

Typically, blue screens are caused by problems with the computer's hardware or issues with its hardware driver software.

Would you be willing to connect with our Support Engineers so we can take a closer look? You can use this link:

Laura Douglas

I as well have been having this occur on many many course, many many growers, including Articulate SCORM Cloud and Articulate review - the only solution has been to apply a seek bar on EVERY slide and advise the learner to grab the seek bar and move it a little bit - and that clears the problem, allowing the page to fully load and the learner to progress.  But it is becoming a tedious process for some learners - in Particular this is most pronounced with Cornerstone (CSOD) But it has happened across the board - going on now for over 3 years.  so for us it does not seem to be version specific - unless it is a reoccurring setting that was added and has been in place for that long.