Go to the nVidia or ATI web sites and download the latest drivers for your graphics card.
Then look for the BadDriver.txt file in this directory and, if you find it, delete it, as detailed in this FAQ.
thank you, but I have checked for the latest nVidia drivers already before posting.
However I did check again just to make sure and I was using the latest driver.
I still removed the BadDriver.txt file and restartet Premiere Elements 10.
The Problem remains the same. After creating or opening a project the application just stops and windows shows the Program has stopped working error.
The BadDriver.txt file did get recreated again with his content:
Thanks for your help.
1 person found this helpful
On the Welcome Screen, select the option to open the Organizer (or open Photoshop Elements). Then go to the Help menu and select Check for Updates.
After all of the Elements updates are downloaded, delete BadDriver.txt again and restart Premiere Elements.
If that doesn't work, I'm not quite sure what's up. First, I'd go to Windows Update and ensure that I have not only the automatic updates but also the optional updates. These often including important updates that aren't installed automatically.
You may also want to go to Windows Disk Cleanup and dump your useless files.
Hi Steve, I checked for updates, but there were none. Deleted the badDriver.txt and tried it again. Still without success.
Windows Update are all installed, except 2 net framework 4.0 updates that seem to fail everytime. I doubt though that's the problem. It still comnplains about the display.dll
I do a regular disc clean with cc cleaner and check for other problems.
Maybe I try to change some settings on the graphic card hardware. Is there something with Premiere, that it doesn't like GPU acceleration or something like that?
Tried turning everything off in the nVidia settings for Adobe Premiere Elements, but still the program crashes...
Maybe I give Premiere a reinstall, but doubt it fixes my problems. Will report back.
1 person found this helpful
I would look over this FAQ Entry: http://forums.adobe.com/thread/792580?tstart=0
It starts as a checklist on setting up PrE to run best, then moved into a series of links on tuning up one's system and OS. It finishes with many links on troubleshooting, including some tools, that can be very useful.
that's quite a list to go through. Will do it over the next days and see how it goes.
The first half has been already checked.
Latest updates, latest drivers, latest quicktime and premiere, disk clean, defragmentation, enough free space (in fact I haven't even been able to set my extra free scratch disk yet, as I don't even get past the start screen. The app stops after I want to start a clean project with no clips added). Deleted the baddriver.txt file every time before trying again.
Will check through your hyperlinks...
When you checked your video drivers did you do it at the nVidia site? If you are relying on Windows Update it is very unlikely they will have the latest versions.
From the nvidia site the latest driver for your card is:
Version: 306.79 WHQL
Release Date: 2012.10.05
Insanity is hereditary, you get it from your children
yes it is the latest from nVidia. I always download my hardware drivers from the manufacturer website.
Meanwhile I tried uninstalling Elements and reinstalled it after cleaning the registry of all the Elements entries that were left, just to make sure I get a clean installation. Unfortunately the problem still exists.
I ran a DxDiag, maybe somebody here can see where the problem is.
In case it helps. Premiere Elements always runs to the point when it asks me for the name of the project and its settings. So I can see the main window in the background. Once I have selected the project parts of the UI are being build before it crashes.
how stupid of me. After going through everything and not finding the solution I double checked my Display settings.
Then in the Resolution settings (previously I thought there is nothing wrong, so I skipped it) I noticed that my screen was set to only 16bit depth...
Now I would have never thought that Premiere cares about that, but apparently it did. Setting it to 32bit solved my problems.
Premiere is running now fine.
Thanks fo everybody who looked into this and tried to help.
Great news, and thank you for reporting the setting that solved the issue.