• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

KR7A: mouse pointer flickers between hourglass and arrow with FSB over 143mhz. Why??

moocat

Platinum Member
Everything works just fine and the system is stable. The mouse pointer just flickers constantly when FSB is at 145-150mhz (I haven't attempted any higher). I've used two different mice, a ps/2 and usb and both exhibit this behavior. They are both Logitech so maybe it's a driver issue (kinda doubt it since there are likely lots of overclockers using a logitech mouse). I posted this a while back but only now have had opportunity to try a different type of mouse interface. Since the problem remained I thought I would repost. Apparently I'm the only person experiencing this problem (at least with a otherwise stable system). I've never experienced lock ups or other abnormalities with either mouse. The system is stable at 150 fsb but I generally keep it at 140 since the flickering pointer is highly annoying.

I welcome any suggestions.

Heres my system:

KR7A (non-raid)
Tbird 1.4@1.53ghz
2x256mb Crucial pc2100
Radeon 8500 oem
Audigy oem
cd, cdrw, and 2 7200rpm HDs
USB zip, modem, and optical mouse
Window98SE

 
You're not the only one. I had this same problem with a Logitech cordless mouse connected to either USB or PS/2 on an 8KHA+, even when not overclocked. I traced the problem to the USR internal 56k modem and the mouse not playing nice. I still have no idea why this happens. I haven't been able to solve it except to remove the modem.

Please let me know if you figure it out.
 
I've got an external USR 56k USB. I've removed the hardware and the problem didn't go away. I've never tried completely uninstalling hardware and software for it though. I'm gonna do some more experimenting tommorow.

I'm just happy to hear someone else has at least seen this problem.


Thanks.
 
Back
Top