Mouse clicks by itself even after the mouse is detached

I'm encountering an issue this is come to the meaningful part. Once my Win7 instate begins to utilize 1.6GBs of RAM, the mouse/"cursor" begins to click independent from anyone else. It happens on any rodent I utilize, and once began it happens even provided that I confine the mouse/mice. I switched the RAM in my work-gave Dell Latitude E6510 (Core i7) from a solitary 4GB DDR3 adhere to a few 2GB DDR3 stays when the issue began, and the issue went distant. It happened utilizing a Logitech MX518 on Win7 Enterprise while associated to a laptop dock, with no overclocking.

I am having the comparable setback like you. It appears to "click", in place of event from most elevated to most minimal, the center (parchment wheel), other side, and right "best" binds, but none of the others. It additionally isn't significantly a "short" click, as when the issue happens, I am able to move the rodent in a 3 desktop symbol by 3 desktop symbol rings and look at it make a crate, just as I was clicking and dragging.

As per me it well-nigh sounds like someone remote regulating your desktop or some sort of virus / rootkit.

I had a truly comparative issue a month or a few back on a partner’s laptop. It manufactured be malware-identified (the sort which utilizes your PC to create cash for the malware creator by clicking on adverts).

When I opened Internet Explorer's history sheet, I would be able to see shifting homepages being stacked (undetectably) out of sight. Every time an offbeat site stacked; there was a rodent-click sound.

Its driver might be the issue. That (a parallel port) is an additional thing that both of the aforementioned systems have in like manner. By reason of I've incapacitated the parallel port in my laptop I've been unable to duplicate the conduct, so I am "warily ideal" about it being the root source. We'll see what my getting into mischief home system states here in a few hours. I basically thought it could have been the mobo simultaneously, but the same thing incident on several systems at the same RAM use level is simply too great of an incident, specifically after the laptop was raised and tested simply a month or something like that back, and my home system is from 2009. Both of them going unfavorable at the same time is simply too abnormal.

I was unable to get the issue to re-happen utilizing the slower Mushkin RAM, so I've put the speedier Corsair RAM once more in the container. It made 20 runs of Intel Burn Test at 800 MHz, so I'll undoubtedly leave it at that speed for now. I'm reloading arrangements and will test again when I'm physically in front of it.

I trust that anybody else encountering this issue spots this string, since this is potentially the most obviously pestering, angering, undeniably absurd PC situation I've ever encountered.

It seems to have been the parallel port creating this issue, in light of the fact that disabling it in BIOS altered it for both systems. In the BIOS of my influenced home system, I impaired the parallel port and set the serial port (which I utilize) for "Auto", so any clashes ought to be settled by Windows.