or Connect
AppleInsider › Forums › General › Genius Bar › Lets talk about Kernel Panics on Macbooks
New Posts  All Forums:Forum Nav:

Lets talk about Kernel Panics on Macbooks

post #1 of 19
Thread Starter 
I've owned my macbook 2.0 GHz with 1 gb of RAM since tuesday afternoon and I've already had 6 kernel panics. I put the computer to sleep and when I wake it up, most of the time its fine, but 6 times I've got the little black box of death telling me to restart my computer.

I've been all over the apple support forums, and been told to do numerous things. I have done all of these things, and none of them has helped.

reset the PMU
reset the PRAM
Ran hardware test: passed
I've even been told to re-install the OS but a few people with my same problem have done it, and it hasnt helped.

A few people on the apple discussion forums have already taken they're Macbook to the Genius Bar at their local apple store and demanded a new one. They got a new one with no questions asked.

I think I might have to do that tomorrow, unless any of you fine people have any bright ideas.

thanks in advance.

(help)
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #2 of 19
What does the panic log say in /Library/logs/panic.log?
post #3 of 19
Thread Starter 
So far I've heard that only apple gods can read this code.......

....... but here are the logs for the 6 panics:

Wed May 31 11:49:43 2006
panic(cpu 0 caller 0x0019C9EF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x223499ae, CR3: 0x00b30000, CR4: 0x000006e0
EAX: 0x00000002, EBX: 0x223499af, ECX: 0x0040c9e0, EDX: 0x001ba9ad
ESP: 0x223499ae, EBP: 0x13783cc8, ESI: 0x001ba9af, EDI: 0x029d3780
EFL: 0x00010246, EIP: 0x003b14c1, CS: 0x00000008, DS: 0x13780010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13783b58 : 0x128b5e (0x3bbf84 0x13783b7c 0x131bbc 0x0)
0x13783b98 : 0x19c9ef (0x3c13b4 0x0 0xe 0x3c116c)
0x13783c48 : 0x197b8d (0x13783c5c 0x13783cc8 0x3b14c1 0x2c2d0048)
0x13783c54 : 0x3b14c1 (0x2c2d0048 0x29d0010 0x240010 0x13780010)
0x13783cc8 : 0x3b25c4 (0x38e0c80 0x29d3780 0x3df45c 0x162fcb)
0x13783d08 : 0x379ba8 (0x24e3c80 0x29d3780 0x13783d48 0x3b1e30)
0x13783d28 : 0x37d401 (0x22fab00 0x29d3780 0x22fab04 0x22fab00)
0x13783d48 : 0x3a29c6 (0x22fab00 0x29d3780 0x13783d78 0x3aed81)
0x13783d98 : 0x1885f0 (0x22fab00 0x33dbfb4 0x33dbfc8 0x11c970)
0x13783dd8 : 0x12b389 (0x2c4a8b4 0x33dbf98 0x0 0x0)
0x13783e18 : 0x124902 (0x2c4a800 0x0 0x18 0x13783efc)
0x13783f28 : 0x192f04 (0x13783f54 0x0 0x0 0x0)
0x13783fd8 : 0x19805b (0x2fdfc08 0x2fdfc08 0x223499af 0x223499ae) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff368

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********

Wed May 31 17:12:32 2006
panic(cpu 0 caller 0x0019C9EF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x22284162, CR3: 0x00d1c000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x22284162, ECX: 0x00502000, EDX: 0x0040c9e0
ESP: 0x22284162, EBP: 0x13a2bcc8, ESI: 0x003c0162, EDI: 0x032a9e40
EFL: 0x00010297, EIP: 0x003b148d, CS: 0x00000008, DS: 0x13a20010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13a2bb58 : 0x128b5e (0x3bbf84 0x13a2bb7c 0x131bbc 0x0)
0x13a2bb98 : 0x19c9ef (0x3c13b4 0x0 0xe 0x3c116c)
0x13a2bc48 : 0x197b8d (0x13a2bc5c 0x13a2bcc8 0x3b148d 0x2ac20048)
0x13a2bc54 : 0x3b148d (0x2ac20048 0x32a0010 0x500010 0x13a20010)
0x13a2bcc8 : 0x3b25c4 (0x247a120 0x32a9e40 0x3df45c 0x162fcb)
0x13a2bd08 : 0x379ba8 (0x33a20c0 0x32a9e40 0x13a2bd48 0x3b1e30)
0x13a2bd28 : 0x37d401 (0x246f200 0x32a9e40 0x246f204 0x246f200)
0x13a2bd48 : 0x3a29c6 (0x246f200 0x32a9e40 0x13a2bd78 0x3aed81)
0x13a2bd98 : 0x1885f0 (0x246f200 0x2e306b4 0x2e306c8 0x11c970)
0x13a2bdd8 : 0x12b389 (0x2f7d2b4 0x2e30698 0x0 0x0)
0x13a2be18 : 0x124902 (0x2f7d200 0x0 0x18 0x13a2befc)
0x13a2bf28 : 0x192f04 (0x13a2bf54 0x0 0x0 0x0)
0x13a2bfd8 : 0x19805b (0x3227c08 0x3227c08 0x22284162 0x22284162) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff368

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********

Wed May 31 21:54:59 2006
panic(cpu 1 caller 0x0019C9EF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x220f61c5, CR3: 0x00d21000, CR4: 0x000006a0
EAX: 0x00000000, EBX: 0x220f61c5, ECX: 0x0024e000, EDX: 0x0040c9e0
ESP: 0x220f61c5, EBP: 0x13a43cc8, ESI: 0x001b91c5, EDI: 0x02744280
EFL: 0x00010297, EIP: 0x003b148d, CS: 0x00000008, DS: 0x13a40010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13a43b58 : 0x128b5e (0x3bbf84 0x13a43b7c 0x131bbc 0x0)
0x13a43b98 : 0x19c9ef (0x3c13b4 0x1 0xe 0x3c116c)
0x13a43c48 : 0x197b8d (0x13a43c5c 0x13a43cc8 0x3b148d 0x2ad20048)
0x13a43c54 : 0x3b148d (0x2ad20048 0x2740010 0x240010 0x13a40010)
0x13a43cc8 : 0x3b25c4 (0x287b940 0x2744280 0x3df45c 0x162fcb)
0x13a43d08 : 0x379ba8 (0x294c2c0 0x2744280 0x13a43d48 0x3b1e30)
0x13a43d28 : 0x37d401 (0x2474200 0x2744280 0x2474204 0x2474200)
0x13a43d48 : 0x3a29c6 (0x2474200 0x2744280 0x13a43d78 0x3aed81)
0x13a43d98 : 0x1885f0 (0x2474200 0x31448b4 0x31448c8 0x11c970)
0x13a43dd8 : 0x12b389 (0x32b74b4 0x3144898 0x0 0x0)
0x13a43e18 : 0x124902 (0x32b7400 0x0 0x18 0x13a43efc)
0x13a43f28 : 0x192f04 (0x13a43f54 0x0 0x0 0x0)
0x13a43fd8 : 0x19805b (0x31d27e0 0x31d27e0 0x220f61c5 0x220f61c5) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff368

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********

Thu Jun 1 17:46:47 2006
panic(cpu 1 caller 0x0019C9EF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x222fb962, CR3: 0x00d27000, CR4: 0x000006a0
EAX: 0x00000000, EBX: 0x222fb962, ECX: 0x0048c000, EDX: 0x0040c9e0
ESP: 0x222fb962, EBP: 0x139c3cc8, ESI: 0x00367962, EDI: 0x02872c80
EFL: 0x00010297, EIP: 0x003b148d, CS: 0x00000008, DS: 0x139c0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x139c3b58 : 0x128b5e (0x3bbf84 0x139c3b7c 0x131bbc 0x0)
0x139c3b98 : 0x19c9ef (0x3c13b4 0x1 0xe 0x3c116c)
0x139c3c48 : 0x197b8d (0x139c3c5c 0x139c3cc8 0x3b148d 0x2a4f0048)
0x139c3c54 : 0x3b148d (0x2a4f0048 0x2870010 0x480010 0x139c0010)
0x139c3cc8 : 0x3b25c4 (0x283a680 0x2872c80 0x3df45c 0x162fcb)
0x139c3d08 : 0x379ba8 (0x3214040 0x2872c80 0x139c3d48 0x3b1e30)
0x139c3d28 : 0x37d401 (0x2479200 0x2872c80 0x2479204 0x2479200)
0x139c3d48 : 0x3a29c6 (0x2479200 0x2872c80 0x139c3d78 0x3aed81)
0x139c3d98 : 0x1885f0 (0x2479200 0x3257cb4 0x3257cc8 0x11c970)
0x139c3dd8 : 0x12b389 (0x2c248b4 0x3257c98 0x0 0x0)
0x139c3e18 : 0x124902 (0x2c24800 0x0 0x18 0x139c3efc)
0x139c3f28 : 0x192f04 (0x139c3f54 0x0 0x0 0x0)
0x139c3fd8 : 0x19805b (0x296e6a0 0x296e6a0 0x222fb962 0x222fb962) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff368

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********

Fri Jun 2 14:51:56 2006
panic(cpu 0 caller 0x0019C9EF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x227705c5, CR3: 0x00d21000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x227705c5, ECX: 0x00321000, EDX: 0x0040c9e0
ESP: 0x227705c5, EBP: 0x1385bcc8, ESI: 0x002575c5, EDI: 0x029046c0
EFL: 0x00010297, EIP: 0x003b148d, CS: 0x00000008, DS: 0x13850010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x1385bb58 : 0x128b5e (0x3bbf84 0x1385bb7c 0x131bbc 0x0)
0x1385bb98 : 0x19c9ef (0x3c13b4 0x0 0xe 0x3c116c)
0x1385bc48 : 0x197b8d (0x1385bc5c 0x1385bcc8 0x3b148d 0x29e70048)
0x1385bc54 : 0x3b148d (0x29e70048 0x2900010 0x320010 0x13850010)
0x1385bcc8 : 0x3b25c4 (0x285e120 0x29046c0 0x3df45c 0x162fcb)
0x1385bd08 : 0x379ba8 (0x285d800 0x29046c0 0x1385bd48 0x3b1e30)
0x1385bd28 : 0x37d401 (0x2474200 0x29046c0 0x2474204 0x2474200)
0x1385bd48 : 0x3a29c6 (0x2474200 0x29046c0 0x1385bd78 0x3aed81)
0x1385bd98 : 0x1885f0 (0x2474200 0x30749b4 0x30749c8 0x11c970)
0x1385bdd8 : 0x12b389 (0x2d447b4 0x3074998 0x0 0x0)
0x1385be18 : 0x124902 (0x2d44700 0x0 0x18 0x1385befc)
0x1385bf28 : 0x192f04 (0x1385bf54 0x0 0x0 0x0)
0x1385bfd8 : 0x19805b (0x2d2a920 0x2d2a920 0x227705c5 0x227705c5) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff368

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********

Fri Jun 2 17:22:15 2006
panic(cpu 0 caller 0x0019C9EF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x22300dc5, CR3: 0x00d21000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x22300dc5, ECX: 0x0032f000, EDX: 0x0040c9e0
ESP: 0x22300dc5, EBP: 0x139b3cc8, ESI: 0x00261dc5, EDI: 0x032ba940
EFL: 0x00010297, EIP: 0x003b148d, CS: 0x00000008, DS: 0x139b0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x139b3b58 : 0x128b5e (0x3bbf84 0x139b3b7c 0x131bbc 0x0)
0x139b3b98 : 0x19c9ef (0x3c13b4 0x0 0xe 0x3c116c)
0x139b3c48 : 0x197b8d (0x139b3c5c 0x139b3cc8 0x3b148d 0x2a040048)
0x139b3c54 : 0x3b148d (0x2a040048 0x32b0010 0x320010 0x139b0010)
0x139b3cc8 : 0x3b25c4 (0x270fc40 0x32ba940 0x3df45c 0x162fcb)
0x139b3d08 : 0x379ba8 (0x28e7ac0 0x32ba940 0x139b3d48 0x3b1e30)
0x139b3d28 : 0x37d401 (0x2474200 0x32ba940 0x2474204 0x2474200)
0x139b3d48 : 0x3a29c6 (0x2474200 0x32ba940 0x139b3d78 0x3aed81)
0x139b3d98 : 0x1885f0 (0x2474200 0x30a62b4 0x30a62c8 0x11c970)
0x139b3dd8 : 0x12b389 (0x3327bb4 0x30a6298 0x0 0x0)
0x139b3e18 : 0x124902 (0x3327b00 0x0 0x18 0x139b3efc)
0x139b3f28 : 0x192f04 (0x139b3f54 0x0 0x0 0x0)
0x139b3fd8 : 0x19805b (0x2ed47e0 0x2ed47e0 0x22300dc5 0x22300dc5) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbffff368

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #4 of 19
Panics could be a sign of bad hardware. Is the memory factory installed or did you add it?
post #5 of 19
Thread Starter 
It was factory. I already ran hardware test: passed.
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #6 of 19
If you have an airport card, it could be that:

http://forums.macosxhints.com/showthread.php?p=295560

though that error is an mbuf error and you are getting a page fault. Page faults still happen with devices though so I'd try disabling Airport and hooking up to the internet via a wired connection.

Apple really should try to make their log files easier to decipher. I don't think anyone can figure out what's going on there because all the log file shows is the CPU register addresses and the contents. The values could mean anything.
post #7 of 19
Do you have anything attached to it via USB or FireWire? If so, remove it.

Most likely it is bad RAM.
--Johnny
Reply
--Johnny
Reply
post #8 of 19
Thread Starter 
I haven't had anything attached when it happens.

The ram is fine. It passed hardware test.
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #9 of 19
Hardware Test hardly ever catches bad RAM (chances improve if you loop it for a few hours).

This might give you more RAM info:

http://www.memtestosx.org/

Otherwise, I'd say arm yourself with the logs and the forum postings and head for the Genius Bar.
eye
bee
BEE
Reply
eye
bee
BEE
Reply
post #10 of 19
Quote:
Originally posted by FormerLurker
Otherwise, I'd say arm yourself with the logs and the forum postings and head for the Genius Bar.

Especially since the machine is less than a week old.
post #11 of 19
Thread Starter 
I ran the memtest. It didnt find anything. I just hope I can get a new computer. This really bums me out
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #12 of 19
Remember - a calm, logical demeanor and cooperative but insistant attitude will get you much further than ranting and raving.
eye
bee
BEE
Reply
eye
bee
BEE
Reply
post #13 of 19
Thread Starter 
yea of course...........and it also helps to get the right person to help you. Some employee's seem to be more reluctant to give you a new machine than others.

I wish I didnt have to take it in and wait for another computer. The machine has been working great for the last week besides the kernel panics. I haven't even had one for 24 hours........and I've put the computer to sleep and woken it up 10+ times. Hmmm

oh well. still heading to the genius bar
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #14 of 19
Thread Starter 
Little UPDATE:

I made a secondary user account with administrative control and ran with that user all day yesterday. I didnt have a kernel panic the whole day, and haven't had one today so far.

How could the problem be user specific?
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #15 of 19
Quote:
Originally posted by mister_volcom88
How could the problem be user specific?

Very unusual, but some utility or shareware could have installed something in /Users/Youraccount/Library. The fact that the new user account works, implies that if something is installed, it is in the ~/Library of the other account, and not in the /System or /System/Library folders.

Try booting the "bad" account while holding down the Shift key (extensions off). A wild guess, but worth trying. Hold down Shift until after the desktop appears and the machine is fully booted.
--Johnny
Reply
--Johnny
Reply
post #16 of 19
Thread Starter 
so I type in my password and hit "log-in" on the "bad" account and then immediately hold the shift key until it's fully booted?


If that doesnt seem to help things out, then I might try Re-installing the OS (although a few people with my problem have done that and it hasnt helped) before I head to the apple store.
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #17 of 19
Thread Starter 
UPDATE******

I re-installed OS X and the kernel panics have seemed to go away. (knock on wood)

I still have a pesky dead pixel on my screen though.
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
White Macbook
2.16 GHz
-------------------------------------------
PSN: DaycareMassacre
Reply
post #18 of 19
Quote:
Originally posted by mister_volcom88
UPDATE******

I re-installed OS X and the kernel panics have seemed to go away. (knock on wood)

I still have a pesky dead pixel on my screen though.

This is very good information. The Conventional Wisdom is that KPs are 99% due to hardware, which may be true, but I have had one case where reinstalling the OS did in fact cure them. That was after running an early Tiger developer build and turning on Quartz 2-D Extreme. I think it set a register in the video card that borked up another kernel extension that was not expecting it.

Aside from that, all other KPs have been cured by some hardware switching.

We should do an Archive and Install if after a fairly good thought process and removing added hardware, nothing is found to point to a hardware problem.
--Johnny
Reply
--Johnny
Reply
post #19 of 19
This is overkill, I know, but when I get a new Mac, I always reformat the drive, write zeroes using erase options, then reinstall the OS and applications.

A fairly easy way to test memory is to fire up photoshop (if you have it) and open a very, very large image file (several hundred megabytes), then manipulate the image. PS is very good at crashing and burning with bad memory in such a situation.
J.C. Corbin, Apple Certified Technical Coordinator
Member, Apple Consultants Network
www.ro3.com
Reply
J.C. Corbin, Apple Certified Technical Coordinator
Member, Apple Consultants Network
www.ro3.com
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Genius Bar
AppleInsider › Forums › General › Genius Bar › Lets talk about Kernel Panics on Macbooks