Sound fucks up every 2-3 minutes -

Thanks for all the suggestions. I've now tried - adjusting bit depth in Windows Control Panel - disabling my UX1 - did a memory test of my ram, they passed - did a general stress-test of my computer, it passed What puzzles me is that it happens around every 2-3 minutes, and that the process swallowing the CPU is reaper.exe. Surely someone must know what reaper.exe does every 2 minutes? Autosave is not enabled. Surely, some programmer must know what reaper.exe tries to do every 2-3 minutes? It sure can't be true that I can only use fewer vst's and tracks than the listed ones. I could use more with a weaker CPU in Windows Vista without any issues.

Now I've also: - uninstalled Autotune - uninstalled HTC Sync Still same problem. Argh.

Did you see KevinW's post about 'auto-save'? Do you have it enabled? At what interval? And for your VST use... it may not be the amount of VSTs you use, it could be one 'rogue' VST. The fun part would be figuring out which one. Also, have you tried updating your graphics driver? :cool:

Try disabling Cool'n'Quiet.

reaper.exe is only the host process and AFAIK Task Manager adds everything to the load display that's attached to that process, modules/plug-ins started by the process, driver, the lot. So it's not clear whether REAPER (least likely), a plug-in or a driver are so busy (or waiting) in that interval or if that's actually caused by yet another event/driver/service someplace else. - I asked you for a different ASIO compatible audio (and probably plug-in host-) software but that another interface shows the same issue rules out the audio system. Another ASIO audio software should show/confirm the same behavior since it's quite unlikely that REAPER is causing an system halting event every 3 minutes. - Does that also happen when no (or only REAPER-plugins e.g. ReaVerb to create some load on the tracks) plug-ins are running? If so, you know pretty re. - Did you go through the usual "optimizing for audio" guides? The only time I ever witnessed that setting Win Processor Scheduling to 'background services' (often recommended there) did something was with a (very obvious tho) GFX-card related issue. Can't harm to check. - A list/screenshot(s) of your running processes could help maybe - also bareboning the services could help you finding out what's going on. Since the system worked before and there's some interval involved, a new autostart item or service polling for the presence of a device or trying to access the internet etc. would match your description. Edit: Screenshots didn'l load before I was writing... what Fabian said and I just found myself very interested in this new "Memory Timming" feature and what that probably does. :D

And the overclocking...? Do I understand correctly that you are overclocking your machine? I'd definitely try without that if disabling Cool'n'Quiet doesn't help.

I'm so gratefull for you guys trying to help. Thanks a lot! I did indeed set Background services in the system properties, but I did that after this problem emerged. Should I change it back? I guess I could try some other DAW, if that's what you're asking? I'm unsure. I tried using both ASIO4ALL and UX1-ASIO with the same result from inside Reaper. What other DAW could I try out? Are there any free ones outthere? If I understand you correctly, I should try adding a lot of the build-in effects (rea) and see if the problem is the same? Will do that. I'll try to disable cool and quiet, and remove the cpu-overclocking. I thought that cool and quiet only had influence on the fanspeed. I'll take a look at that link from blackviper. Thanks again for trying to help me out. Here's my task manager when running reaper (normally I'm not running Adobe Photoshop while running Reaper, ofc) I've been disabling numerous of these processes attempting to solve this issue, though. When the problem occurs, the only process that increases in CPU-usage is reaper.exe. Memory use is unchanged, CPU just goes to 99% for those 25-20 seconds...

I'm suspecting Nvidia, really... but can't say why...

You've probably checked but just incase... Have you looked in system information to see if you've got an IRQ conflict ? If the sound and video cards are sharing the same one it causes problems like this.

Please disable Cool n Quiet!