[SOLVED] Why do games run at 144hz but windows doesn't

skroletz7u7

Commendable
Apr 1, 2018
6
0
1,510
So lately I've been having this problem where I've noticed that my cursor hasn't been running as smooth as it should be, but only after the pc has been on for a while. Meaning that when I first boot my pc, my cursor is fine and everything is fine but as the day goes on, the motion of the cursor seems choppier or slower, as if I had a 60hz monitor (I don't). This only happens in the desktop though. My games seem to run fine at 144hz but whenever I pause the game or open chat and I can see the cursor, it goes back to being choppy or 60hz-like (even the game gets like that). Does anybody have any idea on what may be going on? I've also tried to go to testufo.com to see if everything was fine and running at 144hz but my browser wouldn't be able to sync and it wouldn't reach 144 fps. I also tried Web browser "VSYNC synchronization", display Hz, and input lag tester (vsynctester.com) but it also failed to sync. In addition, every time that starts to happen, I sometimes notice that my audio starts to get a little choppy as well, almost as if it was clipping or something. Lastly, I've already done a Malwarebytes scan and also cleaned up my PC a bit with Ccleaner but the problem still persists (I've also checked task manager to check for anything abnormal but everything is fine). Can anyone help?

My Specs are:
1700x
GTX 1070
16gb 3200Mhz (2x8)
b450m ds3h
Asus vg248 (monitor)
 
Solution
My monitor doesn't have g sync either but some Free sync monitors are still supported by Nvidia. The drivers recognises it can run it. All I have to do is enable Freesync in the monitor settings and it shows up in the Nvidia as partially supported
osrkVh9.jpg


maybe try updating G Hub anyway, just in case.

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any Microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one...
To which refresh rate is windows set to?
Which refresh rate is the monitor reporting in the OSD?

Which mouse are you using? Is it a gaming mouse with different settings for DPI? Might be a settings problem, where the mouse outside the game is differently configured .
 
have you updated the Nvidia drivers as choppy cursors can be caused by Display drivers.

it could be G Sync - https://www.nvidia.com/en-us/geforce/forums/discover/295207/gsync-mouse-lag/

they have it disabled on desktop as it can cause stuttering in some apps.

if you have it set as 144 on the Advanced Display Settings and in the Nvidia control panel, it should run 144 in everything. Including the ufo test.
 
To which refresh rate is windows set to?
Which refresh rate is the monitor reporting in the OSD?

Which mouse are you using? Is it a gaming mouse with different settings for DPI? Might be a settings problem, where the mouse outside the game is differently configured .
I have all my games set to 144hz and windows as well. As for the mouse, I'm using a logitech g502 but I haven't touched the software in a while (way before this started happening) so the mouse shouldn't be the issue
 
have you updated the Nvidia drivers as choppy cursors can be caused by Display drivers.

it could be G Sync - https://www.nvidia.com/en-us/geforce/forums/discover/295207/gsync-mouse-lag/

they have it disabled on desktop as it can cause stuttering in some apps.

if you have it set as 144 on the Advanced Display Settings and in the Nvidia control panel, it should run 144 in everything. Including the ufo test.
I do have the most recent Nvidia drivers and my monitor doesn't have g-sync. I also have it set as 144hz on the Nvidia control panel but the problem is still there sadly.
 
Its major reason would be the monitor working frequency that might be the processor supports the desire range of frequencies but the monitor might not be .
This never happened in the past, I've been using this monitor with this pc for a while and it barely started happening like a week ago or 2. So idk if that would be the issue in this case tbh.
 
My monitor doesn't have g sync either but some Free sync monitors are still supported by Nvidia. The drivers recognises it can run it. All I have to do is enable Freesync in the monitor settings and it shows up in the Nvidia as partially supported
osrkVh9.jpg


maybe try updating G Hub anyway, just in case.

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any Microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.
 
Solution
My monitor doesn't have g sync either but some Free sync monitors are still supported by Nvidia. The drivers recognises it can run it. All I have to do is enable Freesync in the monitor settings and it shows up in the Nvidia as partially supported
osrkVh9.jpg


maybe try updating G Hub anyway, just in case.

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any Microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.
I'll give this a try but it's going to take me a minute because the problem only starts happening after my pc has been on for a while . I should also mention that I'm going to be doing a clean install of windows again because for some reason I have Windows 10 Enterprise and I'm switching to windows 10 home or pro so if I'm going to be doing a clean install of windows, should I even worry about trying to fix this? is this issue hardware related or software related? Because if it does get fixed with the clean windows install then there is no point in doing all this troubleshooting.