Mercury hardware acceleration crashes Media Encoder

My old NVidia with CUDA worked well with Mercury acceleration, but I recently upgraded my graphics card to AMD Radeon R9 200 Series to coincide with the latest Creative Cloud suite. I tried revising the clock speed down to 1000 MHz, I believe.

Hi ND Frizzle,
I have heard of another customer having trouble with this GPU. Let me see if I can find that so that we can find any common issues.
Thanks,
Kevin

Similar Messages

Display Driver has stopped responding and has recovered. bsod if I use mercury hardware acceleration

Hi, I bought a cheap NVIDIA card to go alongside my GTX285 to allow me to use a third monitor for timeline playback. I've done this before with an ati card with no issues but needed to change to a single height card to get the extra slot back.
It installed it's drivers and then whenever I opened premiere CS6 it would immediately hang and blue screen. I removed the card and rolled back to old drivers but no change. NVIDIA support gave me beta drivers but no change either. They suggested that my card or motherboard was faulty. (Motherboard is a EVGA Sr2) Eventually I found I can edit normally if I turn off hardware acceleration for the mercury playback engine and leave it as software only. Not much use when my GPU supports CUDA.
Even now the display driver keeps giving me the "stopped responding" message with or without premiere open so I'm thinking there is some hardware issue somewhere. The Blue screen only occurs when I use mercury hardware acceleration.
I have ordered a GTX470 because I can't afford to spend hundreds on a 690 etc.
The current driver version is 306.97, error occurs in CS5 and CS6
Any suggestions would be appreciated. Thanks, Michael.

The reason the ATI card worked was because that is completely 2 separate drivers. That makes it easier for the OS to sort out the device ID's although that can cause issues with some applications and the ram shadowing done by Win 7 compositing mode. However when you use 2 Nvidia GPU's, the drivers are essentially the same as far as what the OS see's but they have completely different support for things like Direct X. This often can cause major issues with drawing out on the screen. The other issue is the 2 cards may not have resource charts that are far enough apart to avoid resource issues. If you cant return the 470 card then you may want to try a 1GB 620 card for the 2nd video card and see if that will work. That will minimize the resource shadowing and hopefully run the 600 series card in the Direct X version the 400 series card will run.
Eric
ADK

Mercury Hardware Acceleration disappears when upgrading from CS6 to CC.

I have an iMac (27-inch Mid 2011 AMD Radeon HD 6770M 512 MB) with 16gb of memory.
I upgraded Premiere from CS6 to CC. I had mercury hardware acceleration support on CS6. The acceleration option has disappeared following my upgrade to CC.
Have tried this on two machines now.
Can anyone help? Am I missing the obvious?
Ian.
PS. I first posted this in the CC forum. And was, quite rightly, told to post it here…. :-)

They actually didn't raise it. It's always required 1GB.
http://helpx.adobe.com/x-productkb/policy-pricing/system-requirements-premiere-pro.html
It seems an error of sorts that it worked with less on Macs. That's been 'corrected'.

Urgent: constant Crash Media encoder, premiere pro CC and CC2014.

(Sorry by advance, its an Google trad)
Hello everyone!
I meet great difficulties with Premier Pro and Media encode CC and CC2014.
When I want to wire my pending projects that I go through File> Import (or even composition After Premier) or I simply do a drag / drop in Media Encoder .... Half the time it crashes, not charging Dynamic link not or crash Premier pro ..... with CC versions like 2014 .... I have no particular error message. However I have to process the killer Dynamic link, adobe (in general: QT32 server, Adobe ipCbrocker, PProHeadless.exe) via the Windows task manager. If not impossible to reopen the software.
I also noticed that even when the software does not crash, I close the first or afx or other software will not come out of the process, there is ad infinitum in the active process.
When I still manage to import my sequences in MediaEncoder, this plant some encodings but not all .... no particular reason and not telling me why he crashed. If it does not crash, it runs in a loop on the same image and I have to stop myself encoding, which never end. Knowing that all my files are part of a series, there has exactly the same things in it in terms of editing, effects etc.. Which by the way is only melted ....
Rush are my MXF files. And I use the Dynamic Link to import my sequences between Premier Pro and afx. Although it makes me exactly the same problem that I import directly my first or I go through Dynamic Link.
I'm on:
Windos Seven PRo 64bit.
I have a 3.33GHz i7 X980
Nvidia GTX480 driver 337.88 (the latest what)
AND 16GB RAm
My cache is not full, I empty it regularly. It is a hard look at projects and never moves.
So, if anyone has the same problem or knows a solution, I'm interested.
It falls at the wrong time, I have 200 to encode videos in one month.
Thank you in advance.
A.H
Message was edited by: aurel motiond

