Upgrading from 10.6.7 to 10.6.8 issue with GUI

Question

Hi,
I've been trying to upgrade 10.6.7 to 10.6.8 multiple times now on my MBP and gets to the same error every single time.
10.6.7 runs like a charm - no issues no nothing.
I download 10.6.8 v1.1 combo pack and try to install it, it runs and want to restart. Once it boots all I get is either a screen switching/flickering between the apple logo or an orange screen. At this time I'm able to access the shared folders from another mac on my network and check the logfiles that it's done with its upgrade.
Here I notice the windowserver.log doesn't look like it used to do only stating :
Jun 23 13:54:03  [75] Server is starting up
Usually says:
Jun 23 13:21:24  [69] Server is starting up
Jun 23 13:21:38  [69] CGXMappedDisplayStart: Display0 : boot screen
Jun 23 13:21:38  [69] CGXMappedDisplayStart: Display0 : display alias 0x0 valid
Jun 23 13:21:38  [69] CGXMappedDisplayStart: Display1 : display alias 0x1 valid
Jun 23 13:21:38  [69] CGXMappedDisplayStart: Display2 : display alias 0x0 valid
Jun 23 13:21:38  [69] CGXMappedDisplayStart: Display3 : display alias 0x1 valid
Jun 23 13:21:38  [69] MPFinalizeInitialization: Display 0x3f003f unit 3 alias mask 0xa
Jun 23 13:21:38  [69] MPFinalizeInitialization: Display 0x3f003e unit 2 alias mask 0x5
Jun 23 13:21:38  [69] MPFinalizeInitialization: Display 0x3f003d unit 1 alias mask 0xa
Jun 23 13:21:38  [69] MPFinalizeInitialization: Display 0x4272100 unit 0 alias mask 0x5
Jun 23 13:21:38  [69] GLCompositor: GL renderer id 0x0102260c, GL mask 0x00000003, accelerator 0x00003137, unit 0, caps 0x00000003, vram 512 MB
Jun 23 13:21:38  [69] GLCompositor: GL renderer id 0x0102260c, GL mask 0x00000003, texture units 8, texture max 8192, viewport max {8192, 8192} extensions 0x0000000f
Jun 23 13:21:38  [69] GLCompositor: GL renderer id 0x0202260e, GL mask 0x0000000c, accelerator 0x00003c0b, unit 2, caps 0x00000003, vram 256 MB
Jun 23 13:21:38  [69] GLCompositor: GL renderer id 0x0202260e, GL mask 0x0000000c, texture units 8, texture max 8192, viewport max {8192, 8192} extensions 0x0000000f
Jun 23 13:21:38  [69] agc_attach: gMux mode is logout or safe (2)
Jun 23 13:21:38  [69] CGXPerformInitialDisplayConfiguration
Jun 23 13:21:38  [69]   Display 0x4272100: MappedDisplay Unit 0; Vendor 0x610 Model 0x9c84 S/N 0; online enabled built-in (0,0)[1440 x 900], Rotation 0, base addr 0x102000000
Jun 23 13:21:38  [69]   Display 0x3f003f: MappedDisplay Unit 3; Vendor 0xffffffff Model 0xffffffff S/N -1; offline enabled (2464,0)[1 x 1], Rotation 0, base addr 0x112000000
Jun 23 13:21:38  [69]   Display 0x4272102: MappedDisplay Unit 2; Vendor 0x610 Model 0x9c84 S/N 0; offline enabled built-in (2465,0)[1 x 1], Rotation 0, base addr 0x112000000
Jun 23 13:21:38  [69]   Display 0x3f003d: MappedDisplay Unit 1; Vendor 0xffffffff Model 0xffffffff S/N -1; offline enabled (2466,0)[1 x 1], Rotation 0, base addr 0x102000000
Jun 23 13:21:38  [69] Display 0x4272100: MappedDisplay Unit 0; ColorProfile "Color LCD" (MD5 378f9124977f17f13c5312687683813d)
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:24:10  [69] kCGErrorIllegalArgument: CGXSetTrackingAreaOption : Invalid tracking area
Jun 23 13:26:51  [69] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller SystemUIServer
Jun 23 13:26:56  [69] kCGErrorIllegalArgument: CGXSetWindowListTags: Operation on a window 0x6 not owned by caller UserNotificationCenter
I'm able to access it via SSH as well, if the setting is ticked in sharing option, and can see that WindowServer is using 100% cpu on the MBP.
Anyone got any idea on how to get it up and running again and get me to 10.6.8?
Yes I have reset PRAM, SMC, erase and install, etc. Every time I'm able to get the MBP to 10.6.7 without any issues. I've even tried to install the latest CUDA drivers for the nvidia cards which didn't make any difference.
When I start it in verbose mode the last line is:
[ PCI configuration begin ]
Anything would help...

Answer 1

I can add it's the same with upgrading to Lion... So I guess they changed some driver code between 10.6.7 and 10.6.8 and its not compatible with my logic board.
Annoying tbh..