Keyboard Malfunction

--->
> Gerry and Olorin,
>
> I just want to let you guys know that you have been great with the help you
> have given me so far. I'm not a computer geek by any stretch of the
> imagination, but for the past 4 years there has not been an issue I haven't
> been able to resolve until now. Your help is greatly appreciated.
>
> That being said, other then the keyboard issue, the computer is running
> great. There is an issue from time to time when the computer has a mind of
> its own. It sometimes highlights things in blue without me making it do so,
> but it stops when I click in the right spot on the page I'm on. It's more of
> a pain in the ass than anything else, like when I'm writing in notepad,
> wordpad, or document. Been like that for a long time. Don't know what causes
> it, but I'm always able to type and post online.
>
> Anyway, whatever the problem with the keyboard is, I think it is related to
> the "LED" that lights up under the F10 and F11 keys. Those keys never lit
> before I began experiencing this current problem. I could be wrong about
> that, but it is curious. They only light up when I use the Fn key. Until now
> the Fn key was never touched deliberately, but when it was accidentally
> touched the "LED" never lit up. Only green light I ever saw are the ones
> that indicate power.
>
> Anyway, I can't thank you enough for the help you have given me so far. So,
> do we know what the problem is? By the way, haven't seen a "blue screen"
> since the problem arose either.
>
> Thanks again guys.
>
>

