Ryder Synapse 3 40 to 100% CPU usage WMI Provider Host | Razer Insider
Skip to main content
Hello guys, a few days ago I have been having a problem of high cpu usage sometimes up to 100% with the WMI provider host and reading in reedit I realized that several people had this problem and that it was caused by razer synapse 3 software when uninstalling it the problem went away and my cpu returned to normal, do you have a solution for this, my keyboard and mouse are Razer. thank you very much.



Note: I have windows 11 Pro and i9 13900k RTX 4090 and Asus Z790 Hero.
Probably a bad idea but did it anyway. Seems Synapse service not really dependent on Game Manager service.



Explanation:

https://www.reddit.com/r/razer/comments/kpp3hu/ysk_how_to_disable_razer_game_manager_service_as/



Script to run as every Synapse update will re-enable Game Service:

https://github.com/Invertex/RemoveRazerGameManager



Tested I am still able to:



Change RGB colour keyboard and mouse

Macros

Mouse poll rate

Mouse DPI

Fan control

Switch Optimus



Everything thing still seems to work in Synapse. So I wonder what this Game Manager service was for.



Only seemed to minimise WMI CPU usage though.



Crazy how Synapse uses around same handles than my Brave web browser open for few hours with 20 website tabs open...
Unfortunately, for me, WMI provider host is still hogging 10-15% CPU, even after disabling Game Manager service, I can still hear my fan. I would have to resort to restarting WMI in the meantime, very annoying indeed.



I guess I need to switch to liquid cooling if I want to install Synapse 🙂
I've registered just for this. Ever since Saturday when Razer Synapse made an update, i get this issue as well.

Whenever i start the Razer Synapse my WMI goes to space. Either restarting "Windows Management Instrumentation" fixes it, until i try to start the program again.

Fix this or let us go to previous version.
I have the same problem, please fix this or let us go to previous version
Hi everyone,

it seems we are all on the same boat, from the latest synapse 3 update I see Razer Central Service constantly hogging 15/20% of my cpu constantly. Even if I kill the process it comes back on after few seconds.

I hope a solution or update is on its way
Event Log - WMI Activity Logs:



Razer Synapse 3.exe

GameManagerService.exe



Event ID 5858 and 0x80041032 critical error codes being generated



Id = {00000000-0000-0000-0000-000000000000}; ClientMachine = P2; User = NT AUTHORITY\\SYSTEM; ClientProcessId = 8592; Component = Unknown; Operation = Start IWbemServices::ExecQuery - root\\cimv2 : SELECT ProcessId, ExecutablePath, CommandLine, Name FROM Win32_Process WHERE ProcessId=1704; ResultCode = 0x80041032; PossibleCause = Unknown



Cause and possible solution for Razer below from Microsoft Article below:



https://learn.microsoft.com/en-us/troubleshoot/windows-client/system-management-components/wmi-activity-event-5858-logged-with-resultcode-0x80041032
Im having exactly this problem. Restarting WMI does stop it, but I also use Alienware Thermal controls which I don't seem to get working again after the restart of WMI.



Rollback or update, but please get this fixed.
once you close synapse - wmi provider goes to 0% load basically.

Can anyone tell me if the hyper polling remains active when synapse is closed?
@Wendigo-ove



Once exit Razer apps. The Razer services are still running in background but WMI activity log stops logging further events. So it stops WMI requests at that point.



If Synapse open, it starts to look like below...







2nd screenshot. Razer services takes up so much system resources just to change lights/control fans. Hogs more resources than other apps. At this point I don't care about RGB if I can find third party way of fan control.






Hi, I'm also having the same issue! @Razer support, can someone look further in to this issue? Had to go back to SignalRGB...
Posted on other live thread re: WMI issue



Massive issue for me as causes unacceptable battery drain on my laptop while I'm mobile.



(Unfortunately not the first time a Windows update and/or Synapse update has caused runaway Synapse CPU use!)



Temp fix is obviously to uninstall Synapse - kills lighting, sound etc. though!



If like me you need the lighting to see your keyboard caps there is a work around however:

