Link to home
Start Free TrialLog in
Avatar of drdoug99
drdoug99Flag for United States of America

asked on

Cannot start HID input service - Error 126: The system cannot find the module specified

I have a Windows XP Home computer. It has a wireless Microsoft Multimedia keyboard and mouse. When the receiver for the kb and mouse are plugged in, the computer will randomly reboot. The keyboard and mouse used to work fine, except for the rebooting of course. (it does not BSOD, I have that set to show the BSOD if it crashes, this just totally shuts the computer down and automatically reboots)  all throughout the day. Using a PS2 keyboard and mouse work fine with no issues.

There is also a Garmin GPS hooked up through usb too, but this works fine with no issues as long as the wireless kb and mouse are not in use.

Doing troubleshooting, somehow the wireless mouse and keyboard no longer are detected, and do not work anymore.

Reading all over the internet, there are possible solutions that of course do not work for me. I have installed the microsoft intellipoint software for the wireless kb and mouse, this did not help.

This website says to put the 3 files in the system32 directory, which in my case the files were already in the correct place, but I replaced them anyway, without sucess:
http://www.pcreview.co.uk/forums/thread-422431.php

I have run Dial A Fix, which basically re-registers all DLL's and various other program associations and ran the "fix permissions" option in Dial a Fix too.

This website lists a registry edit to fix the problem, I have checked the registry and it is the correct way:
http://thegreenbutton.com/forums/p/34601/144703.aspx

So I've done everything I can think of that I have came across on Google....so I have come here to the experts. Any sugesstions? I'd like to get this service running to verify if once I can get it running, if the computer will still reboot once the wireless keyboard and mouse are plugged in. If it still reboots, then I will replace the wireless kb and mouse.
Avatar of Davis McCarn
Davis McCarn
Flag of United States of America image

You need to have the Remote Procedure Call (RPC) service running for HID to work.  What happens when you try to start it?
Avatar of drdoug99

ASKER

ok, sorry for the late reply. RPC service is set to automatic and is started...

i've attached a couple pictures...
error.jpg
rpc.JPG
ASKER CERTIFIED SOLUTION
Avatar of Davis McCarn
Davis McCarn
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
also I just ran system file checker (sfc /scannow) and it did replace some files, (at least i assume so, since it needed the XP CD) but still no change.

Do you know how or what files system file checker actually changes? does it create a log file?

I will try your advice right now and let you know
Ok, I deleted all HID devices, and there was the device for the microsoft wireless keyboard and mouse I removed too in device manager, but I forgot to take the screenshot until after I did that.

The screenshot shows all the devices I deleted in device manager, then rebooted. Then I ran CCleaner.

Plug in the wireless keboard and mouse, and they both are working now. BUT, the HID Input service still gives error 126. I guess you don't need this service after all? I thought it was necessary for it to be running from what I read.

Now the real test will be to see if the computer will remain stable...the original problem is that with the wireless kb and mouse plugged in, the computer will randomly reboot.

Thanks alot for your time and help Davis!
devmanager.JPG
One of my axioms is, if you plug it in and it works, don't use the CD that came with it.  Some of the extra buttons on the keyboard and mouse may not work correctly; but, I suspect the older version of "Intellipoint" got all fouled up and thats what caused your problem.
Thanks for sticking with me
Avatar of Jsmply
Jsmply

HI DrDoug, we had the same issue.  We eventually ruled out hardware and from there, we spent quite a bit of time investigating and eventually spoke to MS and concluded the service was corrupted.  We recreated the service in the registry through command prompt and it seems to be running smooth thus far.  It starts, stops, restarts, and so far the mouse hasn't stopped working.  Thank God . . . we were really tired of troubleshooting a mouse, lol.