Il ne sert pas à grand chose ce forum, sans vouloir être offensant....

X-Fi Fatal1ty PCI/-Express - All Hardware Acceleration Crashing, Significant R

Hello,
I've made a few posts on the forums recently about various topics to help me isolate the issue I am having. At this point, using the latest stable drivers for either a PCI or PCI-E X-Fi Fatalty, any hardware acceleration of sounds is causing my system to bluescreen, freeze or crash the application. Some games give me no option of not using hardware acceleration (ie. Rainbow6 Vegas 2), resorting in my having to change my Sound Acceleration down to Emulation Only. This setting greatly eases off on the sound latency buffers, resulting in sounds that are delayed an entire second. The good news is no crashes and sounds actually sound correct.
A few things to note about my setup,
) I am an extreme computer professional, programmer and developer. My Windows XP SP2 installation is incredibly streamlined; I only have 6 services running and all non-essential drivers removed, resulting in only 69MiB commit charge at startup across processes and ~950 threads. Suffice to say, my system is baby-cheek clean, and I aim to keep it that way.
2) I have been using this setup for many years now. I have been using NVIDIA video cards for the past 5+ years, currently I have a GTX280, and all of them have behaved perfectly with my streamlined setup. I even unregister every single one of NVIDIA's DLLs and stop all of their services, and the 3D Settings Per Application and Color Control Features still all work. Suffice to say, NVIDIA's drivers, although a trite on the large side, are written well enough to keep drivers away from OS services (as it should be).
3) My other hardware is not at fault. I have tested the X-Fis against multiple PSUs, different video cards, multiple fresh installations of Windows and more. I don't use utilities to clean my drivers; I do it by hand. I know exactly what's on my system and what I want removed. Though it may be egotistical to state, I'm pretty much knowledgable of every component my system has running.
4) As a result of this knowledge and my desire to keep my system clean, I ONLY HAVE INSTALLED the drivers necessary for my X-Fis to work. I DID install Creative Audio Console, but the application seems to have too many dependencies on OS Services, since it never runs, either reporting that my audio device cannot be found, or the application simply does nothing and a bogus error is written to the event log. I have enabled DCOM to make sure it wasn't dependent on that, and it still does not work. To summarize, yes, I have tried enabling every service I could find that it might depend on, and none worked. Creative Audio Console is, to me, a piece of ill-written software. In comparison to NVIDIA's excellent control panel which works no matter how much stuff I remove, Creative's Audio Console fails.
I do not have the Creative Audio Licensing Engine, I do not have the Creative Audio Control Panel, I do not have the Creative Labs Audio Engine Service, I do not have CMSS or any other OS-level services that normally get installed. Remember people, drivers are NOT TO BE DEPENDENT on OS services; they are protocols defining to the OS how to communicate with the hardware. Any necessity of additional "service" software is way past the acceptable standards of drivers.
5) That being said, I had no issues with stability using older drivers on my PCI X-Fi Fatalty cards. These drivers were dated early 2007, and did not install all of the X-Fi Effects, Utility Effects, 20x Effects, etc. drivers. Mind you I preferred these drivers since they were much simpler to track, as they only had a few .sys files.
As it stands, I want to use my PCI-Express X-Fi Fatalty, but I want to use it without all of Creative's bloat. I want streamlined, driver-only installation that does not NEED external applications to reinforce its stability. Creative, IS THAT POSSIBLE? Can someone, by definition of the Windows Driver Management signature system, just use your drivers alone for stable gaming? If not, you're violating standards and should never have received WDM cert. on any drivers. I highly recommend you do NOT spit back, saying that for proper functionality, performance, stability, etc. you must install all of Creative's supplemental software. These requires are in violation of the ethics behind software drivers and receiving Digital Signature Certification from Microsoft on your drivers.

