Recommended Posts

I've had a fresh install of windows 8 consumer preview installed since it was released. I've pretty much left it "as is" and only added a few simple apps like chrome so I can't see what the problem is.

Explorer seems to be using something in the region of 25-30% CPU even when the system is idle and nothing else is running. This isn't random spikes, it's constantly this high.

Anyone heard of this issue, maybe with a fix? How could I go further and find out what is causing the problem if not?

Thanks.

Link to comment
https://www.neowin.net/forum/topic/1066100-explorerexe-constantly-using-cpu/
Share on other sites

I've had a look at the threads relating to explorer.exe with process explorer and there seems to be one thread causing the high cpu usage.

combase.dllCleanupTLSOleSlate+0x3b0

When I kill the thread, nothing seems to go wrong, it simply appears to run as it should. Any thoughts on this?

I've had a look at the threads relating to explorer.exe with process explorer and there seems to be one thread causing the high cpu usage.

combase.dllCleanupTLSOleSlate+0x3b0

When I kill the thread, nothing seems to go wrong, it simply appears to run as it should. Any thoughts on this?

Do you have "Rising AntiVirus 2011" installed ?

Quick search points that "combase.dll" is part of that AV

Other things are saying it is part of a runtime in win 8, maybe update dot net and runtime visual C++ etc ?

I perhaps installed that.

I mean, I (rather stupidly) installed an app. I had a missing directx dll so I went on one of those dll library sites. It had an option for an installer and a simple zip with the dll in it. Feeling lazy, I just thought I'd grab the installer which appeared to also install some crap with it, which went on attempting to scan my system. I think it was legit software (after all, the zip option contained a legit directx dll) but it wasn't welcome so I uninstalled it.

I have a feeling that there's a remnants of it left, is there a way to unregister this dll?

I would install something like Malwarebytes and do a full scan with that, make sure you don't have any bad guys on there

Find the location of that .dll using process explorer > right click the .dll > properties > Path > Take a note of the path

Boot in safemode and find the .dll in that location and move it to the desktop to make sure its not important, if all is well after booting normally, delete it.

Also Start > Run > msconfig > make sure nothing weird is set to start with Windows in there

Empty temp folders during safemode, User temp and Windows temp

Scan with Hijack This > delete anything suspicious

See how you get on after that, might not be malware and removing the dll might sort it, but a few suggestions incase

  • 9 months later...

I've had a look at the threads relating to explorer.exe with process explorer and there seems to be one thread causing the high cpu usage.

combase.dllCleanupTLSOleSlate+0x3b0

When I kill the thread, nothing seems to go wrong, it simply appears to run as it should. Any thoughts on this?

Hello, i got exactly the same issue without any antivirus expecting build in MSE/Defender and On Windows Version 8 Final ? must kill combase.dll through process explorer everyboot else by cpu gets lots of heat After a while and everything is lagging anyway if i don't. If you open combase stack it shows To have something To do with New Windows Push notification Service that i deactivated but No change. How did you fix it? Registred only here because My Special Problem was described just here.

thank you

Hello, i got exactly the same issue without any antivirus expecting build in MSE/Defender and On Windows Version 8 Final ? must kill combase.dll through process explorer everyboot else by cpu gets lots of heat After a while and everything is lagging anyway if i don't. If you open combase stack it shows To have something To do with New Windows Push notification Service that i deactivated but No change. How did you fix it? Registred only here because My Special Problem was described just here.

thank you

I'm sorry to say that this was a long time ago. It was a Windows 8 Consumer Preview version too, I don't believe I ever fixed it as such, it just isn't a problem any more now that I have RTM

  • 4 weeks later...
This topic is now closed to further replies.
  • Posts

    • After watching the Apple event earlier this week it is quite the contrast. Apple is going back and tweaking the code to make things more efficient in may areas of MacOS. Windows is boosting your electric build to hide their issues.
    • It is silly there is no simple way to check whether this profile has been activated. CFRs are normal, but trying to even hide the fact if it's on / off seems silly, especially for something so user-facing. Surely Microsoft is "proud" of their engineering efforts on this one and ought to display it somwhere in the GUI.
    • Many Linux distros are not known for excellent battery life, so I'm not sure that is the best example. A more apt example may be Apple, but Apple's CPUs are simply far more efficient than Intel & AMD at single-threaded tasks like these, so "boosting" is not as power-hungry and less heat-inducing. Not to mention Apple will hardly engage P-cores for basic UI tasks; they use a pretty complicated QoS scheme to only activate P-cores for more serious workloads like HTML / JS execution or decompression or application launch. Microsoft is (smartly) doing it for launch, but also for UI tasks, which is the more nonsensical part: why ... do Windows 11's UIs need modern CPUs to boost? It should load so quickly that there's not even time for the CPU to boost.
    • I've not seen any controlled testing and, judging by Microsoft's mentality, within a year, they'll have added so much more bloat, it'll undo any perceptible latency benefit and we'll have boosted the CPU clocks for nothing.
    • It depends: heat soak is a thing. Initially on cold boot-up, the heatsinks & heatpipes are at ambient temp. After heatsinks & heatpipes warm up (through normal usage), they don't immediately cool to ambient temp when the load goes away. So their baseline is higher and the trigger point for fans is much less stress. Add a few more CPU spikes → it's too hot to stay at the same fan RPM → fans get triggered to start up up much sooner / get triggered to ramp much more quickly.
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      PsYcHoKiLLa
      198
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      74
  • Tell a friend

    Love Neowin? Tell a friend!