Kernel Panics

[amusiccale]

I'm just switching over to OSX (to SR 2.2)-- a mac had never been my full-time machine before, and it seems as if today suddenly brought on a surge of kernel panics (the black box with 4 languages). Would connecting wired LAN at the same time airport in the presence of a wireless network cause this? Or, (the other change) could connecting an external drive [NTFS] cause it? Either way, the computer's quickly losing my trust.

I've repaired disk permissions, but I don't imagine that was a cause (again, I don't really know much about this OS under the hood). I've seen people post logs of some sort up--where should I look for that?

Thanks -- hopefully this is something software/compatibility related!

Edit: Some of the crashes have come while using VLC; I am updating the software right now. Is anyone aware of bugs in that program that could cause this sort of thing?

 

[PlaceofDis]

well it could certainly be one of the issues you describe. but we'll have to figure out whats causing it first to figure out how to make them stop.

you should be able to find the logs in your Console, which is in Applications>Utilities

 

[cal6n]

Kernel panics can be caused by defective or poorly seated RAM. Were you playing large files in VLC when they occurred? It might be worth removing and re-seating your RAM a couple of times to eliminate this possibility.

 

[amusiccale]

Is this what we're looking for?
Also, I am running 10.4.10 with the Macbook Pro update

************

Sat Jul 7 11:35:39 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x01356000, CR4: 0x000006e0
EAX: 0x0000013e, EBX: 0x00000000, ECX: 0x045e7020, EDX: 0x00000002
CR2: 0x00000000, EBP: 0x25dfb918, ESI: 0x000000d8, EDI: 0x045e7004
EFL: 0x00010206, EIP: 0x00c3ceff, CS: 0x00000008, DS: 0x045e0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25dfb6b8 : 0x128d08 (0x3cc0a4 0x25dfb6dc 0x131de5 0x0)
0x25dfb6f8 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x25dfb808 : 0x19aeb4 (0x25dfb820 0x1 0x25dfb838 0x74367f)
0x25dfb918 : 0xc37723 (0x45e7004 0x45f3c04 0x3 0x3)
0x25dfba48 : 0x84260c (0x45e7004 0x45f3c04 0x25dfbb30 0x25dfbb30)
0x25dfbb58 : 0x84233a (0x45e7004 0x45f3404 0x1 0x1c)
0x25dfbbb8 : 0xc3210a (0x45e7004 0x45f3404 0x1c 0xc77160)
0x25dfbc38 : 0xc324f2 (0x45e7004 0x45f3c04 0x100000 0x25dfbd4c)
0x25dfbd98 : 0xc584cd (0x45e7004 0x45f3c04 0x0 0x19a001)
0x25dfbe78 : 0x8392ac (0x45e7004 0x45d6a04 0x0 0x45e7004)
0x25dfbec8 : 0x70940b (0x45e7004 0x45d6a04 0x0 0x1352bb)
0x25dfbf08 : 0x39b3c3 (0x23f3f004 0x4496080 0x1 0x4066a10)
0x25dfbf58 : 0x39a595 (0x4496080 0x135eb4 0x0 0x4066a10)
0x25dfbf88 : 0x39a2cb (0x4273200 0x4060b20 0x4550c4 0x450ddac)
0x25dfbfc8 : 0x19ad2c (0x4273200 0x0 0x19e0b5 0x3ebf680) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.nvidia.nv50hal(5.0.2)@0xbe7000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5c1000
dependency: com.apple.NVDAResman(5.0.2)@0x6f5000
com.apple.NVDAResman(5.0.2)@0x6f5000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5c1000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.7)@0x6cb000
dependency: com.apple.iokit.IONDRVSupport(1.4.7)@0x6e6000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********

