MP 2.8 Crash, memory related

Discussion in 'Mac Pro' started by ZMacintosh, Feb 14, 2009.

  1. ZMacintosh macrumors 6502a

    ZMacintosh

    Joined:
    Nov 13, 2008
    #1
    I recently had one crash with my 2.8 MP today, and twice today where the memory lights on the risers were out and only indicating 2GB ofmemory.

    i have 6gb of memory in my machine, 2x1gb from apple and 2x2gb from OWC
    (**sorry corrected my mistake, 2x2gb not 2x4)

    i had spare memory i know wi installed the memory over 6months ago with no issues, wen through all the memory tests and hardware tests for a few days when i first installed it,
    today i recently took out all my components to do some monthly cleaning since there was built up dust and thats when i started getting all these crashes, i reseated the memory and the riser cards (the 2x2 is on riser A and the 2x1 is on riser B as it has been)

    and ever i replaced the drives and memory thats when i started getting the memory not being recognized.
    i know there is nothing wrong with the memorya s i ran some thorough tests on it today aswell, is there a way to determine what caused it to randomly crash?



    thanks!
     
  2. UltraNEO* macrumors 601

    UltraNEO*

    Joined:
    Jun 16, 2007
    Location:
    近畿日本
    #2
    Er... Usually, if it's a memory fault.
    The lights one the risers should light up.
     
  3. JG271 macrumors 6502a

    JG271

    Joined:
    Dec 17, 2007
    Location:
    UK
    #3
    Its just incorrectly re-seated ram - the ram wasn't connecting right to the board... which is why it crashed. If it isn't that then it could be a faulty module or two, If not then you MAY have a faulty ram slot or even riser. But most likely the first one.
     
  4. ZMacintosh thread starter macrumors 6502a

    ZMacintosh

    Joined:
    Nov 13, 2008
    #4
    thank you all for the responses.


    yeah im running some over night tests again with Rember, did a few AHT passes just for pre-test.

    restarted into Windows and OSX and it all showed up fine, ran some stress test with some apps.

    I think it had to do with reseating, probably wasnt pushed down all the way.
    it happened before prior with my first gen macpro aswell randomly.


    hm, ill keep a look out, since this is the first time ive ever encountered an issue with this machine had it for almost a year =)


    i appreciate the help!
     

Share This Page