I need help to fix my jumpy mouse on Windows 10

[malditocva]

Hi! This week I had one of the strangest pc related problems I've ever had, and I need help to solve it because I've tried everything. Since I don't even understand the problem, I'm going to tell the whole story, from the beginning.

I use KDE Manjaro for work. One night, without having changed absolutely nothing on my PC, I boot this OS as usually, and I find that the mouse pointer is not working properly. If I drew a circle, the movement was being cut off at some point, as if it was randomly skipping a few frames.

Skipping everything I tried to do to fix it inside Manjaro, I finally decided to uninstall it and reinstall it. I deleted my partition and recreated it when I installed the os. When I did the clean boot in Manjaro, the jumpy mouse was fixed. After that, I booted Windows, only to find that the weird jumpyness of my mouse was now in Windows, without making any sense. I tried connecting other mice on my PC, and they all had the same problem, but in Manjaro they all worked perfectly. After days of struggling with this (I tried the control panel solutions, the drivers, malware check, clean boot, etc), I decided to factory reset my whole pc, including all the partitions, undoing them and resetting my whole ssd. Shortly after absolutely everything was erased from my ssd and I did a clean install of windows 10, I boot it, and find out that the ponty mouse was finally solved at the cost of everything. After 10 minutes or so of installing things in my clean windows, the choppy mouse returns. It just doesnt make any sense. In manjaro, the mouse works correctly.

-It isn't my mouse, as other devices work the same and in Manjaro they work fine.

-It can't be my mouse drivers, as I tried to reinstall them several times
-I already tried to fix it from the windows mouse configuration

-The problem isn't in my motherboard USB ports, as they work fine in Manjaro

-It can't be some corrupted file on my ssd, as I did a complete factory reset of it

[↑↑↓↓←→←→BASelect]

Messaggio originale di ☥ - CJ -:

Missing the point of why im asking/mentioning it guys..

Ok listen..
Few months ago i was dusting out/reseating and what not

Turned the PC on, seemed normal, started watching youtube etc and noticed my comp was acting up, RAM showed 15.9GB (which IS NEVER Normal when not using an iGPU) and GPU usage was higher than it should have been in addition to game issues.

I KNEW it was RAM related due to the above mentioned abnormality.
Reseated again, RAM amount showed normal again, GPU usage was back to normal and games and performance were back to normal.

My experience with that TWICE i might add, this was not the first time ive had it happen, is why i mentioned the RAM and GPU usage.

I know my PC well enough to know when something isnt right, so when someone has a similar issue i'll mention it on the off chance its the same problem.

You guys may not understand the relation between one thing and another due to never running into that issue before but that doesnt remove the possibility of it happening to someone else.

Everyone has different experiences and troubleshooting with PCs, this just so happens to be one ive had before.

Hope that explained my reason for asking the OP and why i focused on the GPU usage.

My task manager has 32 GB but in small number above the graph it says 31.9 GB and i have no problems.

[[☥] - CJ -]

There you go, exactly as i described.

Reseat the RAM and GPU for good measure and go from there.
You may not be having issues currently except for the mouse but that isnt normal.

[Bad 💀 Motha]

The Task Manager in Win10 displays the RAM only in dumbed down GB value; like it does when you click Properties on This PC.

