First of all, hi to everybody it's been a while since the last time
I was very furious about midi hanging up at the time ( 5-6 months ago ) and blamed the Scope, yelled and screamed at the CW staff, but now, I am pretty shure that HT causes the trouble in most cases. If you have a HT processor (I had intel@3,0 GHz 1MBcache s478 i865p mobo), there could be odd freezes all the time.
1. Disable HT (by disabling apic acpi support in BIOS or during OS install , in my case - simple disabling HT support in BIOS didn't help - refer on how to do it in this forum, or the net)
2. Do not use Scope's midi (delete "midi seq dest" module from your project)
3. Do it as I have - sell the damn processor and buy AMD ATHLON - I hated AMD a lot, but now I changed my mind. They improved since the old days.
This could not be a solution for your case. It was for me - I tried two completely different configs, part by part, keeping only CPU, and the problem persisted.
Some other people suggested midi filter - I don't agree 'cause I had midi filtering on my KORG KONTROL 49 - no midi sense was transmitted.
I hope I was of some help to you...
BTW, I am going back to Intel, but this time CORE2DUO and p965 - I hope it will work.
One other thing: CW stated at their documentation that working in 2 processor environment may couse trouble - so since HT presents an extra core, making your system see 2 vitrual cores instead of one real, I think this may lead to unstability ( who knows what dark magic has been involved in that to make 2 CPUs out of one

)
Core 2 Duo has two cores also (two real ones - no HT and similar dark sorcery), but there are many users with dual core CPUs and no problems at all... We'll see...