For reference, I tried simply turning off the wireless (unchecking "enable wireless" in the network settings) and that didn't help.
Try turning it off in the BIOS. If your problem is a piece of hardware asking for something to do every so often, then there may be a difference between OFF and Windows-Is-Not-Using-It.
With care, try turning off any other stuff you see there that you may not need.
Try to do it one thing at a time --- for the obvious reasons, and take careful notes of what you change
for the even more obvious reasons!
There's another thing, which I can't just now remember the details of: if you have a multicore processor, make sure all the cores are handling hardware interups. If you need, I'll try to dig that out, but others here are much better informed than I am anyway.
"The main goal in audio-processing is the latency. The latency is the delay between signal-creating and reaching the processing in the system (e.g time between pressing a key on the keyboard and hearing the tone)
I don't think I agree. The main goal in audio processing is not to be interupted
--- which is the goal of the real-time
kernel. But it is a confusing word, and there is, I think, a definition of latency which is how long your process is guranteed the CPU's attention without being interupted.
None of this is the same as the latency displayed by Jack, which is the latency you guys want to know about when recording, monitoring, etc: the one that makes it hard to sing when the sound in your headphones is noticably behind your voice.
There is something horrible called DPC latency. Google will explain. It is just nasty beyond words, and can make a PC unsuitable for even playing background music.
my intellect says, "hey, you're assuming everyone here is male (and heterosexual at that, or is a lesbian woman I guess).
Mine said, Hey, there's a recipe for electrocution!