Infinity7,
I do not want to sound arrogant, but the list of options you provided me with is the stereotypical laundry list of system configuration information for any piece of hardware. I'll address everything though.
) No, I'm not using an NVIDIA chipset. I'm using an ASuS Maximus Extreme, just like you said, which uses the X38 chipset.
2) I'm using Windows XP 32-bit, SP2. I have 2 GiB of memory and do NOT have PAE enabled.
2) I don't have onboard sound; our motherboard has a PCI-E sound card which I do not have installed.
3) I don't have any spyware. I don't browse the web on my system. I know every program running and have no rootkits. Nothing is hiding from me.
4) I don't use antivirus programs. I've been on the internet for 5+ years now and have never needed an antivirus program, since I know when I have a virus and I remove it manually.
5) I have the latest version of DirectX, June 2008 Redistritutable. Note that most of the post DX 9.0c revisions are meant for D3D, and have nothing to do with DSound.
6) I've tried every PCI-E slot I have, including both PCI-E x slots and both PCI-E x6 slots. The card is currently in one of my x6 slots.
7) Any 998+ system is going to have IRQ sharing. Between ACPI BIOSes (more IRQs), Windows XP and drivers, IRQs are rarely in conflict, aside from occasional USB device IRQ sharing. To answer your question, yes, currently both my video card and sound card are sharing IRQ 6. I have done enough work to isolate that IRQ sharing is NOT the issue, though, especially through my testing of the PCI card and the PCI-E card experiencing the same issue.
8) The output sampling rate of games is not always configurable, and never makes a difference. The X-Fi always upsamples everything it gets as it is, though I guess there is some validity to the sampling rates that are streamed into the buffers.
Now, to address the rest of your suggestions I say read my post. I specify that changing acceleration to emulation results in perfect stability and sounds that sound correct, however the relaxed latency results in sounds? that are easily delayed by second. This is unacceptable for gaming, obviously.
As for your ordering of driver installation, it really is through lack of knowledge that people state what order drivers must be installed in. Even NVIDIA's drivers probe for any change through the interfaces they use when the system starts, so any chipset drivers that drastically change the devices in Windows will be detected as changed by other drivers. Be that as it may, I didn't even have the X-Fi in my computer when I installed this latest version of Windows. Only after I had installed everything did I begin to install the Creative Drivers (whilst avoiding all bloatware).
Most importantly, note that I determined when the crashing started occuring with my original PCI version of the card. After I installed the drivers that started including the additional .sys files (X-Fi Effects, 20X effects, etc.) the crashing occured. As far as I know I cannot use older drivers with the PCI-E model, so rolling back to those previous drivers is out of the question.
Lastly, for my system specs,
Motherboard : ASuS Maximus Extreme X38 Chipset, BIOS 0907
CPU : Intel QX9650 (OCed from 3.0GHZ to 3.6GHZ, stable through Orthos testing)
Memory : (2) GiB Corsair Dominator Sticks, 4-4-4-2
Video : eVGA GeForce GTX280 FTW Edition (PCI-Express)
PSU : Thermaltake Toughpower 200W (backed by UPS)
Sound : Creative X-Fi Fatalty PCI / PCI-Express (tried both independently)

Cineform Codec crashes Media Encoder CS4

