Kernel Panic - Ideas?

[island]

Running Parallels, iChat, nothing else really. Went out to dinner, came back and I had a panic on the screen. Any ideas on something that might be failing?



panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x54ae6000, CR3: 0x0132b000, CR4: 0x000026e0
EAX: 0x06a9dc1c, EBX: 0x54ae3200, ECX: 0x0000003d, EDX: 0x0000011c
CR2: 0x54ae6000, EBP: 0x06a9dc00, ESI: 0x05eef8c0, EDI: 0x0472f600
EFL: 0x00010292, EIP: 0x54ae5fff, CS: 0x00000008, DS: 0x258d0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x258d3c68 : 0x128d08 (0x3cc0a4 0x258d3c8c 0x131de5 0x0)
0x258d3ca8 : 0x1a4a55 (0x3d24b8 0x1 0xe 0x3d1cdc)
0x258d3db8 : 0x19aeb4 (0x258d3dd0 0x384864 0x6a9dc00 0x1416ad) Backtrace terminated-invalid frame pointer 0x6a9dc00

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

Model: MacBookPro3,1, BootROM MBP31.0070.B02, 2 processors, Intel Core 2 Duo, 2.4 GHz, 2 GB
Graphics: GeForce 8600M GT, GeForce 8600M GT, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.1.9.3
Bluetooth: Version 1.9.0f8, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: FUJITSU MHW2160BHPL, 149.05 GB
Parallel ATA Device: MATSHITADVD-R UJ-857E
USB Device: PROExpress-7, Atech Flash, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 1.5 Mb/sec, 500 mA
USB Device: Built-in iSight, Apple Inc., Up to 480 Mb/sec, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA

 

[IJ Reilly]

Nothing specific is indicated in the log. If it's a one-time event, I wouldn't sweat it.

If it was me, I'd run a disk integrity check using fsck in Single User Mode, or if you don't know how to do that, booted on the restore disk in Disk Utility, if only because hard shutdowns can cause directory damage.