[casselma]

Recently been having some kernel panic issues (I think, screen dims and I'm told to restart). I've had 3 in the last 2 days, and I've never had them before.

Are they a hardware or software issue typically, or both? Running a MBP with 10.4. The computer has been through some falls and has its problems (battery stopped working about a year ago, still works via power cord.) Unfortunately, no Applecare, I never had any problems with my Macs - Plus to lime iMac and never saw a need. I've learned my lesson, recent Macs need it and notebooks especially!

Had a couple kernel panics on my last restart, so I'm going to back this thing up, ASAP.

Reinstalling OS X help? A total wipe? PRAM (or whatever it's called now) reset?

Suggestions appreciated, I'd like this thing to last another few months or a year, but if it dies, I guess I get a new one, with Applecare!

[Big Mac]

AppleCare is important, and service technicians will tell you it's a poor choice not to buy it. But don't be too concerned, yet. KPs are usually software related. You may have a corrupt installation. Console application logs would help though. . . .

[casselma]

Yes, Applecare is important, or at least it is nowadays. Back when Macs were Macs, they never failed. =P

Would a system.log output be useful? (It doesn't look useful, but then I stopped being up on Mac inner workings with System 7.)

[-Q-]

Yep, Applecare for portables is a good investment, however, it won't cover any faults due to you dropping your laptop. So in this particular instance, you'd need insurance rather than the extended warranty Applecare provides.

Tracking down KP problems can be troublesome. Software is usually the culprit, but I've run into areas where bad RAM caused them, too. I'd set up a new 'fresh' account and see if the kernel panics persist on that account too (probably will). A backup and reinstall would probably be a good next step.

[Big Mac]

Try here (in Console):



Often they aren't that useful, but in some cases (especially recurring ones), they can point to a cause.

[casselma]

Wed Aug 6 19:39:36 2008
panic(cpu 0 caller 0x001A49CB): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000018, CR3: 0x00e33000, CR4: 0x000006e0
EAX: 0x7f21ec24, EBX: 0x02f7a588, ECX: 0x00000000, EDX: 0x000000fe
CR2: 0x00000018, EBP: 0x14013d58, ESI: 0x004bccdc, EDI: 0x000000fe
EFL: 0x00010002, EIP: 0x0013ec53, CS: 0x00000008, DS: 0x14010010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14013b78 : 0x128d0d (0x3cc65c 0x14013b9c 0x131f95 0x0)
0x14013bb8 : 0x1a49cb (0x3d2a94 0x0 0xe 0x3d22b8)
0x14013cc8 : 0x19b3a4 (0x14013cd8 0x270c2dc 0xe 0x140048)
0x14013d58 : 0x13efbe (0x2f7a588 0x7f21ec24 0xfe 0x127ea7)
0x14013d98 : 0x11ff48 (0x2fb6764 0x4b3480 0x0 0x2)
0x14013df8 : 0x125b59 (0x2fb6764 0x113 0x5c 0x7530)
0x14013f08 : 0x195f2e (0x14013f44 0x0 0x0 0x0)
0x14013fc8 : 0x19b81e (0x2f1c0e4 0x0 0x19e0b5 0x2710a10) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0101d38

Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386


*********

Fri Aug 8 14:59:47 2008
panic(cpu 1 caller 0x001A49CB): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x0000000c, CR3: 0x00e33000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x01365584
CR2: 0x0000000c, EBP: 0x13f73c38, ESI: 0x00001000, EDI: 0x00000000
EFL: 0x00010293, EIP: 0x0016e984, CS: 0x00000004, DS: 0x13f7000c

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13f73958 : 0x128d0d (0x3cc65c 0x13f7397c 0x131f95 0x0)
0x13f73998 : 0x1a49cb (0x3d2a94 0x1 0xe 0x3d22b8)
0x13f73aa8 : 0x19b3a4 (0x13f73ab8 0x1365578 0xe 0x190048)
0x13f73c38 : 0x1840ab (0x1365578 0x13f73cd0 0x1000 0x0)
0x13f73cf8 : 0x370790 (0x1365578 0x13f73d88 0x1000 0x0)
0x13f73da8 : 0x33efb8 (0x28aedac 0x26eee70 0x26eeeb4 0x283ed40)
0x13f73f58 : 0x37b300 (0x28aedac 0x26eee70 0x26eeeb4 0x0)
0x13f73fc8 : 0x19b77e (0x259f9dc 0x0 0x19e0b5 0x25a42dc) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff968

Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386

[Big Mac]

Unfortunately, those KPs are of the completely cryptic variety. This link has good suggestions for troubleshooting:

http://www.thexlab.com/faqs/kernelpanics.html

[casselma]

C'mon you know you want to translate the hex! =P

Didn't know if I made it clear, but some of these happen on the gray startup screen, even before the blue screen or the starting up progress bar window.

I saw a mention of an invalid or missing driver when it crashed before startup.

But thanks for the help nonetheless.

[casselma]

Thanks for the link, BigMac.

[Big Mac]

Translating the hex and reconstructing the kernel symbols sounds like fun! Hahaha.

Remove all non-essential hardware. Try reseating your Airport card (if it's not built into the motherboard). If it said there was a driver problem it very well could be a peripheral.

[casselma]

No peripherals. Was going to back it up onto DVDs, the drive acts weird. Takes a while to put the disk on the desktop, but Finder refused to burn to it. Toast says connection is not stable. Going to back up mission-critical files to my iPod.

Suspecting the drive now.

[casselma]

Did a hardware check after booting from the installation DVD. Looped it for 4 hours, no hardware errors found. Proceeded to do an archive and install. Reupgraded to 10.4.11. No crashes since.

DVD writer is still out though. Guess I'll have to find another way to backup.

Thanks for the helpful suggestions, crisis averted!

[Big Mac]

Glad to hear it.