Sound fucks up every 2-3 minutes -

if it's starting to slow down it's very likely RAM related. 4GB is not a lot. You should also run a test on the ram. Otherwise, disabled antivirus? disabled wifi? different PCI slot for the soundcard?

Thanks for the reply! Yeah, I've tried disabling Avast. I've tried killing almost every thinkable process from task manager aswell. 4GB ram should be more than enough for what I'm doing. I'm running heavier software without any issues, and I don't have any huge soundbanks running. Usually only EZdrummer, sometimes some synths. Besides, it was running smooth in Windows Vista and back then I used VSTI much more. I should try putting the card in another PCI-slot. Think I heard someone mention this before. Thank you for your suggestions :)

Changing PCI slot did not work, unfortunately. Should I try to use ASIO4ALL instead of the EMU ASIO?

Thanks for input. I've ran latency checker before, but never while also running Reaper. Trying that now. Also tried to disable all stuff related to my HTC-phone. Allthough I think I've tried that before...

Yeah, when running latency checker, it does show bad latency as the problem occurs in Reaper. Strangely, this ONLY happens when running Reaper. Even when running Reaper, it stays well below 100 latency at all times, except when the problem with the sound occurs, and I get the following message: "Some device drivers on this machine behave bad and will probably cause drop-outs in real-time audio and/or video streams. To isolate the misbehaving driver use Device Manager and disable/re-enable various devices, one at a time. Try network and W-LAN adapters, modems, internal sound devices, USB host controllers, etc." So I guess I should try all that. The thing that I don't understand is that this ONLY happens when running Reaper. Also, I only get 1 pillar that goes red, the rest of them stays green - but the sound is bad for around 15 seconds.... Installing ASIO4ALL actually did seem to help slightly. The periods with problems are shorter and not as distorted as before. I'll go through my drivers in Device Manager, I guess. Thanks again for input. You guys disabling your normal network adapters, by the way? That would mean no internet access?

Thanks again for more input. Strangely - and this is quite strange, I think, when I disable all network connections, I still get the fucked up audio but no red pillar in Latency checker. It never goes above 380us, but it stays above 340 for all 15 seconds. When network was enabled it went up to around 8000us on a single pillar then back to less than 100us. This is becoming more and more aargh! I'm going to try to disable the paging file in Windows now, as apparently that could cause stuff like this...

My PC used to work fine, then I started getting problems. The following helped me to get to the bottom of it, but this was for a Vista 32 bit OS. I opened the Task manager, clicked on the processes tab and sorted the processes by CPU usage. Then I ran the dpc latency checker and watched to see if any processes increased their CPU usage to coincide with the occurrence of peaks in the dpc latency checker. It took a while, but I eventually spotted that something called IAANTmon.exe increased its CPU usage at the same time that the red bar occurred in the dpc latency checker. If I stop IAANTMON.exe, the problem goes away and my computer still functions OK. But before you kill any processes, do a bit of Googling to check that it's not going to cause other problems. Pet

Hi Strat. Funny that you just posted, cause' that's what I'm doing at the moment. I noticed that my CPU stays at around 40% usage most of the time, but when the soundproblem appears it goes to 100%. So at least now I think I know that it's the CPU being overloaded. I'll do as you did and watch out for cpu-usage when the problem appears. Have 4 cores though, wonder if that makes it even more advanced. How about only letting reaper use 2 cores, could that help?

Ok, further suggestions and help would be most welcome. This is getting more and more frustrating. I was checking up on which processes were swallowing all of the cpu power when my sound problem occured and the process doing so was... ta-da: Reaper.exe! To add further drama to the whole thing, I got the first blue screen and shut-down I ever had since installing Windows 7 a year ago. This happened as I clicked on stop in Reaper during the sound problem. I've done that plenty of times before though, without that happening. This time I had the task manager window open at the same time and maybe it could be a matter of timing - pressing that stop button at the right (wrong) milisecond...? Checking out my event log, there's kernel-power error clearly indicating that the CPU was overloaded, I think. Now, the question is: why would Reaper suddenly use all of the CPU and even overload the whole system for 15-20 seconds every third minute? It runs smooth most of the time, this happens every 2-3 minutes (and seems to increase in occurance the longer it's loaded). Anyone got the slightest idea why Reaper would do this? Suggestions appreciated.

Some more strange info. When I'm not doing any playback in Reaper, the latence seems ok, but the interface becomes unresponsive or "lagging" for 15-second intervals, just as it would during the poor latency periods. I'm going to try to upgrade to v. 4, see if that helps. Should I get the 64-bit version?