Cursor lag when mouse cursor changes?
Hire the world's top talent on demand or became one of them at Toptal: https://topt.al/25cXVn
and get $2,000 discount on your first invoice
--------------------------------------------------
Music by Eric Matyas
https://www.soundimage.org
Track title: Puzzle Game 5 Looping
--
Chapters
00:00 Cursor Lag When Mouse Cursor Changes?
01:16 Answer 1 Score 5
01:46 Answer 2 Score 4
02:36 Answer 3 Score 6
02:58 Accepted Answer Score 8
05:15 Thank you
--
Full question
https://superuser.com/questions/492685/c...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#mouse #windows8
#avk47
ACCEPTED ANSWER
Score 8
DevDoc's answer made it clear to me that it was the Intel Graphics drivers. And it only happens when multiple screens are connected to the Intel Graphics chip. (By that, I mean that they are connected to either the motherboard video output ports (desktop), or (in my case) any laptop video output)
Rolling back to these drivers (15.28.7.64.2867) worked for me. (Intel i7-2630QM on Windows 8 64-bit)
Check which drivers you need on this page. I suggest simply grabbing the "previously released" drivers.
Edit
I also suggest FIRST trying to update to the newest drivers at the time of reading this, THEN downgrading. By the time of anyone reading this, they may have already fixed it. If so, please post a comment to this answer, and I will update it.
Edit 2
I have found out, that, after a few reboots, the lag randomly appeared again, and contacted Intel support. They weren't of very much help, as I quote: "Please be aware that we provide generic drivers that have not been developed or tested specially for your system.". I personally read this as "Intel obviously has 0 to do with the drivers not working, it's definitely the manufacturer of your laptop..."
I will keep at this, until I find a solution. Meanwhile, I just installed the new 9.17.10.2875 driver, and the issue seems to persist.
Update
According to an Intel official over at the Intel forum topic, the issue has been resolved, and will be included in the next update.
I suggest you guys keep checking the driver download page for an update for your HD Graphics. I would assume getting the update WHQL certified (meaning it'll be automatically updated through Windows Update) will take quite a few weeks. They'll probably release a beta on the driver download page before it comes through Windows Update.
Remember to revert the Group Policy rule of installing Intel drivers, as described in this post, for anyone who applied it in the first place, otherwise it simply won't install.
Update 2
It seems like Intel has fixed the issue!
For some reason, my driver did NOT automatically update through Windows Update though, a manual installation may be required. Download the version appropriate for your CPU here.
ANSWER 2
Score 6
For me the workaround was to install the Intel HD Graphics drivers 9.17.10.2770.
I had the same problem with a Samsung Chronos, AMD Radeon HD 6750M + Intel HD Graphics 3000, only with a secondary monitor.
ANSWER 3
Score 5
I'd say this was an issue with the video drivers, since only that and skype were installed between the cursor being fine and the cursor being laggy.
As a first try, I'd suggest rolling the graphics drivers back, if you can. Failing that you could try getting the latest drivers from the manufacturers sites specifically, maybe trying the Release Candidate (RC) versions if they have any.
Another option would be to try a system restore, however obviously that's a bit more drastic.
ANSWER 4
Score 4
This issue is linked with the nVidia drivers newer than 306.97 as that's the latest confirmed-working driver available on Windows Update. I've only tested with 310.33, so anything newer than 306.97 but older than 310.33 might work fine, and 310.33 is still in beta so it's worth informing nVidia about this issue in the hope that a fix can be included when the newest 310.xx driver gets WHQL certified.
EDIT: On further investigation, it appears that there's more to this than previously assumed: It seems that when apps are put on secondary monitor, the problem exists even with 306.97. Can someone confirm this?
EDIT2: Submitted bug report on feedback form to nVidia, waiting to hear back.