Premiere crashes on icon view

Dear Adobe Community,
I'm having serious problems with my Premiere.
I work with the latest version (7.2.2) of the application on a Windows PC.
My configurations are the following:
Intel i7 2600k @ 3.40 GHz
16GB DDR3 Corsair Vengeance @ 1600MHz
120GB SSD Samsung 840 Series Basic
Sapphire ATI Radeon R9 270 2GB VRAM
I have the latest drivers installed.
The crash occurs as soon as I try to switch from list view to icon view in my project browser. The thumbnails come up but Premiere crashes with a serious problem notification shortly after (no further infos whatsoever).
I've tested my RAM by using MEMtest86: No errors. I have narrowed it down to my graphic card. I plugged it out for testing and had no problems with the icon view.
The graphic card has currently the AMD Beta-Driver (14.3 Beta) but that didn't help. Before that I had the 13.12 version installed.
I've also tried switching the Open_CL Support off.
Do you have any idea what could be the problem?
Thank you very much for your answer in advance!
Greetings,
Nicolas

I'm having the same exact problem when I switch to Icon View from List View, except my crash occurs almost as soon as I start scrolling through the Icons/thumbnails.
This crashes my system EVERY TIME!! I have the latest updates for my Mac, Premiere Pro CC and my nVidia CUDA drivers.
I would greatly appreciate someone's help. Thank you in advance.
Regards,
Dave

Similar Messages

Premiere Pro crashes when scrolling in Icon View

Dear Adobe Community,
My Premiere Pro CC crashes EVERY TIME when I switch to Icon View from List View, almost as soon as I start scrolling through the Icons/thumbnails.
I have all the latest updates for my Mac, Premiere Pro CC and my nVidia CUDA drivers. Also, my Renderer is set at the CUDA setting.
I would greatly appreciate someone's help. Thank you in advance.
Regards,
Dave

What is the pixel size of the photos?
Try updating or rolling back your video driver.
Try disabling GPU acceleration.

How to sort clips in icon view mode in Premiere

I am trying to sort clips alphabetically or by metadata in the icon view mode. When I switch from list view to icon view, premiere seems to arrange the clips randomly, not even alphabetically, which is frustrating because I can't even see the entire clip name. I love icon view mode, and it's nice to be able to drag the clips around, but I would like even more to be able to sort them.

You can't sort in Icon view as their are no 'columns' to sort by. All you can do is move then around manually.

Can't view most folders in icon view, it just crashes.

When I try to do icon view in most folders, finder freezes and restarts. But the strange thing is that icon view works in most sections of my home folder.
http://www.youtube.com/watch?v=DjyHbiO_cY4

Try another user account to see if it is only in your account.
Also, try starting in Safe Mode which will disable any third-party extensions that might be interfering.
If either of those prevent the issues, we can try to sort it out from there.

Maps crashes on satellite view

Each & every time. Why does maps do this? Is it because it's an unfinished piece of alpha software that a chimpanzee could have written or is there another reason?
Jon.

I'm having the same exact problem when I switch to Icon View from List View, except my crash occurs almost as soon as I start scrolling through the Icons/thumbnails.
This crashes my system EVERY TIME!! I have the latest updates for my Mac, Premiere Pro CC and my nVidia CUDA drivers.
I would greatly appreciate someone's help. Thank you in advance.
Regards,
Dave

Any way to get frame accurate in icon view mode?

Does anyone know if there is a way set frame accurate in points in icon view mode? I know that if you are "hover scrubbing" a clip, and then click on it you can use the JKL keys to shuttle through the footage. But is there any way to go frame-by-frame through the footage as well?
I ask because I have a 4-camera shoot where the clips were synced by a slate clap. I'd like to make a multicam clip from the shots so am going through and setting the "clap" as the in point of each clip, and then using them as sync points for the multicam clip. I hover scrub to the general area of the slate clap (works great) then use the JKL key to narrow in "clap" even more (also works great). However, it is nearly impossible to stop exactly on the frame where the slate hits using the JKL keys. So I would like to get in the general vicinity using JKL, and then use some other keys or method to get to the exact frame of the "clap". One would assume that the arrow keys would do this, but they don't.
Does anyone know if there is a way to accomplish this? Thanks in advance for any help.