Trying out current trial version of Cineform Neoscene. Regardless of Codec settings, exporting with Cineform Codec crashes my AME (PPro CS4). Eventually only a hard reboot will get things running again. Other codecs work fine. Hoping for some suggestions to rectify this.
I need to render Intermediates - one of 3 project tapes (all of them HD footage from an XHA1 on brand new tapes) is corrupted and I have to slide the audio around and export synchronized clips as this tape's footage captures with dropped/red frames resulting in shifted (not drifting, aparrently) audio/video sync. (Same - or worse - capture problem with HDV split and Cineform capture also. Gave up on digesting synched footage after days of attempts.) Have succesfully captured many hours of DV with the system except from this one tape.
The export problem occurs with any footage (uncorrupted included) I put on a timeline in any format of project I've tried (DV included). It occurs whether PPro is running, minimized, or closed when AME is run.
(This install of CS4 has been working okay otherwise, though - to solve some recent performance slow-downs and crashes-on-quit - I could not reinstall the programme unless I added a second user/admin account. Adobe don't know why.)
I've ensured firewall and antivirus are off when both installing/reinstalling all this and when running these exports. XPpro is a new install with all drivers and components up to date. Bios recently flashed to current.
I'm otherwise having modest success doing this small HD project on a lowish-spec pair of PCs (one's a backup) and rented cameras in part to determine my next upgrade (PPro PC or Mac, FCP - not sure what HD camera)to an HD-optimized system.
The spec I'm using is minimal but acceptable for getting something out of Cineform, according to the readme. I would expect that at least the lowest settings would work, but all crash identically - within a few seconds after "Start Queue" is clicked; always before any progress is tabulated/shown. A crash notice replaces AME, including a window to report the crash to Adobe. I dispatch that and try again. Eventually the system goes up to 100% CPU use after one of these crashes and stays there despite attempts from panes or Task Mgr to close Ppro/AME. Each AME attempt adds another instance of PProHeadless to the Process list, but the performance is equally crashy from first through to the final attempt.
I've tried every solution my research has unearthed. Suggestions appreciated.
CS4
P4 3Ghz
3.2 GB ram
GEforce 8800 GT
7200 RPM SATA drives

Yes, as I noted, capturing this problem footage as HD in any way nets out of sync so that's off the table.
And yes Ann, thanks, it gives those minimums on the CF download page and I'm pushing the envelope with this exploration. Nevertheless, CF's readme gives P4 as a minimum - perhaps a complete error but I've assumed more a matter of degree of performance rather than absolute failure at the spec I'm attempting.
I'm finding that I'm able to off-line edit in SD and then render subsituting identical HD clips with any other codec I've chosen on this system - that's the workflow I'm having success with. (So being able to generate identical clips between the SD and HD is crucial. Hence ideally being able to work with the longest possible clip of agglomerated shots, logging it and down-resing it as one operation, and not needing to down-res render a myriad of individual clips.)
Maybe the descrepancy between download page and Readme is a complete error, but it's lead me to expect that the codec would be just painfully slow with this system. That would not prevent using it to render (only to edit.)
Thanks for your thoughts. It may indeed not work at all with CF, and in that case I'll probably use Lagarith (aparrently lower quality, but it works on this system) but I was hoping to find a way to make CF work. If this problem is in fact a minimum spec issue - and it looks likely, doesn't it - it will be the first tech problem I'm had where the actual problem was an obvious one! (They're often system configuration, conflict, or - usually - undocumented settings issues.)

Render video is crashing media encoder

I have a long video presentation 1hr 7 min, in which I had to remove an rf transmitter with the clone brush. This is shot on 2 cameras so many layers. I finished about half the show and sent it to render overnight. Which it did. I continued work on the remainder of the show and it is crashing in ME.
Am I demanding too much from ME or is there something else going on.
Late 2009 12 core macpro
40 gb ram
Video drive Xserve raid
Video card Kona III
Graphics, quadro 4000
Photoshop CC 7.2
Thx...jim watt

Probably a damaged source footage file. Could be as trivial as a discontinuous timecode. Try to re-export/ convert the source file. If you used a clip format for rendering, you should try to export an image sequence and then convert it in a second pass.
Mylenium

