Input lag / floaty mouse caused by RAM/BIOS

[maestr0en]

I've been having this issue for a loooong time.. Some days when i start my computer i can instantly tell just by navigating on the desktop that my mouse input is as it should be. But more often than not there is this floaty feeling.. leading to overflicking and no control i games. I had a discovery two days ago when i cleared CMOS and went with no EXPO (all other settings the same). The mouse was fine then. However when i switched to EXPO 1 it came back and won't go away even if i go back to no EXPO or clear CMOS again. In the past the mouse have felt fine on both EXPO 1 and EXPO 2, i think it was more of a coincidence that it was no EXPO that worked this time.

Any ideas??? What's going on? Can it be related to my RAM at all?

Asus TUF Gaming B650-PLUS WIFI
7800x3d
4070ti
Kingston Fury Beast DDR5 6000MHz 2x16GB CL 36
Asus TUF Gaming 1000W GOLD

[Hyote]

I can only give the generic answer here, that any kind of underclocking and resetting would cause a positive change but only for a while. It's possible for those profiles to cause lag if they are poorly configured but the negative performance hit you get with no OC is also not worth it. Base RAM profiles with auto settings are almost always going to feel like your inputs are tighter.

This isn't an existing theory but a thing I noticed. Every startup you get different ProcessIDs (task manager) and if you focus on csrss, smss, wininit, winlogon there is a massive difference (for me) when they get assigned lower values. For example my ideal values would be 320, 420, 590, 596, 696. Usually they are 4 or 8 digits higher and the input difference is noticeable and it stays the same until I restart. The only way to get the lowest values is to keep restarting.
Again this is just my observation but they always consistently followed the pattern of higher values = worse performance, input lag, desync.
Otherwise I can't recommened any single thing to fix it as everything has been tried. If you apply each individual setting then they greatly reduce the effect of floatiness.

[Mr1991]

I can only give the generic answer here, that any kind of underclocking and resetting would cause a positive change but only for a while. It's possible for those profiles to cause lag if they are poorly configured but the negative performance hit you get with no OC is also not worth it. Base RAM profiles with auto settings are almost always going to feel like your inputs are tighter.

This isn't an existing theory but a thing I noticed. Every startup you get different ProcessIDs (task manager) and if you focus on csrss, smss, wininit, winlogon there is a massive difference (for me) when they get assigned lower values. For example my ideal values would be 320, 420, 590, 596, 696. Usually they are 4 or 8 digits higher and the input difference is noticeable and it stays the same until I restart. The only way to get the lowest values is to keep restarting.
Again this is just my observation but they always consistently followed the pattern of higher values = worse performance, input lag, desync.
Otherwise I can't recommened any single thing to fix it as everything has been tried. If you apply each individual setting then they greatly reduce the effect of floatiness.

Interesting, I just wanted to post that I managed to manipulate them (but I guess for worse), when I used a performance analyser tool this is what my Csrss and DWM end up having: https://ibb.co/fv8pFLm

And this is a normal reboot: https://ibb.co/m6qzm0Q

I haven’t had much time to mess around with it, but I thought it was interesting that you could change their numbers, now I just gotta figure out how to get them lower

[ablemor]

PID = Proccess id, wehat are u talking about

[Inputlagg3r]

Had these parts and ended up returning the PC!

I suspected it was the ram, as when i fiddled with settings related to them it felt better, but not just enough as my old PC.

[kosmicSeven]

I can only give the generic answer here, that any kind of underclocking and resetting would cause a positive change but only for a while. It's possible for those profiles to cause lag if they are poorly configured but the negative performance hit you get with no OC is also not worth it. Base RAM profiles with auto settings are almost always going to feel like your inputs are tighter.

This isn't an existing theory but a thing I noticed. Every startup you get different ProcessIDs (task manager) and if you focus on csrss, smss, wininit, winlogon there is a massive difference (for me) when they get assigned lower values. For example my ideal values would be 320, 420, 590, 596, 696. Usually they are 4 or 8 digits higher and the input difference is noticeable and it stays the same until I restart. The only way to get the lowest values is to keep restarting.
Again this is just my observation but they always consistently followed the pattern of higher values = worse performance, input lag, desync.
Otherwise I can't recommened any single thing to fix it as everything has been tried. If you apply each individual setting then they greatly reduce the effect of floatiness.

This made a difference for me too. I wrote a batch script that restarts DWM every ~10 seconds until it gets a PID between 1–999. Since you can’t reserve or assign PIDs directly, this brute-force loop is the best method I’ve found. Usually takes 2–10 minutes to land under 1000.

[kosmicSeven]

I can only give the generic answer here, that any kind of underclocking and resetting would cause a positive change but only for a while. It's possible for those profiles to cause lag if they are poorly configured but the negative performance hit you get with no OC is also not worth it. Base RAM profiles with auto settings are almost always going to feel like your inputs are tighter.

This isn't an existing theory but a thing I noticed. Every startup you get different ProcessIDs (task manager) and if you focus on csrss, smss, wininit, winlogon there is a massive difference (for me) when they get assigned lower values. For example my ideal values would be 320, 420, 590, 596, 696. Usually they are 4 or 8 digits higher and the input difference is noticeable and it stays the same until I restart. The only way to get the lowest values is to keep restarting.
Again this is just my observation but they always consistently followed the pattern of higher values = worse performance, input lag, desync.
Otherwise I can't recommened any single thing to fix it as everything has been tried. If you apply each individual setting then they greatly reduce the effect of floatiness.

This made a difference for me too. I wrote a batch script that restarts DWM every ~10 seconds until it gets a PID between 1–999. Since you can’t reserve or assign PIDs directly, this brute-force loop is the best method I’ve found. Usually takes 2–10 minutes to land under 1000.
github /KosmicSeven/DWM-Low-PID-Restarter-Bat/

[MontyTheAverage]

I can only give the generic answer here, that any kind of underclocking and resetting would cause a positive change but only for a while. It's possible for those profiles to cause lag if they are poorly configured but the negative performance hit you get with no OC is also not worth it. Base RAM profiles with auto settings are almost always going to feel like your inputs are tighter.

This isn't an existing theory but a thing I noticed. Every startup you get different ProcessIDs (task manager) and if you focus on csrss, smss, wininit, winlogon there is a massive difference (for me) when they get assigned lower values. For example my ideal values would be 320, 420, 590, 596, 696. Usually they are 4 or 8 digits higher and the input difference is noticeable and it stays the same until I restart. The only way to get the lowest values is to keep restarting.
Again this is just my observation but they always consistently followed the pattern of higher values = worse performance, input lag, desync.
Otherwise I can't recommened any single thing to fix it as everything has been tried. If you apply each individual setting then they greatly reduce the effect of floatiness.

This made a difference for me too. I wrote a batch script that restarts DWM every ~10 seconds until it gets a PID between 1–999. Since you can’t reserve or assign PIDs directly, this brute-force loop is the best method I’ve found. Usually takes 2–10 minutes to land under 1000.
github /KosmicSeven/DWM-Low-PID-Restarter-Bat/

Tested. No change or placebo.