new MBP13" kernal panic...issue?

[kimcicle]

Hey guys..so...as soon as the computer was started and showed desktop screen, the screen was suddenly went dark and said "restart the computer.....etc"
i found out it was a kernal panic issue...
i have had this problem before on my old ibook g4 and it was logic board failure...
Does anyone know why did happened to the new computer that is about 2 weeks old?


and i don't exactly know but i feel like the computer takes more time to boot after that short incident....is it relative problem that i should be concerned about?

 

[sam10685]

Hey guys..so...as soon as the computer was started and showed desktop screen, the screen was suddenly went dark and said "restart the computer.....etc"
i found out it was a kernal panic issue...
i have had this problem before on my old ibook g4 and it was logic board failure...
Does anyone know why did happened to the new computer that is about 2 weeks old?


and i don't exactly know but i feel like the computer takes more time to boot after that short incident....is it relative problem that i should be concerned about?

Bad computer probably.

 

[MacDawg]

Kernel Panic's are usually a result of some hardware/memory issue

Here are some resources on that issue for you to look at:

Isolating issues in Mac OS X

Resolving Kernel Panics

Since it is brand new, you might want to take it in for evaluation

Woof, Woof - Dawg

 

[r.j.s]

I'd take it to the Genius Bar to get looked at.

 

[kimcicle]

Bad computer probably.

wow..thanks alot

 

[NewMacbookPlz]

wow..thanks alot

I think he meant since it's new, return it.

Something's obviously wrong....

 

[jamesryanbell]

wow..thanks alot

He wasn't trying to be a smartass. haha. He's seriously probably right. Just take it to the genius bar, and they'll get it worked out for you.

 

[kimcicle]

I think he meant since it's new, return it.

Something's obviously wrong....

the thing is, my last week to return was last tuesday, 7/7/09....can i still return the computer with this issue?

 

[bossxii]

the thing is, my last week to return was last tuesday, 7/7/09....can i still return the computer with this issue?

Take it in, even if your past the 14 day return period you have 1 year of Apple Care and since it is so new, they may just swap it out for another. Just be honest with em and remain calm, they will take care of it via a fix or swap either way your not stuck with a non working machine.

 

[jamesryanbell]

the thing is, my last week to return was last tuesday, 7/7/09....can i still return the computer with this issue?

Yeah, it should be covered by the one year warranty.

 

[NewMacbookPlz]

the thing is, my last week to return was last tuesday, 7/7/09....can i still return the computer with this issue?

See, your first sentence+thread title confused us then..."new MBP13" and "as soon as the computer was started" made it seem like the first boot-up had this happen. Although, if I paid attention further into the post, I would have seen where you said it's now 2 weeks ago F-me....

Try resetting the PRAM and see if that'll help things along http://support.apple.com/kb/HT1379

 

[kimcicle]

I apologize if the question was confusing,
the computer was bought about two weeks and half ago, and my last day to return was 7/7/09,

is there any other way that i can diagnose the problem and possibly prevent the future kernal panic?


btw, the log about the keranl panic was...

Description: Panic (system crashes) log
Size: 6 KB
Last Modified: 7/13/09 4:16 PM
Location: /Library/Logs/PanicReporter/2009-07-13-161638.panic
Recent Contents: Mon Jul 13 16:16:38 2009
panic(cpu 1 caller 0x003F0DD4): "A driver releasing a(n) IOBluetoothL2CAPChannel has corrupted the registry\n"@/SourceCache/xnu/xnu-1228.14.1/libkern/c++/OSObject.cpp:241
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x5d727d98 : 0x12b4c6 (0x45f1bc 0x5d727dcc 0x13355c 0x0)
0x5d727de8 : 0x3f0dd4 (0x4a18a8 0xa27884 0x941d004 0x941d000)
0x5d727e28 : 0x3f0d44 (0x941d000 0x0 0x1 0x40)
0x5d727e48 : 0x3f0e11 (0x941d000 0x0 0xd 0x0)
0x5d727e68 : 0xa106c9 (0x941d000 0x0 0x1 0x941d000)
0x5d727e88 : 0xa123f6 (0x91a1000 0x941d000 0x0 0x0)
0x5d727ea8 : 0x41364e (0x941d000 0x91a1000 0x5d727ed8 0x40a563)
0x5d727ed8 : 0x4254f7 (0x91a1000 0x941d000 0x0 0x0)
0x5d727f08 : 0x4132a2 (0x6fcbb80 0x4135e4 0x91a1000 0x941d000)
0x5d727f58 : 0x417314 (0x0 0x0 0x0 0x0)
0x5d727fa8 : 0x4174e9 (0x5 0x1 0x4174c8 0x7469b40)
0x5d727fc8 : 0x1a14ec (0x5 0x0 0x1a40b5 0x6e9f8b8)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOBluetoothFamily(2.1.7f5)@0x9f9000->0xa32fff

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9J3050

Kernel version:
Darwin Kernel Version 9.7.1: Thu Apr 23 13:52:18 PDT 2009; root:xnu-1228.14.1~1/RELEASE_I386
System model name: MacBookPro5,5 (Mac-F2268AC8)

System uptime in nanoseconds: 215105523198
unloaded kexts:
com.apple.driver.InternalModemSupport

....
..


Thanks guys!

 

[HLdan]

Use the restore disc and run hardware test first. If nothing comes up bad then just wait for the next one, it could've been just a memory crash, there's no need to "panic" over one kernel panic. A bad logic board in one computer doesn't mean the same for every other. Also a kernel panic is the same as BSOD in Windows, it doesn't mean something is defective.