Re: Premiere Elements 10 Error on load -

Nick Strapp Calculating status...

Currently Being Moderated

Premiere Elements 10 Error on load - "we have detected an incompatible display driver"

Dec 16, 2011 5:25 AM

Tags: #adobe #premiere #elements #display #10 #intel #incompatible #driver #bear #lake

Greetings! I was happily using this software for several weeks without problems when one day for no apparent reason (no new hardware or significant software changes) I now get this error constantly when trying to run the software - "we have detected an incompatible display driver. to get better and faster playback performance, please update your display driver. display driver details : intel - intel bear lake B 1.4.0 - Build 7.15.10.5218"

I then updated the intel graphics drivers to the latest version but to no avail. I have tried four different driver versions from oldest to newest and still no success. I have un-installed the software, drivers, started from fresh with all imaginable combinations, CCleaner-ed the hard drive, virus scanned, defragmented, updated windows, etc. I am now at a loss for what to do next, beyond insisting for a refund and going to another software company for my video editing needs.

My machine is a 2Ghz Dual-Core, 4GB RAM, 80GB available HDD space, running windows XP pro SP3, updated everything drivers and OS.

I find this problem even more confusing given the fact that is was working, then decided not to work any more. Perhaps something updated in the background without my knowledge?

Any help would be greatly appreciated.

PS - I have tried all the things on this list relating to Premiere Elements version 9, but none have helped - http://kb2.adobe.com/cps/875/cpsid_87588.html

3014 Views 26 Replies Latest reply: JMJarrige, Jun 10, 2012 12:39 AM

Replies

Currently Being Moderated

1. Bill Hunt,

Dec 16, 2011 7:22 AM in reply to Nick Strapp

Report

PrE (and PrPro) interfaces very closely with the display driver. Those are very fragile things, and even a simple OS update, or hot-fix, can render them obsolete. That is why companies, like ATI/AMD and nVidia release them on a monthly basis.

Now, Intel makes good chips, but they are not good at releasing drivers. Because of this issue, I would never go with anything but ATI/AMD, or nVidia - their driver support is very good.

One test that you could run, would be to create a manual System Restore Point for now, and then boot to Safe Mode, choosing to use an older System Restore Point, from back before the error message. From that older System Restore Point (probably before an OS update), I would test the system. It only takes a moment, and if there is no improvement, you still have today's System Restore Point.

If your computer is a desktop, you might want to investigate getting an ATI/AMD, or nVidia, video card, and by-passing the on-board Intel graphics chip. You should be able to either disable that display chip in the BIOS, or perhaps with a jumper/switch on the MoBo.

Good luck,

Hunt

|
Mark as:
Currently Being Moderated

2. movieMogul72,

Dec 19, 2011 9:23 AM in reply to Nick Strapp

Report

I have the same problem. PRE9 working fine, then one day says" Incompatible displary adaptor:" I too tried older display drivers for my NVDIA 7300LE.
I could use the oldest one, but then my display wasnt what I wanted. The newest driver from NVIDIA is also incompatible. One way around this is to disable the display adaptor in the control panel when using PRE. Still its a royal pain.
Runing Vista Home Premium Core 2 duo and NVIDIA 7300LE with driver date 10/15/2011.

|
Mark as:
Currently Being Moderated

3. Steve Grisetti,

Dec 19, 2011 9:24 AM in reply to movieMogul72

Report

Have you done this?
http://forums.adobe.com/thread/769303

|
Mark as:
Currently Being Moderated

4. movieMogul72,

Dec 19, 2011 10:09 AM in reply to Steve Grisetti

Report

Thanks for responding back so quickly Steve. I have updated to PRE 9.0.1, with latest NVIDIA driver. When I go to Users/Program Data/Adobe/AdobePRE, i see no baddriver.txt file and View all files is enabled in the Contr. Panel. Searching on my entire hard drive for baddriver.txt, or even just bad shows up anything. Not sure where this file to be deleted is.

|
Mark as:
Currently Being Moderated

5. Steve Grisetti,

Dec 19, 2011 4:09 PM in reply to movieMogul72

Report

You added to a thread on version 10, moviemogul, but you say you're using version 9? I'm confused.

|
Mark as:
Currently Being Moderated

6. VDOSurfer,

Dec 19, 2011 10:02 PM in reply to movieMogul72

Report