To see the true #, bring up Resource Monitor and click the Memory tab.
Now RAM should be shown in MB instead. This is much more helpful and accurate. Your installed RAM size; whatever that is, when shown in MegaBytes should always be bigger (since MB will be displayed using the proper 1MB = 1024 KiloBytes method. Again more accurate.

So for example;
8GB RAM should be seen as 8192 MB
16GB = 16384
32GB = 32768

If your # is different in Windows when viewing the RAM as MB; then something is wrong.

[[☥] - CJ -]

That isnt what hes seeing bud
And that isnt what i explained

i think i explained it enough by now(not very well), but THAT is not whats going on.

Just trust me on this one

[Bad 💀 Motha]

Well if it's displaying 31.9GB for example and the Onboard GPU is disabled and/or not actively used, then it should say 32GB of course -or- 32768MB

[[☥] - CJ -]

Messaggio originale di Bad 💀 Motha:

Well if it's displaying 31.9GB for example and the Onboard GPU is disabled and/or not actively used, then it should say 32GB of course -or- 32768MB

Exactly, its showing 31.9GB, for me it was 15.9GB
and as i explained before, when i had that happen it affected my GPUs performance, to fix it i had to reseat the RAM and GPU, after doing so everything went back to normal.

15.9 or 31.9 is not normal any which way you look at it, Especially when the iGPU isnt being used.

I also have a feeling that if the OP would check Hardware Reserved memory it will add up to the missing amount. When i had the issue Hardware Reserved Memory was 130mb+ or so instead of its normal amount of 92MB and is another indication of the issue i described.

There are many subtle hints when a PC is acting up that people look for when troubleshooting, this just happens to be one that people mistake for something else..

[Bad 💀 Motha]

Yes I agree CJ. An issue that can easily be over-looked because many users will tend to be looking at it perhaps being a more complex problem.

[Illusion of Progress]

Messaggio originale di ☥ - CJ -:

Turned the PC on, seemed normal, started watching youtube etc and noticed my comp was acting up, RAM showed 15.9GB (which IS NEVER Normal when not using an iGPU)

Messaggio originale di ☥ - CJ -:

You may not be having issues currently except for the mouse but that isnt normal.

Messaggio originale di ☥ - CJ -:

15.9 or 31.9 is not normal any which way you look at it, Especially when the iGPU isnt being used.

This isn't correct. There will typically be a portion of RAM allocated aside as hardware reserved, and a PC lacking a discrete GPU with dedicated VRAM is not the sole situation in which this happens. In fact it happens almost all (if not all) of the time, but usually it's a trivial amount and won't be enough to cause Windows to show that less than the full amount is usable, even though the EXACT full amount almost never is. Open Resource Monitor and see for yourself how much is hardware reserved. Mine reserves 85 MB. My prior two PCs reserved some. My HTPC reserves some. None of these systems have iGPUs in use, and my current one doesn't even have one period. There's usually just some that is set aside for various things, so it's not necessarily uncommon to see xx.9 GB or xx.8 GB (or whatever amount) usable out of the total, even on PCs without a GPU.

Say you have 10 GB of RAM, and the particular PC reserves 95 MB, then it may simply show "10 GB" but if it reserves "105 MB" it may show "10 GB (9.9 GB usable)". This is not at all an accurate number, by the way, as I don't know what the actual thresholds are for where it decides enough is reserved to count it worth pointing out.

It also has nothing to do with GB being shown instead of MB. It has nothing to do with a conversion when one isn't taking place (it absolutely still counts a GB in binary as 1024 MB still and not a "dumbed down" amount, because if it didn't and counted it as 1,000 MB or something, those with 16 GB would have been seeing 16.3 GB or 16.4 GB usable, and my system would be reporting 65.5 GB usable instead and it doesn't. There is no conversions. It's using the proper binary counting. It's simply "is enough set aside to consider it worth pointing out". That's it.

That said, yeah, in my experience it should be consistent (presuming no hardware changes or BIOS changes), meaning if it shows the full amount, it always should, and vice versa. I've never seen the hardware reserved amount change (again, presuming no hardware or BIOS changes), but if it can and does by a MB or few, and you're right on the edge of where the threshold changes, it could explain it.

Messaggio originale di ☥ - CJ -:

You guys may not understand the relation between one thing and another due to never running into that issue before but that doesnt remove the possibility of it happening to someone else.

Everyone has different experiences and troubleshooting with PCs, this just so happens to be one ive had before.

Nah, no harm in pointing it out if that's been your experience. Just clarifying that "above a given percentage of RAM being hardware reserved if you don't have a GPU signifies an issue" isn't true either, because it seems like you have an issue which also may have caused your hardware reserved amount to be up while having the issue, a reseat fixed whatever your actual issue was, and now you're incorrectly presuming that if anything is set aside when an iGPU isn't present that it means there's a problem and that's not the case.

[[☥] - CJ -]

Well
My only experience with the RAM amount being incorrect has been caused by the issue i explained. Never once have i encountered it during normal operation while an iGPU was not in use.

So to each their own experiences i guess.

but im saying its a fact (In my personal experience) that i encountered the same problem. He described the EXACT RAM amount of which i expected to be the direct cause of his problems.

We will just have to wait to see if his reserved hardware memory is near the amount i suspect it is.

[Illusion of Progress]

Messaggio originale di ☥ - CJ -:

Well
My only experience with the RAM amount being incorrect has been caused by the issue i explained. Never once have i encountered it during normal operation while an iGPU was not in use.

So to each their own experiences i guess.

but im saying its a fact (In my personal experience) that i encountered the same problem. He described the EXACT RAM amount of which i expected to be the direct cause of his problems.

We will just have to wait to see if his reserved hardware memory is near the amount i suspect it is.

Yeah, that's why I included the second quote as I figured it's where you were coming from, and I knew you were only trying to help. It's worth checking as a reseat of those things won't hurt anyway.

Just clarifying that this is purely Windows behavior. It's not necessarily inaccurately reporting anything; it's just reporting what is left sans hardware reservation. I don't know what the threshold is for when it points out less is usable but once it passes whatever that is, that is what causes it to show that. Most systems probably don't reserve enough to show less than the full amount usable, but I've seen it, even on PCs with dedicated GPUs. I've also seen PCs with iGPUs report the full amount. Hardware or BIOS changes can cause this to reflect differently, too. My laptop had 6 GB originally, and reported 6 GB. I upgraded it to 16 GB and now it reports 16 GB (15.9 GB usable).

[[☥] - CJ -]

Weird..
Ive always had 16GB be shown, only time it wasnt were the 2 times i described which also caused GPU instability.

In both times reseating the RAM and or GPU resolved it
Both times it happened after i was dusting out the case, DIMM slots and PCIE slots.

Well as i said, just have to wait n see what the OP says.

Thx for understanding my lack of being able to explain very well :p

[Illusion of Progress]

Yeah it's system to system. All depends on how much the particular system hardware reserves.

The best way to think of it is "when the system starts, the BIOS requests certain RAM exclusively be set aside for it and ONLY for it that the OS can't use" and Windows will subtract this as "hardware reserved". Then, if it's above a given threshold, the "xx usable" addition shows up alongside your installed RAM amount. That's mostly all that means.

While systems that rely on system RAM for the GPU will use more than those that have their own dedicated VRAM, this is usually done out of a variable sized shared pool and isn't subtracted at the hardware reserved level. The minimum amount the GPU reserves may be little, and is sometimes configurable in the BIOS.