Hey everyone!  I'm new to the forum here, so bear with me as I try to post my issue.
I'm running Sonar 8, Producers Edition, using a PreSonus Firepod FP10 using ASIO.  Dell Latitude E6520 - Windows 7 Enterprise x64, 8GB RAM, Intel Core i7 2.8Ghz.
 
What I'm running into is I'm using multiple tracks from the Firepod to record direct outs from my mixer, and when I'm recording, the Firepod will glitch and stop recording in random spots - Cakewalk continues recording, but the audio just drops, then will come back.  I feel it has something to do with the laptop, because I've used the same setup with my desktop and didn't have this issue.
 
Any ideas on what to check?  I'm running 44.1kHz with latency set at 32 samples.
 
Thank you for any advice you may have!

My guess is you buffers are set too low. 

I agree, 32 samples is too low I think. Have you tried raising it?

Bibs

For whatever the worth, I record using an ASIO Buffer Size of 128 samples, and that seems to be a good balance for my system and hardware.
 
I have tested going down as low as 32, but had some issues and raised it, eventually settling for 128, which I never seem to have to change, while recording.  (when moving on to mixing, I bump it up to 1024, to allow for effects with look-ahead processing and such).
 
I also suggest you look to see if you have your laptop's wi-fi adapter enabled, when you are running Sonar.  The reason I mention it is that wi-fi adapters are notorious for causing massive DPC Latency spikes, which can cause intermittent dropouts, crackles, and such.  Soooo, what lots of folks do is to shut off their wi-fi adapters, either using a switch - if available, or they go into Windows Device Manager and disable it their, just prior to launching Sonar.  Then, when they finish their Sonar session, they turn the wi-fi adapter back on, or enable it, and then web access is immediately restored.  That seems to be quite helpful, so again, I urge you to give this a shot, too.
 
Bob Bone
 

Ya what Bob said about laptops and many issues are related to DPC latency issues. Download the DPCLAT latency tester and see what's up, It works with XP and W7 but gives false reading of 1000ms on W 8. But I'll agree your asking for trouble if tracking multi tracks at 32. 
 
http://www.thesycon.de/deu/latency_check.shtml

same here, I can ocassionally get away with 32 or 64 early on in a project, but 96 -128 seem to be pretty stable for me. what bit depth are you recording at? Did 8 PE have PDC(plugin delay compensation) button? If not, you may want to run lean when recording to reduce latency.Disable whatever plugins you can while tracking. That will help all the way around.