Hi MGW07 and welcome to our community
I've seen this reported a few times as well as having seen it happen myself. I believe that I finally narrowed it down to this. Memory is being exhausted. Assume you have recorded in full motion mode. Further assume that you end up with perhaps 40 slides that each contain a full motion clip. As each full motion clip plays, it is loaded into memory. What I seemed to observe was that as my virtual memory filled up, I then saw the red screen of death you are talking about.
Note that it required me to jump through some hoops in order to induce this myself. I have 2 gigs of RAM and a fairly large paging file. So I had to manually reduce the size of my paging file before I could induce the issue.
The bottom line here is that as each full motion clip plays, it is retained in memory and not released to free memory.
About the only suggestion I can offer is to create smaller segments and limit full motion. You should also report this as an issue via the WishForm/Bug reporting form. You may do so using the following link: Click here to visit the WishForm.
I need to induce the "red screen of death" in the fastest possible way , so that I can verify that a problem has been resolved.
I tried reducing page file size to 0 and even installed a memory bloater tool, with no luck.
Is there quick easy way to recreate "red screen of death"?
I was once advised by a member of the Captivate development team that in version 4 they resolved the issue of Red Screen Of Death. (RSOD) So if you are attempting to reproduce it using this version, it may well be a futile attempt.
Out of pure curiosity, why do you need to induce it?
Helpful and Handy Links
I am getting red screen with adobe flash
Player 9 in a live environment.
When application runs continuously on a pc that
has not been restarted in approximately 3 weeks.
I am trying to fast track the creation of
this error in a test environment.
I did not create SWF. I am integrating it into a java application.
It is definitely not fixed in Captivate 4. Maybe in 5 when it comes out? I am troubleshooting for a coworker (we are both new users) on a similar project where she is using FMR. She has an older machine, so the virtual memory explanation makes since.
I have a brand new machine with about 8 GB available, and I still have the red screen when I publish to her project to AVI. Time on clip is only 2:52. (min/sec).
I am going to reboot (it's been a while) and try adjusting some settings to see if it solves the problem on my side.
Seems to be just further confirmation that Full Motion is *NOT* the strong suit of Captivate!
So out of idle curiosity, how long is the clip? Just a few minutes or more like an hour?
Helpful and Handy Links
It's 2 minutes 52 seconds long. Rebooting, closing all other applications, and quadrupling the size of my paging file had no impact at all. Interesting that all the other clips she created - all between 1 and 3 minutes in length - are not having this issue.
Bottom line is that FMR is not the right way to use Captivate. My coworker is coming over from Camtasia and she jumped on FMR because it looked just like what she already knows. There's no reason why we can't learn to use Captivate according to its strengths - just going to take some time (and maybe a training class).
For what it's worth, I used the same FMR twice in a project, once recorded "live" and the second a copy of the first. The first ran fine but the second resulted in the red screen of death when published to SWF.
I opened a new project, into which I imported the good FMR. I then opened my original project, imported my good FMR back from the new project and presto. Now both FMRs work fine. Just copying an FMR inside Captivate was enough to corrupt it evidently.
I wouldn't give up on FMRs, they are a valuable tool when illustrating processeses going on in between mouse clicks. The key is to keep the FMRs short, so you can redo them if necessary.
Hope this helps.
What version of Adobe Captivate are you using?