Kernel Panic on shutdown?!?

Every time I shut down, I get a Kernel Panic!!! I have no clue why! Please help! Posted here is the dump:

Fri Jan 11 00:47:50 2008
panic(cpu 2 caller 0x001A7BED): Kernel trap at 0x00000000, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x01021000, CR4: 0x00000660
EAX: 0x08f12700, EBX: 0x08f12300, ECX: 0x00000000, EDX: 0x08f12500
CR2: 0x00000000, EBP: 0x6da5ba88, ESI: 0x086f33c0, EDI: 0x0052f078
EFL: 0x00010246, EIP: 0x00000000, CS: 0x00000008, DS: 0x08f10010
Error code: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x6da5b888 : 0x12b0e1 (0x455670 0x6da5b8bc 0x133238 0x0)
0x6da5b8d8 : 0x1a7bed (0x45ea20 0x0 0xe 0x45e1d4)
0x6da5b9b8 : 0x19e517 (0x6da5b9d0 0x206 0x6da5ba88 0x0)
0x6da5b9c8 : 0x0 (0xe 0x8f10048 0x6da50010 0x620010)
0x6da5ba88 : 0xbc9447 (0x8f12300 0x0 0x6da5ba98 0xc1)
0x6da5baa8 : 0x3e809c (0x8f12400 0x52f078 0x1 0x120fb5)
0x6da5bac8 : 0x3eccf7 (0x8f12400 0x52f078 0x6da5bb18 0x3e8109)
0x6da5baf8 : 0x3ecbb2 (0x86f33c0 0x0 0x1 0x0)
0x6da5bb18 : 0x3e809c (0x86f33c0 0x0 0x1 0x1)
0x6da5bb38 : 0x3e8169 (0x86f33c0 0x0 0x6da5bb68 0x3e809c)
0x6da5bb58 : 0x406d8a (0x86f33c0 0xffff 0x87069c4 0x3e8169)
0x6da5bb78 : 0x406dbd (0x87069c0 0x206 0x6da5bbb8 0x8bdbba0)
0x6da5bb98 : 0x3e809c (0x87069c0 0x0 0x1 0x1e)
0x6da5bbb8 : 0x3e8169 (0x87069c0 0x0 0x6da5bc08 0x0)
0x6da5bbd8 : 0x186b84 (0x87069c0 0x9120348 0x1e 0x6da5bc08)
0x6da5bc28 : 0x12d17c (0x8bdbba0 0x940a5a0 0x8 0x11d965)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.digidesign.mbox2.driver(7.3f117)@0xbc3000->0xbe4fff
dependency: com.apple.driver.AppleUSBMergeNub(3.0.3)@0x648000
dependency: com.apple.iokit.IOAudioFamily(1.6.4b7)@0xb02000
dependency: com.apple.iokit.IOUSBFamily(3.0.3)@0x619000

BSD process name corresponding to current thread: UserEventAgent

Mac OS version:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)




Model: MacPro1,1, BootROM MP11.005C.B08, 4 processors, Dual-Core Intel Xeon, 2.66 GHz, 5 GB
Graphics: kHW_ATIr580Item, ATY,RadeonX1900, spdisplays_pcie_device, 512 MB
Memory Module: DIMM Riser A/DIMM 1, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 512 MB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 3, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 4, 1 GB, DDR2 FB-DIMM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (4.170.25.8)
Bluetooth: Version 2.0.0f20, 2 service, 0 devices, 1 incoming serial ports
Network Service: Built-in Ethernet 1, Ethernet, en0
Network Service: Built-in Ethernet 2, Ethernet, en1
PCI Card: ATY,RadeonX1900, display, Slot-1
Serial ATA Device: ST3750640AS P, 698.64 GB
Serial ATA Device: ST3250820AS P, 232.89 GB
Parallel ATA Device: PIONEER DVD-RW DVR-112D
USB Device: TRAVELDRIVE 005B, Memorex, high_speed, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA
USB Device: Hub in Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 500 mA
USB Device: Apple Optical USB Mouse, Mitsumi Electric, low_speed, 100 mA
USB Device: Apple Extended USB Keyboard, Mitsumi Electric, full_speed, 250 mA
USB Device: hp LaserJet 1012, Hewlett-Packard, full_speed, 500 mA
FireWire Device: built-in_hub, unknown_value, unknown_speed


Does anybody know what that "stuff" means? It mentions Mbox2 somewhere up there, but I don't even have it plugged in!

Any help is very much appreciated...thanks!

Did you ever...?

Did you ever find a resolution to this occurence? I am getting the same problem with my MacBook Pro. Drives me crazy.

It appears to be something with the IO USB interface you are using or maybe a USB hard drive going to sleep. Wake them up before you restart and see what happens.

I'll try to keep that in mind- thanks moosemissle.

The problem now is that it has mysteriously fixed itself (as before), but I'm sure it will come back again mysteriously in a few weeks (as before). But this time, when it does, i'll try what moosemissle said.