Sat Jul 7 11:38:59 2007
panic(cpu 0 caller 0x0019A676): interlock timeout for mutex 0x3fb100c
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2587b528 : 0x128d08 (0x3cc0a4 0x2587b54c 0x131de5 0x0)
0x2587b568 : 0x19a676 (0x3d0f90 0x3fb100c 0x0 0x0)
0x2587b598 : 0x197fa7 (0x3fb100c 0x206 0x2587b5d8 0x1d22d0)
0x2587b5a8 : 0x1d22d0 (0x3fb100c 0x1000 0x2587b5d8 0x32deb0)
0x2587b5d8 : 0x1d245e (0x1d45cb8 0x206 0x2587b648 0x1416ad)
0x2587b638 : 0x1d2712 (0x12400 0x12401 0x449c388 0x68)
0x2587b688 : 0x1d40af (0x1 0x443340 0x7899400 0x78a1cc0)
0x2587b6e8 : 0xb1f73f (0x0 0x34 0x2587b710 0x2587b744)
0x2587b768 : 0xb1e7a3 (0x3fb1900 0xab6 0x7430210 0x2587bee0)
0x2587ba58 : 0xb216a3 (0x45fc200 0x7430210 0x2587bee0 0x4534000)
0x2587bac8 : 0x1e5038 (0x2587bae8 0x2587bafc 0x2587bf08 0x0)
0x2587bb18 : 0x1ccc89 (0x7430210 0x2587bdcc 0x2587bee0 0x2587bf08)
0x2587bb88 : 0x1cd4af (0x2587bdb4 0x100 0x2587bdd4 0x0)
0x2587bc38 : 0x1d91d5 (0x2587bdb4 0x0 0x0 0x0)
0x2587bd68 : 0x1d9636 (0x37ed70 0x0 0x0 0x0)
0x2587bf28 : 0x1d96cb (0x37ed70 0x0 0x0 0x0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.ntfs(1.2.1)@0xb1b000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********

Sat Jul 7 11:44:09 2007
panic(cpu 0 caller 0x0019A676): interlock timeout for mutex 0x488f60c
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25853698 : 0x128d08 (0x3cc0a4 0x258536bc 0x131de5 0x0)
0x258536d8 : 0x19a676 (0x3d0f90 0x488f60c 0x1 0x1)
0x25853708 : 0x197fa7 (0x488f60c 0x206 0x25853748 0x1d22d0)
0x25853718 : 0x1d22d0 (0x488f60c 0x0 0x25853748 0x32deb0)
0x25853748 : 0x1d245e (0xe62 0x3c73b236 0x40c9004 0x6)
0x258537a8 : 0x1d2712 (0x4162e1c 0x4162e1c 0x258537e8 0x19a319)
0x258537f8 : 0x1d40af (0x1 0x443340 0x1d44ae8 0x40e6e60)
0x25853858 : 0x2f4319 (0x0 0x34 0x25853908 0x415f1d4)
0x25853968 : 0x2fa9d6 (0x40c9004 0x458118c 0x25853ee0 0x25853a94)
0x25853ac8 : 0x1e5038 (0x25853ae8 0x25853f08 0x25853f08 0x0)
0x25853b18 : 0x1ccc89 (0x458118c 0x25853dcc 0x25853ee0 0x25853f08)
0x25853b88 : 0x1cd4af (0x25853db4 0x100 0x25853dd4 0x0)
0x25853c38 : 0x1d91d5 (0x25853db4 0x0 0x0 0x0)
0x25853d68 : 0x1d94c1 (0xbffff448 0x0 0x0 0x0)
0x25853f28 : 0x1d9556 (0xbffff448 0x0 0x0 0x0)
0x25853f58 : 0x37ad83 (0x48a0000 0x4778af8 0x4778b3c 0x0) Backtrace continues...

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*********

 

[CybrMike]

if your using the new sr mb pro there is another thread on this. Basically it has to do with your wireless security. In my case changing from wpa to wep stopped causing the panics. Some people have had to disable wireless security all together.

 

[amusiccale]

Well, in my case, I've been using WEP security seemingly without issue-- my last KP was a few weeks ago. Today, then, I ended up with three. I will try reseating my RAM once I can get access to some of those tiny screwdrivers at my parents' house.