I've been following this thread because my Sony Vaio laptop occasionally
did strange things also. I narrowed it down to a keyboard "function
service" called 'HKserv.exe' which is a hot key server. It is supposed
to kick in when I press the Fn key and let me access such things as
volume, brightness, contrast, mute and switch from LCD screen to VGA
monitor. For some reason it started to go 'bad' (I know, software
doesn't go "bad" but this did) and I had to download and reinstall it.

The whole point of this is you might check for that type of service and
see if it is causing your troubles.

Wanderer

Service: "Human Interface Device Access" - From a newsgroup post: "The
following error will occur if any of the following three files are
missing, namely: "hidserv.dll", "mouhid.sys", and "mouclass.sys". Error
description: "Could not start the Human Interface Device Access service
on Local Computer. Error 126: the specified module could not be found".
To fix this problem extract "hidserv.dll"", mouhid.sys" and
"mouclass.sys" from the file "drivers.cab", located on the Windows XP
Setup CD to "<SystemRoot>\windows\system32\".
1. Insert Windows XP Setup CD.
2. Browse to <CDROM drive letter>:\i386\drivers.cab
3. Double click the "drivers.cab" file. The compressed files in the
".cab" file will be listed.
4. Copy the three files to "<SystemRoot>\windows\system32\". Reboot the
computer".
Source : EventID. net

Also read here:
http://www.blackviper.com/WinVista/S...ice_Access.htm

Some of the other Reports are going outside my understanding! How is or
was the computer networked?

I am also puzzled why some reports seem incomplete? How were they
copied?

Symbolic Name: EVENT_BOOT_SYSTEM_DRIVERS_FAILED
Message: The following boot-start or system-start driver(s) failed to
load: %1

Explanation
The specified drivers did not load correctly. The driver might not be
in the expected location.

Where it says "load %1" I would expect the name of a driver.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

truevirgo61 wrote:
> Gerry,
>
>
> Here's what I have for today, since I turned on PC this morning. I
> dont
> have access to a conventional keyboard. All laptops in our household.
>
> System Events
>
> Error
> 7:43am
> Service Control Manger
> None
> 7026
> N/A
>
> The following bootstart or system-start driver(s) failed to load.
> Avg7Core, Avg7RsXP (I haven't used Avg in almost two years.
> Currently
> using Threatfire)
>
> Details
> Product: Windows Operating System
> ID: 7026
> Source: Service Control Manager
> Version: 5.0
> Component: System Event Log
> Symbolic Name: EVENT_BOOT_SYSTEM_DRIVERS_FAILED
> Message: The following boot-start or system-start driver(s) failed to
> load: %1
>
> Explanation
> The specified drivers did not load correctly. The driver might not be
> in the expected location.
>
>
> Error
> 7:43am
> Service Control Manager
> None
> 7023
> N/A
>
> The Human Interface Device Access service terminated with the
> following error: The specified module could not be found.
>
> Details
> Product: Windows Operating System
> ID: 7023
> Source: Service Control Manager
> Version: 5.0
> Component: System Event Log
> Symbolic Name: EVENT_SERVICE_EXIT_FAILED
> Message: The %1 service terminated with the following error:
> %2
>
> Explanation
> The specified service stopped unexpectedly with the error indicated
> in the message. The service closed safely.
>
> Version: 5.2
> Symbolic Name: EVENT_SERVICE_EXIT_FAILED
> Message: The %1 service terminated with the following error:
> %2
>
> Explanation
> The specified service stopped unexpectedly with the error indicated
> in the message. The service closed safely.
>
>
>
> Warning
> 7:43am
> SNMP
> None
> 1101
> N/A
>
> The SNMP service is ignoring extension agent key
> SOFTWARE\Microsoft\IPXMibAgent\CurrentVersion because it is missing
> or misconfigured.
>
> Details
> Product: Windows Operating System
> ID: 1101
> Source: SNMP
> Version: 5.2
> Symbolic Name: SNMP_EVENT_INVALID_EXTENSION_AGENT_KEY
> Message: The SNMP Service is ignoring extension agent key %1 because
> it is missing or misconfigured.
>
> Explanation
> The Simple Network Management Protocol (SNMP) service cannot load an
> extension agent because the extension agent is no longer installed on
> the computer or is incorrectly configured in the registry key.
>
>
> Warning
> 7:42am
> Server
> None
> 2506
> N/A
>
> The value named AutoShareWks in the server's registry key
> LanmanServer\Parameters was not valid, and was ignored. If you want
> to change the value, change it to one that is the correct type and is
> within the acceptable range, or delete the value to use the default.
> This value might have been set up by an older program that did not
> use the correct boundaries.
>
> Details
> Product: Windows Operating System
> ID: 2506
> Source: Server
> Version: 5.2.3790.1830
> Message: The server service configuration was invalid but system
> recovered.
>
> Explanation
> This rule generates an alert any time a service attempts to start up
> with an invalid configuration. In this case, the alert has
> warning-level severity, denoting that while the service's
> configuration was detected as invalid, the service was still able to
> start successfully. However, the service may not be running in the
> desired configuration.
>
> Cause
> This alert occurs when the service's configuration parameters in the
> registry are invalid. Possible causes include:
>
> The service itself experienced an error while updating the
> configuration settings.
> The configuration value may have been incorrectly modified through
> manual administrative action.
> Another application incorrectly modified the service's configuration
> settings.
>
>
> Application
>
> Warning
> 7:43am
> EvntAgnt
> None
> 1015
> N/A
>
> TraceLevel parameter not located in registry;Default trace level used
> is 32.
>
> Details
> Product: Windows Operating System
> ID: 1015
> Source: EvntAgnt
> Version: 5.0
> Component: Application Event Log
> Symbolic Name: SNMPELEA_NO_REGISTRY_TRACE_LEVEL_PARAMETER
> Message: TraceLevel parameter not located in registry; Default trace
> level used is %1.
>
> Explanation
> Debug tracing is turned off. This is the default condition of the
> system. Debug tracing should only be turned on when you are debugging
> software.
>
> These error events will continue to be logged when you restart the
> computer, unless you reconfigure the Evntagnt.dll.
>
>
>
>
>
>
>
> "Gerry" wrote:
>
>> I suggest you post the first six Error Reports from the System log
>> for the current boot, if necessary reboot, so that we can see how
>> problems develop. All reports record the date and time. Most Reports
>> should be Information Reports and you can ignore these.
>>
>> Event Type: Error
>> Event Source: Service Control Manager
>> Event Category: None
>> Event ID: 7023
>> Date: 31/05/2008
>> Time: 01:40:42
>> User: N/A
>> Computer: PC0939
>> Description:
>> The Application Management service terminated with the following
>> error: The specified module could not be found.
>>
>> For more information, see Help and Support Center at
>> http://go.microsoft.com/fwlink/events.asp.
>>
>> You can dispense with the part of the Report corresponding to /
>> beginning with "For more information". The link only works on the
>> machine where the Error was generated. You can see further details
>> after the link but the information is not intelligble to us mere
>> mortals.
>>
>> What happens if you connect an old style wired conventional keyboard
>> U (used normally with a desktop)? Does it work without error?
>>
>> --
>>
>>
>>
>> Hope this helps.
>>
>> Gerry
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~