Macbook crash after ram upgrade.

Discussion in 'MacBook' started by richj86, Jul 28, 2009.

  1. richj86 macrumors newbie

    Joined:
    Jul 28, 2009
    #1
    Hi.
    I installed 2x2gb crucial ram in my macbook 2.1.

    It all installed fine, but then after about 3 hours use, the system froze, the screen went all pixelated and a loud static screech came out the speakers.
    Its done it 3-4 times in 48 hours, so im guessing its the ram.
    It also gets hot just where the ram would be (but not super mega temps according to the program readout)

    Im getting the ram replaced under warranty, but if it does happen again, does anybody know what to do.

    Somebody on the crucial forum suggested adjusting the controller and voltage, but i dont think thats it? Can the 2.1's handel 4gb?

    Specs below

    Model Name: MacBook
    Model Identifier: MacBook4,1
    Processor Name: Intel Core 2 Duo
    Processor Speed: 2.1 GHz
    Number Of Processors: 1
    Total Number Of Cores: 2
    L2 Cache: 3 MB
    Memory: 4 GB
    Bus Speed: 800 MHz


    Size: 2 GB
    Type: DDR2 SDRAM
    Speed: 667 MHz
    Status: OK
    Manufacturer: 0x2C00000000000000
    Part Number: 0x3136485446323536363448592D3636374731
    Serial Number: 0xE612E6F3

    BANK 1/DIMM1:

    Size: 2 GB
    Type: DDR2 SDRAM
    Speed: 667 MHz
    Status: OK
    Manufacturer: 0x2C00000000000000
    Part Number: 0x3136485446323536363448592D3636374731
    Serial Number: 0xE612E6E5

    Any help greeted :)

    Thanks
    Rich
     
  2. eawmp1 macrumors 601

    eawmp1

    Joined:
    Feb 19, 2008
    Location:
    FL
    #2
    Put the original RAM in, or the replacement sticks. If it's all better you got bad sticks (sounds like RAM).

    Do the usual - Run Disk Utility/repair disk and permissions
    Zap PRAM

    If still with problem, the time to get it looked at.
     
  3. richj86 thread starter macrumors newbie

    Joined:
    Jul 28, 2009
    #3
    Yeah i just chucked the original 2x512's in now.
    Hopefully it was just a bad stick, but memtest did a scan and didnt report anything.
    Might have just been a pre-packed static thing.
     

Share This Page