Windows 7 64-bit mouse freezes/stutters multiple times per minute when network activity is high

Anonymous
2010-09-20T19:37:48+00:00

Hi All,

I recently bought a new Packard Bell computer with an OEM Windows 7 that have a problem with the mouse and keyboard. I have been in contact with the manufacturer but they are as puzzled as I over this issue. After searching through numerous of threads regarding mouse problems in windows 7 I have found that there are many who have this problem but there is no consistency in HW setup, i.e. it seems more of an OS problem.

I really like both the machine and Windows 7 but I have a nagging issue with frequent 1-2 second freeze/stutter of the mouse during "high" network activity (e.g. streaming a YouTube video). During my search I have encountered at least 4 people who refer that to network activity affect the mouse behavior.

Sometimes both keyboard and the mouse becomes totally unresponsive and the system must be restarted. However, at these occasions, the rest of the system is not affected - e.g. skype and other programs continue to run without any glitch or lag.

To try to solve this I have done the following (with no affect on the problem):

  • Updated all drivers to the latest.
  • Tried different version of the mouse drivers (running latest now).
  • Tried different versions of the network driver (running latest now).
  • Changed keyboard/mouse to the PS2 that came with the computer.
  • Set the system to "high performance"
  • Changed to USB mouse
  • Tried different Bios "Power/suspend mode" settings (proposed as a solution in another thread)

One thing that did have a strange affect on the problem was:

  • Having both PS2 and USB mouse present, touching one when the other freezes/stutters will instantly resolve the freeze/stutter.

What I have investigated/noted:

  • There has never been an "error box" popping up in Windows when this happens.
  • In the event viewer I see warnings from "i8042prt" regarding (remember, thie is translated from swedish :) "The device sent an erroneous reply after the keyboard was reset" (This was what I found, if you need more info please ask but provide what to search for and where)

My system has the following specs:

Operating system:        Microsoft Windows 7 Home Premium

Versions:                     6.1.7600 build 7600

Manufacturer:              Packard Bell

Computer model:         ipower G3720

Computer type:            x64-based PC

Processor:                   Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz, 2801 Mhz, 4 core, 8 logic processors

BIOS-version and -date American Megatrends Inc. P01-B1, 2010-03-23

SMBIOS-version 2.6

HAL (Hardware Abstraction Layer) Version = "6.1.7600.16385"

Installed physical memory (RAM) 6,00 GB

In addition to the original outfit, I have also installed a Wireless PCIe network card, D-Link DWA-556 Xtreme N PCIe Desktop Adapter (using the latest windows 7 drivers from d-link)

FYI: this is an offspring per request from MS support, trouble report first posted here:  http://social.answers.microsoft.com/Forums/en-US/w7performance/thread/01655e0a-1489-44e0-ad75-e9ee5486d91e?prof=required

Thanks for any help in this matter

/Rasgra

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2010-11-24T19:20:24+00:00

Hi Chris,

I might have a happy ending to this topic :)

I returned my old system end got another one, it worked fine initially but then the mouse started to stutter yet again.

The system had only a few programs installed so I began to uninstall them to see if it changed anything.

One program did - Skype.

I never suspected it as friends of mine are using Windows 7 and Skype without any problem, although they might not be using 64 bit version and quadcore.

My system has now been without stutters and glitches for a week, so I'm fairly sure that this was the problem.

As Skype is a very wide spread IM, it might apply to others as well.

Thanks for your help!

/Rasgra

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

68 additional answers

Sort by: Most helpful
  1. VARADHARAJAN K 9,726 Reputation points Volunteer Moderator
    2013-03-20T16:48:14+00:00

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2013-03-20T15:00:16+00:00

    I tried the suggestion dealing with msconfig  and changing the number of processors win 7 seems to think I have. So do, msconfig --> boot --> advanced options --> number of processors. Win 7 had that option set @ 1! How can 7 be so dumb? I have a dual core! So I checked the box and changed to 2 cores and did a reboot. This problem has dropped by at least 99.9%. Win 7 is as good as XP was/is, why has this not been fixed? -lol- It seems to be such a simple problem! I've had this problem for so long and put up with it until it was unbearable. Why no patch? I update!

    Anyway, I hope this works as well for you as it seems to have for me.

    If you're curious, I'm running Win 7 pro. 64bit, a USB mouse (Logitech M110), and a home made PC who's specs I really don't think matter in this case, EXCEPT for the number of cores you're running and what 7 believes you have. SIMPLE! Thanks go to the guy that posted this solution elsewhere.

    By the way, I don't think this problem, for me, was related to network use. Give it a try though. Got nothing to lose.

    Update -- 1hr later -- Still not completely gone though

    Was this answer helpful?

    0 comments No comments