The file should be in "%programdata%\Adobe\Premiere Elements\". Delete that and see if it works for you..

|
Mark as:
Currently Being Moderated

7. JMJarrige,

Dec 20, 2011 1:56 AM in reply to movieMogul72

Report

I had the same problem with Premiere elements 9 last february, 3 weeks after fresh install.
The solution (thaks to the forum) was to delete the baddriver file in the folder
Programdata/Adobe/Premiere elements/9.0 on a Vista laptop.
The problem appeared again 2 or 3 times this year, even having marked this
file as 'read only'...The delete solution works fine in my case.
No same problem on my main computer iMac, so I think Bill's advice on software updates
is important. Nevertheless, as we can't (in windows area) stop these regular updates which are
fortunately most of the times without consequences, it seems usefull to keep your
solution available, when you will have one, as we say in french : 'au cas ou'.

As it seems version 10 is also impacted, I suppose this issue is not simple to solve for Adobe
developpers.

|
Mark as:
Currently Being Moderated

8. Nick Strapp,

Dec 20, 2011 2:13 AM in reply to Bill Hunt

Report

Thank you Bill for taking the time to respond. Your comments are appreciated

Regarding your system restore suggestion - I created a current restore point easily enough, but each time I chose to restore the computer to a previous checkpoint, after rebooting the PC, windows simply reported that system restore was "unable to restore the computer to a previous checkpoint" with no explaination or advice. Another triumph for microsoft. I tried a dozen or so previous checkpoints ranging in dates from ten days ago to two months ago. My system restore capability is simply broken. And I didn't want to go off on another tangent trying to fix this (Russian Doll windows problems).

Failing to solve the problem and becoming increasingly frustrated, I have ordered a budget ATI graphics card - Sapphire ATI Radeon HD 5450 650Mhz 1GB DDR3 PCI-Express DVI (Low Profile) - which should arrive today. I really hope this solves the problem and Elements 10 can happily use this card. I will ignore the drivers on the CD and download the latest from ATI website.

Do you recommend un-installing Elements 10 prior to installing the new card then re-installing? Or isn't this necessary?

Nick

|
Mark as:
Currently Being Moderated

9. Nick Strapp,

Dec 20, 2011 4:27 AM in reply to Steve Grisetti

Report

" Have you done this?
http://forums.adobe.com/thread/769303"

As far as I can tell this doesn't apply in version 10. No such baddrivers.txt file exists in this location.

|
Mark as:
Currently Being Moderated

10. VDOSurfer,

Dec 20, 2011 4:36 AM in reply to Nick Strapp

Report

The link for the file given in the post looks like that of an XP machine. For Windows 7, there is a folder named "ProgramData" in the OS root. Look for BadDrivers.txt inside that...

|
Mark as:
Currently Being Moderated

11. Bill Hunt,

Dec 20, 2011 6:15 AM in reply to Nick Strapp

Report

Nick,

