Am I reading your posts?  Really?  
 
I have gone to the point of searching for, downloading, and reading multiple sets of documentation for your Allen & Heath, not to mention all of the searching the web for other things related to the known information, trying to help you make progress, including looking up error codes, potential fixes, other people's similar issues, etc., in addition to looking up the specs for your motherboard AND for it's supplied Firewire chip set.
 
I have put in quite a bit of time trying to help figure out what was happening, some of which was wasted, due to incomplete information, such as neglecting to let me know you had disabled the on-board Firewire ports.
 
And still you have not supplied the requested information on what chip set your second Firewire card has.
 
I believe your system has hardware and/or software conflicts that will not likely be solved without your changing one or more hardware components, most likely your motherboard, and possibly your secondary Firewire card, or possibly both.
 
I believe you might make some progress by physically removing your secondary Firewire card, reloading Windows, applying all maintenance, checking for errors in the Event Viewer, taking a system image if the hardware errors had gotten resolved by removing that Firewire card (you would be able to use that for recovery to a stable point later, if needed), shutting down, restarting and disabling the NIC, putting the Firewire card back in, restarting, THEN installing Sonar (and completing manual completion of Sonar registration - which I think you can do, but am not sure), NOT yet installing other applications, taking another system image, then proceeding with installation of other applications.
 
The above MIGHT get you farther, by completely avoiding the now known conflict between your NIC and your Allen and Heath.  No guarantees the above would work, but it to me a logical path to pursue.
 
In any case, I am bowing out of this thread.  CLEARLY, you have system issues not related to Sonar, and quite frankly, your asking if I have been reading your threads is a bit insulting, given my level of participation.
 
Best of luck with it all, 
 
Bob Bone
 
 
 

Thanks Bob...but some of the questions you ask I have answered in previous posts.
 
My Power supplies I use exclusively in my builds are made by Corsair and go in spec between 750watts and 850 watts...more than enough power is supplied to the system mother boards...I believe it is a 850 watter I put in that Music machine..but if it is a 750 watt supply it is no of concern as it is working well.
 
I see you are reading into the events...as one is saying power might be a issue...it is not power shortage that caused the error there...I turned off the system because it was hanging!...by reset button....I know this is not the best solution, but sometimes it is the only one to do to solve for the hanging of Win 7...or xp...as I have no way to gain control of the OS when in that state.
 
So ,.,,removing the firewire B 400/8000 and using the onboard firewire is not going to work with the allen and heath audio desk properly either....As it is not recommended to use this onboard firewwire chipset.
As it is disabled in Bios, there should be no conflicting issues with the one installed..
But perhaps You may have more reason to believe it does, than I...as I am not up to speed with win 7, and these boards and how they work....when turning things off in Bios...and how the os and mb resolve that.
 
I have not neglected to inform...if I am using a PCIe x1 firewire card, do you think having the onboard one would work well?...No...in my specs that are tagged to my posts...You will see I have installed a 800 firewire card, and made not to put redundant things or pairing same devices in play....redundant things have been turned off in Bios..in the statements below the specs of my system Bob,,,no disrespect, but in every post your Question has been answered in some way...and all the posts I have made over many moons...and such Bob....THanks for reading up on the events....and doing some leg work... all of you...very helpful indeed ...
 
It seems the install of Sonar products along side the others was part my fault in doing incorrectly...perhaps.
Also Somewhere something was not installed correctly with Bitbridge or rewire...and Acid/sony/FL studio/Propellerhead/ has installed a lot of Plugins and such in past installs..and will continue to do so if I do not resolve some issues with OS knowledge of how to install them..
I also have some Wave Musicians Bundle, and Sasquatch Plug ins I want to use on the Music system....Some 32 bit and some 64 bit....(Sonar counted in total 280 plugins when scanning)
I will also be installing East west Play and using three libraries of theirs soon.
Also have to install XT midi device, and the Korg Kronos x stuff again.
 
Installing them softwares more neatly and with admin rights given by following the advice of you Bob, and any instructions by the manufacturing companies of these thing, and compatibility  mode for some sony products and others...if this should work out..But I believe that compatibility mode is questionable..as Acid Pro 7 crashes period on all the OSs I used it on.
 
As the 2nd tech said, There is nothing wrong with the new install of win 7 at this point, and everything is working and has been installed ok..in regards to updates....(So I got that right
? )...even though we have new errors and warnings and critical errors happening at the get go...it's normal...So AlexS is correct on that common remark...( So let's wait a bit for Microsoft to chime in  tonight,  so you do not waste leg work on this...I will ask for a summation be written down of the things done/found, and how they were resolved more technically speaking...SO I can post some stuff up for others to read who are having issues like I was.
 
Seems the Admin install the way you instructed, might be the cure all.
And using compatibility mode for older applications might make them work better..SO more learning...more possible problems ..and more circles to come....but it is coming to a resolve of sorts..
 
So yes thank you, as I believe I have said....You all gave me hope...You helped me see the corruption...and I made choices to solve them my way, and yours.....Perhaps this cannot be resolved with said devices on the table.
 
So one more go...and then if this continues to be buggy... I think I will move the second x79 build in to take over...and move Asus Sabertooth 1366 x58 to the other end of the studio.
 
See resolves are coming...one way or another.
 
Thanks Bob and all the rest...please stand by...I am going to install more things, remove someothers and reinstall them again, finish installing sonar candy, and run them for a test drive...Before the call comes in from Microsoft....and I believe I have 30 days to still run the ticket if anything goes south after that call.
 
 
Cheers!
Sir Les.

As it was, last night I reinstalled win 7 pro, and did updates most of the night, and into the morning hours to get the system fresh..
Once done these errors and event logs were noticed , with some odd behavior.
 
Just to confirm you wiped the partition and started again, you didn't just install windows on top of windows?
 
Cheers

When installing from the dvd...I selected to format the partiton C: or 0 as usual.
Once done I continued to reinstall the OS.
I am not sure if the boot partition gets wiped out with formatting on SSD....in that formating of the Partition.
 
So is there a issue?...please advise if so.
 
Thanks AlexS

Nope just checking - cheers... I would get that virus scanner out (just a precaution!).  You probably know already that you can generate reports about your system via msinfo32 app bundled with windows.

My purpose in asking you to physically remove the installed Firewire card was to avoid any conflicts from it, and was not requesting you to enable the on-board one.
 
I had wanted you to completely remove ANY Firewire card, ONLY for the purpose of getting a clean Windows 7 install, by not having any chance of a conflict from your secondary Firewire card, and also I had not asked you to enable the on-board one.
 
Since at least part of the issue, from what I understood, is a conflict between your NIC and likely your secondary Firewire card, and since you need NIC access to the web to download Windows 7 updates, I suggested you FIRST get Windows 7 installed cleanly, by removing that secondary Firewire card - thereby also not connecting your Heath and Allen.  AFTER getting a clean and updated Windows 7, and AFTER taking a full system image, THEN you could proceed with other installations and disabling NIC and all of that, including putting the Firewire card back in.
 
Bob Bone
 

No, I did not know about msinfo32...but I believe something like that was done by the 1st Microsoft tech, and given to the 2nd tech...cause the second tech did not want to really go into the eventviewer...he did open some applet..?.but he closed it real quick, and I did not see what it was.
 
So thanks for that tip...I will check all of my systems with the eventviewer, and the msinfo32 thingy...from now on.
 
Defender was installed on updating also....and you like the UAC left on...and so I left it alone...wink.
If you guys want something from that msinfo posted let me know...
 
I know the x79 build is long in coming to the forefront...but I am still building up slowly my software for music on it, and testing Motu pre 4 usb with UAD Solo card....It seems to be working with Protools 11....but I want to make sure the system is stable, and all things installed are working right as rain before I move it, if need be...if so I have to swap out the audio devices,and UAD card ...and that opens up a hole new bottle of worms.
So I am trying not to go that route....as that x79 system was intended for mastering, and video editing.
 
But it looks like x58 is not able to do what I wanted it to..with win 7....my opinion is being made as we go backwards to go forwards.

Hi Bob...My IRQ's are posted...there are no conflicts happening...that is something I learnt to sniff, and resolve out on many many builds and bad experiences, and trouble shooting folly...with mead in hand...I think I got it right...but windows is still sharing virtual Irqs all the time...So who is to say its working correctly...one day it is fine, the next time you boot something isn't fine....I think it is a random virtual sharing technic Microsoft employs....sometimes...LOL.
 
So you think it is the firewire card?...can you be more specific as to what is drawing that line?
 
thanks
 

Firewire, and nic work well together..If I turn off my ALLEN AND HEATH r16 mixing desk, the driver for it is not installed or loaded...all internet functions work ok.
If I turn on the mixing desk, the driver gets loaded and then we get odd to bad behavior.
 
It is tied to the firewire card, but it is not the card persay...it is the r16 mixing desk drivers and how they work with the firewire card...that is the issue when the Nic card is on....from what I was told by the technician...and there is no work around or fix to make them behave together...So turning off the nic when using the mixing board solves the problem.
 
And towards AlexS...If the Nic is off ...and my system is clean..there is no need for security to be running in the background.
No Networking..So some of those services can be disabled...or put to manual or delay start.
Same with auto updates and apps....not going to be connecting to the net...so to defeat that...disable them aswell.
 
See...my logic?
 

Now to send error reports to CW when the crashes occur...I have to open a music app with the board? and internet...to send it...which causes logs to be made...some of those errors are from doing just that...before the reinstall of win 7.
And to use the online help while trying to setup and use Sonar...this is a big problem for me....more logs made for mead consumption....
 
Another solution coming to mind is the New coming Mac computer with thunderbolt, which A&L say the firewire r16 will work with, with a adapter.
 
And I wil then need to move to another software platform like Protools.