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.

Thanks for the tip. I'm going to give it a shot over the weekend. I'll let you guys know how it goes.

So far, so good
 

Here's an update. I unistalled everything Adobe and Cineform related, deleting all render and cached files that I could think of. I then ran CCleaner to make sure the registry was good to go.

Then I reinstalled Adobe CS5 fresh and new, 5.0.0. Before I updated I installed the newest Cineform build, 291. Then I updated CS5. After several unsuccessful attempts to download 5.0.2 from Adobe's archive, I updated to 5.0.3. I had work to do, so I figured I'd give it a shot. Update was successful.

So far editing has been much more stable than before the reinstall. I have not yet re-enabled the Mercury hardware engine though. I'm suspicious that it might the problem as the 5.0.3 update was primarily a CUDA support update. I have not yet tried any exporting either.

More later as I find issues.

Chad

Thanks for the update, Chad.

Seems to be stable
 

I've rolled back to CS5 5.0 and am running Neoscene's 5.2.7.290, codec V. 6.9.2.529. Seems to be working OK. Am very reluctant to update Adobe CS though.

Thanks Shmuley. If you do upgrade and run into trouble, please post and tell us the details.