My TrackIR software uses around 16-20% of my CPU and causes Windows Driver Foundation to jump to 25%. In total my CPU usage on idle is between 45 and 55%!
As soon as I close the software, the CPU goes down to 5-8%.
i5-4690K CPU 3.50Ghz @ 4.10GHz; 32GB DDR3 1600MHz; GeForce GTX 1660 Super; LG IPS225@1920x1080; Samsung SSD 860 EVO 1TB; Windows 10 Pro
Any help is highly appreciated.
Software causes high CPU usage
Re: Software causes high CPU usage
I've solved the problem by replacing: file with an .exe file that does nothing and the issue is no longer occurring. TrackIR is back to its normal 2-3% of CPU.
Clearly there is some problem with TrackIR app and the Windows Driver Foundation. On exactly the same machine running Windows 7 the TrackIR app is working normally.
Code: Select all
Windows/System32/WUDFHost.exe (Windows Driver Foundation)
Clearly there is some problem with TrackIR app and the Windows Driver Foundation. On exactly the same machine running Windows 7 the TrackIR app is working normally.
-
- NaturalPoint Employee
- Posts: 313
- Joined: Fri Sep 02, 2022 6:40 am
Re: Software causes high CPU usage
Hello s411728,
As an alternative to using an empty .exe file, you may wish to try disabling the Windows Driver Foundation service as noted in this Microsoft forum: https://answers.microsoft.com/en-us/win ... 846a79e398.
Kind Regards,
As an alternative to using an empty .exe file, you may wish to try disabling the Windows Driver Foundation service as noted in this Microsoft forum: https://answers.microsoft.com/en-us/win ... 846a79e398.
Kind Regards,
Jillian Smythe
TrackIR Support Representative
TrackIR Support Representative
Re: Software causes high CPU usage
Thank you for the advice Jillian,
unfortunately in my case the "Windows Driver Foundation" is not listed as a service, so there was no way for me to disable it as the article suggest. I had boot my machine in Linux and manually "kill" this thing.
unfortunately in my case the "Windows Driver Foundation" is not listed as a service, so there was no way for me to disable it as the article suggest. I had boot my machine in Linux and manually "kill" this thing.