Windows 7 Audio Glitching

I am running a dual core AMD 4400X2 (Dual Core) with 4 GB RAM. Separate hard drives for the OS and audio.
 
I had this system running fine with Windows XP.  Decided to try Windows 7 64 bit.  Now when I record, it has a clicking sound (even with one track).  It did NOT do this even when playing back 20+ tracks with plug-ins on XP Pro.
 
Any Ideas?  I have not touched the defauslt installation of Windows 7 (Aero on, UAC on, etc).  DO I need to run the black viper tweaks?
 
http://www.blackviper.com/Windows_7/servicecfg.htm
 
Is there some key to all this?   Note I DO have the 64 bit driver for my Presonus FirePod.
Should I be using the ASIO or other driver?
 
Geez I hope I don't have to go back to Windows XP, I like the 64 bit interface.
 
 

Check your DPC latency:

http://www.thesycon.de/deu/latency_check.shtml

I had issue on an Intel system (I know you're on AMD) when I first switched from XP to 7, and found that there were some BIOS tweaks that needed to be done. There are functions in the BIOS that XP ignores, and VISTA and 7 recognize that cause issues. Not sure what it could be in your case, but it's worth a look.

I dont have X1 on Windows 7 64 bit currently but I do have a laptop running on Windows 7 64 bit with an i3 processor and 4GB RAM running other popular music programs and DAW (mainly for performance) and I most definitely believe your machine SOHOULDNT require any OS tweaks to run a simple audio track in Sonar.

I think you should look elsewhere or even better wait for responses from experienced 64 bit Sonar uses but definitely not fiddle with your OS. Actually as time goes by, Im more and more un-eager to fiddle anything on OS level because experience has shown that usually these tips are sometimes inaccurate or generally not applicable or at their best do not provide such a performance boost they promise. Most of the times you might get the oposite result of what you were hoping: recent example being, disabling AERO in Vista and 7 because ppl thought the simpler graphics would un-strain the system which later on was proved to be a false assumption.

So, the last three years or so, the only thing I do in my OS is just simply disable windows sounds - nothing other than that! ;)

had issue on an Intel system (I know you're on AMD) when I first switched from XP to 7, and found that there were some BIOS tweaks that needed to be done. There are functions in the BIOS that XP ignores, and VISTA and 7 recognize that cause issues. Not sure what it could be in your case, but it's worth a look.

emwhy

What BIOS settings needed changing?  I know we are on different platforms,(AMD vs. Intel)  but knowing which direction to look may help. 
 
 
 
 

Have you checked energy options in Windows 7?

Windows 7 is good at unwanted energy saving, especially on Notebooks, and AMD adds to the confusion with its own energy options.
Things like stopping harddisks after 20 Minutes, or applying USB-enenergy management without you ever having decided about these options may lead to funny results with music applications.

Just check your energy settings, and click the advanced settings there as well.

Normally firewire has its own controller, but I'm not sure how Windows 7 handles it.

Patm

It seems to be a problem with The firepod and the window 7 drivers for the firepod.  I too tried Sonar X1 with windows 7 as a new OS install and I had the same problem... Popping, Clicking..and slow audio.   I changed from WDM to ASIO back to WDM and my buffer settings as well and nothig helped.   I removed Window 7 from my PC and re-installed XP SP3 and the old Firepod drivers and All worked well.   I am stayig with XP SP3 with my Intel QUAD Core 4GB machine.

Peace.