Kernel Panic when waking from sleep :(

Discussion in 'Mac Basics and Help' started by n8236, Apr 12, 2007.

  1. n8236 macrumors 65816

    Joined:
    Mar 1, 2006
    #1
    Didn't install any strange software and no hardware changes lately.

    Recently (and still) I have been experiencing Kernel Panics when my computer comes out of sleep and randomly. I have fixed permissions through various methods, but the crashes are still happening.

    Does anyone have any ideas? Here's my log:

    panic(cpu 1 caller 0x001A429B): Unresolved kernel trap (CPU 1, Type 5=bounds check), registers:
    CR0: 0x80010033, CR2: 0x35cff000, CR3: 0x00e1b000, CR4: 0x000006e0
    EAX: 0x03b52e40, EBX: 0x00000020, ECX: 0x004ae958, EDX: 0x03a30160
    CR2: 0x2526bc08, EBP: 0x2526bc48, ESI: 0x00000004, EDI: 0x03adadc1
    EFL: 0x00010202, EIP: 0x03a30195, CS: 0x00000008, DS: 0x039d0010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x2526ba78 : 0x128d08 (0x3cb134 0x2526ba9c 0x131de5 0x0)
    0x2526bab8 : 0x1a429b (0x3d0e4c 0x1 0x5 0x3d05d8)
    0x2526bbc8 : 0x19ada4 (0x2526bbd4 0xe 0x25260048 0x120010)
    0x2526bc48 : 0x3c0e94 (0x3adadc0 0x39d9b40 0x0 0x3c10ef)
    0x2526bc68 : 0x3c188a (0x39d9b40 0x0 0x0 0x0)
    0x2526bca8 : 0x3c18f7 (0x39d9b40 0x3d88900 0x70b3340 0x1628d8)
    0x2526bce8 : 0x38663c (0x39bc980 0x0 0x2526bd28 0x3c1002)
    0x2526bd08 : 0x389e5b (0x39a2380 0x3cd45c0 0x0 0x39a2380)
    0x2526bd28 : 0x3b1448 (0x39a2380 0x3cd45c0 0x2526bd58 0x3bdfd9)
    0x2526bd78 : 0x188511 (0x39a2380 0x5f7bfb4 0x5f7bfc8 0x11cc32)
    0x2526bdb8 : 0x12b4c3 (0x5f7bab4 0x5f7bf98 0x0 0x0)
    0x2526bdf8 : 0x124b17 (0x5f7ba00 0x0 0x18 0x2526bedc)
    0x2526bf08 : 0x195a42 (0x2526bf44 0x0 0x0 0x0)
    0x2526bfc8 : 0x19b21e (0x4093148 0x0 0x19e0b5 0x40d68b0) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xb011e3c8

    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: MacBookPro1,1, BootROM MBP11.0055.B08, 2 processors, Intel Core Duo, 2 GHz, 2 GB
    Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
    Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
    Memory Module: BANK 1/DIMM1, 1 GB, 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
    Network Service: Parallels NAT, Ethernet, en3
    Network Service: Parallels Host-Guest, Ethernet, en2
    Serial ATA Device: ST9100824AS, 93.16 GB
    Parallel ATA Device: MATSHITADVD-R UJ-857
    USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
    USB Device: Maxtor 3200, Maxtor Corporation, Up to 480 Mb/sec, 500 mA
    USB Device: IR Receiver, Apple Computer, Inc., Up to 12 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: USB Receiver, Logitech, Up to 1.5 Mb/sec, 500 mA


    If I reinstall OSX, will my info still be there along w/ my Boot Camp?
     
  2. trainguy77 macrumors 68040

    Joined:
    Nov 13, 2003
    #2
    Have you added any third party RAM? Any other USB or firewire 3rd party items?
     
  3. dhc macrumors regular

    Joined:
    Jan 10, 2006
    Location:
    UK
    #3
    No advice I'm afraid, and not meaning to hijack your thread, but my 1.83 CD MBP has very recently started intermittently exhibiting the same behaviour. Log:

    Sat Apr 14 22:50:14 2007
    panic(cpu 1 caller 0x001A429B): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00df6000, CR4: 0x000006e0
    EAX: 0x03424540, EBX: 0x027c07c0, ECX: 0x033dafe4, EDX: 0x0278c800
    CR2: 0x00000000, EBP: 0x13f738f8, ESI: 0x02ad5c40, EDI: 0x003997a4
    EFL: 0x00010246, EIP: 0x00000000, CS: 0x00000008, DS: 0x004b0010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x13f73728 : 0x128d08 (0x3cb134 0x13f7374c 0x131de5 0x0)
    0x13f73768 : 0x1a429b (0x3d0e4c 0x1 0xe 0x3d0670)
    0x13f73878 : 0x19ada4 (0x13f73884 0xe 0x4b0048 0x130010)
    0x13f738f8 : 0x39ad7c (0x278c800 0x1 0x2ad5c40 0x0)
    0x13f73938 : 0x39aa7d (0x27c07c0 0x3997a4 0x1 0x2ad5c40)
    0x13f73968 : 0x39924e (0x27c07c0 0x1 0x2ad5c40 0x0)
    0x13f73998 : 0x2a4c7665 (0x278c800 0x2ad5c40 0x13f739c8 0x133bdeee)
    0x13f739b8 : 0x2a4c6be5 (0x2c4b400 0x3 0x2c92248 0x390ba9)
    0x13f739d8 : 0x2a4c3b32 (0x2c4b400 0x297 0x13f73a38 0x2c4b400)
    0x13f739f8 : 0x390f6f (0x2c4b400 0x0 0x2c4b400 0x2c4b400)
    0x13f73a28 : 0x393d98 (0x2c4b400 0x0 0x13f73a58 0x393e2c)
    0x13f73a58 : 0x392db1 (0x2c4b400 0x1 0x0 0x0)
    0x13f73a98 : 0x392e5a (0x2c4b400 0x0 0x31fbe80 0x3bd3b6)
    0x13f73ac8 : 0x3930c7 (0x27c3e00 0x31fbe80 0x1 0x0)
    0x13f73b18 : 0x393e2c (0x27c3e00 0x1 0x13f73b58 0x0)
    0x13f73b38 : 0x392db1 (0x27c3e00 0x8 0x0 0x0) Backtrace continues...
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.driver.IOBluetoothHIDDriver(1.7.2b2)@0x2a4c1000
    dependency: com.apple.iokit.IOBluetoothFamily(1.7.14f14)@0x6f7000
    dependency: com.apple.iokit.IOHIDFamily(1.4.10)@0x54c000

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



    I added a stick of crucial RAM about 8 months ago and am only now seeing problems- can RAM go bad?

    Can someone who is fluent in the 'Language of the Logs' offer any advice to the OP and I?
     
  4. oticon6 macrumors regular

    Joined:
    Feb 10, 2008
    #5
    I can't relate to the first guy in this thread, but dhc's message is the same message I get. Kernel panic, when waking from sleep, at random, suggesting Bluetooth driver is the cause. I noticed I've been leaving Bluetooth active lately, when prior I would always disable it. I'm going to leave Bluetooth off and see if it keeps happening over the next few days.

    Considering it states the affecting driver in the panic, I'm assuming this'll be fixed in 10.5.2.
     

Share This Page