Hello - I have just updated from Premiere 5.0.2 to 5.0.3 and also updated my Cineform Neo 4K plug-in to 5.2.5.288

The system previously fine is now quite unstable and crashes often when sliding along the timeline. The fauting module is ntdll.dll (see event viewer log below).

Any ideas on how to fix this?


Source: Application Error
Faulting application name: Adobe Premiere Pro.exe, version: 5.0.3.0, time stamp: 0x4ce382d1
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
Exception code: 0xc0000005
Fault offset: 0x000000000004d036
Faulting process id: 0xbf0
Faulting application start time: 0x01cb995d6a5bd1b1
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 61842af5-0553-11e0-86c2-20cf303e62d1

Did you try uninstalling Cineform to see if the crash still occurs? If no crash then, contact Cineform. If it still crashes, make sure to file a bug report to Adobe.

Thanks.

I have since rolled back Cineform to the previous version I was running (5.2.2.283), but am still getting this new instability problem with Premiere 5.0.3. I have now filed a ticket with Adobe support.

Thanks Steve. Let us know how it goes with Tech Support.

I am having almost identical problem with the new update, whenever I click outside cs5, either to another window, desktop etc it instantly crashes, sometimes it just crashes anyway, seemingly just for fun. Editing is impossible... been down this road so many times in the past with adobe support. Ready to hang myself at this point or start using Windows Movie Maker.

I would occasionally get this with large projects before the upgrade, but even splitting a 22 min show into 3 timelines and editing one sequence at a time I can't get any edits done. I have tried deleting previews, reseting effects cache etc.

