Just upgraded to CS5 yesterday and am having the same issue when I build preview files. Still searching for an answer... any help is appreciated!
Windows Vista Ultimate 64-bit SP2
Intel Xeon 24GHZ (dual quad-core 3GHZ processors)
CalDigit 2TB Raid
Blackmagic Multibridge Pro
More info: If I shorten the work area bar and render a few frames at a time, previews build fine--could be a preview file size issue?
Also, if I turn off GPU acceleration, I can build previews over a larger span of unrendered clips before crashing. Any ideas?
Possibly, for me. But what about the author of this thread? "AdvanceHD", are you using a third party video board? The answer to that may help tie some common strings together for a solution.
I'm having the same issue:
Faulting application name: Adobe Premiere Pro.exe, version: 22.214.171.124, time stamp: 0x4bf119d2
Faulting module name: Backend.dll, version: 126.96.36.199, time stamp: 0x4bf0dba0
Exception code: 0x40000015
Fault offset: 0x00000000001baafb
Faulting process id: 0x15a8
Faulting application start time: 0x01cb1b96d983de39
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\Backend.dll
Report Id: 6d0f1532-878a-11df-a3c5-81e14690b8b6
Crashing during rendering.
I 'm running Windows 7, 64 bit, Dell Covet 6400, Nvida Quadro FX3700M, 4gb ram.
Issue occurs at the same frame, 802 of 2961 everytime I make at attempt to render.I've also noticed the Premier remains in memory after the crash.
Has this been reported to Adobe or added to the bus list? If not, any idea how to get it added?
We got your bug report.
I dont think it will fix your problem but at least update to the 5.0.1 update.
I'm already on version 5.0.1 - unless I'm missing something?
I know you had 5.0.1 but the OP had 5.0.0 listed in his error report part.
Not that I ever thought that would fix your problem.
Wish I could help: GLenn
I realised as soon as I posted that - that you meant the OP! Thanks anyway GLenn.
I've opened a bug with support, hopefully it won't take too long to fix - as it's a real pain not being able to render inside of Premier.
Have you tried changing your Scratch disk to a different hard drive ?
Good suggestion, GLenn. I've tried varying scratch disks. No change.
I am having same extact issue, cannot render due to this error.
Windows 7 64bit / Premier CS5
Core2duo, 2x nVidia 8700m GT's
I have worked in premier for a couple weeks, now I can't get this project to render for the life of me, same error over and over and over.
I updated my NVIDIA card to the latest driver available and seem to be having less of a problem with this... the issue isn't gone, but it's happening on fewer projects--and only in HD projects, which still suggests preview file size. Check your NVIDIA driver version. You can also try changing the "preview file format" under sequence settings to see if other formats crash the system less, or--like me--try rendering tiny blocks at a time... again, not a fix--but a workaround if necessary.
Windows Vista Ultimate 64-bit SP2
24GHz Intel Xeon (dual quad-core E5450 @ 3GHz)
CalDigit 2TB SCSI Raid5
NVIDIA Quadro CX v258.96
Blackmagic Multibridge Pro v7.7.2
Premiere Pro CS5 v5.0.1
I've had bizarre rendering problems in the past, that I never could explain, but at least in my case I found a way to work around them. Keep an eye on the green line indicating what has been rendered; when the error is thrown or the crash occurs, make a note of where the green render bar stopped. When you're back in the program, move the WAB (work area bar) in marker to a point in time that is later than the "trouble" spot. I usually go the next edit, as Premiere renders each individual clip as its own preview file. Attempt rendering again; if the error/crash occurs again, move the WAB-In later in the sequence. If the render succeeds, now move the WAB-In back before the trouble spot, and see if it will render. In all cases that I've had, this has allowed me to finish the render. No guarantees that it will work in your scenario, but it is worth a shot.
My best guess is that this is due to a mildly corrupted project file, as for me at least, it happened infrequently and only in projects where I was stacking a lot of layers.
What I have found since originally posting is that when inside a Blackmagic sequence, instead of rendering I will export. The program seems to render out fine that way. But it is an extra and possibly long method of dealing with it and it doesn't seem to remember the renders when back inside the program but at least I can get the projects out.
I have also started to use the stock Adobe sequences, doing my edit, etc. and when complete only transferring to a Blackmagic sequence if I need to send it to tape.
I did try to do as Colin suggested and it did work in most cases.
The Premiere Pro CS5 (5.0.2) update fixes some issues that result in the "R6025 - pure virtual function call" error. Also, we've been working with several providers of plug-ins, codecs, and hardware devices (such as Cineform and BlackMagic) to assist them in updating their software to fix some errors and crashes. Please take this opportunity to download and install updated codecs, plug-ins, and drivers from these providers, as relevant to your work.
When you have updated Premiere Pro CS5 and your supporting software, let us know whether your problem is fixed.
See this page for details about the Premiere Pro CS5 (5.0.2) update:
Please report bugs that persist after the update here:
Todd - Thank you for your help - it works like a charm!
To the Forum - I just want to say that both Adobe and Cineform really did a
great job here or addressing the problem and keeping me informed. I can
I'm still having the problem, well into v5.0.3 now ...but only in Blackmagic HD timelines. I'll take it up with Blackmagic Design from here.