uMBP 17" Early 09' Kernal Panic's

[harodude]

I've been having some issues with kernal panic's on one of my uMBP 17"...

Opened the lid on 2 occasions, panic's and it has served me this message after force restart. Any ideas?

Fri Jul 10 20:35:18 2009
panic(cpu 0 caller 0x001AB0FE): Kernel trap at 0x581e09b0, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x01909000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x08ea3500, ECX: 0x581e0954, EDX: 0x08e8ac00
CR2: 0x00000000, EBP: 0x57123bd8, ESI: 0x00000007, EDI: 0x08e8ac00
EFL: 0x00010206, EIP: 0x581e09b0, CS: 0x00000008, DS: 0x00540010
Error code: 0x00000000

Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x571239b8 : 0x12b4c6 (0x45ec20 0x571239ec 0x13355c 0x0)
0x57123a08 : 0x1ab0fe (0x468ecc 0x581e09b0 0xe 0x468678)
0x57123ae8 : 0x1a1703 (0x57123b00 0x5103d0a4 0x57123bd8 0x581e09b0)
0x57123af8 : 0x581e09b0 (0xe 0x8800048 0x8800010 0x540010)
0x57123bd8 : 0x7bcfa6 (0x8ea3500 0x8e8ac00 0x5103d04c 0x0)
0x57123c08 : 0x7bce88 (0x8ea3500 0x1 0x8e8ac00 0x0)
0x57123c48 : 0x4268e5 (0x8ea3500 0x57123cc0 0x0 0x0)
0x57123c98 : 0x7bcf04 (0x76af100 0x7bce46 0x57123cc0 0x0)
0x57123ce8 : 0x7bd1a9 (0x8ea3500 0x8e8ac00 0x7bcf54 0x8ea3500)
0x57123d18 : 0x7b7cdd (0x8ea3500 0x8e8ac00 0x57123d48 0x7bea16)
0x57123d68 : 0x7b7f50 (0x8e8ac00 0x8ea3500 0x0 0x75e86b0)
0x57123db8 : 0x7b81df (0x8e8ac00 0x8ea3500 0x8000 0x1)
0x57123df8 : 0x7c083f (0x8e8ac00 0x8ea3500 0x8000 0x1)
0x57123e48 : 0x7bce88 (0x8e8ac00 0x1 0x0 0x0)
0x57123e88 : 0x4268e5 (0x8ea3500 0x57123f00 0x0 0x0)
0x57123ed8 : 0x7bcf04 (0x76af100 0x7bce46 0x57123f00 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBEthernetHost(1.0.0)@0x581df000->0x581e2fff
dependency: com.apple.iokit.IONetworkingFamily(1.6.1)@0x7b5000
dependency: com.apple.iokit.IOUSBFamily(3.4.3)@0x5aa000
com.apple.iokit.IONetworkingFamily(1.6.1)@0x7b5000->0x7cafff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9J61

Kernel version:
Darwin Kernel Version 9.7.0: Tue Mar 31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386
System model name: MacBookPro5,2 (Mac-F2268EC8)

System uptime in nanoseconds: 3971458289260
unloaded kexts:
com.apple.driver.AppleUSBEthernetHost 1.0.0 - last unloaded 3195300051648
loaded kexts:
com.apple.driver.AppleUSBEthernetHost 1.0.0 - last loaded 3644977455663

 

[celticpride678]

Most of the time, kernel panics are caused by these things:http://www.thexlab.com/faqs/kernelpanics.html

Defective or incompatible RAM are the most frequent causes of kernel panics. Despite being a highly-reliable product, RAM can fail. Modern operating systems, like Mac OS X, are sensitive to RAM. Purchase additional RAM from either Apple or third parties who guarantee their RAM is compatible with Mac OS X, offer a liberal exchange policy, and provide a lifetime warranty should the RAM become defective or a later version of Mac OS X introduce incompatibilities.
Incompatible, obsolete, or corrupted kernel extensions. If a third-party kernel extension or one of its dependencies is incompatible or obsolete with respect to the version of Mac OS X you are using, kernel panics may occur when the kernel executes such extensions. Likewise, if a kernel extension or one of its dependencies is corrupted, such as the result of hard disk corruption, kernel panics are likely to occur when the kernel attempts to load or execute such.
Incompatible, obsolete, or corrupted drivers. Similar to kernel extensions, drivers for third-party hardware which are incompatible with the version of Mac OS X you are using, or which have become corrupted, will cause in kernel panics.
Hard disk corruption, including bad sectors, directory corruption, and other hard-disk ills.
Incorrect permissions on System-related files or folders.
Insufficient RAM and available hard disk space.
Improperly installed hardware or software.
Defective hardware or software. Hardware failures, including a defective CPU, or programming errors can result in kernel panics.
Incompatible hardware. While rare, this is generally the result of a third-party hardware vendor’s product failing to properly respond to the kernel or a kernel extension in an expected way.

Are these anythings that happened to you/you did?

 

[harodude]

This computer is 3 weeks old and is as configured from Apple. No upgrades or modification have been done.

 

[celticpride678]

This computer is 3 weeks old and is as configured from Apple. No upgrades or modification have been done.

I would take it to Apple and see what they say. Is this the first time you have seen this?

 

[iLog.Genius]

Before taking it to Apple, I'd just do a reinstall of the OS and get that out of the way. You'll get a more quicker solution since Apple is going to perform one themselves anyway to rule out software.

 

[celticpride678]

Before taking it to Apple, I'd just do a reinstall of the OS and get that out of the way. You'll get a more quicker solution since Apple is going to perform one themselves anyway to rule out software.

Yep, I would do that to. Sorry for leaving that out.

 

[harodude]

Already 00000000000'd it out!!! I have been through so many repairs on the previous computer (this is the replacement) and would hate to go through that hassle again!

Does anything in that report point to a certain hardware issue?

Thanks for the replys!