Choppy display in preview/after publication

[namedujour]

I'm very new to Captivate, so I don't know what I'm doing wrong.

I just created my first software simulation. It was nothing fancy - no audio, no animation. I even removed the highlights on the fields. All it has is screen shifts, scrolling, mouse actions and text boxes. I messed with the slide times a little, but did nothing else. When I realized the preview was acting as if I had a memory issue (images went all wonky), I shut all the other applications down.

The project contains 86 slides. It begins to act up in the middle when I display online help that has a editable PDF form in the window. I demonstrate how you add text to the PDF fields, and the screen goes black for a few seconds, but you see the mouse. Then the image reappears as I'm typing in the field.

Further down it acts up again. It displays the contents of an earlier slide superimposed over the one that's supposed to display. This is where I began suspecting a memory issue - but I have the maximum amount of RAM, so that's odd. But then it heals itself toward the end of the presentation and acts as if nothing is wrong.

I published it to both SWF and HTML5 (I have to post it in Robohelp, so I need both). The published version acts up the same way the preview did.

Are there any known software conflicts that could be causing this? Should I be flipping a switch somewhere to prevent it?

Edited: I tried "Force Re-publish" and it still doesn't work. In fact, there may even be MORE screens that black out on me than before. (I'd have to compare versions to be sure). But you see the text box on a black background, and you see mouse movement. Thoughts?

[namedujour]

Does anyone know how I can contact an Adobe developer about this?

[namedujour]

Update: I called our Tech Support team and told them I suspected an "integration issue" - I have more software than anyone else in the company, so it only makes sense to start there. At first I wondered if I should maybe move Captivate to my D:\ drive to isolate it from all the other software. 

But he messed around on my workstation, and noticed I had Adobe Reader 10, which may have been why things went all wonky on a PDF file in the simulation, but not on any other type of screen.  He said that version had been "quirky" and upgraded it to Reader 11. That appears to have solved the problem! Still testing though. If things continue to go haywire, I'll be back.