Harm! I just uninstalled anything with Matrox in the name (not only all of the driver stuff but really everything) and the problem PERSISTS.

Yes, I too thought the problem could be Matrox but now I consider it proven not to be so.

So this is a Premiere CS6 - NVidia problem as far as I can see. Getting interesting, because I do see some more or less comparable discussions on the internet, but overall they are few and nobody seems to have exactly the same problem...

It almost looks as if the Mercury Playback Engine is asking too much from the nVidia card... by the way, this all happens both in SD and HD.

Hmm? Any ideas on where to go from here?

Hi Harm,

I rolled back two versions indeed, to get the CS5 certified version back again. As I noticed again, there is no officially certified version of the NVidia driver for CS6 yet.

The only difference is that now, when I switch on the Mercury Playback Engine, the entire computer is rebooted without notice. I simply switch in Premiere to the MPE GPU accelerated workflow, Premiere comes up with the usual "delete preview files" option and whether I press "keep" or "delete" the screen goes instantly black and the beeps of the resetting motherboard are heard within a second. Pulling the AC plug from the computer couldn't close the system down faster than the Adobe's MPE can :-)

I will repost this question in a different way; because I would like to find out if there is anyone out there who has Premiere CS6 working with the MPE on an NVidia Quadro 4000 switched to GPU acceleration flawlessly. Maybe it's some kind of NVidia setting I'm not aware of.

Thanks anyway for your time !

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...

Hai Ulf,

thanks for your reply. I already uninstalled and wiped Adobe out of my system but perhaps I left out a couple of tiny Adobe leftovers, so I am going to try again and see what pops up.

Thanks again!

Hi everyone,

IMPORTANT, VERY IMPORTANT news for this thread!!!! I re-installed the CS5 Creative Suite again WITH A NOT EVEN CERTIFIED NVIDIA DRIVER because it is the latest version, that is supposed to work with CS6, not CS5 yet, AND with the latest version of Matrox drivers, which I had installed especially for the CS6 upgrade and GUESS WHAT????

Premiere CS5 has NO PROBLEM at all running the Mercury Playback Engine with my hardware and software and drivers, even the drivers that were written after the release of CS5.

Perhaps insolent but unfortunately true conclusion: I spent a whole lot of money for an Adobe CS upgrade THAT S*CKS.

This is very, very sad indeed: I am sure now that there has been no testing whatsoever with Premiere CS6 and NVidia Quadro 4000, or this issue should have popped up.

My thanks go to all people here who really tried to help me in this impossible quest. I am now going to point a few arrows to the Adobe crew concerning either refunding the money or solving this issue. I checked all system requirements and they were easily met, yet I'm stuck with a beta-like version of rapidly stuck-together software that cost me a few days to eventually throw in the garbage can. Very disappointing, but I am on the rails again with the good old CS 5.

Harm, Gary and Ulf: thanks again, I think it's obvious now why we couldn't figure this out. So long!

Thanks Harm, I think there indeed is no suitable driver from nVidia yet, but it still questions me what, in the beta stage circumstances, made the difference for Premiere to work... or it might have something to do with another combination of software e.g. Windows 7 playing a role... not sure.

I will certainly file a bug report - hope that I find out how to do that so maybe I will ask for your help once more. But I will be back to report.

Cheers !

Thanks, I found it. Official bug report on its way!

Thanks Harm.