10.5.3 MacBook Dual Monitor Crashes

Question

I've noticed what I consider to be a *very serious* problem with 10.5.3. In the week since installing 10.5.3 on my MacBook C2D/2Ghz/3Gig RAM I've had 2 hard lock-ups. Another MacBook owned by my company (similarly configured) has also experienced a hard lock-up under the same scenario that I'm about to describe:
I normally use my machine while I DJ (with Native Instruments Traktor) along with GarageCube's Modul8 to run an external display. Prior to the 10.5.3 update, I've never had a problem with this setup (I should also mention that AirPort was off). However, this past weekend, I experienced a hard crash running this config. Normally, I would have been alarmed (as any hard lockup will do), but I'm even more troubled because we had the same kind of hard crash on another machine similarly configured but running QuickTime Player instead of Modul8 (for the second display).
Initially, I had attributed this either to my DJ program or my Video program, however today, I was in the office using a totally different set of apps (but still with a second monitor connected) and I had another hard freeze.
As if the hard freezes aren't bad enough, it doesn't look like ANY log entries are being generated as a result. Neither do I get the "This Computer Unexpectedly Restarted" dialog when restarting. I know that the 10.5.3 update worked on a lot of graphics stuff (particularly related to the MacBook), but it looks like more things were broken than were fixed (at least as far as my setup is concerned).
Has any one else experienced this type of problem?
I've tried all of the routine troubleshooting stuff, but like I said, when it happens on one machine, it's one thing, but when it happens on two different machines, then I really start to wonder...

Answer 1

With all due respect, I highly doubt that there is some connection between Modul8, QuickTime Player, and Daylite (a CRM app from Marketcircle) that's causing this crash. Moreover, OS X really should be able to handle a flaw gracefully if it is application based.
As for the backup, like I said, this is something that's happening on two different machines. If you're suggesting that something went wrong on two different systems, I would have to say that it's more of an Apple issue than it is an isolated incident...
And, no offense, but I know all of the hoops I could try to jump through (e.g. reinstalling, etc.)... What I'm really looking for is to see if others are experiencing the same problems and, if so, if they've been able to trace them down. In short, I just don't have the time to try to shoot at this issue with a shotgun type approach. If the only way to fix it is to go back to 10.5.2, then that's what I will do, but if that's the case, then I hope this is something that Apple takes notice of and makes an effort to address sooner rather than later...