I have tried the Jmicron kexts and they were incompatible with my board (caused a KP at boot).

Here is the output from the console - I'm not sure if this is the actual panic. The log was written at the same time as the panic, but OSx86 machines don't log to panic.log like real apples do? I have set debug 0x100 so next time it panics I'll take a photo.

Title "SystemUIServer_2008-12-19-215719_Bluemeany.crash

Process: SystemUIServer [744]
Path: /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer
Identifier: SystemUIServer
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1]

Date/Time: 2008-12-19 21:57:19.374 +1100
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 com.apple.CoreFoundation 0x96ad8688 CFDictionarySetValue + 40
1 com.apple.systemuiserver 0x00020f68 0x1000 + 130920
2 com.apple.systemuiserver 0x00009022 0x1000 + 32802
3 com.apple.systemuiserver 0x0000618a 0x1000 + 20874
4 com.apple.systemuiserver 0x00005cb6 0x1000 + 19638

Thread 1:
0 libSystem.B.dylib 0x9136268e __semwait_signal + 10
1 libSystem.B.dylib 0x9138d36d pthread_cond_wait$UNIX2003 + 73
2 ...e.ImageCaptureNotifications 0x000d2eaa _StaticProcessIOObjectsArray + 95
3 libSystem.B.dylib 0x9138c6f5 _pthread_start + 321
4 libSystem.B.dylib 0x9138c5b2 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x9138bf66 kevent + 10
1 libSystem.B.dylib 0x9138c6f5 _pthread_start + 321
2 libSystem.B.dylib 0x9138c5b2 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0xa08824ec ebx: 0x96ad866b ecx: 0x945cc858 edx: 0x00000010
edi: 0x00000000 esi: 0x00523940 ebp: 0xbffffc68 esp: 0xbffffc10
ss: 0x0000001f efl: 0x00010283 eip: 0x96ad8688 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000


There was a heap of other stuff about binary images too.

Normally I can't deciper the panic dumps on the screen. They all have 14=page fault at the top, and don't point to any kext as the cause.

Thanks for your help guys.