Macs are crashing, need help

Discussion in 'macOS' started by luminol74, Oct 6, 2008.

  1. luminol74 macrumors member

    Joined:
    Apr 17, 2008
    #1
    HI,

    My macs are suddenly crashing every now and then, maybe once a day or once every two days. I have a MacBook C2D and an iMac aluminium both loaded almost identically in terms of software. I need to sort this out prompto because I need to use the MacBook live this Sunday and I can't have a random crash. Here's the crash report:

    Mon Oct 6 10:03:08 2008
    panic(cpu 0 caller 0x001A8CEC): Kernel trap at 0x5558c333, type 14=page fault, registers:
    CR0: 0x8001003b, CR2: 0x00000004, CR3: 0x00d00000, CR4: 0x00000660
    EAX: 0x00000000, EBX: 0x34fd7c74, ECX: 0x00000000, EDX: 0x0000010c
    CR2: 0x00000004, EBP: 0x34fd7d88, ESI: 0x34fd7eec, EDI: 0x00000000
    EFL: 0x00010206, EIP: 0x5558c333, CS: 0x00000008, DS: 0x658b0010
    Error code: 0x00000000

    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x34fd7a78 : 0x12b0fa (0x459234 0x34fd7aac 0x133243 0x0)
    0x34fd7ac8 : 0x1a8cec (0x4627a0 0x5558c333 0xe 0x461f50)
    0x34fd7ba8 : 0x19eed5 (0x34fd7bc0 0x1 0x34fd7d88 0x5558c333)
    0x34fd7bb8 : 0x5558c333 (0xe 0x55590048 0x10 0x10)
    0x34fd7d88 : 0x5555ee1a (0x34fd7eec 0x44fd924 0x0 0x0)
    0x34fd7f28 : 0x55564d9f (0x3fc9004 0x3ed0004 0x3fc9280 0x0)
    0x34fd7fc8 : 0x19eccc (0x3fc9004 0x0 0x1a20b5 0xb37e6b0)
    Backtrace terminated-invalid frame pointer 0
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.filesystems.afpfs(8.5.7)@0x55559000->0x5559dfff

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:
    9F33

    Kernel version:
    Darwin Kernel Version 9.5.0: Wed Sep 3 11:29:43 PDT 2008; root:xnu-1228.7.58~1/RELEASE_I386
    System model name: iMac7,1 (Mac-F42386C8)


    I'm running 10.5.5 and apart from that the most recent updates have been iTunes 8.01 (or whatever the latest is). The only other thing is I've recently put CS3 web premium (with latest updates) on both macs but I'm pretty certain that this behaviour started before I installed that (although can't really be positive on that). Please advise if you can or have seen similar.

    Thanks,

    Simon
     
  2. luminol74 thread starter macrumors member

    Joined:
    Apr 17, 2008
  3. pwn247 macrumors 6502

    pwn247

    Joined:
    Aug 30, 2008
    Location:
    West Virginia, USA
    #3
    Backup your personal files and do a complete format of the drive, and then reinstall Leopard. It seems to be a sort of system error.
     

Share This Page