Its probably even better to trim it down further to like 1.02msps or lower. I am on a older machine a single core running SDR# 1304 with wide FM Stereo at 1.44msps 512 resolution on the FFT also trimmed down audio from 48khz to 22050, 44100 is alright as well. Use direct sound not Microsoft Sound mapper. Max cpu usage is 73%. Figured that out by watching process monitor for 5 minutes.
Cpu is a single core Pentium M @1.73ghz, 1GB ram a Dell Latitude D610 laptop ATI X300 64mb ram. 533mhz FSB rated PCIe 1.0 or 1.1 (cannot remember) architecture.
No issue.
If you Google Black Viper Windows 7 service files then when you're on his page download the Safe services zip file extract run the reg file then reboot. I am not guaranteeing that it works for some and may not work for some. Turning services off doesn't really gain a whole lot but it could. Depends on how much you have loaded with windows. If you have 3 or more icons by your clock then maybe not enough to just turn off services.
I had to adapt my first time learning software defined radio. What is going on is your CPU is constantly decoding radio samples in real time from the RTL dongle. The wider the sample rate the more the cpu cycles. SDR# is built on net framework 3.5 and that alone adds to the processes because SDR# literally pushes .net framework hard. Its probably the purest sdr windows software. HDSDR works well and way lighter and it has no prerequisites other than a EXTIO dll file for the rtl dongle. This is found and downloaded from HDSDR's website in the hardware section. Easy find. Put it into the HDSDR installation folder thats all.
This is why I use the same tactics for gaming to free some resources for software defined radio. Lighten it but don't break it!