Skip to main content
C
CtheProducerJBO
Participating Frequently
November 22, 2017
Frage

Crashes after about 5min of work on a Windows 10 Machine

  • November 22, 2017
  • 7 Antworten
  • 2043 Ansichten

Same issues on crashes after about 5min of work on a Windows 10 Machine. Mainly working in teams, but getting the issues in non-teams projects as well.

Leave computer to go to a meeting, come back Premiere has crashed. Also randomly crashes after 5 min or so while editing. Other projects have seemed to be a little more stable. Reality TV shows is the content with mainly raw Sont AVCHD footage mixed with GoPro content.

6 Cores and 32GB's of RAM. Running a GTX1080Ti with 11GB of VRAM, and did the driver update a couple weeks back when CC18 first launched.

    Dieses Thema wurde für Antworten geschlossen.

    7 Antworten

    C
    CtheProducerJBOAutor
    Participating Frequently
    December 12, 2017

    So I reinstalled Windows 10 to see if the memory issue would happen on a fresh machine. Before even letting Windows restart upon initial setup, I turned off all auto update features and the dreaded "install apps without you knowing" feature.

    I installed Creative Cloud and the respected apps. I formatted my cache drive. I did not mess with anything else in windows, nor did I install anything other than my RAID and Graphics driver.

    Upon opening the teams project, everything took a while to load, but it did (a little over 4,000 clips in this project). Then, as it sits and conforms, I get memory error and crash. I had tried to save out a normal project before it crashed, but get memory errors and freeze while it is trying to save out the normal project.

    Bellow is the system log that I can see threw the memory error in the event viewer. Please advise.

    I will say, it seems a normal NON TEAMS project works in CC18', with only 1 or 2 crashes a day.

    System Log:

    Log Name:      System

    Source:        Microsoft-Windows-Resource-Exhaustion-Detector

    Date:          12/12/2017 1:28:27 PM

    Event ID:      2004

    Task Category: Resource Exhaustion Diagnosis Events

    Level:         Warning

    Keywords:      Events related to exhaustion of system commit limit (virtual memory).

    User:          SYSTEM

    Computer:      DESKTOP-8RULES0

    Description:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Adobe Premiere Pro.exe (9904) consumed 34104979456 bytes, Adobe Media Encoder.exe (3384) consumed 746311680 bytes, and TeamProjectsLocalHub.exe (1468) consumed 639238144 bytes.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" />

        <EventID>2004</EventID>

        <Version>0</Version>

        <Level>3</Level>

        <Task>3</Task>

        <Opcode>33</Opcode>

        <Keywords>0x8000000020000000</Keywords>

        <TimeCreated SystemTime="2017-12-12T18:28:27.498199400Z" />

        <EventRecordID>864</EventRecordID>

        <Correlation ActivityID="{D53041EF-E281-4F99-B9F2-58A5C5F80D46}" />

        <Execution ProcessID="4704" ThreadID="14868" />

        <Channel>System</Channel>

        <Computer>DESKTOP-8RULES0</Computer>

        <Security UserID="S-1-5-18" />

      </System>

      <UserData>

        <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">

          <SystemInfo>

            <SystemCommitLimit>57708621824</SystemCommitLimit>

            <SystemCommitCharge>57449279488</SystemCommitCharge>

            <ProcessCommitCharge>36882079744</ProcessCommitCharge>

            <PagedPoolUsage>457621504</PagedPoolUsage>

            <PhysicalMemorySize>25760481280</PhysicalMemorySize>

            <PhysicalMemoryUsage>13396398080</PhysicalMemoryUsage>

            <NonPagedPoolUsage>608587776</NonPagedPoolUsage>

            <Processes>131</Processes>

          </SystemInfo>

          <ProcessInfo>

            <Process_1>

              <Name>Adobe Premiere Pro.exe</Name>

              <ID>9904</ID>

              <CreationTime>2017-12-12T16:01:54.633996300Z</CreationTime>

              <CommitCharge>34104979456</CommitCharge>

              <HandleCount>146439</HandleCount>

              <Version>12.0.0.224</Version>

              <TypeInfo>201</TypeInfo>

            </Process_1>

            <Process_2>

              <Name>Adobe Media Encoder.exe</Name>

              <ID>3384</ID>

              <CreationTime>2017-12-12T15:40:21.075771600Z</CreationTime>

              <CommitCharge>746311680</CommitCharge>

              <HandleCount>51691</HandleCount>

              <Version>12.0.0.202</Version>

              <TypeInfo>210</TypeInfo>

            </Process_2>

            <Process_3>

              <Name>TeamProjectsLocalHub.exe</Name>

              <ID>1468</ID>

              <CreationTime>2017-12-12T16:06:25.381292400Z</CreationTime>

              <CommitCharge>639238144</CommitCharge>

              <HandleCount>48074</HandleCount>

              <Version>2.0.1.0</Version>

              <TypeInfo>219</TypeInfo>

            </Process_3>

            <Process_4>

              <Name>

              </Name>

              <ID>0</ID>

              <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

              <CommitCharge>0</CommitCharge>

              <HandleCount>0</HandleCount>

              <Version>0.0.0.0</Version>

              <TypeInfo>0</TypeInfo>

            </Process_4>

            <Process_5>

              <Name>

              </Name>

              <ID>0</ID>

              <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

              <CommitCharge>0</CommitCharge>

              <HandleCount>0</HandleCount>

              <Version>0.0.0.0</Version>

              <TypeInfo>0</TypeInfo>

            </Process_5>

            <Process_6>

              <Name>

              </Name>

              <ID>0</ID>

              <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

              <CommitCharge>0</CommitCharge>

              <HandleCount>0</HandleCount>

              <Version>0.0.0.0</Version>

              <TypeInfo>0</TypeInfo>

            </Process_6>

          </ProcessInfo>

          <PagedPoolInfo>

            <Tag_1>

              <Name>MmSt</Name>

              <PoolUsed>124281952</PoolUsed>

            </Tag_1>

            <Tag_2>

              <Name>CM31</Name>

              <PoolUsed>84553728</PoolUsed>

            </Tag_2>

            <Tag_3>

              <Name>Sect</Name>

              <PoolUsed>34526704</PoolUsed>

            </Tag_3>

          </PagedPoolInfo>

          <NonPagedPoolInfo>

            <Tag_1>

              <Name>MmSc</Name>

              <PoolUsed>134217600</PoolUsed>

            </Tag_1>

            <Tag_2>

              <Name>smNp</Name>

              <PoolUsed>109203456</PoolUsed>

            </Tag_2>

            <Tag_3>

              <Name>smBt</Name>

              <PoolUsed>69959680</PoolUsed>

            </Tag_3>

          </NonPagedPoolInfo>

          <ExhaustionEventInfo>

            <Time>2017-12-12T18:28:26.492064600Z</Time>

          </ExhaustionEventInfo>

        </MemoryExhaustionInfo>

      </UserData>

    </Event>

    E
    excited_Genie16B8
    Legend
    December 13, 2017

    as it sits and conforms, I get memory error and crash.

    That is a known memory leak with Dolby encoded camera audio.  The only "fix" for now is to import the media in small groups, let them conform, then restart PP to clear the memory and import the next small group of clips.

    You'll have to figure something out for current projects with so much media.

    E
    excited_Genie16B8
    Legend
    December 15, 2017

    Thanks for the info Jim. Is this something that is Dolby / Windows related, or something that is not just working within Adobe? Sounds like a fix is going to come in the the form of a Windows update, not a premiere update.


    Here's the data.

    Changes to Dolby Decoding and Encoding Support

    There seems to be a memory leak associated with that code change.  I believe Adobe will need to be the one to fix.

    C
    CtheProducerJBOAutor
    Participating Frequently
    December 11, 2017

    Jim, I think this is the info you are looking for . If I need to grab the data from another window please advise.

    SYSTEM EVENT that had a warning or error next to them with Adobe:

    Log Name:      System

    Source:        Microsoft-Windows-Resource-Exhaustion-Detector

    Date:          12/4/2017 1:12:28 PM

    Event ID:      2004

    Task Category: Resource Exhaustion Diagnosis Events

    Level:         Warning

    Keywords:      Events related to exhaustion of system commit limit (virtual memory).

    User:          SYSTEM

    Computer:      DESKTOP-SSS6GI8

    Description:

    Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Adobe Premiere Pro.exe (10092) consumed 22942978048 bytes, Adobe Media Encoder.exe (4704) consumed 18851459072 bytes, and TeamProjectsLocalHub.exe (10832) consumed 863481856 bytes.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Microsoft-Windows-Resource-Exhaustion-Detector" Guid="{9988748E-C2E8-4054-85F6-0C3E1CAD2470}" />

        <EventID>2004</EventID>

        <Version>0</Version>

        <Level>3</Level>

        <Task>3</Task>

        <Opcode>33</Opcode>

        <Keywords>0x8000000020000000</Keywords>

        <TimeCreated SystemTime="2017-12-04T18:12:28.068618800Z" />

        <EventRecordID>1373</EventRecordID>

        <Correlation ActivityID="{B94CD4CE-63E6-4B87-B1FA-B547484709E5}" />

        <Execution ProcessID="15512" ThreadID="12860" />

        <Channel>System</Channel>

        <Computer>DESKTOP-SSS6GI8</Computer>

        <Security UserID="S-1-5-18" />

      </System>

      <UserData>

        <MemoryExhaustionInfo xmlns="http://www.microsoft.com/Windows/Resource/Exhaustion/Detector/Events">

          <SystemInfo>

            <SystemCommitLimit>57708621824</SystemCommitLimit>

            <SystemCommitCharge>57653514240</SystemCommitCharge>

            <ProcessCommitCharge>46560661504</ProcessCommitCharge>

            <PagedPoolUsage>437309440</PagedPoolUsage>

            <PhysicalMemorySize>25760481280</PhysicalMemorySize>

            <PhysicalMemoryUsage>22731579392</PhysicalMemoryUsage>

            <NonPagedPoolUsage>517689344</NonPagedPoolUsage>

            <Processes>154</Processes>

          </SystemInfo>

          <ProcessInfo>

            <Process_1>

              <Name>Adobe Premiere Pro.exe</Name>

              <ID>10092</ID>

              <CreationTime>2017-12-04T15:56:00.775351400Z</CreationTime>

              <CommitCharge>22942978048</CommitCharge>

              <HandleCount>54626</HandleCount>

              <Version>12.0.0.224</Version>

              <TypeInfo>201</TypeInfo>

            </Process_1>

            <Process_2>

              <Name>Adobe Media Encoder.exe</Name>

              <ID>4704</ID>

              <CreationTime>2017-12-04T16:48:38.389033700Z</CreationTime>

              <CommitCharge>18851459072</CommitCharge>

              <HandleCount>43108</HandleCount>

              <Version>12.0.0.202</Version>

              <TypeInfo>210</TypeInfo>

            </Process_2>

            <Process_3>

              <Name>TeamProjectsLocalHub.exe</Name>

              <ID>10832</ID>

              <CreationTime>2017-12-04T15:56:05.442211300Z</CreationTime>

              <CommitCharge>863481856</CommitCharge>

              <HandleCount>25685</HandleCount>

              <Version>2.0.1.0</Version>

              <TypeInfo>219</TypeInfo>

            </Process_3>

            <Process_4>

              <Name>

              </Name>

              <ID>0</ID>

              <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

              <CommitCharge>0</CommitCharge>

              <HandleCount>0</HandleCount>

              <Version>0.0.0.0</Version>

              <TypeInfo>0</TypeInfo>

            </Process_4>

            <Process_5>

              <Name>

              </Name>

              <ID>0</ID>

              <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

              <CommitCharge>0</CommitCharge>

              <HandleCount>0</HandleCount>

              <Version>0.0.0.0</Version>

              <TypeInfo>0</TypeInfo>

            </Process_5>

            <Process_6>

              <Name>

              </Name>

              <ID>0</ID>

              <CreationTime>1601-01-01T00:00:00.000000000Z</CreationTime>

              <CommitCharge>0</CommitCharge>

              <HandleCount>0</HandleCount>

              <Version>0.0.0.0</Version>

              <TypeInfo>0</TypeInfo>

            </Process_6>

          </ProcessInfo>

          <PagedPoolInfo>

            <Tag_1>

              <Name>MmSt</Name>

              <PoolUsed>108031216</PoolUsed>

            </Tag_1>

            <Tag_2>

              <Name>CM31</Name>

              <PoolUsed>87756800</PoolUsed>

            </Tag_2>

            <Tag_3>

              <Name>Sect</Name>

              <PoolUsed>16340048</PoolUsed>

            </Tag_3>

          </PagedPoolInfo>

          <NonPagedPoolInfo>

            <Tag_1>

              <Name>MmSc</Name>

              <PoolUsed>134217856</PoolUsed>

            </Tag_1>

            <Tag_2>

              <Name>smNp</Name>

              <PoolUsed>92061696</PoolUsed>

            </Tag_2>

            <Tag_3>

              <Name>smCB</Name>

              <PoolUsed>58417152</PoolUsed>

            </Tag_3>

          </NonPagedPoolInfo>

          <ExhaustionEventInfo>

            <Time>2017-12-04T18:12:30.597794900Z</Time>

          </ExhaustionEventInfo>

        </MemoryExhaustionInfo>

      </UserData>

    </Event>

    APPLICATION EVENT ERROR:

    Log Name:      Application

    Source:        Application Error

    Date:          12/4/2017 1:16:13 PM

    Event ID:      1000

    Task Category: (100)

    Level:         Error

    Keywords:      Classic

    User:          N/A

    Computer:      DESKTOP-SSS6GI8

    Description:

    Faulting application name: Adobe Premiere Pro.exe, version: 12.0.0.224, time stamp: 0x59d4c660

    Faulting module name: HandlerTimecode.dll, version: 12.0.0.224, time stamp: 0x59d4c5d8

    Exception code: 0xc0000005

    Fault offset: 0x000000000000ac61

    Faulting process id: 0x276c

    Faulting application start time: 0x01d36d186196372a

    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2018\Adobe Premiere Pro.exe

    Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2018\HandlerTimecode.dll

    Report Id: b0df801d-f476-4747-bd48-3f6590985c05

    Faulting package full name:

    Faulting package-relative application ID:

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="Application Error" />

        <EventID Qualifiers="0">1000</EventID>

        <Level>2</Level>

        <Task>100</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2017-12-04T18:16:13.136564400Z" />

        <EventRecordID>1188</EventRecordID>

        <Channel>Application</Channel>

        <Computer>DESKTOP-SSS6GI8</Computer>

        <Security />

      </System>

      <EventData>

        <Data>Adobe Premiere Pro.exe</Data>

        <Data>12.0.0.224</Data>

        <Data>59d4c660</Data>

        <Data>HandlerTimecode.dll</Data>

        <Data>12.0.0.224</Data>

        <Data>59d4c5d8</Data>

        <Data>c0000005</Data>

        <Data>000000000000ac61</Data>

        <Data>276c</Data>

        <Data>01d36d186196372a</Data>

        <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC 2018\Adobe Premiere Pro.exe</Data>

        <Data>C:\Program Files\Adobe\Adobe Premiere Pro CC 2018\HandlerTimecode.dll</Data>

        <Data>b0df801d-f476-4747-bd48-3f6590985c05</Data>

        <Data>

        </Data>

        <Data>

        </Data>

      </EventData>

    </Event>

    E
    excited_Genie16B8
    Legend
    December 11, 2017

    OK, so there's three things there you can take a look at.  The first is that you're running out of Virtual Memory.  Have you changed the default for that in any way?  I recommend letting Windows handle it.

    The second is the Faulting Module - Timecode.  Are you using that effect in any way?  If so, try removing it.

    The third thing to look at is the Exception Code: 0xc0000005.  A little research shows this can be triggered by memory issues, which goes back to the first item.

    C
    CtheProducerJBOAutor
    Participating Frequently
    December 11, 2017

    I just changed the settings to "performance" on the windows side of things. I will look more into the Virtual Memory and see what might of been changed there but did not make any known changes myself. Hopefully that can help the third error as well.

    For the timecode, I use the TC window under the Program Monitor. I do not have the effect on any clips though. I will close the TC window for now and see if this helps.

    Thanks for the feedback Jim, I will post up what I find with the virtual memory and no TC window being used.

    C
    CtheProducerJBOAutor
    Participating Frequently
    December 4, 2017

    Jim, what is the best way to get the logs out of the event manager to you? I have just had a crash due to low memory on Premiere while attempting to create proxies on my current CC18 Teams project, happened while I went to lunch. Media Encoder is actually still up and cranking, but Premiere closed down. Sense then I have just been doing admin stuff in Google Chrome until Media Encoder is done and I can restart.

    I exported the application logs and System Logs, and could send them over. Also a couple screen shots of the errors windows throws. Again, this happened when I went on lunch, was plugging along fine till then. I came back and had the memory error code showing.

    Thanks!

    C
    CtheProducerJBOAutor
    Participating Frequently
    December 4, 2017

    Jim, I have yet to capture a shot of the task manager when the random crash happens. If it happens today while editing, I am going to grab some shots of it.

    E
    excited_Genie16B8
    Legend
    December 4, 2017

    Not Task Manager, Windows Event Viewer.  You can look at those crash logs any time.  Specifically I'm looking for the Exception Code and the Faulting Process.

    C
    CtheProducerJBOAutor
    Participating Frequently
    December 4, 2017

    It is Sony A7s AVCHD footage. It also has GoPro Ciniform content in it. About 1TB of content in total, 7 Days of shooting with a A/B cam setup.

    GoPros are used as POV action cams, and there is about 10 in use per-day.

    Do I need to transcode it all and relink to see? I am using a Presonus Scarlet Solo with the AISO driver, should I switch something there?

    Also, I do have the 4-drive setup as recommended in the white pages. Media Cache is being sent to its own 10,000RPM drive. Content is on a G Speed sS Pro with SAS connection though PCI and in RAID 5 format. SSD Program drive. Then another 7200RPM drive for export just to note.

    I was also wandering, would working with Proxies get around ProRes transcode?

    Thanks a million for all the input Kevin.

    E
    excited_Genie16B8
    Legend
    December 2, 2017

    What does Windows Event Viewer say about the crashes?

    Kevin J. Monahan Jr.
    Community Manager
    Kevin J. Monahan Jr.Community Manager
    Community Manager
    December 1, 2017

    CTheProducer,

    Branching as you are on a Windows machine and the OP is on Mac. Often the issues are different, so hopefully this will help you find a solution faster.

    I'm guessing that your AVCHD footage is causing the issue because of the .ac3 files require Dolby decoding. Those decoders are now supposed to be part of Windows 10. I think we need to make a determination as to why these files are giving you trouble since the decoders are supposed to be installed natively with the OS.

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Allgemeine NutzungsbedingungenAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices