4 Replies Latest reply on Dec 3, 2009 10:15 AM by Cozmicone

    Rendering video crashes with 8G of RAM

    Cozmicone Level 4

      I'm running Windows 7 Enterprise 64-bit and Adobe CS4. I've been using 4G of RAM and recently put in another 4G but now when I try to encode video from Premiere Pro, Media Encoder crashes. I've attempted to render the video multiple times and each time AME crashes at different stages in the encoding process. The crash also impacts the computer in different ways. Sometimes AME just crashes, other times the entire computer gets a blue screen and then reboots. The blue screen never states what exactly crashed and only gives a numerical error code.

       

      I can't locate any of the crashes in Event Viewer if AME creates a blue screen crash. The AME crashes that are logged in Event Viewer show that PProHeadless.exe crashes first and also has an additional error message, then AME crashes. These are the error messages:

       

      Faulting application name: PProHeadless.exe, version: 0.0.0.0, time stamp: 0x4ae004ae

      Faulting module name: ImporterHost.dll, version: 0.0.0.0, time stamp: 0x4adff7d2

      Exception code: 0xc000001d

      Fault offset: 0x0004587c

      Faulting process id: 0x1038

      Faulting application start time: 0x01ca6a194355fa43

      Faulting application path: D:\software\Adobe\Adobe Premiere Pro CS4\PProHeadless.exe

      Faulting module path: D:\software\Adobe\Adobe Premiere Pro CS4\ImporterHost.dll

      Report Id: a54f80b3-d60c-11de-b22c-001e2a376084

      ------

      Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program PProHeadless.exe because of this error.

       

      Program: PProHeadless.exe

      File:

       

      The error value is listed in the Additional Data section.

      User Action

      1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.

      2. If the file still cannot be accessed and

                      - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.

                      - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.

      3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.

      4. If the problem persists, restore the file from a backup copy.

      5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

       

      Additional Data

      Error value: 00000000

      ------

      The program Adobe Media Encoder.exe version 4.2.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

      Process ID: 388

      Start Time: 01ca6a19db334efc

      Termination Time: 11

      Application Path: C:\Program Files (x86)\Adobe\Adobe Media Encoder CS4\Adobe Media Encoder.exe

      Report Id: bd2a96ac-d60e-11de-b22c-001e2a376084

       

       

      These are the error logs from Premiere:

      - Source File: C:\Users\MSTEPH~1\AppData\Local\Temp\Fathers Panel_6.prproj

      - Output File: F:\Fathers panel\FANAWithTeenagers.wmv

      - Preset Used: NTSC Source to Download 512kbps

      - Video: 360x264, 15 [fps]

      - Audio:  64 kbps, 48 kHz, stereo VBR

      - Bitrate: Compressed, VBR, 2 Pass, Audiences:1, Avg 400.00 [kbps]

      - Encoding Time: 00:03:39

      11/20/2009 2:08:29 PM : Encoding Failed

      -------------------------------------

      The Operation was interrupted by user

      -------------------------------------

       

      - Source File: C:\Users\MSTEPH~1\AppData\Local\Temp\Fathers Panel_7.prproj

      - Output File: F:\Fathers panel\Panel1.wmv

      - Preset Used: NTSC Source to Download 512kbps

      - Video: 360x264, 15 [fps]

      - Audio:  64 kbps, 48 kHz, stereo VBR

      - Bitrate: Compressed, VBR, 2 Pass, Audiences:1, Avg 400.00 [kbps]

      - Encoding Time: 00:00:19

      11/20/2009 2:09:38 PM : Encoding Failed

      -------------------------------------

      The Operation was interrupted by user

      -------------------------------------

       

      These are my system specs:

      Windows 7 Enterprise 64-bit

      ASUS M3A mobo

      AMD Phenom 9500 Quad-Core 2.2Ghz

      (4) 2G OCZ Reaper 8500, 5-5-5@2.2V

      GeForce 8800 GTS 640M

      Coolmax 600W PSU

       

       

       

        • 1. Re: Rendering video crashes with 8G of RAM
          the_wine_snob Level 9

          First thing that I would do is set the computer to NOT Reboot on Error (or whatever the exact syntax is for your OS). Then, you should be able to read the BSOD message completely.

           

          It sounds like you have memory issues. Do your RAM chips match 100%? Are they seated properly? Have you added the new RAM in SetUp in the BIOS? How does the RAM show up in SetUp and in the OS? These would be the areas that I would look into first. It sounds like something about that new RAM is just not correct. Could be SetUp, or maybe some DIP/jumper on the MoBo?

           

          Good luck,

           

          Hunt

          • 2. Re: Rendering video crashes with 8G of RAM
            Jim_Simon Level 8
            other times the entire computer gets a blue screen and then reboots.

             

             

             

             

            At this stage of Windows development, that usually indicates a hardware problem.  Since it happens when the CPU is likely to be maxed out, I'd maybe look at some overheating issues.

            • 3. Re: Rendering video crashes with 8G of RAM
              Harm Millaard Level 7

              To check memory, use MemTest86+, to check temperatures during rendering, use SpeedFan 4.39 or RealTemp.

               

              What are the last 4 digits on the BSOD code? 0101, 0124, or what? What does system event viewer say about errors ?

              • 4. Re: Rendering video crashes with 8G of RAM
                Cozmicone Level 4

                I checked and my BIOS was really out of date. I flashed the updated ROM to the BIOS and did a test render that completed without any problems. I'll have time to do more encoding next week and if it continues to crash I'll post follow-up info.

                 

                Thanks for the input everyone.  =^ )