Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

bill4588

macrumors 6502a
Original poster
Feb 2, 2006
588
0
Kennesaw, GA
My MacBook was acting fine until a few weeks ago. About once or twice a week I get a random kernel panic, for what seems like no reason. Yes, I have speakers, a wireless mighty mouse, and a printer that I have been using since I got the computer, but I don't see why those peripherals would be causing a problem now. My computer never had a kernel panic before, so what could be the problem?

PS - I've repaired permissions.
 
Might have something to do with the RAM.

Try to run the hardware check off of the OS X install discs that came with your system. Hold down 'c' at the bootup to run the hardware check. That's the most likely thing to tell you if there's a problem.

If it doesn't show anything based on that, then I'd probably take it to the Apple Store and ask them about it.
 
What changed between last week and this week? And don't say "nothing". You installed absolutely nothing? Unplugged and replugged absolutely nothing?

What do your panic logs say? /Library/Logs/panic.log
 
Mon Apr 16 12:24:27 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x0002a424, CR3: 0x00d9b000, CR4: 0x000006e0
EAX: 0x0002a400, EBX: 0x05f60400, ECX: 0x0777fc80, EDX: 0x00000000
CR2: 0x0002a424, EBP: 0x25533ef8, ESI: 0x3cbeb684, EDI: 0x3cbe7f64
EFL: 0x00010206, EIP: 0x003bd3b3, CS: 0x00000008, DS: 0x00460010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25533ce8 : 0x128d08 (0x3cb134 0x25533d0c 0x131de5 0x0)
0x25533d28 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x25533e38 : 0x19ada4 (0x25533e50 0x0 0x25533e68 0x1a3010)
0x25533ef8 : 0x3cbe7f81 (0x5f60400 0x3cbeb684 0x25533f28 0x38073e)
0x25533f28 : 0x39c536 (0x5f60400 0x6cdeac0 0x8 0x2)
0x25533f78 : 0x13d7d9 (0x6cdeac0 0x705cab1 0x0 0x0)
0x25533fc8 : 0x19ac1c (0x0 0x0 0x10 0x4250840) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.IOBluetoothHIDDriver(1.7.2b2)@0x3cbe1000
dependency: com.apple.iokit.IOBluetoothFamily(1.7.14f14)@0x6d4000
dependency: com.apple.iokit.IOHIDFamily(1.4.10)@0x531000

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'm guessing it's the BT mighty mouse?
 
any chance anyone know what this is???

Sun Apr 15 10:19:31 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00d82000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x04506e00, ECX: 0x00000000, EDX: 0x008b9840
CR2: 0x00000000, EBP: 0x25223ed8, ESI: 0x04506e00, EDI: 0x008a9f4c
EFL: 0x00210206, EIP: 0x00666b78, CS: 0x00000008, DS: 0x03870010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25223cc8 : 0x128d08 (0x3cb134 0x25223cec 0x131de5 0x0)
0x25223d08 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x25223e18 : 0x19ada4 (0x25223e30 0x3fa9300 0x0 0x1)
0x25223ed8 : 0x8a923c (0x4506e00 0x8b85dc 0x37d0cc0 0x3)
0x25223f18 : 0x8aac8b (0x4506e00 0x200 0x0 0x22eec130)
0x25223f58 : 0x8a9f65 (0x4506e00 0x0 0x25223f78 0x19e23a)
0x25223f78 : 0x13d7d9 (0x4506e00 0x0 0x0 0xbfff75c0)
0x25223fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x3d9ff40) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOSCSIBlockCommandsDevice(1.5.3)@0x8a6000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.5.3)@0x664000
dependency: com.apple.iokit.IOStorageFamily(1.5.1)@0x5ee000

Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
 
they're about a month old. I would hope that the batteries would last longer than that.

Not with constant use. That's why I HATE BT devices. You spend so much on batteries, it'd pay for a damn wired mouse.

any chance anyone know what this is???

Something to do with an HD. Do you have a SCSI card? Do you have a SCSI HD? Do you have multiple HDs or an external HD?
 
Well I upgraded my internal one to a WD 120GB SATA HD a couple months back. And I have an external WD MyBook drive that's used only as a backup, so I only plug it in to update it.
 