Premiere CC exports crash, media encoder CC crashes, after effects cs6 to cc modify composition

Hi,
we are working in a project formed by many episodes of 1 hour each episode.
We have also many clips that come to premiere from after effects throught dynamic link (masks that hide unwanted elements, this kind of things).
The point is that we decided to update to cc from cs6, and the hell's been unleashed...
We have converted premiere projects cs6 to CC, as well as each premiere project file, and in many clips that came from after effects the work has been alterated, we see fly's that we got hide, some other clips the image is totally distorted by something that before was a mask...many of the work is ruined...and it's not easy to detect because sometimes are little parts of image. It's like somebody's been playing with our compositions...if we reopen the cs6 version just before converting to cc everything's fine, after it's chaos... the problem is that we return to cs6 we will lose a month and could be critical...
When whe export in differents formats, (720p, 1080i, .mov, mpeg2, mpeg4, blu ray...) we have success 1 time each 10 (normally it get's stuck in a image or it pops up an error message of premiere), and if it succeed exporting, the export has strange artifacts like green or purple parts of the image that we cannot see in the timeline, and that disappear if we export only the affected part of the timeline...
None of this things happened before with cs6, somebody has the same problem? is there a solution? We are really disappointed with CC, it's very unpleasant to start to see flyes ant stuff that we had hided, especially because the changes are not evident and hard to detect.
Help!
Our computer:
Processor 2 x 3.06 GHz 6-Core Intel Xeon
Memory 32 GB 1333 MHz DDR3 ECC
Graphics NVIDIA Quadro K5000 4096 MB / BlackMagic Decklink Studio 2
Software OS X 10.8.4 (12E55)
everything up to date, we formatted and updated last week and nothing changes

Hello Jim,
Thank you for your answer.
Bye.

Adobe Media Encoder CS6 crashes when quit

OS X 10.7.4
Multiple hardware types
Adobe Media Encoder CS6 as installed from Adobe Production Premium CS6. NOTE: CS6 was installed under a different user than the new user that is having AME crash.
Issue:
Open AME. Encode a file or do not encode a file because the end result does not matter. Now quit AME (either hotkey or File --> Quit). AME then crashes. Keep in mind that no other CS6 programs are affected this way, just AME.
I ran into this problem weeks ago and found a solution that worked. The fix was to delete one of the many many folders Adobe creates in your user folder. The problem now is I cannot find that same posting where the fix was listed.
I deleted this "mystery folder" we will call it and then AME CS6 worked fine. The catch was that I had to redo the whole "Adobe ID" sign in BS and retype the serial number when I opened one of the other programs.
Any guesses as to where this folder might be so I can delete it again? I was hoping some others may have run into this same issue. I will keep looking for the fix, and post it back here if I finally find it.

Just deleting the Adobe Media Encoder folder in the given directory works just fine and this saves a lot of trouble because your settings are maintained as are your presets.
But thanks a lot for the help

AME Adobe Media Encoder Cuda GPU Acceleration not activated, How do I activate it

Mac Pro Early 2009 4.1, Processor 2.93 GHz Quad-Core Intel Xeon, Memory 16 GB 1066 MHz DDR3 ECC, Graphics NVIDIA GeForce GTX 680 2048 MB, Software OS X 10.9.2 (13C64)
Adobe CS6 suite up to date all programs as of 3-18-14
NVidia Cuda Driver 5.5.47 installed, Open CL and GL capable
I read this article http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-mercury-playback-engi ne-in-the-macbook-pro-retina/. it shows GPU acceleration through AME (see below). In my AME que window I do not see this

Todd:
(edit)
Just reread - sorry, CS6 vs CC.
What about AME CC?
http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-m ercury-playback-engine-in-the-macbook-pro-retina/
So, CUDA acceleration in AME and OpenCL is supported. Anyway to monitor this? I get FAILED when I try either (on a box with nVidia, or a box with AMD).
Found this: http://helpx.adobe.com/media-encoder/using/whats-new-media-encoder-7-1.html#gpu-accelerati on
GPU acceleration
Adobe Media Encoder now takes advantage of GPU for rendering purposes. Both CUDA and OpenCL are supported. The latest release of AME uses the GPU for the following renders:
Scaling (HD to SD; SD to HD)
Timecode filter
Pixel format conversions
Deinterlacing
Aspect ratio changes
All effects in the Effects tab
GPU accelerated effects in Premiere Pro
If you are rendering a Premiere Pro sequence, Adobe Media Encoder will use the GPU render preference you have set for the project. All GPU rendering capabilities of Premiere Pro are utilized.The limited set of GPU renderable tasks in Adobe Media Encoder is only for renders that originate in Adobe Media Encoder.
If you are rendering a sequence with native sequence support, the GPU setting in AME is used and the project setting is ignored. In this case, all GPU rendering capabilities of Premiere Pro are utilized directly in AME.
If your project uses 3rd party VSTs (Virtual Studio plugins), the GPU setting in the project is used. The sequence is encoded through headless Premiere Pro just as in earlier versions of Adobe Media Encoder. If Enable Native Premiere Pro Sequence Import option is unchecked, headless Premiere Pro will always be used and the GPU setting is used.

Adobe Premiere Pro - Crashing with OpenCL Hardware Acceleration on Export

Hey everybody,
One of the major reasons I decided to buckle down and pay for PPCC was the OpenCL Hardware acceleration with AMD cards. I run two AMD Radeon 7870s in Crossfire right now, and I immediately noticed a huge difference in performance when editing. When it came time to export my video, though, Premiere Pro would crash after rendering around 2% of the full video. I've tried both with and without Crossfire activated but using OpenCL with Hardware acceleration crashed my export no matter what. As soon as I turned it back to regular Mercury Playback (software only), the project rendered just fine.
I currently have the lastest AMD drivers and have had no other issues with my card, and I also gave PPCC the latest update as well. Any idea why this might be happening? I wouldn't be surprised if I need to wait for a latest AMD driver in order to get things to work with the brand new CC apps, but I figured I'd farm my question out here just in case. I'm running on Windows 8 64 bit.

Yes. I have problems with my new AMD 1950 3GB. I creat 2h 20 min project on premiere cc and put on all material color correction. NO lumetri. Premiere crache on export about 1h after working.
I was editing AVCHD material and export from presets to Blu-Ray H264 and mpeg2 with the same result.
My conf.
Xeon E5-2620
Asus Z9PE-D8 WS
System&Apps disc: SSD vertex 3
Project: veloci raptor 250GB
Export: veloci raptor 250GB
RAM: 32 GB
Graf: radeon HD7950 3GB, Gigabyte
When I switch to my old card - nvidia - GTX470 everything just go fine and my export is finish perfectly.
I was using beta driver from amd 13.4.
It is confusing because I bought that card especially for Premiere CC, and I was thinking to bought second one, and maybe more...
Please help what can I do with it.
Sory for my english

Adobe Flash Media Live Encoder 3 - Video Hardware Acceleration Warning

I have been looking for an answer for this error for a few days without any luck.
I just loaded the Adobe Free Encoder 3 and the Flash Media Server (Free Version) on a Dell PowerEdge 1950 running Windows 2003 server standard edition with Service Pack 2. The computer has an Intel Pentium III Xeon 2.66GHz Quad core processor with 4GB RAM. I am using an Osprey 240 video capture card.
The computer was previously running Windows Media Encoder and it was working fine, but I needed to upgrade to a flash stream.
Whenever I start the Adobe Flash Media Live Encoder I get the following error:
"The video card's hardware acceleration level is set too low. Open the Display Properties, Settings tab and click Advanced, then select the Troubleshoot tab and increase the Hardware acceleration setting. Then restart the application, etc...
I did as instructed and it did not work. I also tried changing the display settings to lower and higher resolutions. I also updated the video card to the latest drivers. I double checked the hardware requirements. http://www.adobe.com/products/flashmediaserver/flashmediaencoder/systemreqs/ and it looks like I'm ok.
I also checked the approved hardware list http://www.adobe.com/support/documentation/en/flashmediaencoder/FMLE_DeviceMatrix3.0.pdf.
The Osprey 240 is not listed, but that seems to be working fine.
I'm thinking that the internal video card that I have may not be compatible with the Adobe Encoder. The video card that I have is an ATI ES1000 embedded video that has only 16MB of RAM.
I have the latest version of DirectX - I ran DxDiag and it shows that I'm running DirectX 9.0c (4.09.0000.0904), Under the Display tab it says that the DirectDraw Acceleration, Direct3D Acceleration and AGP Acceleration are not available.
Any help would be greatly appreciated.
Thanks.
Anthony

http://forums.adobe.com/community/flash/flash_media_live_encoder

Premiere CC and Media Encoder crashing new Mac Pro

Since installing CC on my new Mac Pro (Late 2013) Premiere and Adobe Media Encoder have been continually crashing my system.
At first, my comp would freeze and I'd have to hard restart, then it switched to rebooting on in's own. This would happen 10-20 times a day while editing.
This began shortly after I synced settings from a previous version of PP but since I've installed new RAM; reinstalled CC/PP; reformatted my HDD and reinstalled Mavericks, CC, PP; and have not synced my settings. I've also tried editing multiple projects of different sizes with different media types -- all are experiencing the same problems.
When I edit the same projects on my MBP, everything works fine.
Recently, I have disabled GPU acceleration in all of my PP projects and that seems to have solved the problem.
My office received 3 Pros at the same time with the same hardware configurations and software -- I am the only one experiencing this problem.
Here are some specs:
Late 2013 Mac Pro
2.7 Ghz 12-Core Intel Xeon E5
64 GB 1867 MHz DDR3 ECC
AMD FirePro D700 6144 MB
All drivers, CC, and software is up to date.
So what do I do now?
Any help is much appreciated!

I am on Windows, but have a few saved Mac discussions that may help (or, may not... but free to read)
Mac and Root User http://forums.adobe.com/thread/879931
-and http://forums.adobe.com/thread/940869?tstart=0
Mac & nVidia Driver http://forums.adobe.com/thread/1075592
-and http://www.nvidia.com/object/mac-driver-archive.html
Mac Retina Bug http://forums.adobe.com/thread/1159632
Troubleshooting guide for Mac freeze
http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.html
External speakers stop playback http://forums.adobe.com/thread/1370072?tstart=0
OSX Crash http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html

Premiere Pro / Media Encoder crash during encoding

Afternoon guys, wonder if anyone has any tips on how to solve my issue. It's a new pc that I'm working on, my first project on it, everything working great in terms of the edit, but crashing whilst encoding both through Premiere Pro and Media Encoder with an error message (below). I'm not great with this stuff so please let me know if I need to provide more info and I'll provide much information as I can.
I'm a creative cloud user.
-Premiere Pro cs 6 (6.0.3) - I have tried to re-install the software, and ran all the updates yesterday after the install. Problem still persists.
-Encoder cs6 (6.0.3.1)
-Windows 7 Professional service pack 1, 64bit. Whilst I was online re-installing Premiere Pro windows did some updates (I generally keep my editing pc's offline).
-DSLR footage (.mov) for video, up to 3 sources of video (nested for multicam shoot) and running one source of audio (mp3 file). Two of the timelines I'm trying to encode are about 45 minutes long.. I have succesfully encoded other clips (a 5 minute, and a 35 minute previously. Miraculously this morning I encoded a 1h12m clip using the mpeg2-dvd preset with only adjustment of quality bumped from 4 to 5). So this was encoded after all the updates, however since then everything else is not working.
-Initially encoder was either freezing, or giving me an error message. Since re-installing all the software yesterday it now does not freeze, but I get the error message: "Adobe Media Encoder CS6.0 has stopped working... A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." I get the same message when encoding with both AME and Premiere Pro. I click "close" from here and nothing else happens.
-Trying to export to mpeg2-dvd, I have tried the PAL widescreen preset, as well as trying to adjust the settings, doesn't seem to make a difference, the error message pops up different points during encoding.
-The only plugin I have used is magic bullet looks for some grading. It also fails to encode with no plugins used.
-PC     - Intel i7-3770 @ 3.40ghz,
          - 32GB ram
          - Operating system and Adobe Suite on c: (SSD 240gb)
          - Project source footage (video, audio, etc) f: (2tb)
          - Encoding files to e: (SSD 240gb)
          - my case is an Antec 902, with no additional fans. It does sound like it's working harder during encoding, not sure if a heat issue could be causing the software to error?
-I am using the mercury playback engine with a Gefore gtx 680 (2gb).
I have not been able to find any definitive answeres with regard to the crashes. I did also have encoder hanging whilst reading the xmp file. I have tried encoding video only (audio disabled) and whilst it doesn't hang during reading of xmp file, it still stops working with the above error message.
I also run an older PC with i920, 24gig, gtx570 and it never crashes but performs much slower. It is also running windows 7, same setup but different hardware. Not sure if the hardware on my new pc could be causing the issues, if you you guys have any troubleshooting tips it would be much appreciated. At this point i have tried starting a new project, new timelines, nothing seems to work, so I have transferred the data to my old pc for encoding (as I need to deliver the discs to a client), but I need to get this new setup working properly.
Cheers,
Stevan

Hi Axel,
Thanks for your suggestions, I just tried cleaning out the media cache and also rendered out a wav file of the audio and placed it in the timeline and deleted the mp3 version.. Tried once again to encode an mpeg2-dvd file.
1st attempt encoding through Media Encoder, pal widescreen with variable bit rate set to 6, 7 and 8 = everything froze, had to restart via button.
2nd attempt encoding through Media Encoder = this time tried video only same settings just no audio = same error (Adobe Media Encoder cs6.0 has stopped working...)
3rd attempt encoding through Premiere Pro, same settings with audio = same error message.
4th attempt encoding through Media Encoder, pal wide preset as standard with no change = same error message.
5th attempt encoding through Media Encoder, h264 preset for vimeo, 720p = same error message.
6th attempt encoding through Media Encoder, AVI (Uncompressed) 720 x 480 preset. 1m40s in the dreaded blue screen appeared. "A problem has been detected and windows has been shut down to prevent damage to your computer. A clock interrupt was not received on a secondary processor within the allocated time interval. " Bla bla bla.
In all instances the encoding is absolutely flying, but always ends up crashing.

Media Encoder crashes with Bluescreen

I'm using Adobe Premiere CS4 w/ Windows XP to edit some MPEG2-Videos. All I do is importing them, doing some edits and exporting them back as MPEG2. Everything worked just fine with Premiere CS2. But since I upgraded to CS4, everytime I try to export a file with Media Encoder, my system crashes.
In about half the cases, there's a Bluescreen 000000B8 "A wait operation, attach process, or yield was attempted from a DPC Routine". In the other cases, the BSOD errors vary (PFN_LIST_CORRUPT, PAGE_FAULT_IN_NONPAGED_AREA), the system just freezes or restarts without warning.
What I've tried so far:
Updating mainboard/chipset drivers
Upgrading BIOS to latest version
Switching graphics accelerator
Trying different hard disks
Changing RAM
Checking Syslog for errors
Lightning a candle on Sunday :-)
Reinstalling Apple Quicktime
Deinstalling all Adobe Software and reinstalling them from scratch
All Adobe programs and Windows itself are up to date
Any more advises?

Often these problems can be caused by a faulty PSU or by heat problems. Use Speedfan or HWMonitor to check these and please post a link or screenshot to the results. Can you give some more details on the hardware side? Mobo, processor, RAM, PSU, video and disk setup, etc.

Mercury hardware acceleration crashes Media Encoder

Similar Messages

Maybe you are looking for