Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Memory could not be read… Crash, crash!

  • Memory could not be read… Crash, crash!

    Posted by Enginn Heima on September 19, 2008 at 5:20 pm

    I’ve got a problem.

    First of all, I’ve got a large project in 720p. I’ve got CS3 and it keeps on crashing. And everytime it crashes it takes up to 20 minutes just to reload the project.

    The error message I get most of the time is the famous “Adobe Premiere has encountered a serious error and needs to shut down”

    Sometimes in those cases the application tries to save the project but most of the time it just shut down.

    Then another error messages that shows up on crash, but is more rare is: “The intruction at “0x00C90718” referenced memory at “000001ac”. The memory could not be “read”. Click on OK to terminate the program.”

    I’m going mad, mad, mad. I have ten days to finish this thing and Premiere keeps on doing this.

    Now, the specs are

    – Intel dual core 3ghz
    – 4 gb ram
    – winxp sp2
    – cs3 v.3.2
    – geforce 8800GT with dual display
    – dedicated media drive configured RAID0
    – another non-RAID dedicated for Media Cache and Previews.

    When does the problem occur?

    Now, there is another problem. I can’t seem to find out a pattern. It is mostly when I’m going from one window to another. Like say, from the timeline window to the project window. But this is really not always the case.

    What else programs am I running?
    I’ve tried to switch of literally EVERYTHING while running Premiere, but the problem remains.

    Another thing that I’ve tried to fiddle with is the virtual memory in windows, from custom to system managed size. No success.

    I’ve done tons of internet research trying to figure this out, but I’m out of breath.

    If anyone can help, it would be more than appreciated…

    Best regards.

    Jonathan Simard replied 16 years, 3 months ago 4 Members · 6 Replies
  • 6 Replies
  • Eddie Lotter

    September 19, 2008 at 6:41 pm

    It could be a bad codec or a problematic video driver.

    Here are some troubleshooting tips.

    Cheers
    Eddie

  • Mike Velte

    September 20, 2008 at 10:47 am

    What size is your Project file (.prproj)?

    Could be bad memory. try trying removing half the memory and retry, then try the other half.

  • Enginn Heima

    September 20, 2008 at 11:26 am

    The project file is 57mb.

    By memory, do you mean the RAM?

  • Mike Velte

    September 21, 2008 at 10:40 am

    Yes, RAM= Random Access Memory. A process of elimination could reveal a bad stick.

  • Enginn Heima

    September 21, 2008 at 6:09 pm

    I did like you proposed Mike, removed two of the memory sticks and surprisingly no crash, until after an hour of editing. Replaced the memory sticks with the other two and I was even able to go for one and a half hour without a crash. Don’t think any of the sticks are bad though, but it seems like premiere “likes” it better with only 2gb of RAM rather than 4gb.

    Since anyway Windows only sees the 4gb as 3.25 (under winxp pro 32bit) I will stick with only the 2gb since it seems to run more smoothly with Premiere.

    But the problem remains, even though it’s a bit better… Don’t know what I can do more. I was actually thinking that my problem could be related to the graphic card. I have the geforce 8800GT, was wondering if there is any possible tweaking to do with the graphic card settings. Anyone?

    Greetings.

  • Jonathan Simard

    February 21, 2010 at 5:17 am

    I have the same problem. I have a quad core but my video card is a nvidia geforce 8800 GTS 512. Premiere crashes with a blue screen of death and computer reboots. It never done that until I pluged a second monitor. I think that Premiere hates dual display (but can’t figure out why). Now my raid has degraded and it’s repairing, so I can’t try to use it with just one monitor. I’ll try to use only one display for premiere but let the other one active, and if it doesn’t owrk, I’ll remove the second display.

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy