tlw
So, corrupted drivers by the sound of it (fingers crossed). I had similar problems with drivers some time ago, and a re-install sorted it out, which is why I suggested you give it a try.
I've no idea what caused the problem in the first place though or whether it was a Sonar issue or a Vista/Windows one.
What I figured out was this. It was not the updates that caused the problem. It was the update process! I wonder if I would have had these problems if Microsoft did not update during a time when I was not using those drivers. Maybe I would still have the problems I don't know.
It has been my experience over the years when Microsoft installs updates, it downloads them then in most cases it installs them. The message in the update window will indicate what number the update is when it is installing.
Once done if any update has anything to do with the operating system the update process will ask for a reboot. Sometimes when you reboot the computer upon shutdown the updates go through a reconfiguration process. When I watched this there seemed to be a 3 step reconfigure on shut down and boot up
The latest round of updates downloaded them and installed and reconfigured the computer upon shutdown. When this happened Microsoft shut down most of the services running in the background. I closed the project I was working on and shut Sonar down, but maybe Sonar was not completely shut down and part of the program was working in the background when Microsoft began to take over the computer.
I think and suspect that something happened during the reconfiguration process to make the drivers unstable. Maybe something that was changed in the registry file caused a conflict. If it were the updates themselves then Sonar would still have problems.
I ran several tests last night and everything is now working fine. I want to thank everyone for their input and help.