System is i7 960 clocked to 4Ghz - 12 GB Mem
O/S on 80 GB raid 0 array (drives - 2x intel x25 SSD's)
Cache on 160 GB raid 0 array (drives - 2x intel x25 SSD's)
Video card Nvidia FX4800

Project is 29 MB and has about 800 clips linked from (200mb/sec average w/r) raid 5 e-sata Array),

Here is the fault.

Faulting application name: Adobe Premiere Pro.exe, version: 5.0.3.0, time stamp: 0x4ce382d1
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b
Exception code: 0xc0000005
Fault offset: 0x000000000004d256
Faulting process id: 0x2a20
Faulting application start time: 0x01cb9a7310a3dcc3
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 606f87e4-0667-11e0-8a91-e0cb4e0ff8b0

OK so Adobe support replied with the view that the problem is a corrupt registry error and advising I contact Microsoft.

Before I do that does anyone have any advice on fixing registry issues? Is there a good registry cleaner or dll fixer I could use? Or would a simple uninstall and reinstall of Premiere do the trick?

I am trying a complete system rebuild right now with nothing other than CS5 and cineform, btw I was also getting crashes due to MSVCR90.dll errors. Some part of me thinks perhaps there is some hardware or drivers in my system that just don't jive well together. So many people report a good experience with CS5 and Cineform but I have been plagued with issues since the dawn of time. CS5 although much richer has been crashing far more that CS3 did. The bigger a project or more linked media, the worse the problem gets.
I will report back with if this is any better after the fresh build.

Hey guys,

Similar issue on my end. I am having a problem when working in Premiere CS5 which causes it to crash. Looking in my event viewer, I see the issue is the file MSVCR90.dll. I have included the text from this below, as well as the link. The entire project uses files Cineform AVI's. You're literally both the first that I've seen with a similar problem.
Been working on this for days, and finally did a system reinstall today. Will report back tomorrow to let you know if it made a difference.

SS


https://cid-b8b5a06569777398.office..../MSVCR%20Error



Log Name: Application

Source: Application Error

Description:
Faulting application name: Adobe Premiere Pro.exe, version: 5.0.2.0, time stamp: 0x4c731297
Faulting module name: MSVCR90.dll, version: 9.0.30729.4926, time stamp: 0x4a1750b0
Exception code: 0xc0000417
Fault offset: 0x0000000000054fc0
Faulting process id: 0xf18
Faulting application start time: 0x01cb94479d2ad0e5
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554\MSV CR90.dll
Report Id: 15ce75e0-003d-11e0-b0a2-485b3914204f
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-12-05T06:58:38.000000000Z" />
<EventRecordID>6595</EventRecordID>
<Channel>Application</Channel>
<Computer>Owner-PC</Computer>
<Security />
</System>
<EventData>
<Data>Adobe Premiere Pro.exe</Data>
<Data>5.0.2.0</Data>
<Data>4c731297</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.4926</Data>
<Data>4a1750b0</Data>
<Data>c0000417</Data>
<Data>0000000000054fc0</Data>
<Data>f18</Data>
<Data>01cb94479d2ad0e5</Data>
<Data>C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe</Data>
<Data>C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe5 54\MSVCR90.dll</Data>
<Data>15ce75e0-003d-11e0-b0a2-485b3914204f</Data>
</EventData>
</Event>

Just wondering what mobo you guys are using. I know its a long shot but I can't help but supect that perhaps we have a driver thats causing issues with the crashing. I have an ASUS P6X58D Premium board and i7 960 CPU, with 12 GB RAM...been thinking about a trying a different board with all the issues.

After rebuilding the system completely Premier still crashes (ntdll.dll) with latest 5.0.3 update and Cineform build 288.

** C:\ drive formated and rebuilt to Windows 7 (64 bit)
** All windows updates installed
** Latest system drivers installed
** Latest Quicktime Installed
** No other software installed, firewall off

This is not encouraging, I am at a complete loss as to what would cause this?

--------------

Faulting application name: Adobe Premiere Pro.exe, version: 5.0.3.0, time stamp: 0x4ce382d1
Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b802
Exception code: 0xc0000005
Fault offset: 0x000000000004d036
Faulting process id: 0x8a0
Faulting application start time: 0x01cb9ba3a6e6daf8
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: a5942b94-0797-11e0-9bf4-e0cb4e0ff8b0

I just reported this issue to the team.

Just wondering what mobo you guys are using. I know its a long shot but I can't help but supect that perhaps we have a driver thats causing issues with the crashing. I have an ASUS P6X58D Premium board and i7 960 CPU, with 12 GB RAM...been thinking about a trying a different board with all the issues.

I have an ASUS motherboard too, but the model down P6X58D-E. Only thing I would say is the problem seems to be new, only appearing immediately since moving to Premiere 5.0.3. Things were fine before. Although it's also fair to say this PC set-up is only a month or so old and the current project I have is more stretching than ones I have had on this kit so far.

Kevin - Thanks for referring this issue. A more in-depth response from the Adobe team would be helpful.

I have an Asus Rampage 2 Extreme, so that's all of us. But I agree with Steve - only has happened since 5.0.3, so I'm at a bit of a loss myself. That being said, it's been a while since I've updated the bios on my mobo, but from what I understand, it's not something that should be done at the drop of a hat. Going to test tonight and will report back. Finger's crossed!

Thanks for the diligence on this Kevin.

SS

I updated my Asus bios a few weeks ago now to the latest while trying to fix another issue. I doubt that will make any difference for you folks. I have gone back to 5.02 for now, I can edit now but it still crashes though not as often as 5.3. I need to finish 2 x half hour shows so in a bit of a fix and trying to remove any footage I don't need from the project. May end up making proxies just to get it done. I re-imported the sequence to a fresh project, tried desktop, tried cineform presets it's does not seem to make any difference with regards to the crash

By the way, during testing with 5.03 I had a bare bones system, the only connected devices were a USB keyboard. mouse, Shuttle Pro 2 controller and external 4 TB e-sata array, no additional cs5 plugins or software and it would crash anytime I clicked outside of the application. I also moved all my files to a different e-sata raid-0 array just in the off chance that was causing the issues but it did not help.

Thanks for looking into this Kevin.

I put in a report about multiple people having the same issue this morning. Unfortunately, I got called away from my office this afternoon but I did see that I got a response. I've got that on my list for first thing tomorrow morning.

Just a post to let you know that we are looking at this issue.

Cheers all.

Great - thanks.

Just tried out cs5 v.5.0.0. Still crashing, error is still msvcr90.dll.

Hope we can solve this!

Here's the answer I got from the team:

"The crash regarding msvcr90.dll last week, and this crash in ntdll.dll are most likely two separate issues.

A crash in ntdll.dll doesn’t point to a bad DLL or a corrupt registry necessarily. Especially since more than one person is hitting the same problem. In general, for those with Cineform installed, it would be good for them to request help in the Cineform forum (http://www.dvinfo.net/forum/cineform-software-showcase/).

It’s also important for them to provide the specific Cineform product and version they’re using, their project preset, and what they’re doing that leads up to the crash."

I've filed a bug report on this with Adobe but I'm running into the "ntdll" problem regardless of whether or not I'm using Cineform files. Curiously, I'm only running into it when switching into and out of another application when I have a titler window open in CS5.03.

I'm running PPro under Win 7 on an I7/920 with 12 gb RAM and a GTX260 (MPE enabled) with a Matrox MXO2 mini. (I'm still using Matrox Utilities ver. 3.1 and have not updated to the recently released version 5, yet.) I'm using Cineform NeoHD v. 5.25b288, but I do not believe that either Cineform or Matrox are causing or contributing to the issue.

Here's the workflow. I scan text from a concert's printed program (cast names, composers, etc.) and run it through OCR. I call up the OCR text file in a wordprocessor (say, WorPerfect X4 or WordPad), open CS5, create a title, and cut-and-paste some text from the wordprocessor into the titles/credit. I've been doing this for years without significant issues. Prior to allowing the CS5.03 update a few days ago, I rarely got a Pro crashes when doing this. (Like, maybe, one every couple of months.)

A few days ago, PPro installed the CS5.03 update. I then started a new multi-cam concert project with 3 AVCHD tracks and 2 HDV tracks. No problems with the editing. No problems with scrubbing the timeline. All but one of the video tracks used Cineform NeoHD files. I was running under a Matrox 1920x1080i/29/97 project (that's 60i for those who insist on using the older terminology). Now, at the end of the project, I'm working on titles/credits, and I get frequent crashes in PPro when I alt-tab back to CS5.03 from WordPad. The Win 7 event viewer log has the error message listed at the outset of this thread.

Sometimes, I can go out and back 6 or 7 times before PPro crashes. Sometimes it crashes on the first alt-tab to the other app.

The source program does not seem to make any difference to this. I tried this with WordPerfect as the source and and also tried going directly from the OCR program (OmniPage SE4) and get the same problem.

The reason I think that this is not related to the Matrox presets or the use of Cineform files is that I get the same problems when I tried switching out and back from other apps in new projects without using Matrox presets and without Cineform files. That is, I rebooted the computer, set-up entirely new projects, created sequences using using only Adobe HDV or AVCHD presets, imported the original HDV or AVCHD files, and then tried to create titles by cutting-and-pasting text from WordPad. I also tried uninstalling Cineform NeoHD, rebooting, repeating the cut-and-paste test, and still got the same crashes in PPro.

Today's new development in this is that I also see PPRo crashing when I: (a) dynamic-link a PPro project to Encore; (b) author a DVD in Encore; (c) burn an image; (d) close encore and (e) go back to PPro only to find that it has locked up and eventually gives me the message that PPro has encounterd an error and needs to close.

Hi Kevin,

While I appreciate your help on this, I must say that I'm a bit discouraged. Did your team take a look at my .dll issue? All I'm seeing are suggestions for the ntdll.dll issue that Rich and Steve had, which, as you said, is separate. Apologies if the frustration is coming through, it just feels like the buck is getting passed here.

SS

I emailed the team again. While we are awaiting another response, can you please repost your issue in the Cineform forum? We think it is a Cineform issue.

Make sure to post your version of Cineform, your project preset and what you were doing that lead up to the crash with your Cineform post.

Kevin - I think what you are suggesting is the common link could be we are all using Cineform in some way (we may still have the plug-in installed even if not using Cineform AVIs - Jay's situation?). So I will post a ticket with Cineform support and update you back on this forum on their response.

As mentioned in my posts above, given that the problem only emerged for me when I moved to Premiere 5.0.3 - Cineform / Premiere were working fine before - I'm not sure Cineform is the full story here. But the Cineform team are always helpful so let's see what they come back with. I am keen to resolve this issue for all of us.

Shmuley,
Let's try to resolve your issue back on your original thread. Please see my post over there.


Hi Steve,
Yes, please repost the issue on the Cineform forum. Thanks for reporting back with what Cineform has to say. We are working with some users to see if Adobe Premiere Pro is causing issues with Cineform or vice versa.

Hello Kevin - I have just posted a ticket directly with Cineform support (rather than on the DVInfo.net forum). I will update back here on progress.

I also have filed a trouble ticket with Cineform. For the reasons stated in my previous post, I remain doubtful that this is a Cineform issue, but we'll have to wait and see what further investigation turns up.

Heard back from Cineform on my trouble ticket. This is what they told me.

"I saw the forum post and i've been communicating with steve about this same issue. although i'm not sure why kevin from adobe sent you both here when the faulting module is not ours. that said, we certainly want to figure out what is going wrong. this is happening on my home edit computer as well... and like you, it seems to happen during dynamic link operations."

"I'll share your findings with david newman when i'm in the cineform office tomorrow and hopefully be able to reproduce the issue on a debug system. I'll let you know if we come up with anything."

Hi Guys,
Believe me, we are working hard to get to the bottom of the issue. Will follow up in the morning with you. Thanks for your patience on this. I'm giving it my all.

Thanks. I appreciate your effort. I, at least, am able to work around this thing for the time being.

Cineform have just sent and asked me to test a replacement file for one of their components. I will check it out over the weekend.

Cool Steve, let us know.

Yes please keep us posted with regards to the cineform file.

By the way, I reverted back at 5.02 (cineform build 281) and moved my cache media and database to another drive raid0 array and so far I am not getting many crashes (every hour or so), perhaps this is related to media cache ? - Would be nice to have a rock solid system I gotta say.

I also received the Cineform file -- an older version of the Cineform importer plug-in. I swapped that one in. Crashes continued. PPro became more and more unstable. After restoring the previous version of the file, I continue to get frequent ntdll crashes.

I was going to try to revert CS5.0.3 back to CS5.0.2 (under Win 7, right click the PPro icon, select "revert to previous version".) I now discover that all of my restore points have been erased and Windows only lists the Windows updates on December 16 and 17. Everything prior is gone.

I was contemplating an onerous complete uninstall/reinstall of all of CS5, Cineform and Matrox. Before starting that, I tried creating a new admin user profile and deleting the one in which I had been running PPro. So far, things are a great deal more stable, so I'm trying to get some editing done for a Monday deadline.

A further update.

I found what seems to be a possible new culprit, at least on my system. One is that there seems to be some incompatibility between CS5.0.3 (when used with MXOs mini) and some of the most recent Win 7 "critical" security updates. I had tried uninstalling and physically removing the Matrox hardware and software and still got frequent PPro crashes. When I rolled back the last couple of Windows security updates, I stopped getting the frequent crashes.

I'm now back to using Cineform and the MXO2 mini. However, for some reason, PPro CS5.0.3 is only letting me have one multi-cam sequence per project. If I try to create a second multi-cam sequence, PPro hangs. The event viewer simply says that PPro CS5.0.3 stopped communicating with Windows. It does not seem to be reporting errors in the "ntdll.dll" module. So, for now, at least, I can edit enough to meet Monday's deadline.

Am having a problem here too: whenever I try and export from PPro via AME I get an error screen that says "PPro Headless.exe has stopped working"
The error message in full is below and includes the ntdll.dll issue.

I am not using Cineform but I AM using MXO2 with most recent (5.00) drivers.
Am now going to try installing MXO2 Mini with Max and its drivers and see if that improves things.

Cheers

Mark


Problem signature:
Problem Event Name: APPCRASH
Application Name: PProHeadless.exe
Application Version: 0.0.0.0
Application Timestamp: 4ce34c66
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16559
Fault Module Timestamp: 4ba9b802
Exception Code: c0000005
Exception Offset: 000000000005664c
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 75cb
Additional Information 2: 75cb8e21ed726286b9cdb2651d59de91
Additional Information 3: 523a
Additional Information 4: 523ad2da949d500e4fecab2b3c5e5efd

I have now had two full days of editing with the test file sent to me by Cineform support and have not had a recurrence of the ntdll.dll faulting module error I had after moving to Premiere 5.0.3

My system did crash once while attempting to render, but the error reported involved a different file CFHD_File_Exporter.prm. The project monitor play button also locked up a few times requiring me to exit and restart Premiere. But I suspect these are separate issues.

Overall my system is much more stable vs. being barely useable before installing the test file.

I have now responded back to Cineform support. So hopefully this means this issue is on the way to getting sorted.

That's great news, Steve. I've been watching from the sidelines on this issue. Thanks.

Nice to know, after I get done with my latest project I will give it another try with the test file, mabey cineform will update their next package with it.

We continue to monitor this situation, we don't believe we are the cause as there are several reports from non-CineForm users, but we looking to find a workaround. Please work with both Adobe support and that of the affected plugin vendor.

David Newman
CTO, CineForm

5.02 and build 281 has been pretty stable for me the last few days David, thanks... will stick to this for now, indecently when I built a fresh O/S for testing I only had CS5.03 and latest (288) Cineform installed no other software or plugins at all and it crashed constantly (every time clicking outside the application window the dreaded ntdll.dll error. We can't rule out weirdness with our systems I guess also, so I have ordered some new faster memory (24 GB - 1600). If that fails I will get a new mobo, if its still unstable I may put my head in an oven for a while or maybe switch platform or app. I have a lot of time invested in my current system would be a shame to let it go :)

Hi All,
Thanks for your patience. We're still looking into and working on this issue. One thing our engineering staff is looking for is a debugger from any crash you have. If you do have one, please contact me by email and attach the debugger to the mail.

Thanks!

5.02 and build 281 has been pretty stable for me the last few days David, thanks... will stick to this for now, indecently when I built a fresh O/S for testing I only had CS5.03 and latest (288) Cineform installed no other software or plugins at all and it crashed constantly (every time clicking outside the application window the dreaded ntdll.dll error. We can't rule out weirdness with our systems I guess also, so I have ordered some new faster memory (24 GB - 1600). If that fails I will get a new mobo, if its still unstable I may put my head in an oven for a while or maybe switch platform or app. I have a lot of time invested in my current system would be a shame to let it go :)

I'm now using CS5.03 (because I have been unable to roll back to CS 5.02). I was able to roll back to Cineform NeoHD 281 and have been using the Matrox 3.01 software. As noted above, I created a new admin user account on Sunday and rolled back the previous two Win7 "critical updates." I deleted the user account I had been using. I was able to finish the project I had on Sunday and deliver it Monday morning without a crash as long as I did not try to create another multi-cam sequence in the Project. I did another project on Monday and had only one crash which was not a ntdll issue. (This was a problem I used to see under CS2 where the audio tracks would get stuck and continue to play even when the video stopped.) The Monday project was a concert project with two HDV tracks and 3 HDV, all converted to Cineform, I had no limitations on having multiple multi-cam sequences as had been the problem with the previous project. Previously, I had found PPro's title functions to be unstable, but I've done multilayer 30 plus titles without a lock-up or crash The only real issue I have had is an annoying 1-3 second lag when clicking "play" on the timeline after making edits. and when adding titles. I don't know if Cineform build 288 had anything to do with the stablity problems. I rather doubt that it did but I haven't had time to see if the newest Cineform build makes any difference. I also finally got through reading the update notes for the Matrox Mini ver. 5 software and it sounds like it might be troublesome for a while, so I'm going to skip that upgrade until I get to a point where I don't have projects stacking up on me. .

I am planning on trying 5.03 and latest cineform again shortly to see if the crashes return. I upgraded RAM from 12 to 24 GB, the system seems smoother and more stable with 5.2, no crash yet since installing new memory for 5.02. One thing I always do is take ghost backups periodically of different builds. This way if the system tanks I can revert back to a working build within about 10 minutes. Ghost 15 for Win7 works well for me, and my SSD raid 0 logical volumes. Will report back with a status on trying 5.03 again shortly.

Will be interested to hear how you get on.

My system is still limping with additional issues even though no more ntdll.dll crashes since my last post. Per requests above, I have sent more info on this to both Adobe and and Cineform today.

Hi Steve,
I passed along your crash log to engineering. We're back from our holiday break, so work will now continue on this issue. Thanks for your cooperation.

Just a quick update regarding 5.3 and the ntdll.dll module error.

I upgraded my system to 24 GB of new RAM and overclocked it to 1600, also the CPU (i7, 960) is overclocked to 4ghz and the system is running very stable. I have upgraded to CS5 5.3 and using build 291. So far its running very well, I have not had the system crash yet and I have been editing for about 8 hours and so far so good. The only niggly issue is every so often the source monitor stops playing back any loaded clips for trimming and I have to restart the app. I have a feeling this is a cineform issue because it happened before and they released an update fix. Other than that the system seems fine.

Another point is my system is only using about 10 to 11 GB of RAM, I am wondering is this is due to the amount of cores?

I have been using Cineform build 291 with Premiere 5.0.3 too and have had no recurrence of the ntdll.dll crash either...

However, I am experiencing a similar issue with monitor playback ceasing to work. Although in my case with the program monitor. If you don't close and reopen the application at this point you can induce a crash. Also creating sequences out of sequences causes the system to crash too. Am finding these problems start to cause real issues with a larger project.

Both these issues reference Cineform files in the error reporting. Have been in touch with Cineform so hopefully further fixes are on the way.

Thanks for the update Steve,

Although I have not had any ntdll.dll module crashes yet. Today I had 4 app crashes due to MultiBand2.dll. Never had this before with 5.2, its a dynamics compressor chain I am using I think. If it ain't one thing its another :)

Faulting application name: Adobe Premiere Pro.exe, version: 5.0.3.0, time stamp: 0x4ce382d1
Faulting module name: MultiBand2.dll, version: 2.0.0.1, time stamp: 0x4b042ca5
Exception code: 0xc0000005
Fault offset: 0x0000000000066054
Faulting process id: 0x26a4
Faulting application start time: 0x01cbb28a3e4fc4a8
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CS5\Plug-ins\en_US\VSTPlugins\MultiBand2.dll
Report Id: 36a523d8-1e82-11e0-9811-e0cb4e0ff8b0

Another update on 5.3.

After playing with CS5.3 and cineform build 291 for a few days I have found several bugs, well for me anyway. The biggest of them is I am unable to output (cineform 4:2:2 filmscan avi's) via adobe media encoder, the project starts working for a few mins and then halts / - frames seem to freezes. I tried this several times with the same issue with 2 projects. Each timeline is a 22 minute master sequence with 3 nested sequences inside, I am only doing it this way due to crashes. The second bug is very often the source monitor stops responding, The 3rd issue is the program crashes or stops responding.

I have ghosted my O/S and app build back to 5.2 and CF build 281 and all seems to be good (so far) and I am able to export again. I shall stick with this build I think for now until other significant updates come along.

Rich, that's exactly what's happening with my system. I've been following this thread for a week or so to see how it plays out. I just recently upgraded from CS4 to CS5, at a time when I finally had CS4 running very stable, and immediately updated to 5.0.3. I've been experiencing these problems since day one with CS5.

I just got off the phone with a buddy of mine who has been stable for quite a while. I ask about the what versions he's been running. He's on 5.0.2 and Cineform build 289. He's been editing very confidently for a couple of months now. I'm seriously considering an uninstall of both softwares and a reinstall of 5.0.2 and build 289.

Chad

Hi Chad - I think its worth a shot, my experience with 5.3 has been pretty miserable, a lot of wasted time with crashes, testing, tweaking, crashing, more tweaking and more crashing etc. It would be nice to have the latest code but the 5.02 build I have is much more stable, and for now I think I will just stick with it unless there is a compelling reason to try the upgrade again.

If you go back to 5.2. I would recommend that you delete all rendered previews and clean the media cache database.