Event ID 7031 - the HID Service....

Hi Dave;

No other errors at all. If I set that service to automatically re-start in
case of failure I get that same error repeated many times in the event log.

The system is rock-solid and has been for years. It's my own workstation and
it's clean, clean, clean Except for this error that is.

Thanks Dave!


"Dave Patrick" <DSPatrick.TakeThisOut@nospam.gmail.com> wrote in message
news:F3DBA0FF-AD80-48EA-A92C-55115747439D@microsoft.com...
> No other system event log errors? Device Manager errors or stop codes?
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Dave Onex" wrote:
> > Hi Folks;
> >
> > I have Win2k AS with all the updates properly installed. Recently it
> > started
> > coughing up this error in event viewer;
> >
> > Event ID: 7031
> > The HID Input Service service terminated unexpectedly. It has done this
1
> > time(s). The following corrective action will be taken in 60000
> > milliseconds: Restart the service.
> >
> > This machine has been rock-solid for years - it's my chosen workstation.
> > Does anyone have any idea on how to combat this error or what it means?
> >
> >
>

You might try;
sc query "hidserv"

to see what win32 exit code is generated. You can get sc.exe (service
controller tool) here.
ftp://ftp.microsoft.com/reskit/win2000/


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Dave Onex" wrote:
> Hi Dave;
>
> No other errors at all. If I set that service to automatically re-start in
> case of failure I get that same error repeated many times in the event
> log.
>
> The system is rock-solid and has been for years. It's my own workstation
> and
> it's clean, clean, clean Except for this error that is.
>
> Thanks Dave!

Hi Dave;

Thanks for the tip - but I don't know what it does Here's what the
command comes up with;

C:\Temp>sc query "hidserv"

SERVICE_NAME: hidserv
TYPE : 10 WIN32_OWN_PROCESS
STATE : 1 STOPPED

(NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 1067 (0x42b)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0

Does that shed any light on the issue?
Thanks!

"Dave Patrick" <DSPatrick RemoveThis @nospam.gmail.com> wrote in message
news:4DF21985-2770-4A56-A2BD-546A77AA093E@microsoft.com...
> You might try;
> sc query "hidserv"
>
> to see what win32 exit code is generated. You can get sc.exe (service
> controller tool) here.
> ftp://ftp.microsoft.com/reskit/win2000/
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Dave Onex" wrote:
> > Hi Dave;
> >
> > No other errors at all. If I set that service to automatically re-start
in
> > case of failure I get that same error repeated many times in the event
> > log.
> >
> > The system is rock-solid and has been for years. It's my own workstation
> > and
> > it's clean, clean, clean Except for this error that is.
> >
> > Thanks Dave!
>

More than likely hardware related. What was changed or installed recently?
Look at devices under "Human Interface Devices" in Device Manager.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Dave Onex" wrote:
> Hi Dave;
>
> Thanks for the tip - but I don't know what it does Here's what the
> command comes up with;
>
> C:\Temp>sc query "hidserv"
>
> SERVICE_NAME: hidserv
> TYPE : 10 WIN32_OWN_PROCESS
> STATE : 1 STOPPED
>
> (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
> WIN32_EXIT_CODE : 1067 (0x42b)
> SERVICE_EXIT_CODE : 0 (0x0)
> CHECKPOINT : 0x0
> WAIT_HINT : 0x0
>
> Does that shed any light on the issue?
> Thanks!

Hi Dave;

I installed a Microsoft Wireless keyboard and Microsoft Wireless mouse. I
installed only the latest drivers from the MS site and there were no errors
for a couple of weeks but now there are.. .

Those are the only devices under Human Interface Devices in Device Manager.
I'm using Intellipoint 6.1 on both devices. I did try un-installing
Intellitype the other day and re-booting but the errors were still there so
I re-installed the MS software again.

Hmmmmm....... curiouser & curiouser.


"Dave Patrick" <DSPatrick.DeleteThis@nospam.gmail.com> wrote in message
news:7B903B85-9FA7-46E9-8779-9A230BBF3516@microsoft.com...
> More than likely hardware related. What was changed or installed recently?
> Look at devices under "Human Interface Devices" in Device Manager.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "Dave Onex" wrote:
> > Hi Dave;
> >
> > Thanks for the tip - but I don't know what it does Here's what the
> > command comes up with;
> >
> > C:\Temp>sc query "hidserv"
> >
> > SERVICE_NAME: hidserv
> > TYPE : 10 WIN32_OWN_PROCESS
> > STATE : 1 STOPPED
> >
> > (NOT_STOPPABLE,NOT_PAUSABLE,IGNORES_SHUTDOWN)
> > WIN32_EXIT_CODE : 1067 (0x42b)
> > SERVICE_EXIT_CODE : 0 (0x0)
> > CHECKPOINT : 0x0
> > WAIT_HINT : 0x0
> >
> > Does that shed any light on the issue?
> > Thanks!
>

You might try the wired devices again to confirm. Also try asking in the
hardware group.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"Dave Onex" wrote:
> Hi Dave;
>
> I installed a Microsoft Wireless keyboard and Microsoft Wireless mouse. I
> installed only the latest drivers from the MS site and there were no
> errors
> for a couple of weeks but now there are.. .
>
> Those are the only devices under Human Interface Devices in Device
> Manager.
> I'm using Intellipoint 6.1 on both devices. I did try un-installing
> Intellitype the other day and re-booting but the errors were still there
> so
> I re-installed the MS software again.
>
> Hmmmmm....... curiouser & curiouser.