Microsoft keyboard and kernel panics

A few weeks ago, I replaced my keyboard/mouse with a Microsoft Wireless Media Desktop 1000* keyboard/mouse combo, thinking that I’d save a USB port by having the keyboard and mouse communicating through the same wireless gizmo. Since then, I’ve gotten frequent kernel panics and I’m wondering if anyone has any insight.

By frequent, I mean at least once a week. Honestly, I had never seen one before since getting my Mac in 2006 (Mac mini, 1GB RAM, 55 GB hard disk, System 10.6.2). The panics seem to appear when I’m cursoring through a document. I can’t say whether this is 100 percent true, but the last several seem to appear right after I’ve hit the down arrow several times to scroll down a document.

The package came with Microsoft’s IntelliType/IntelliPoint software, v. 6.3. In the installation it said it would notify if there was an update. Receiving none, I assumed it was up to date. After several panics, I went to the Microsoft web site and found that the latest was 7.1. I upgraded several days ago. I had been “panic free” since then. Today I had my first with the new software.

Although I haven’t kept a log, I’m fairly certain the panics come after the computer has gone a day or two without a restart. If it’s possible there’s some memory leak in the drivers, is there some way to automate a restart each evening after the Mac does it’s daily housekeeping scripts? Is that wise?

The simplest thing to do would be to go back to my previous keyboard/mouse, but I’d like to take a stab at repairing the current situation first. I don’t believe the Microsoft keyboard or mouse can operate without the MS drivers.

mt

* Quick review: Keyboard is fine, although for some reason Microsoft defaults the standard OS X F1-F12 actions to FCN F1-F12. In their place are a series of standard menu commands. The software however can put things right. The mouse, however, is substandard largely because the clickwheel’s performance is very spotty.

Thanks Nadyne ... I'll do more research. The keyboard/mouse and their drivers are the most likely suspects, but something else could be the cause.

mt

jbolden1517 said:

I had the same problem with the 4000. A kernel panic every few days rather than one every few years.

Click to expand...

I finally gave up on the Microsoft keyboard and mouse combo and I haven't had a kernel panic since. Something is wrong with the software, or at least the MS software and my system. But it's bloody impossible to track down.

mt