I have recently been experiencing problems with my PC going in to moments of (Not Responding) status.
I notice it most with firefox because that's what I use most of the time. I have seen the same issue while trying to work in winmail
I even tried Google Chrome to see if it was directly related to firefox or an add-in.
Even typing this message is a chore as things keep "pausing" Sometimes my KB input is still captured - sometimes it is not and I have to type things over again.
I use F-Secure provided by my ISP. It is up to date.
I couldn't run F-Secure in safe mode.
I have run updated mbam and sas. Both in "regular" mode and safe mode. mbam found the notepad registry entries "bug" that they report as a non-issue.
I removed them anyway.
I also use iolo System Mechanic to keep things tuned up.
Looking at Task Manager, I see that fssm32.exe is using a lot of memory 388,568 K at the moment and climbing. CPU utilization is high as well - 50 to 70%
I thought that was normal as I had the scan settings set to run after 5 minutes of inactivity. But it never would stop climbing when I start using the PC.
F-secure doesn't have any way of indicating that it is doing a background scan. So, I'm not even sure if it is doing that.
I changed the settings to scan at a specific time but the problem still exists with pauses and fssm32 eating up resources.
While searching for a solution, I cam across this thread here and I fear I might be taking the same path.http://www.bleepingcomputer.com/forums/t/248573/one-cpu-of-a-pentium-d-dual-core-pegs-at-100-malware/
I'll wait for guidance though.
For me, the app that doesn't seem to want to close is firefox.
Also, IE has not run on this PC for a LONG time. I always get a rundll32.exe DEP error
I do get DEP errors with WMV files as well. I just haven't figured out which codec is the cause - if it is a codec.
Also of note is that I recently removed 2 GB of RAM as I was getting a BSOD every day. While I can't pin it down for certain, I suspect that they were caused by F-Secure because they would always occur with .sys files that begin with the letter 'v' Such as vmci.sys for vmware or volmgr.sys for windows. I suspect that F-Secure was getting that far in the scan before encountering a problem.
The MS debug tools indicated memory corruption as a likely cause. So, I took 2 sticks out and ran memtest86 SMP on the remaining and it tested out fine. So, I've just been running with 2 GB since. I realize that 4 GB was too much for 32-bit Vista, but it ran fine for quite a long time.
Thanks in advance for any help.