Moving mouse causes fps drop in CPU intensive games only

[TessellatedGuy]

Hello, I noticed that framerate would drop pretty hard while playing some games when I look around or move my mouse. So I decided to test out many games and found that this happens only in CPU intensive games, like Battlefield 1 and Watch dogs 2 (I assume it's cpu intensive because it's got the same effect). In games like GTA 5, Shadow warrior 2, or Witcher 3, the game runs perfectly even when moving my mouse. I did some more testing and found that the fps drop amount decreases as my framerate becomes lower, it's really weird. For example: In battlefield 1 campaign, I get 120 fps while looking at a certain point and when I move my mouse it drops to about 99-105 fps so about 20 fps is decreased by just moving the mouse, now as I play a 64 player conquest the game gets pretty demanding and my framerate comes down to about 70, so when I move my mouse then, I get an fps drop of only 6 tops (And even lower drops when it's below 60 fps, about 2-4 fps tops). Same thing happens in watch dogs 2 in CPU intensive areas like the middle of the city.

The thing is.... I've got an i5 4690K overclocked to 4.5Ghz, which should easily handle any polling rate I throw at it. I've heard that polling rate isn't a problem for CPUs to handle nowadays, especially a beefy CPU like mine. I've tried everything from BIOS updates, to DPC latency checking using latencymon (Latency there seems to be fine, only reaching the slightly brown area), to USB drivers for my logitech G502, to even clean installing my graphics driver and downgrading it. None of them do anything. Is this something I should worry about or is this normal?

Specs:
GTX 1070
i5 4690K
16 gb DDR3
Windows 10
Gigabyte Z97X Gaming 3 motherboard.


View attachment DxDiag.txt
View attachment msinfo.txt

 

[TessellatedGuy]

Update on the issue, it's been fixed. I don't know which one did the trick, but I installed the default PCI drivers and rebooted, and then I got a error from "esrv.exe" not being able to open and then I force closed "esrv_svc.exe" and deleted all files related to it by doing a quick disk search with file explorer and POOF, it's all gone. I really hope this helps someone but I don't recommend doing the PCI driver thing without a system restore point because it could cause a LOT of problems. I was stupid to take the risk without doing a system restore point but I guess it's worth it?

Edit: I think I spoke too soon, it's actually still there, just maybe a lot less intensive.

 

[BetaLeaf]

Good evening.

May we please know what mouse you are using? If possible, please try to decrease the pooling rate (Hz)/increase the response rate (ms). If that is not possible, then try using another mouse. Cheap ones usually won't have excessively tight response rates.

The Response or Polling rate is simply how many times the mouse reports activity to the computer. A higher number means more reports and thus more cpu usage to process these reports. If your mouse is rated for 1000 Hz, then it should report every 1 ms or 1000 times a second. Likewise, a 250 Hz mouse will report every 4 ms or 250 times a second.

I hope this grants you a better understanding. Have a good day.
Jeff Savage ~ BetaLeaf

 

[BetaLeaf]

I looked at your attached files. I see you are using the Sweetlow USB Mouse Rate Adjuster Lower Filter. I would recommend you uninstall this and see if the issue continues.
You are using the Logitech G500 Gaming Mouse which is capable of picking the response rate. I would follow the guidelines in the post above and change your response rate.

 

[TessellatedGuy]

I looked at your attached files. I see you are using the Sweetlow USB Mouse Rate Adjuster Lower Filter. I would recommend you uninstall this and see if the issue continues.
You are using the Logitech G500 Gaming Mouse which is capable of picking the response rate. I would follow the guidelines in the post above and change your response rate.

Good evening.

May we please know what mouse you are using? If possible, please try to decrease the pooling rate (Hz)/increase the response rate (ms). If that is not possible, then try using another mouse. Cheap ones usually won't have excessively tight response rates.

The Response or Polling rate is simply how many times the mouse reports activity to the computer. A higher number means more reports and thus more cpu usage to process these reports. If your mouse is rated for 1000 Hz, then it should report every 1 ms or 1000 times a second. Likewise, a 250 Hz mouse will report every 4 ms or 250 times a second.

I hope this grants you a better understanding. Have a good day.
Jeff Savage ~ BetaLeaf

Hello, thanks for the reply. I know that decreasing polling rate will stop the fps drop but I want to know why this is happening in the first place. I read in many articles that polling rate doesn't affect performance at all because CPUs nowadays are powerful enough. Is polling rate really the problem here or is there a bigger issue that I'm not aware of? Because it seems lowering polling rate to 125hz does the trick but I really don't want to play fast paced first person shooters at that due to the added response time. I'm really looking for if this is normal or not. Also, unfortunately this issue was present even before I installed the Sweetlow USB mouse rate adjuster filter and after uninstalling it there's little to no change in performance.

 

[BetaLeaf]

My pc is running an AMD Phenom II x965 Black Edition, and with my polling rate at 1000 Hz, my cpu usage when I move the mouse increase by 16%. Lets assume your monitor has a refresh rate of 60 fps. A pooling rate of 125 Hz would update your cursor twice every frame, which in my personal opinion is more than enough. Lets also say you have a high end monitor, and it's refresh rate is 144 fps. I would set your polling rate to 250 Hz. It's not quite double, but its still more than enough. You want at least 1 update per frame. Any more than that is just wasting cpu cycles for no perceivable gains.