I understand your point, and it never ocurred to me that I part of my normal workflow when doing things like that to more than a few clips is to select all of the clips and put them all in the Source Monitor with a single command. (Select them all, right click, and select "Open in Source Monitor".) So I don't go back and forth between windows. I guess I have been doing it so long I missed that step in the explanation. Sorry about that. Also, please understand that I skipped CS4 and CS5 so when I started using CS6 I have never really been comfortable with the hover scrub for anything serious. Not yet anyway.
I figure that all of the clips will end up in the Source Monitor anyway before they hit the timeline, so why not put them up there and as I finish with each one I close that window and start on the next one.
Those of us who go back to when Premiere became Premiere Pro have been waiting for some of these features a very long time. Slap-your-head it might be to you or me, but Adobe only has so much money to pay engineers and there is always something more important to work on. Like becoming codec agnostic or handling huge frame sizes. Adobe has borrowed many features from FCP, but it is still a work in progress. We just submit feature requests and attempt to convince others to do the same. You can't imagine how much time we spent a decade ago getting people to create the proper sequence. Now you just drag a clip to the New Item button and your sequence is perfect. That is magic to someone like me, who taught people how to use Premiere Pro 1.5 by copying FCP tutorials and recreating them in Premiere Pro (for Lynda.com) using the same footage.
Jim Simon is often quite vocal about things he would rather see done that some of the requests. I agree with him most of the time, but every now and then a little thing I think should be done is not on his list and he will let me know in no uncertain terms why he thinks what he thinks. He can be pretty persuasive and it is difficult to argue with his logic. The Adobe folks read these forums, yes, but they read the feature requests and look to see how many customers want certain things done. Not a bad way to prioritize. Now that more FCP people will be submitting requests, there is a good chance that you will see more features that you want.
So, while it may be obvious to you, it isn't obvious to Adobe until the masses speak. I suggest that you might want to consider being a rabble rouser, getting like minded people to put in the same requests. That is probably the best way to get what you want.
As for going in reverse.... I think that if you have never had some of these things, they are not important to you. They are not all like adding reverse. Some are but some of these are like the tailfin on the 1959 Caddilac. The higher the better back then. But are they necessary?

Is Adobe Premiere Crashing on you??? - Solution to almost every cause...

