macbook Coreduo ram slot defect? Kernel panics...

Discussion in 'MacBook Pro' started by PDE, Apr 21, 2007.

  1. PDE macrumors 68020

    Joined:
    Nov 16, 2005
    #1
    I have never seen a macbook/MBP that doesn't have some defect or developed some defect over time. I have lost all confidence in Apple over the past year and a half - I need to make a spreadsheet to figure out how many macbooks and macbook pros I've had. They are really too many to count an it's not just bad luck. QC at Apple does simply not exist.


    Anyway enough of my daily rant. My girlfriend's macbook stopped working last night while we were watching a DVD. Before I rush off with it to the applestore, I thought I'd ask around here. Here are the details:

    Symptoms:

    While watching a DVD, the DVD stalled first, followed by a kernel panic. I restarted, it booted up as normal. Started the DVD again and within a few seconds, kernel panic. Rebooted, started a browser, kernel panic.

    So, I reset the PMU and PRAM and rebooted. watched a few minutes of the DVD and then kernel panic again. Rebooted, but it wouldn't reboot, just a white light not flashing and some humming sound. Kept holding and pressing the power button and eventually it started up with no backlight. Held down the power button again,it rebooted as normal. I inserted the Apple dvd and ran the disk repair and repair permissions function. It booted quite slowly, but without a problem. Rebooted and tried opening a browser = kernel panic within a few seconds.


    So I removed one ram module, rebooted and everything was fine. I put in another ram module that I know is ok and still kept getting kernel panics.

    It seems like this is a faulty ram slot, but what do I know? It's worked fine since October, except for the original display which was replaced and then a sporadic, daily backlight flicker...

    Any ideas if there's anything I've overlooked software wise? I hate giving Apple the computer to mess around with because they often mess up other things in the process of repair....


    Thanks!
     
  2. EricNau Moderator emeritus

    EricNau

    Joined:
    Apr 27, 2005
    Location:
    San Francisco, CA
    #2
    Is that the original RAM, or have you installed your own?
     
  3. PDE thread starter macrumors 68020

    Joined:
    Nov 16, 2005
    #3
    Both modules were from other macbooks and were the original APPLE (Samsung and Hynix) ram.
     
  4. Hockeypuck macrumors regular

    Joined:
    Sep 29, 2006
    #4
    We have seen a few of these bad RAM slots at the service place I work at. Definatly could be your problem. If you send it to apple they'll probably replace the logic board.
     
  5. PDE thread starter macrumors 68020

    Joined:
    Nov 16, 2005
    #5
    Thanks for the reply - good to know. Can anybody help me decipher this kernel panic log?

    panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x1ef42828, CR3: 0x00d6e000, CR4: 0x000006e0
    EAX: 0x003f0202, EBX: 0x0faf3cd0, ECX: 0x1ef42828, EDX: 0x1ef42828
    CR2: 0x1ef42828, EBP: 0x0faf3c88, ESI: 0x02a20600, EDI: 0x00000000
    EFL: 0x00010202, EIP: 0x005dca9b, CS: 0x00000008, DS: 0x0faf0010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0xfaf38b8 : 0x128d08 (0x3cb134 0xfaf38dc 0x131de5 0x0)
    0xfaf38f8 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
    0xfaf3a08 : 0x19ada4 (0xfaf3a18 0x53 0xe 0x48)
    0xfaf3c88 : 0x5c9762 (0x2a20600 0xfaf3cd0 0xfaf3cb8 0x0)
    0xfaf3cf8 : 0x3b04ad (0x2a20600 0x1 0xfaf3d2c 0xfaf3d28)
    0xfaf3d38 : 0x3b3969 (0x2a20600 0x1 0x2175440 0x1)
    0xfaf3d68 : 0x189db1 (0x2a20600 0x1 0x2175440 0x2b157c0)
    0xfaf3db8 : 0x12b4c3 (0x2b1578c 0x283fda0 0xfaf3df8 0x11e042)
    0xfaf3df8 : 0x124b17 (0x2b15700 0x2142340 0x13d25dc 0x0)
    0xfaf3f08 : 0x195a42 (0xfaf3f44 0x0 0x0 0x0)
    0xfaf3fc8 : 0x19b21e (0x2186c94 0x1 0x19e0b5 0x272d160) Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0xfaf35b8 : 0x128c61 (0x3cb0d8 0x246 0xfaf36a8 0x17a104)
    0xfaf35f8 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
    0xfaf3708 : 0x19ada4 (0xfaf3718 0x1d33fd0 0xe 0x2180048)
    0xfaf3868 : 0x1a9609 (0xfaf38b8 0x10 0xfaf38b8 0x131f90)
    0xfaf38b8 : 0x128d08 (0x3cb134 0xfaf38dc 0x131de5 0x0)
    0xfaf38f8 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
    0xfaf3a08 : 0x19ada4 (0xfaf3a18 0x53 0xe 0x48)
    0xfaf3c88 : 0x5c9762 (0x2a20600 0xfaf3cd0 0xfaf3cb8 0x0)
    0xfaf3cf8 : 0x3b04ad (0x2a20600 0x1 0xfaf3d2c 0xfaf3d28)
    0xfaf3d38 : 0x3b3969 (0x2a20600 0x1 0x2175440 0x1)
    0xfaf3d68 : 0x189db1 (0x2a20600 0x1 0x2175440 0x2b157c0)
    0xfaf3db8 : 0x12b4c3 (0x2b1578c 0x283fda0 0xfaf3df8 0x11e042)
    0xfaf3df8 : 0x124b17 (0x2b15700 0x2142340 0x13d25dc 0x0)
    0xfaf3f08 : 0x195a42 (0xfaf3f44 0x0 0x0 0x0)
    0xfaf3fc8 : 0x19b21e (0x2186c94 0x1 0x19e0b5 0x272d160) Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0xfaf32b8 : 0x128c61 (0x3cb0d8 0x0 0x1000 0x0)
    0xfaf32f8 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
    0xfaf3408 : 0x19ada4 (0xfaf3418 0x1d33fd0 0xe 0x2180048)
    0xfaf3568 : 0x1a9609 (0xfaf35b8 0x10 0x0 0x199ef1)
    0xfaf35b8 : 0x128c61 (0x3cb0d8 0x246 0xfaf36a8 0x17a104)
    0xfaf35f8 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
    0xfaf3708 : 0x19ada4 (0xfaf3718 0x1d33fd0 0xe 0x2180048)
    0xfaf3868 : 0x1a9609 (0xfaf38b8 0x10 0xfaf38b8 0x131f90)
    0xfaf38b8 : 0x128d08 (0x3cb134 0xfaf38dc 0x131de5 0x0)
    0xfaf38f8 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
    0xfaf3a08 : 0x19ada4 (0xfaf3a18 0x53 0xe 0x48)
    0xfaf3c88 : 0x5c9762 (0x2a20600 0xfaf3cd0 0xfaf3cb8 0x0)
    0xfaf3cf8 : 0x3b04ad (0x2a20600 0x1 0xfaf3d2c 0xfaf3d28)
    0xfaf3d38 : 0x3b3969 (0x2a20600 0x1 0x2175440 0x1)
    0xfaf3d68 : 0x189db1 (0x2a20600 0x1 0x2175440 0x2b157c0)
    0xfaf3db8 : 0x12b4c3 (0x2b1578c 0x283fda0 0xfaf3df8 0x11e042) Backtrace continues...
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.AppleIntelGMA950(4.5.2)@0x5bc000
    dependency: com.apple.iokit.IOPCIFamily(2.2)@0x582000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.5)@0x592000
    dependency: com.apple.iokit.IONDRVSupport(1.4.5)@0x5ad000

    Kernel version:
    Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

    Model: MacBook1,1, BootROM MB11.0061.B03, 2 processors, Intel Core Duo, 2 GHz, 768 MB
    Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
    Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz
    Memory Module: BANK 1/DIMM1, 256 MB, DDR2 SDRAM, 667 MHz
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 0.1.31.1
    Bluetooth: Version 1.7.14f14, 2 service, 0 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: ST96812AS, 55.89 GB
    Parallel ATA Device: MATSHITADVD-R UJ-857, 7.3 GB
    USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
    USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
    USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
    USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
     
  6. PDE thread starter macrumors 68020

    Joined:
    Nov 16, 2005
    #6
    I put in a 256mb ram stick so that it's paired with the other 256mb and it hasn't caused a kernel panic for the past 20 mins. The computer has been running fine on 768mb (512mb +256mb) since October so to me it doesn't make sense that it would suddenly cause a kernel panic - or does it? I've run unmatched pairs on MBPs and macbooks without any problem before....

    Could this have anything to do with it or it just a coincidence?
     
  7. TraceyS/FL macrumors 68040

    Joined:
    Jan 11, 2007
    Location:
    North Central Florida
    #7
    I had RAM die at about a year old. Computer just started doing the strangest things.... i narrowed it down to the right SIMM (ok, they will always be SIMM's! LOL!!), but it took some work. Mine would only die when it reached a certain part out on the chip - and i was trying to install OSX, so it was kinda hard to force it.

    But I was positive it WASN'T the RAM too - shocked me based on the problems i was having....

    And even Apple RAM will die. But the slot thing makes a lot of sense too - unless like what happened with me it wasn't until you got "out there" that it happens.
     
  8. PDE thread starter macrumors 68020

    Joined:
    Nov 16, 2005
    #8
    The only thing is that I tried another ram module that I know was good and that did the same thing. It seems that it must be a) ram slot or b) the ram wasn't seated properly (even though I thought it was).

    I don't know if the kernel panic log will shed some light on the problem? Hope somebody who knows this stuff comes by...
     
  9. PDE thread starter macrumors 68020

    Joined:
    Nov 16, 2005
    #9
    Strangely, things now seem to be working normally even with the 512mb and 256mb sticks installed. Could it have been that the ram was not pushed in properly? Would that cause the above problems?

    The screen does flicker after sleep like so many others - could the kernel panics be related to that?

    It's strange that it would stop acting up when the situation was so bad before. Anybody able to interpret anything from the kernel panic log?
     
  10. gnasher729 macrumors P6

    gnasher729

    Joined:
    Nov 25, 2005
    #10
    It is well known that RAM modules that are not pushed in properly cause problems. And it is also well known that RAM modules are hard to push in properly in a MacBook.

    If your Mac doesn't work right, and removing and reinserting RAM modules fixes it, then it isn't Apple's fault, but the fault of whoever didn't manage to put in the RAM properly. Could you ask the person responsible to not try to modify any Macs in the future?
     
  11. PDE thread starter macrumors 68020

    Joined:
    Nov 16, 2005
    #11
    Well, I've had quite a few macbooks and putting in the ram is not something I've had problems with. I know that you need to push them in with a lot of force and I did that. At least I thought I did. The macbook worked without problems for six months so that's why I'm puzzled. Also, when I did replace one ram stick the other day, it continued to panic. Then yesterday I put in a paired ram module (2X 256mb) and it worked. I then tried again to put in the 512mb ram stick together with the other 256mb and it worked too so I can't explain what was going on.

    I'm not blaming Apple. However, I'm very inclined to believe that Apple's computers are defective given Apple's record (and my personal experience with 10+ macbooks and MBPs ) w since the intel switch. And, as I mentioned, there is also the screen flickering problem that happens after sleep. As you can see, I came here before I went to Apple, hoping that somebody can help decipher the above log so that I can troubleshoot and fix the problem. Putting in a ram module is hardly a modification of the macbook!
     

Share This Page