Recently I realized that explorer.exe was using too much cpu, floating between 30% to even 70% of CPU's overall usage, even if nothing but explorer is open. Even if I close the explorer's windows themselves, explorer.exe runs in high percentages in background, even though I do absolutelly nothing.
(sorry, I'm brazilian so my windows it's in portuguese - also, sorry, English isn't my first language, feel free to correct me.)
So I scanned my pc with MalwareBytes, SuperAntiSpyware and even Avast Free. No malwares was found.
Then I ran a system check inside SuperAntiSpyware and looked for potencially harmful programs, registry, rootkits, whatever. Also, I checked system's integrity with sfc /scannow, all was right.
Finally, I thought that it may be due to junk files, temp and so on, so I cleaned up with ccleaner, and although it deleted like 8gb, nothing changed in explorer's performance. All was right, except explorer's performance.
So I downloaded microsoft's Process Explorer to explore what the heck was using it, and found that the highest cpu's consuming threads, like 99% of the high cpu usage we see in explorer's cpu's usage, it's this Audioses.DLL+0x1141b0.
I scanned audioses.dll in virustotal, nothing was found. Also scanned my explorer.exe in virustotal and nothing still.
When I double-click audioses.dll, it appears this list of threads:
Don't know when this started, but it's been a while already, like several months now.
I updated my sound driver, nothing changed.
I went to look which program was using audioses.dll and found something rather odd. It was listed two times in process explorer...
In resources monitor I found this AudioSes.dll.mui associated with chrome.exe PID 8672.
So I went to look what else was associated with this chrome.exe PID 8672, and about a hundred dll's are associated with it. Is this normal?
So... can anyone please help?
I've already posted on two other forums, and they couldn't help me. One user referred me this forum, said i should ask for help here.
Don't know if it is allowed here, but i can link the original thread here so you can get a better look.