I've been trying to fix this problem of mine, and I've found that countless people have had the same problem with previous versions of premiere and still do with even the more recent versions. I'm going to be posting this on multiple forums to help out. Well, I might be being a little cocky saying that I have a solution to every case of Adobe Premiere not working, but I will give as many solutions as I know starting with my problem, which I've had happen multiple times, and then go through the possible solutions to other countless people's errors that I've seen while trying to fix my problem.
It might almost seem like it's not worth it to go through all of my steps and instead just format your hard drive, but some people have too much stuff to have to copy off the drive to do that so that is why I'm posting this. For example, I myself have over a Terabyte of music on my computer =/.
PREMIERE PROBLEM CRASHES
When I would click on Premiere, no matter what version ( I only tried Adobe Premiere 6.5, Pro 7, and CS3 but I'm sure it would've been the same for all ) it would pop up as it usually does and then it would crash ( for search provider purposes I'm going to put every word I can think of ) lock up, freeze, shut down, close out, not work, wouldn't start, doesn't open, won't run, can't load, etc. Premiere 6.5 for example would say "Initializing" and then give a send or don't send error message. Similar thing for CS3 except it didn't say "Initializing" it said something else, but it would only say the first thing it would try to do and then the same error messages every time. This seemed to be an unfixable problem I've had multiple times with adobe premiere and I've tried the following possible fixes but none worked: System restores, uninstall and reinstall, uninstall all audio and video codecs I can find, Delete every adobe premiere file that exists on my computer including documents and settings / my documents / windows / program files / temp files / prefrence files / application data / etc., also going into my regestry editor and going to HKCU... as well as HKLM / Software / Microsoft / Windows / CurrentVersion / RUN and RUN Once and deleted any proccesses I knew I didn't need on startup, I've also tried unchecking Load Startup Items under the Selective Startup section using "msconfig" in the run command and then restarting without those background programs running and then tried Premiere, and I've even tried to do a repair install of Windows XP, but not a single one of those things in any combination would do the trick!!!
POSSIBLE CAUSES
The problem actually started after doing a system restore, maybe undoing something I wasn't aware of even though the system restore itself was only created a few days back so I'm not sure how that could be, none-the-less the problem started just after. It might have also had something to do with a new program I had installed to clean my registry. I don't believe that was the problem because after cleaning my registry and before the system restore the program worked just fine, but maybe the combination of the two things caused the problem this time. A few other problems I've heard of as possible causes / solutions are...
· Conflicts with Audio Codecs such as - Lame Mp3 / Ra-Audio codec12 / RC3 / etc.
· Conflicts with Video Codecs such as - Ligos, ffdshow, Darim Vision, Moonlight WinDivX, WMP DVD Playback, Core Video, Matrox, Fraps, etc. etc.
· Malware, Viruses, Spyware, bogus Registry Cleaners like RegCure, Pirated Software ( big no no), and other vulnerabilities.
· Prefrence files that needed to be deleted like: Prem60.prf, Premiere 6.5 Prefs - in C:\Documents and Settings\YourUserNameHere\Application Data\Adobe\Premiere, and a few other pref files I can't really remember.
· QUICK TIME, you should uninstall quicktime (which might have been my problem) and delete all files associated with it including Apple Software.
· Start Up proccess conflicts. Use Msconfig in the run command line to bring up msconfig, then under General / Selective Startup, uncheck Load Startup Items and restart your computer. If after restart Premiere doesn't work read on...
· Ace Mega Codecs Pack: This one can cause a lot of conflicts... Here's a screenshot of what your Ace MCP settings should be on through a Custom install, or you can use your control panel to modify an already existing install... http://frankreu.ipower.com//AceSettings.jpg
MY SOLUTION ( to possilby every case of Premiere crashing )
This is a very good solution to have so that you don't have to try all the other things first, I guarantee this is the best solution and it will take a little courage on your part but does the trick without having to format your Hard Drive. The first thing I did was uninstall all versions of Premiere, then Ace Mega Codecs pack v5.93.8971, I also uninstalled all extra audio codecs I could find, and uninstalled any extra software I didn't need on my computer while I was at it which might be causing the conflict such as Fraps, Growler Guncam, and any other little programs I didn't need and could reinstall. Even going as far as looking through the Program Files for things I didn't recognize, and if I were anyone else I would google it to make sure it is not a necessary file, and then delete all the folders to programs I had already uninstalled that were left over or other folders to things that I didn't need. If you're going to do this make sure you go into your My Computer folder, then at the top select the Tools tab and click on Folder Options, then on the view tab make sure that Show Hidden Files and Folders is selected and click apply. Then I went into C:\Documents and Settings\ (Every different account there was) and looked through the Application Data folders and the Local Settings folders for left over Adobe Premiere files and folders and deleted them all. I also cleaned out every temp folder I could find by selecting the files and pressing shift + delete to skip the recycling bin proccess. If you come across any files that say "cannot delete" due to file permissions just look on google for the program called Unlocker 1.8.7 and download it for free, here's the current link http://ccollomb.free.fr/unlocker/unlocker1.8.7.exe. After installing it, should only take seconds, you can right click on any file or group of files and click unlocker, then select the delete option and press the Unlock All button. If the process winlogon.exe or svchost is in the list of processes you are going to unlock do not do it, this will freeze up your computer. After deleting all those left over files you should use your Search command in your start menu to look for anything with the name Premiere in it, make sure you select Advanced Options and then put checkmarks next to Search System Folders, Search Hidden Files and Folders, and Search Subfolders. Delete all those files, but make sure they are related to Adobe Premiere and not something else. Then, and this may not be a necessary step so don't panic, I ran Uniblue Registry Booster to clean out my registry files of all unecessary entries and also did a registry defrag. Uniblue is software you have to pay for though so you might want to fish around on the internet for a good free registry cleaner, do not use RegCure though that one's a scam.
Then, and this is where you have to be kinda brave, I went into the registry editor by pressing the start button on my tastbar and opening the run command I then typed regedit.exe, or just regedit, to open the system registry editor. First you should make a backup of your registry before going any further by clicking the File / Export button, and saving the registry to your My Documents folder or somewhere else you will be able to find it. I would then use the Find command with all options checked to look for Adobe and then Premier seperately to make sure I found every place that had Premiere entries in it and then deleted those entries. Make sure you start from the top by having My Computer selected. Some would only say Prem~.exe and things similar to that, so that is why you have to look for Adobe as well to find all the entries. Once you click find, you can press F3 to do a find next and continue the seach after each value you delete. If a folder contained only a value with an Adobe Premiere property in it I deleted the whole folder. I then searched for the following words and began the same proccess with them: Ligos, Matrox, Fraps, Quicktime, and during the search if I saw any values I wasn't sure of because they didn't seem to be what I was referring to I left them alone. I also deleted any entries that I knew I nolonger needed in there such as Apple Software, and refrences to game demos or other programs I knew I had already uninstalled. Be carefull with that though, you should be absolutly sure before deleting anything from the registry. You have a back up so don't get too scared if you damage it, just double click your backup of the registry, then reboot and start over. Worst case is that you might have to do a windows repair install if you mess up.
Anyway, after you're done in the registry create a system restore point and then restart your computer. Once it loads up again try reinstalling Adobe Premiere and make sure you cross those figers, that's the most important part. Viola, that's my solution. If it doesn't work for you, well, most likely you have some serious malware or a trojan that just doesn't like Premiere. I myself use Panda Titanium 2009 as well as Uniblue PowerSuite to keep my system clean. If you can't afford that try Lavasoft Adaware freeware + Microsoft Malicious Software Removal Tool and see if they don't catch anything. Good luck, and I really hope that I help at least one person with all of this lol.

Jeff:
I have had both good and bad experiences with Acronis True Image. I got the recent copy of ATI via a Newegg.com bundle. I haven't tried it yet on any Windows 7 editing systems. ATI installs some services that I would rather not have running in the background.
What made you change from ATI to ShadowProtect Desktop Edition?
Are you running Windows 7?
What do you see as advantages to running ShadowProtect Desktop Edition as opposed to Acronis True Image?
Thanks

Icon View Issue

I am trying out the new Premiere Pro CS5.5 and I found an odd issue. I like working in the Icon View when orginizing my media files. In CS4 you could at will orginize your media anyway you wanted, i.e. row by row and move the rows up or down you could leave a gap in a row and put items after that and such. In CS5.5, all you can do is put them end to end, you can't have spaces and they wrap around to the next row like a word doc. To me this seems very inefficient. Maybe this is a bug but the way it is, it is not very useful anymore!

Peter-
Other weird developments. While this is icon view is more of a nuissance than a problem it has shown some bugs in my system. Turns out I can access Icon view if I use Motion's window layout scheme but if I switch to mine the library window will freeze. I have thrown out my widow layouts and started fresh but it will not work. I was wondering if there are any other files I should trash other than the .plist file?
thanks
Bill

Premiere crashing if using other applications

I'm having problems with Adobe Premiere crashing on me.
It seems to happen whenever I use another application (like Chrome or Windows Explorer) while Premiere is open, then go back to Premiere. It pretty much instantly crashes as soon as I click inside the Premiere window.
This is the error message I get in Event Viewer:
Faulting application name: Adobe Premiere Pro.exe, version: 7.2.1.4, time stamp: 0x52aed7f3
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
Exception code: 0xc0000005
Fault offset: 0x0000000000018e5d
Faulting process id: 0x530
Faulting application start time: 0x01cf3baa978a06e0
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e214e2e5-a79d-11e3-a90b-bc5ff4488183
My system:
Intel i7 3770 @ 3.5 GHz
8GB RAM
Nvidia Geforce GTX 670 (Driver: 334.89)
Windows 7 Pro 64bit
*edit*
I've done a little more testing and found out that it doesn't have anything to do with using other applications. It happens if I minimize Premiere as well.
Another thing which might help pinpoint the problem: if I open a new empty project, it's fine, but if I add a new sequence and minimize Premiere it crashes instantly.
Message was edited by: machinemade
*edit 2*
I seem to have figured it out. I did a reset of the prefrences (by holding ALT while starting Premiere) and it hasn't crashed since.
I also installed the newest Quicktime. Not sure which of these changes fixed my problem, but it seems to have done it.
Message was edited by: machinemade

hi rutra!
hmmmmm. let's just check through the possibilities here:
How to troubleshoot "Cannot lock iPod" error message
let's try making sure that "terminate and stay resident" programs like antivirus packages are also shut down prior to trying the update. this InstallShield article might be of some help with that:
Close Applications Running in the Background
love, b

Premiere Crashes when sending Audio File to Audition

On OSX Lion, 12-core Mac Pro...
Premiere crashes whenever I attempt to EDIT a file to Audition from timeline. Happenes everytime. Fully updated on all programs...

Best to post specific product questions in that product's forum
http://forums.adobe.com/community/premiere/premierepro_current?view=discussions

Every time that I try to print a page from the internet, my Mac crashes and I get a "Crash Reporter" icon. Any suggestions?

Every time that I try to print a page from the internet, My Mac (Maverick 10.9.4) crashes and I see a "Crash Reporter" icon. Any suggestions?

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if iTunes crashed, you would enter "iTunes" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Premiere crashes on me whenever I try to import video! HELP!

Okay, I've never had problems with Adobe Premiere Pro when using it at school, and decided to install the trial version for a summer project.
After 4 hours of installation, I was ready to start editing, when I realized that there's a fatal flaw:
Premiere crashes on me whenever I attempt to import a video!
Basically, as soon as I click File>import, I get the import menu opened, then everything crashes.
Please help me, this is for my required summer project for college.
Sincerely,
Mike

More information needed for someone to help http://forums.adobe.com/thread/416679
Some is general about your computer and OS, some is specific to video editing
Build a Configuration file http://www.piriform.com/speccy
Brand/Model Computer (or Brand/Model Motherboard if self-built)
How much system memory you have installed, such as 2Gig or ???
Operating System version, such as Win7 64bit Pro... or whatevevr
-including your security settings, such as are YOU the Administrator
-and have you tried to RIGHT click the program Icon and then select
-the Run as Administrator option (for Windows, not sure about Mac)
Your Firewall settings and brand of anti-virus are you running
Brand/Model graphics card, sush as ATI "xxxx" or nVidia "xxxx"
-or the brand/model graphics chip if on the motherboard
-and the exact driver version for the above graphics card/chip
-and how much video memory you have on your graphics card
Brand/Model sound card, or sound "chip" name on Motherboard
-and the exact driver version for the above sound card/chip
Size(s) and configuration of your hard drive(s)... example below
-and how much FREE space is available on each drive (in Windows
-you RIGHT click the drive letter while using Windows Explorer
-and then select the Properties option to see used/free space)
Windows Indexing is BAD http://forums.adobe.com/thread/676303
While in Properties, be sure you have drive indexing set OFF
-for the drive, and for all directories, to improve performance
Some/Much of the above are available by going to the Windows
Control Panel and then the Hardware option (Win7 option name)
OR Control Panel--System--Hardware Tab--Device Manager for WinXP
And the EXACT type and size of file that is causing you problems
-for pictures, that includes the camera used and the pixel dimensions
Plus Video-Specific Information http://forums.adobe.com/thread/459220?tstart=0
Read Bill Hunt on a file type as WRAPPER http://forums.adobe.com/thread/440037?tstart=0
What is a CODEC... a Primer http://forums.adobe.com/thread/546811?tstart=0
What CODEC is INSIDE that file? http://forums.adobe.com/thread/440037?tstart=0
Report back with the codec details of your file, use the programs below
For PC http://www.headbands.com/gspot/ or http://mediainfo.sourceforge.net/en
For Mac http://mediainfo.massanti.com/
Once you know exactly what it is you are editing, report back with that information...
and your project setting, and if there is a red line above the video in the timeline,
which indicates a mismatch between video and project
Read Bill Hunt on editing a VOB/MPG file http://forums.adobe.com/thread/464549?tstart=0
Edit Vob http://premierepro.wikia.com/wiki/FAQ:How_do_I_import_VOB_files_/_edit_a_DVD
Read Hunt on Using MOD/TOD files http://forums.adobe.com/thread/699990?tstart=0
Work through all of the steps (ideas) listed at http://forums.adobe.com/thread/459220?
If your problem isn't fixed after you follow all of the steps, report back with ALL OF
THE DETAILS asked for in the FINALLY section at the troubleshooting link
Also read file troubleshooting http://kb2.adobe.com/cps/407/kb407928.html

Just installed Quadro 4000 Mac, now Premiere crashes when I try to open existing project

Mac Pro 4,1
Premiere Pro 5.5
OS X 10.6.8
I just replaced the stock ATI card with a PNY Quadro 4000 for Mac.
Via CUDA Preferences, have updated CUDA driver to 4.0.50
GPU driver is 1.6.37.0 (256.02.25f01)
When I try to open any existing Premiere project, Premiere crashes.
This happens whether I'm running the OS X 32-bit kernel or the 64-bit kernel.
If I launch Premiere and create a new project, Premiere seems to run OK. (I haven't yet tried adding any content or working with the content.)
As you can imagine, the only reason I shelled out for the CUDA-capable card was to take advantage of the hardware acceleration in Mercury. So ... not a very satisfying "upgrade" so far.
Any clues?

There are four sequences in all. Two are super-simple, with only one clip in each. A third has only a single clip plus four titles. The main sequence has multiple clips, two stills and three titles plus one extra audio track.
When the crash occurs, there's no error dialog box. What I see is this:
After I double-click the project file -- or open Premiere and choose the project from the splash screen -- the "loading" progress bar appears and seems to complete loading.
Premiere starts to draw the window for its workspace. It creates a solid white rectangle, the wristwatch "wait" icon appears briefly, then Premiere crashes.
The log captured by the Apple and Adobe crash reporters shows (among much else):
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
The last few lines captured for Thread 0 are:
77 com.adobe.premiere.frontend
0x000000010c7b4aa4 FE::MacApplication::RunSelf(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 164
78 com.adobe.premiere.frontend
0x000000010c7621a7 FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 2503
79 com.adobe.premiere.frontend
0x000000010c7b7c1d AppMain + 253
80 com.adobe.premiere.startup
0x000000010c9343e8 (anonymous namespace)::LaunchFrontendFramework(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 232
81 com.adobe.AdobePremierePro
0x0000000100003540 (anonymous namespace)::CallStartupFramework(int, char const* const*) + 288
82 com.adobe.AdobePremierePro
0x0000000100003ac7 main + 167
83 com.adobe.AdobePremierePro
0x00000001000033a8 start + 52

Opening a bin of clips to Icon View defaults sorting to "User Order"

It seems like almost any time I open a bin of clips directly into Icon view, Premiere always defaults to sorting them in a random "User Order," instead of by clip name (which would be preferred).
Any setting I am overlooking that would cause this? Premiere 7.1 on Mountain Lion 10.8.4
Cheers

That makse sense, I suppose, but I don't think I've ever consciously imported media from the media browser NOT in sequential order (in terms of hitting CMD-A, selecting all, and Importing)

Mercury playback engine makes Premiere crash after cs6 update

Hi there everyone,
I have been working with Premiere cs5 for over a year without any serious errors. Since I upgraded the entire Creative Suite to cs6 however, I am forced to use the software playback method instead of the GPU accelerated one. Using the last mentioned causes Premiere to crash immediately when trying to drag any sort of video on the timeline. This happens in new projects as well as in cs5 ones; and all of the footage involved in both cases was ingested in the wellknown Matrox i-frame codec that always worked fine before. Specs:
Windows 7, 24 gB RAM (not sure whether DDR3 or 5), NVidia Quadro 4000, dual six-core CPU, several terras of HD @ 7200 rpm, Matrox MX02 LE, CS6.
I tried every possible combination and order of uninstalling an reinstalling Premiere, the Matrox drivers and the nVidia drivers, including older versions of the last two mentioned, but to no avail. Though it looks like an NVidia issue (I read somewhere about CS5 and 5.5 certified NVidia drivers but not CS6 yet) this problem manifested right after the upgrade to CS6.
The error reported is about the graphics card being reset, it stops and then recovers, leaving Premiere to hang. The card's hardware reacts with a noisy cooling fan acceleration sound that slowly falls back to its normal rpm.
-Sigh- I am sorry to bother you with this, but does anyone have any idea or experienced something similar? Does the combination of the mentioned elements ring a bell...?
Any help is utterly appreciated !

Hi Harm,
I couldn't find anything in the logs about temperature, but I did find some other logs. However: when I re-install a newer NVidia driver version, the PC will not crash, only Premiere crashes in that case, which lets me believe this is not just a hardware defect. The hardware however does play a role.
What I found in the event viewer are messages like:
A request to disable the Desktop Window Manager was made by process (4)
The Desktop Window Manager was unable to start because composition was disabled by a running application
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available ETC ETC.
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0 Problem signature:
P1: Adobe Premiere Pro.exe
P2: 6.0.1.0
P3: 4fac933f
P4: e05a
P5: 1 ETC ETC
The program Adobe Premiere Pro.exe version 6.0.1.0 stopped interacting with Windows and was closed.
The NVIDIA OpenGL driver lost connection with the display
driver due to exceeding the Windows Time-Out limit and is unable to continue.
The application must close. Error code: 7
Visit http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=3007 for more information.
Most of all I saw this:
Activation context generation failed for "C:\Windows\system32\vsnpstd3.dll".Error in manifest or policy file "C:\Windows\system32\vsnpstd3.dll" on line 2. The value "X64" of attribute "processorArchitecture" in element "assemblyIdentity" is invalid.
This report pops up hundreds of times... but I don't think the vsnpstd3.dll file, dating back to 2009, could be a problem all of a sudden.
It looks more like a Windows Time-out thing causing to reset the graphics card because the load of graphic data is too big to handle. The only strange thing is that the time-out action is taken by Windows before the usual two seconds have passed, it takes just a fraction of second. This leads me to believe that, during the demand from the Mercury Playback Engine to the NVidia card, "false information" is passed to Windows... i.e. a software problem.
I am thinking about rolling back to Premiere CS5 to see what happens... if this version would be working flawless again, that would be pretty steady proof for doubting the MPE of CS6.
To be continued...

Premiere crashes on icon view

Similar Messages

Maybe you are looking for