Well I upgraded my internal one to a WD 120GB SATA HD a couple months back. And I have an external WD MyBook drive that's used only as a backup, so I only plug it in to update it.

Your problem is with a Bluetooth device.. whatever you've got. If it's only a mouse, then it's the mouse or the BT device on the Mac. Probably the mouse. Start by replacing the batteries.

The HD thing was for the other person who asked about his kernel panic.
 
any chance anyone know what this is???

Sun Apr 15 10:19:31 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00d82000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x04506e00, ECX: 0x00000000, EDX: 0x008b9840
CR2: 0x00000000, EBP: 0x25223ed8, ESI: 0x04506e00, EDI: 0x008a9f4c
EFL: 0x00210206, EIP: 0x00666b78, CS: 0x00000008, DS: 0x03870010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25223cc8 : 0x128d08 (0x3cb134 0x25223cec 0x131de5 0x0)
0x25223d08 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x25223e18 : 0x19ada4 (0x25223e30 0x3fa9300 0x0 0x1)
0x25223ed8 : 0x8a923c (0x4506e00 0x8b85dc 0x37d0cc0 0x3)
0x25223f18 : 0x8aac8b (0x4506e00 0x200 0x0 0x22eec130)
0x25223f58 : 0x8a9f65 (0x4506e00 0x0 0x25223f78 0x19e23a)
0x25223f78 : 0x13d7d9 (0x4506e00 0x0 0x0 0xbfff75c0)
0x25223fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x3d9ff40) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOSCSIBlockCommandsDevice(1.5.3)@0x8a6000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.5.3)@0x664000
dependency: com.apple.iokit.IOStorageFamily(1.5.1)@0x5ee000

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

Some kind of SCSI storage device you use I'd imagine.
 
I repaired permissions on my external drive and this was the only line that came up:

Symbolic link ./mach->mach_kernel repaired

Try repairing the disk. Not just the permissions. Disk util can do this with the "Repair Disk" button.
 
Some kind of SCSI storage device you use I'd imagine.

While this is the obvious answer, the SCSI Architecture Model family provides support for firewire, ATAPI, and USB devices as well. So it's not necessarily only a SCSI storage device, as they are very rare now-a-days (outside of server infrastructure).
 
While this is the obvious answer, the SCSI Architecture Model family provides support for firewire, ATAPI, and USB devices as well. So it's not necessarily only a SCSI storage device, as they are very rare now-a-days (outside of server infrastructure).

Hmm good point.

Would be nice to know his setup.
 
EDIT: nevermind I was confused lol.

For future ref, you cannot repair permissions on any device except the boot device. That is the only place that the BOM archives in /Library/Receipts/ points at. And it doesn't decend into /Users (unless so defined in a receipt, and that's likely to be a big no-no).
 
I'd be very surprised if a bluetooth mouse could cause kernel panics. I'd be far more suspicious of the bluetooth module on the motherboard, or a corrupted bluetooth driver.
 
I'd be very surprised if a bluetooth mouse could cause kernel panics. I'd be far more suspicious of the bluetooth module on the motherboard, or a corrupted bluetooth driver.

Frankly, I'd be more surprised if his BT module suddenly "went bad", particularly since it's tied to the wifi NIC.

But no bluetooth devices right?

Thanks.

He's got a bluetooth mighty mouse.

Again.. replace the batteries in the BT mouse and see if the KPs go away.
 
Frankly, I'd be more surprised if his BT module suddenly "went bad", particularly since it's tied to the wifi NIC.

Why? This kind of thing happens all the time. On these boards we've seen kernel panics caused by AirPort cards going bad, RAM going bad, motherboards going bad. Why not bluetooth? One thing I've never seen is a kernel panic caused by low batteries in a bluetooth mouse. But maybe I've missed something??
 
I'm not saying it wouldn't happen... If other BT devices cause KPs, then sure.. it's likely a problem with the BT on the logic board.

But I'd prefer that the user went for the cheap route first. Replace batteries. Try other BT devices.

I just don't believe that's the first conclusion to jump to.
 
Okay, put 'em up. ;)

Seriously, you're right, it could not hurt but I think the batteries theory is kind of far-fetched, especially given the symptoms (weekly kernel panics). Batteries in bluetooth devices last only a few weeks, at least in my experience. They go from low to dead pretty darned quickly, like in a matter of days.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.