[Solved] Possible Screen Freeze Source

I'm a 2 (actually 3) monitor user.
 
I tried using just one screen for all work on a project that was giving me freeze problems across 2 screens.
The project seems much more stable...no crash at all over the usual time working.
 
I don't know your set ups...just throwing this out there for you to try if you want.  If you are using just one screen, and getting freezes anyway, I want to hear from you anyway, if you like.  If you are a two-screener getting crashes try this and let me know if you get better results...or if there is no difference.
 
Thanks. 
 
[SOLVED] My UM-3G was plugged into a  6 port USB Hub, instead of into a USB port directly in the back of the Motherboard.  All problems are now gone.  Unbelievable.  Apologies to all for wasting your time.  Richie
 

It's no use.  Sonar froze when I was laying down markers.  Just did the June update too.  Sonar had only been open for 10 minutes.  I am now out of ideas.  I've done and tried everything, including using my studio B computer...Sonar crashes on that computer too.  But I'm using files brought over from this computer.  So the file has to be corrupted to begin with.  The only common denominator between the two computer is they are both made by HP.  The motherboards, processors, memory, midi and sound cards, usb devices, monitor screens and graphics cards are all different.  I have two very good computers, and perhaps I will list every component in both of them, but I am broken at this point.
 
I have 8 midi channels triggering 8 tracks in my Yamaha MOX6
I have one stereo audio channel for recording an acoustic guitar.
My guess is this is a midi problem with my MOX6.
My midi box is a UM-3G
The computer freezes when I press play on the spacebar, or move the cursor to a new spot on the timeline.
 
I doubt I would have these problems with all audio files.
Midi is causing the problem.
Specifically, midi coming into and out of the MOX6, and what those midi files end up looking and behaving like once they are inside Sonar.  Local control on the MOX6 is OFF.
Anyone else think this is a decent conclusion?
 

I stopped the song.  I forwarded the cursor to the END of the looped region.  I pressed play.
Crash.

Driver is up to date...
The only thing left is the motherboard, processor , and ram. 
 
Ok...I now have to devise a different method.  I will record all the midi tracks as audio.  Then delete the midi tracks.
 

That was it.  Midi was causing the screen freezes.  To be specific in this case, externally routed midi to and from an external hardware synth (MOX6).
 
I now have two versions of this project.  One all midi files and one all audio files.
The one with midi files crashes Sonar.
The one with audio files won't crash no matter what I do to it...even machine-gunning the spacebar.
 
So, Sonar.  Cakewalk.  What is the problem.  Midi?  Me?  You?  Microsoft?  Or Yamaha?
 
I have been here since Pro Audio 8, and the old Cakewalk Newsgroup.
My old name was R*lpo Mirac*lous, r*chiedoc, R*ch** M*ll*r, so some of you may remember me.
I wish I had my old forum account back...I lost control of it somehow...now I'm just some newbie with issues.
And I just bought the lifetime Updates pack.
 
Hello to all my old friends here.  Thanks for all the ideas over the last 6 weeks on various threads.  Good luck on your projects.  Relpo out.
 

Solved it Zarggs.  I feel like a moron...but thanks for your time.  UM-3G was plugged into a USB hub instead of directly into the back of the computer, in it's own motherboard USB port.  Now it all makes sense.