System and compressed memory high CPU usage

Hi, recently the process called System and compressed memory started acting up, when I'm browsing demanding sites CPU usage spikes to 20%-40% causing my sounds to get crackles and freeze for a split second. It's extremely annoying and was not happening before. It started this week when I came back after a few weeks and my PC updated many programs and the system too I guess. It happens when I'm using Chrome, Vivaldi, Steam, even when Gefore Experience is downloading new drivers... I don't know what this thing does and where it came from but I want it gone obviously it's not working the way it's supposed to. I haven't found much useful information on how to get rid of it and what I found either didn't apply or didn't work. Any help is much appreciated.

I've solved my problems so I'm posting for anyone still interested: I used Process Explorer to make a little investigation of my own and found under System's threads it's cfosspeed6.sys driver using over 20% of my CPU. Uninstalling the program solved my issues immediately. Idk if it was due to the fact that apparently I've been using old version (10.10, newest is 10.12) but I'll be checking to see if it still causes me problems on the newest version and contacting cFos support if so.

It's called cFosSpeed it's kind of internet optimization tool, allows you to download from torrents and play games at the same time without lagging etc.

Or we can fix it by going to Windows 7 instead. I have 10, I liked 10, until this mess. I did a clean install. Everything was stable. I only added the steam client, not even any games yet. Up pops the problem. Shutdown the steam client. Wait 5 minutes and boom, there is System and Compressed memory eating up 8% of my 8 core CPU. What the resource monitor shows is that it's pegging my clock speed to its over-clocked maximum even though it is only jumping cores and using around 8%. So the CPU is running wide open. 4 Ghz x 8 physical cores is a lot of heat/wasted energy.
Say what you will, Microsoft screwed up the system and compressed memory process. It should not be cranking up CPUs to their max speed. It should not need to eat up so much CPU on lower end systems. Drivers and programs should not be breaking it. The page file system before this never had these issues. Whoops, I mean never had these issues after they fixed it in the original Windows NT. They need to fix the process so that it is robust. I'm sorry, but right now it is super fragile falling over anytime an application, or driver, is installed.

Win10 and the scripting on websites lags and bogs Win10 is so bad, it's horrific! The people who wrote Win really messed up, and makes people sit through a long time while it fumbled through long scripts.. Edge browser actually works the best now, regular IE browser now barely works online, it cannot handle the scripts at all. That just outright crashes in Win10. IMHO

Solved: 'System and Compressed Memory Service process' High CPU Usage

After upgrading to Windows 10 on July 29, 2016 (ok, I'm a procrastinator, alright?) I noticed a process called 'system and compressed memory' that was eating up 18-19% of my CPU non-stop. Searched and found several 'solutions', none of which worked (drivers, BIOS, Registry hacks, Settings, etc.).

I started killing processes one by one and discovered the process 'speech runtime executable' to be the culprit. When I killed it, CPU usage for 'system and compressed memory' went to zero.

However, after killing the 'speech runtime executable' I could no longer talk to Cortana (Hey Cortana). Oh well. At least I got my system back.

All I have to do is click the 'O' in Quick Launch on the Task Bar and then type or just click the Mic in the bottom right corner to talk to Cortana. Works fine. But after you talk to her that 'speech runtime executable' process shows up again and the 'system and compressed memory' process is pegged back at 19% CPU again.

Once you kill the 'speech runtime executable' process, the CPU usage for the 'system and compressed memory' process goes back to zero.

Note that this has nothing to do with the process called 'Cortana'. I left that alone.

Microsoft needs to address this major flaw with Cortana. I'm not giving up 20% of my CPU just so she can listen for commands.

Wrightclick said:

Solved: 'System and Compressed Memory Service process' High CPU Usage

After upgrading to Windows 10 on July 29, 2016 (ok, I'm a procrastinator, alright?) I noticed a process called 'system and compressed memory' that was eating up 18-19% of my CPU non-stop. Searched and found several 'solutions', none of which worked (drivers, BIOS, Registry hacks, Settings, etc.).

I started killing processes one by one and discovered the process 'speech runtime executable' to be the culprit. When I killed it, CPU usage for 'system and compressed memory' went to zero.

However, after killing the 'speech runtime executable' I could no longer talk to Cortana (Hey Cortana). Oh well. At least I got my system back.

All I have to do is click the 'O' in Quick Launch on the Task Bar and then type or just click the Mic in the bottom right corner to talk to Cortana. Works fine. But after you talk to her that 'speech runtime executable' process shows up again and the 'system and compressed memory' process is pegged back at 19% CPU again.

Once you kill the 'speech runtime executable' process, the CPU usage for the 'system and compressed memory' process goes back to zero.

Note that this has nothing to do with the process called 'Cortana'. I left that alone.

Microsoft needs to address this major flaw with Cortana. I'm not giving up 20% of my CPU just so she can listen for commands.

I'm willing ot bet this has nothing to do with Cortana itself but rather your mic listening the entire time -> sound card drivers. I've read a lot of threads trying to solve my problem and 99% of the time it was related to some driver.

maxiu said:

99% of the time it was related to some driver.

I agree but I went through and made sure I had all the latest drivers. Even did a BIOS update.

It may not be Cortana itself but it is Cortana-related. Killing that 'speech runtime executable' process is a repeatable fix.