Ryder Synapse 3 40 to 100% CPU usage WMI Provider Host

If you don’t want to have any problem, consider suspend wmi process after open the game. Some process like steam needs to have this service active.

All network interface MAC addresses are also captured inside the file “MSInfo.log” in SynapseLogs.zip

The file “MSInfo.log” in SynapseLogs.zip contains machine details like BIOS, CPU, RAM, Time Zone, mother board manufacturer, etc. 

@Razer.Speedcr0ss  Just curious, has Razer development successfully replicated the issue?  Or Razer development still needs more customer log in order to be able to replicate the issue?

@Razer.Speedcr0ss  already submitted my logs yesterday

It’s funny because even with all the razer services stopped and the headset still working, I still having hicups and sound cuts randomly (it didn’t happen before the update playing the same games btw). Basically the update broke a lot of the CPU management for the device lol

 It is trying repeatedly to scan for PnP-devices and enumerate them … i.e. count and identify them if they are known or new... thus hogging CPU cycles as it never “completes”.  

It seems people have created 2 duplicate threads in support section of forum.

https://insider.razer.com/razer-support-45/razercentralservice-takes-too-much-cpu-since-update-20230212-43714

https://insider.razer.com/razer-support-45/razer-central-service-30-cpu-usage-always-43587

This thread has much more useful information in terms of providing logs. Might be better to keep/move this into support section then direct other 2 threads to this instead.

Very much urge if below can be passed onto Razer software developers. It is a strong avenue to look at first in the way timeout value on Razer client side is set in issuing WMI requests.

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

@Razer.Zionzedd

@Michelle-RazerCortexPC 

same here.

The microsoft article states WMI client application, so in this case Razer software is sending WMI requests and causing constant loop.

• If you Stop the WMI service completely.
• Right click in services.msc and select "pause" then "stop"
• Check WMI service still stopped
• Now load up Synapse 3. Can still change RGB lighting, macros, cooling fan, mouse dpi and mouse poll rate.

https://devicetests.com/mouse-rate-test (To check poll rate. Only applies to Wireless dongle/wired mice as Bluetooth has 125hz limit)

However disabling WMI service completey causes problem only on next reboot. i.e. It only holds my mouse settings from last time and can't change on demand anymore, even after starting WMI service again.

So WMI service is still needed initially only, but not thereafer for Synapse to work.

I bet if everyone loads up their WMI activity log it will look like this: ResultCode=0x80041032

Also people can match the process ID in log to Razer process in task manager.

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

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.