Random kernel panics on SR MBP

Discussion in 'Mac Basics and Help' started by yhelothar, Jul 4, 2007.

  1. yhelothar macrumors newbie

    Joined:
    Jul 4, 2007
    #1
    In the past two days, I've had two kernel panics while not really doing anything. I think I was just browsing the internet when both happened. The more recent one happened right after I opened Camino. I am using Airport to connect to the internet, but the panic log doesn't blame the Airport drivers or anything like in the other topic. According to the log, the two panics seem unrelated as well.

    I haven't added any RAM or done anything really in terms of hardware.

    I've tried running Disk Utility and repairing the disk and permissions, but it found no errors. The Apple Hardware Test also found no errors.

    Anyway, the log is as follows:

    Code:
    Mon Jul  2 23:23:43 2007
    panic(cpu 0 caller 0x3CAFF808): ntfs_pagein error = 2
    Backtrace, Format - Frame : Return Address (4 potential args on stack) 
    0x25f6bb68 : 0x128d08 (0x3cc0a4 0x25f6bb8c 0x131de5 0x0) 
    0x25f6bba8 : 0x3caff808 (0x3cb00658 0x2 0x0 0x20000) 
    0x25f6bc28 : 0x1e5fc6 (0x25f6bc4c 0x1 0x1000 0x20000) 
    0x25f6bc88 : 0x374de6 (0x82d3f78 0x4d30cc0 0x0 0x20000) 
    0x25f6bcf8 : 0x186ecb (0x82d3f78 0x4d30cc0 0x0 0x20000) 
    0x25f6bd48 : 0x15ee4f (0x771c334 0x20000 0x0 0x1000) 
    0x25f6bdf8 : 0x16133c (0x5718c38 0x20000 0x0 0x1) 
    0x25f6bf48 : 0x1a4cc8 (0x5507790 0x3f6000 0x0 0x1) 
    0x25f6bfc8 : 0x19ade4 (0x54bc220 0x0 0x10 0x0) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfffd608
          Kernel loadable modules in backtrace (with dependencies):
             com.apple.filesystems.ntfs(1.2.1)@0x3caf9000
    
    Kernel version:
    Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
    
    
    *********
    
    Wed Jul  4 00:35:35 2007
    panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x80010033, CR2: 0x2570dee4, CR3: 0x0134f000, CR4: 0x000006e0
    EAX: 0x2570dee0, EBX: 0x05aead68, ECX: 0x072e747c, EDX: 0x00000000
    CR2: 0x2570dee4, EBP: 0x2570bb18, ESI: 0x00000008, EDI: 0x2570bdb4
    EFL: 0x00010246, EIP: 0x001c4f64, CS:  0x00000008, DS:  0x00000010
    
    Backtrace, Format - Frame : Return Address (4 potential args on stack) 
    0x2570b8c8 : 0x128d08 (0x3cc0a4 0x2570b8ec 0x131de5 0x0) 
    0x2570b908 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc) 
    0x2570ba18 : 0x19aeb4 (0x2570ba30 0x4d6150 0x2570ba3c 0x1) 
    0x2570bb18 : 0x1ccb59 (0x2570bdb4 0x2570dee0 0x457fad4 0x2570bf08) 
    0x2570bb88 : 0x1cd4af (0x2570bdb4 0x100 0x2570bdd4 0x0) 
    0x2570bc38 : 0x1d91d5 (0x2570bdb4 0x297 0x2570bc68 0x50b8714) 
    0x2570bd68 : 0x1d9636 (0xbfffed50 0x0 0x0 0x0) 
    0x2570bf28 : 0x1d96cb (0xbfffed50 0x0 0x0 0x0) 
    0x2570bf58 : 0x37ad83 (0x48275dc 0x6353408 0x635344c 0x0) 
    0x2570bfc8 : 0x19b28e (0x4c7b660 0x0 0x19e0b5 0x4c7b660) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbfffedc8
    
    Kernel version:
    Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386
    
    
    *********
    
    
    Does anyone know what these mean? What can I do to fix it? I've just passed the 14-day limit for returns, so that's out of the question.

    Thanks for the help.
     
  2. mad jew Moderator emeritus

    mad jew

    Joined:
    Apr 3, 2004
    Location:
    Adelaide, Australia
    #2
    So do you keep a shared folder or drive from a PC running continuously? The second one looks like RAM, but I could be wrong. If it is RAM, then Apple should be good about helping you out despite the thing being older than two weeks. :eek:
     
  3. yhelothar thread starter macrumors newbie

    Joined:
    Jul 4, 2007
    #3
    Er, no, but I've shared folders before without much trouble. I also was running Parallels for much of the day if that counts >_> (but I had closed it before the panic happened).

    Is there anything I can do about the RAM or should I just call Apple?

    Thanks.
     
  4. mad jew Moderator emeritus

    mad jew

    Joined:
    Apr 3, 2004
    Location:
    Adelaide, Australia
    #4
    If it is bad RAM, it'll need to be replaced and since you got it from Apple, it's probably best to go through them for the replacement. However, there's a chance it's merely badly seated in which case seating it properly may help. At this stage though, I'd wait for another panic, keeping a close eye on the logs and what you're doing at the time of the panic. Since the first and second panic seem unrelated at this stage, it might not be enough to warrant replacement RAM from Apple. :eek:
     

Share This Page