Audio Dropouts

This is actually a fairly common scenario: somebody writes that they've got a top-spec machine with gobs of RAM and yet they can't play even a one-track project without dropouts.
 
It's frustrating because no one can tell you with certainty what your exact problem is. However, when it happens it's always for the same general reason:  one or more of your computer's resources (CPU, RAM, I/O bus or disk bandwidth) is overburdened. The computer doesn't have enough time to process the audio data and fill the output buffer before it needs to be dumped to the interface.
 
Remember, audio data needs to go out at a specific consistent rate, e.g. 44,100 samples per second, not whenever the computer can get around to it (like with other types of I/O such as copying a file). If it can't fill that buffer in time, the resulting data underrun causes an interruption in the data stream and you hear it as a click or a pop.
 
One thing you can do is give the CPU more time to fill a buffer by making the buffer bigger. That may or may not always be practical, though, because it also increases latency. But when latency is not an issue, such as during a mixing session (versus a tracking session), then increasing the buffer size is the easiest way to deal with dropouts. If you're using ASIO, open the ASIO driver's control panel and adjust the buffer size in bytes. I usually run mine at 2048 for mixing and almost never have dropouts, and my machine's not nearly as powerful as yours.
 
In severe cases you may not be able to increase the buffer size enough to eliminate the dropouts. When that happens, you have to become a sleuth and ferret out the underlying reason why the system can't keep up. More often than not, it's a software problem - something is monopolizing the CPU or the I/O bus to prevent it from paying enough attention to audio.
 
The first place to look is the Windows Task Manager. Look for processes that are eating large amounts of RAM or CPU cycles. Sometimes it'll be a Windows service (e.g. svchost.dll) that's gobbling all your memory. That indicates a service that probably shouldn't be running while you're recording. Public Enemy #1 in that camp is the Windows Automatic Update service. Shut that bad boy off. Another common culprit is realtime antivirus protection. Disconnect the network if it makes you feel safer, but shut down any anti-malware software for audio sessions. 
 
If you don't see any obvious villains on the task list, it's possible that the resource hog is just not showing itself. Lots of things are going on in the computer that don't have the decency to report themselves to the task list. One of the most common are Interrupt Service Routines, and their hitman partners in crime, Deferred Procedure Calls.
 
ISRs are little programs that respond to hardware interrupts. They run at a priority that's so high it's not even part of the prioritization scheme. Everything stops for an ISR. They're supposed to be short and fast, to get in and out quickly. But some devices can't resist the allure of being king for a millisecond and employ ISRs that take too long. Or, they're just very badly written; that happens, too.
 
In order for an ISR to not totally screw everything up by abusing its elevated status, it usually hands the heavy interrupt-handling duties off to a cohort called a DPC. This is like a low-level henchman who, unlike the ISR, has to wait in line like any other process. But even though the DPC may be better-constrained, it still runs at an elevated priority and if it's not well-behaved can wreak havoc. The salient point here is that when an ISR or DPC is running, audio is not being fed to the output buffers. 
 
The #1 suspect for excessive DPCs: wireless network adapters. Always disable them for DAW sessions. Second in line: network adapters in general. If there is no need to have an active network, kill it. Third suspect: fancy video adapters made for gaming. They assume that nothing is more important to you than screen refreshes and frame rates. If you bought a $400 video card because Half-Life will play with cinematic smoothness, ditch it for a $60 generic card that won't dominate your DAW. Or turn off every advanced feature and acceleration option.
 
I'll have to leave it there for now, as I've got to get back to work. Hopefully this'll at least give you something to mull over.