Though some users say that it is not necessary, when doing a System Restore, I always boot to Safe Mode (on my XP-Pro SP3 OS's), and from there, just use the prompt to Restore to a System Restore Point. I have never had any issues doing it that way. The biggest problem is that it's sometimes tough to get my F8 key pressed at the right time (happens quickly on my computers) to get to Safe Mode. If I have not had enough coffee, it might take 2 - 3 tries to get it right. Otherwise, has been 100% for me.

Good luck,

Hunt

|
Mark as:
Currently Being Moderated

12. Nick Strapp,

Dec 20, 2011 6:42 AM in reply to VDOSurfer

Report

I have windows XP. No such file exists for version 10 as it does for 9.01

|
Mark as:
Currently Being Moderated

13. Nick Strapp,

Dec 20, 2011 6:43 AM in reply to Bill Hunt

Report

Yes I have been doing it from safe mode every time. Same result as in normal mode.

|
Mark as:
Currently Being Moderated

14. Bill Hunt,

Dec 20, 2011 6:47 AM in reply to Nick Strapp

Report

Hm-m, if you cannot do a System Restore from Safe Mode, there is something very wrong with your system.

Some malware can block System Restores, and I would investigate that very closely, just in case.

Good luck,

Hunt

|
Mark as:
Currently Being Moderated

15. Nick Strapp,

Dec 20, 2011 7:08 AM in reply to Bill Hunt

Report

Its not as if system restore gives me any useful error or anything. It takes a while to process, then restarts the system, then box appears after logon saying it was unable to restore anything. I have run many different anti-virus/malware scans (symantec, malware bytes, hitmanpro, dr.web, MRT, avast, ESET) to be certain nothing nasty is residing.

Anyway, my new card arrives soon so hopefully this will all be mute. God help me if the same error appears with a new card.

|
Mark as:
Currently Being Moderated

16. nealeh,

Dec 20, 2011 3:22 PM in reply to Bill Hunt

Report

Bill, you can increase the delay time on the boot screen to give you longer to hit the key. I have mine (W7-64) set to ten seconds.

Cheers,
--
Neale
Insanity is hereditary, you get it from your children

|
Mark as:
Currently Being Moderated

17. Nick Strapp,

Dec 24, 2011 3:41 AM in reply to Nick Strapp

Report

So after all of my attempts to resolve the fundamental issue of Elements 10 not working with my intel graphics (once was working then stopped working), and after receiveing useless support from the official adobe support team after raising a ticket (you guys on these forums have been amazingly helpful however, thankyou, especially Bill), my new ATI graphics card arrived and worked straight away.

To summarise, the core issue still exists and I imagine is causing problems for other users of intel graphics, and the only way I could find to resolve was to upgrade my graphics card. I suspect that something on the PC updated without my knowledge and caused the problem. Since I was unable to rollback via system restore, I cannot offer any further insight as to what this might have been.

If any others out there have a similar problem, good luck and hopefully you can shed some light on what was at the root of this issue. Otherwise, buy a new graphics card!

Thanks, and happy Christmas!

Nick

|
Mark as:
Currently Being Moderated

18. Bill Hunt,

Dec 24, 2011 7:18 AM in reply to Nick Strapp

Report

Nick,

Great news, and thank you for the kind words. The people here really do try hard to help everyone.

What most likely happened with your Intel graphics chip, was that some OS update rendered it obsolete. That happens all too often. As Premiere (both Elements and Pro) interface with the driver more than most programs, they crump. That rendering obsolete is one reason that nVidia and ATI/AMD issue new drivers about monthly, or even more often, in times of heavy OS updates.

As mentioned above, Intel makes great chips, but driver support is nearly non-existant. For general computing, most users never really notice, but if one is an active gamer, 3D artist, or video editor, they are in for a very rude surprise, right around the corner.

Recently, there was a thread on the PS Forum, asking about the Intel Sandybridge chipset, which features graphics, and the jury is still out on how well it will work, over the long haul, with programs like Premiere, Photoshop (getting more GPU intensive with each version) and After Effects.

Good luck, and Merry Christmas,

Hunt

|
Mark as:
Currently Being Moderated

19. Steve Grisetti,

Dec 24, 2011 9:23 AM in reply to Nick Strapp

Report

Of course it does, Nick!

You just need to enable your system to Show Hidden Files.

|
Mark as:
Currently Being Moderated

20. carfamoudia,

Feb 9, 2012 3:13 AM in reply to Nick Strapp

Report

Thank you very Nick for this magical solution....on Pre 10 bad Display Solution.... i had the Program for les than 10 days...when i first see it..
NOTE NICK..YOU SAID:{AS far as i can tell this does not apply in premiere 10 no such baddriver.txt exist in this location..}
MY REPONSE IS IT DOES EXIST UNDER: {Start .> control panel > apparence and personalization > folder option > Click on show hiddens files and folders....then scoll down and chech to show hidden files and folder...save and exits}

Finaly { start ...My computer...double click on C driver and look for Programdata...double Click ADOBE...Double Premiere elements...now double click Premiere element program number you would like to fix.....In MY case i Clicked 10.0 there you will see "badDrivers" select and delete it...it will not harm you Computer...Deleted is the best way to go instead of Renaming....

All Appreciation and Credit Goes to Nick...

|
Mark as:
Currently Being Moderated

21. movieMogul72,

Feb 10, 2012 5:13 AM in reply to carfamoudia

Report

I have PRE 9, spent full retail for it. Windows Vista, Nvidia LE7300 graphics card. PRE 9 keeps saying Incompatible display adaptor drivers. I have tried the newest and 5 earlier versions...same problem. Video will not load into PRE. The weird thing is for the first month I had PRE9 around Dec 2011, it worked fine. Reinstalling also does not fix the problem. One post said try to delete the "bad drivers" file. It does not exist. It is a hidden file, and even though my file setting are already set to "show hidden files", it does not exit...so that fix is out. Its not supposed to this hard fellas.

The 2nd problem, and it is not as important as the above problem, is that PRE always tries to go online, keeps downloading some big files even though it is already fully patched up. I installed a software firewall to block it, but PRE tries every single port to get online.

On to Sony Vegas or some other software

|
Mark as:
Currently Being Moderated

22. VDOSurfer,

Feb 11, 2012 7:54 AM in reply to movieMogul72

Report

If none of the troubleshooting for the display adaptor (graphics card driver update, BadDrivres.txt etc.) do not work, we have to understand that the display could actually not be supported. By display, I mean the card-driver-driver version combination. So,
1. It could be a bad card - None of the available drivers work for the application. Here, ditch the card and get a newer one that works.
2. It could be a bad driver - For e.g. Only DirectX drivers work, OpenGL ones could be pathetic (Many games detect this and if this is bad, I have seen Photoshop struggle with this). Or some display configurations would be badly supported (multiple monitors, some funny resolutions, some of the ports, crossfire etc.). Older drivers/cards/some OEM drivers etc. have these issues in my experience.
3. It could be a bad driver version - Here upgrade or a downgrade works.

Because of a Video editor, the (lack of) capabilities of the card is highlighted. Video Playback alone doesn't nearly exercise the capabilities the cards usually have to offer. Editing really does. That is why it matters if the Video Editor actually says that it supports Graphics acceleration (Or GPU acceleration) for any of the workflows.

What I am saying here is that when we blame the application for any of the issues, we have to be certain that the issues are NOT due to one of the mentioned three causes. I have seen this all too often in the gaming forums, Nero forums (some years back), in PPro forum, and here. If the application menufacturer is really to blame, the mistake would be all too obvious and too many of us would have complained about it. I do not think this is the case with Premiere Elements 10.

Introspection works.

|
Mark as:
Currently Being Moderated

23. Bill Hunt,

Feb 11, 2012 8:26 AM in reply to VDOSurfer

Report

VDOSurfer,

So very true. Often what users observe, is that a certain program, such as PrElements, or even recent version of Photoshop, that seem to be the only ones that do not work - so they deduce that it IS the program. What is actually happening is that that/those program(s) are just interfacing more with the display sub-system, and especially the video driver, more than the other programs on the computer.

Most programs hardly touch the video driver, and if it can control the card/chip and get something displayed on the monitor, there appears to be no problem. Then, with a program like PrE, things go really bad. Well, other than 3D creation apps, CAD programs, and extreme gaming, nothing else will tax a system, as much as will Video editing. The user does not see problems with browsers, spreadsheet apps., browsers and e-mail apps., but ONLY with more intense programs.

Thanks for helping out here,

Hunt

|
Mark as:
Currently Being Moderated

24. Evanf1237,

Jun 9, 2012 4:20 PM in reply to Bill Hunt

Report

This is happening to me as well. i have premiere elements 10. and my display driver has been working fine until 5 days ago for no reason at all. its says incompatible display driver, so ichecked, but there are no new updates. mines up to date. i have found the file called bad driver, like you guys were talking about earlier. Should i delete it? would that help?

|
Mark as:
Currently Being Moderated

25. Bill Hunt,

Jun 9, 2012 4:42 PM in reply to Evanf1237

Report

It is possible that Windows has updated, or installed hot-fixes. Those can render a video driver obsolete.

What is the make/model of your video card/chip?

What is the version/date of your installed driver?

When you checked whether your video driver was up to date, did you go to the mfgr's. Web site, plug in your video card's model, and your OS, and then compare their latest driver, with the one that was installed?

Just removing the BadDrivers file will not likely help, until you can install the latest video driver.

Good luck, and welcome to the forum.

Hunt

|
Mark as:
Currently Being Moderated

26. JMJarrige,

Jun 10, 2012 12:39 AM in reply to Evanf1237

Report

You can delete this file : bad drivers.txt, as indicated on previous discussions on this forum.
It happens sometimes on my PC Vista, I guess (as suggested by Steve Grisetti) it is due to
updates from Microsoft which seem to invalidate or alter some drivers.
Bon courage.

|
Mark as: