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

Can someone analyze this kernel panic for me?

Warbrain

Warbrain

macrumors 603
Original poster
Jun 28, 2004
5,702
293
Chicago, IL
I've had a series of kernel panics over the past few days, many of which had happened so fast the computer couldn't even log the panic. Today I finally had one that could log it. Any idea what this could be? I've read that it might be memory so I took out my 1GB stick and everything is running fine but we'll see if something comes up. But please, take a look and let me know.
Tue May 6 22:14:14 2008


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000008 PC=0x00000000000831E0
Latest crash info for cpu 0:
Exception state (sv=0x35f95500)
PC=0x000831E0; MSR=0x00009030; DAR=0x00000008; DSISR=0x42000000; LR=0x000831CC; R1=0x3625BB00; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00956960 0x00084B64 0x000671C0 0x000AF1EC 0x000B2A78
kmod scan stopped due to missing kmod page: 00000000
Proceeding back via exception chain:
Exception state (sv=0x35f95500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2fcfa280)
PC=0x00911474; MSR=0x00009030; DAR=0x48211D53; DSISR=0x40000000; LR=0x00911454; R1=0x3625BEB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000
backtrace terminated - unaligned frame address: 0x00000001

kmod scan stopped due to missing kmod page: 00000000
Exception state (sv=0x2a13dc80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9C7010

Kernel version:
Darwin Kernel Version 9.2.2: Tue Mar 4 21:23:43 PST 2008; root:xnu-1228.4.31~1/RELEASE_PPC
System model name: PowerBook6,7
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x0009B478 0x0009BE1C 0x00029DD4 0x000AF210 0x000B2A78
kmod scan stopped due to missing kmod page: 00000000
Proceeding back via exception chain:
Exception state (sv=0x35f95500)
PC=0x000831E0; MSR=0x00009030; DAR=0x00000008; DSISR=0x42000000; LR=0x000831CC; R1=0x3625BB00; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00956960 0x00084B64 0x000671C0 0x000AF1EC 0x000B2A78
kmod scan stopped due to missing kmod page: 00000000
Exception state (sv=0x2fcfa280)
PC=0x00911474; MSR=0x00009030; DAR=0x48211D53; DSISR=0x40000000; LR=0x00911454; R1=0x3625BEB0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000
backtrace terminated - unaligned frame address: 0x00000001

kmod scan stopped due to missing kmod page: 00000000
Exception state (sv=0x2a13dc80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP0
Click to expand...
 
What were you doing at the time? Did you install anything recently (such as drivers)? What happened before the first time this happened? Have you tried repairing your disk?

I doubt it is any peripheral itself but rather a driver. You have any HP drivers installed for instance?
 
NAG said:
What were you doing at the time? Did you install anything recently (such as drivers)? What happened before the first time this happened? Have you tried repairing your disk?

I doubt it is any peripheral itself but rather a driver. You have any HP drivers installed for instance?
Click to expand...

I was web browsing. Nothing outside of Leopard drivers are new because I did a complete wipe last night to see if that would take care of the problem. I suspect it's not drivers in this case.

I removed my RAM and then put it back in, making sure that it was seated property and tight. So far everything has been fine and fast. It's entirely possible that the RAM was slightly out of the socket and was causing errors. But I still want a better idea of what the panic log says...
 
I'm not claiming to know much about kernel panics, but like you said, it looks like a memory error. I'd run a memory test just to see the results.
 
I ran the hardware test and it confirmed what I suspected was the problem: the 1 GB stick from Kingston. I started the hardware test and it locked up during memory so I figured I would remove the RAM that I could and see if it worked all the way through - it did. So I dug out a 512 MB stick from an IBM sitting in my house and put it in to see if it would pass - it did. So it appears that the 1 GB stick is bad in way and needs to be replaced.
 
Yet another lesson on the most frequent source of kernel panics and the value of OSX reinstalls in solving them. File and remember!
 
Warbrain said:
I ran the hardware test and it confirmed what I suspected was the problem: the 1 GB stick from Kingston. I started the hardware test and it locked up during memory so I figured I would remove the RAM that I could and see if it worked all the way through - it did. So I dug out a 512 MB stick from an IBM sitting in my house and put it in to see if it would pass - it did. So it appears that the 1 GB stick is bad in way and needs to be replaced.
Click to expand...

aahh good to hear. take it back!!!
 
No, it couldn't be as simple as the 3rd party memory...

It's the onboard memory. This is something that's not easily fixable.

Looks like I'll be pondering my options.

Thanks for all the help, though.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back