Windows 10: Why are random apps taking up so much resources

For the past week I have been having issue with my windows where random apps that normally don't take much resources suddenly start using resources for the next 30 seconds or so. Then go back to there usual state. For example, in the picture below you can see a processes called com surrogate using approximately 2gb of ram. Then after 30 seconds it went back to normal. Then 2 minutes later another process took over and did the same the picture is below Then you will think it is only windows apps but in the image below you can see free download manager doing the same

:)

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

geforce experience takes an age to load..

Well that's why I asked. Mine is on SSD and takes 11 seconds. Your list of games will not appear if it has not checkd for updated suggested settings for awhile until it checks.

When it says it is refreshing the game list, it is checking, because NVIDIA periodically updates suggested settings. Plus it will look for those for new games you have installed.

So, the less it is run, the slower it will be.

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.