Search for OpenRGB on gitlab (Author is Adam House) - will let you control your backlight to enough of a degree as to be useable. (May work for other peripherals, but I haven't tested).

So after some digging arround, i found a log reporting tool for razer.

this created: Razer Synapse 3.log which contains 3786 entries of:

"StatusCode: 500, ReasonPhrase: 'Internal Server Error'"



so its fairly easy to pinpoint whats going on - obviously the synapse is requesting something that is not available.



https://virtuedk-my.sharepoint.com/:u:/g/personal/odc_virtue_dk/EdXy0QF5BUlNkFz1Uyw0aQYBH4EoGcQrtwkvYbDC-sCjSw?e=wkIp3I

pw: razer



im suspecting that the dev machine they run this on have IIS installed with ASP.net options that are not available to the general windows installation.
Any alternative software for programing the razer keypads?
Can Razer support please confirm this thread is monitored?
Same problem since yesterday.
Maybe we need to raise a support ticket on this issue. This forum may not be monitored by Razer support team.



https://mysupport.razer.com/
ivan.yu
Maybe we need to raise a support ticket on this issue. This forum may not be monitored by Razer support team.



https://mysupport.razer.com/


this topic cannot be ignored. because that would not make sense to exist the forum razer insider.

even more so far several people have committed to reporting the problem. do you find it useless or do you want direct answer from them?
ivan.yu
Can Razer support please confirm this thread is monitored?


Can Razer support please respond whether you are looking at this topic at all?
AndreAzevedo
this topic cannot be ignored. because that would not make sense to exist the forum razer insider.

even more so far several people have committed to reporting the problem. do you find it useless or do you want direct answer from them?




I have re-requested Razer support to confirm that they are actually looking at this topic.
Also experiencing this issue. Restarting WMI service does act as a workaround, but I ran into another issue while troubleshooting this.



I completely reinstalled Synapse, and now my "Razer Central Service" is stuck using 30%+ of my cpu, and not allowing the cpu to throttle. I've reinstalled and repaired multiple times, and just did a clean reinstall following the clean uninstall guide and the issue is still there.



Basically the software is unusable for me.



I moved away from logitech last year to get away from their frustrating software issues and I'm on the verge of tossing this mouse in the garbage and going back. Incredibly frustrating software and this isn't the first time I've had to do the repair/reinstall dance with Synapse.

Razer Insider Forum is now back online.


I raised a support ticket (Incident Reference # 230214-003164), the ticket contains snippets of logs posted in this forum on the root cause for this CPU hogging issue.

 

Razer support replied to my ticket, saying in order to start investigation, I need to further provide

  1. All the logs collected via Razer Log Collector for my machine
  2. MSINFO logs for my machine

 

If I decide that the required logs are too privacy invasive and do not feel comfortable providing  them, the ticket will not be investigated.


If I decide that the required logs are too privacy invasive and do not feel comfortable providing  them, the ticket will not be investigated.

You can unpack the Support file, as it’s zip archive containing a lot of txt files / logs. So you can check and decide if it’s privacy invasive or not :)


The WMI activity logs do indicate to below errors. There is possible resolution below.

 

https://learn.microsoft.com/en-us/troubleshoot/windows-client/system-management-components/wmi-activity-event-5858-logged-with-resultcode-0x80041032

 

I’ve attached screenshot of errors and also CSV export of WMI activity log in below link.

https://easyupload.io/m/25qk1o

 

I’ve researched and same problems have occured to other manufacturer software like Alienware, Asus. Even non gaming like VMware.

 

It is the way the software polls via WMI of the hardware. Whilst it may or may not be resolution. Certainly something Razer can look into.

 

It may be just that Windows itself is the problem since other manufacturers have faced same problem.

 

Alternatively just provide Razer update that simply allows turning off WMI requests after Razer services start because if I disable WMI service entirely I can still control lights, fans, macros, DPI etc without it. But I would rather not disable WMI service itself because it is still required by windows or other applications that rely on this. If can’t solve then it is a way around it. Disable WMI requests coming from Razer software after Razer services started because it certainly isn’t required afterwards to control RGB, cooling fans, macros, DPI on mouse etc. I’ve tested it.

 

This error can happen if the WMI application calls IEnumWbemClassObject::Next with a timeout value (lTimeout) that is not long enough to retrieve the object being queried, and is not checking for a return code of WBEM_S_TIMEDOUT (0x40004) in order to issue the request again.

Resolution
The WMI client application should be modified to issue calls to IEnumWbemClassObject::Next to retrieve the full result set, before releasing the IWbemContext object. If no objects are received, make sure that the timeout value (lTimeout) is greater than 0 and that WBEM_S_TIMEDOUT (0x40004) is not being returned.

 

@Razer.Zionzedd  I received an email from you on 20th Feb to use Razer Log Collector software. I re-created the WMI errors and used it to capture logs as per your request. I’ve attached in link below.

https://easyupload.io/qbjwac

 


But the timeline does not quite add up though.

 

The Microsoft KB is dated 09/23/2021, so this WMI change must have been changed a while ago.

 

In my own case, I did not have any Windows Update at all, I only had Razer update, then this CPU hogging issue started happening.

 


Reply