Here's the chain of events:
 
Sunday afternoon - hold final recording session using Sonar in BootCamp mode with my MacBook Pro (i.e. in Windows).  Save work but don't close Sonar.  A few hours later, listen to streaming audio of a radio station; sound comes through external sound card (FP10).  Close streaming audio, close Sonar, and shut down.
 
This morning (two days later, not having used soundcard or Sonar since Sunday but having used the Mac in Mac mode a few times) - start up laptop in BootCamp mode.  Get notice that there are windows updates being installed.  Get blue screen of death somewhere in that process.  Start up in bootcamp again in normal mode.  Windows updates continue and seem to work.  Windows appears to function.  FP10 appears to be in working order (blue light is on and properties in Windows says it is working properly).  Open a project that I was working on Sunday, but got message that the audio engine does not support the song's settings or the audio engine is in use.  Then everything is slow in the song (e.g. starts running a couple seconds after hitting Play) and get audio dropout almost immediately when it does start going.  Even when it does run a couple of seconds before audio drops out, there is absolutely no activity on any of the peak meters (tracks or master).  Tried a song that was not part of Sunday's session and same thing.  Rebooted and started in Mac mode using Studio One and in there, there is no audio dropout and the peak meters do respond, but there is still no sound out of the.  Went back to Windows and Sonar and try WDM drivers and still no response.
 
When in Bootcamp, I went to the properties of the Firepod and tried deselecting the options in the Advanced tab for Exclusive Mode, thinking that maybe whatever drove the streaming audio on Sunday evening still had a hold on the FP10.  But that didn't do anything either.  So I no longer know where to turn.  It could be Windows (given the update and blue screen of death); it could be the FP10, given that I don't hear anything in either Mac or BootCamp (Windows) mode - I doubt that it is Sonar though, but who knows, given that I don't see any peak meter activity, which Studio One does have.  The one thing that is different on Sunday that I don't think I did before since I moved to my MacBook Pro was listen to the radio over the internet (streaming audio) while I still had Sonar open.  I can't help but think that the problem is somehow rooted in that ...
 
I am recording a Christmas album for a local teen band and they want to begin distribution in a couple of weeks, understandably, so their friends and family and whoever can enjoy the Christmas songs during Christmas season ... obviously.  I am no expert in home recording or computers, by any means, and am doing this all pro bono, so ... Help, please!!
 
 

I just tried doing a system restore in Windows (Bootcamp) but it gives an error almost instantly that it was unsuccessful, no matter which restore point is selected.  So I guess that is off the troubleshooting list of possible fixes ...

i think you may need to transfer the project to another machine to get it finished in time? good luck

Sounds like the Firepod's sample rate changed, and SONAR can't force it back for some reason. The Firepod should have a standalone ASIO Console app that you can use to reset it. You should also be able to access that console via the "ASIO Panel' button in Preferences > Driver Settings.
 
This can also happen if the driver didn't load properly and SONAR isn't seeing a clock signal from the interface at all, in which case a driver reinstall or just a reboot might be needed.
 

I wonder if your sample rates have got screwed during the Windows updates?

I think the sample rate may have been changed when you were listening to streaming audio. This has happened to me. As others have mentioned you should be able to adjust your sound cards sample rate through the ASIO panel.
 
Good luck and I hope you get it straightened around.
 
Regards,

IF the above does not correct the issue, perhaps the Windows update process had a bad hair day.
 
If nothing else can be done, you could back up all of your data files and reload the OS, then reload programs and data files.  It would suck to have to do this, but if you end up with no other options....
 
If you did the above, you would also need to apply a boatload of maintenance prior to installing Sonar and other application programs again.
 
Bob Bone
 

What they all said...

Thanks everyone for your suggestions.  Before getting radical, I thought I would try recreating the problem, in a sense, based on my impression that my Mac was still "hooking my soundcard into" the streaming audio engine.  So I had sonar running and then opened a video (with audio, of course) from YouTube.  Much to my surprise, it played out of the soundcard!  So then I went back to Sonar and started up one of the songs.  Lo and behold, it played, too!!  I really can't explain it (and that worries me a bit).  So I didn't touch anything and finished my mixing.   Didn't want to chance screwing it up.  But I must confess I am now worried I will have to start some kind of audio from the internet before I can use the soundcard with Sonar or another DAW.  Anyways, I am happy it is working for now, at least.

Since it is up and running I'd set some backups up if you haven't all ready. Glad to hear it worked out for you.
 
Regards,