Computer Typing By Itself

[TurricanII]

Whilst troubleshooting is great fun when you're new to the business I would recommend to Windows System Restore to a point before the problem occurred if at all possible for a quick fix.

 

[redagent001]

I think the OP mentioned changing KBs so that puts it on the computer not the KB and that theory could be tested by plugging in the KB into another PC. If it is the keyboard at fault it should continue on any PC it is plugged up to.

Yes. Tried that as well. Its on the PC and its something else. Used Malware bytes again, and then Superanti spyware and avast to scan and nothing comes up.

 

[Slaters Kustum Machines]

Have you checked scheduled tasks or run autoruns? What about safe mode?

 

[ComputerRepairTech]

Yes. Tried that as well. Its on the PC and its something else. Used Malware bytes again, and then Superanti spyware and avast to scan and nothing comes up.

Unlikely to be malware but ....how long has avast been on the machine? Did you know avast hooks into the keyboards upperfilter registry entry? its possible something could be wrong with the avast install.

 

[mrapoc]

Have you tried a linux live boot yet?

 

[redagent001]

My next move is to do a windows refresh see if that works once I backup a few important information.

Unlikely to be malware but ....how long has avast been on the machine? Did you know avast hooks into the keyboards upperfilter registry entry? its possible something could be wrong with the avast install.

I surely never thought about that. Ill take a look at that tonight.

 

[redagent001]

Have you tried a linux live boot yet?

I have prepared a Linux cd, thats already on my to do list once I return to the office.

 

[redagent001]

Unlikely to be malware but ....how long has avast been on the machine? Did you know avast hooks into the keyboards upperfilter registry entry? its possible something could be wrong with the avast install.

Have you checked scheduled tasks or run autoruns? What about safe mode?

I have checked auto runs but haven't tried safe mode yet. I will be heading back to the office. I have manually cleaned a out of the leftovers of the program for the keyboard. Which now it does just 70 over and over. there is a change but all day she stated nothing happened at all. Until later last night. Its completely random.

 

[Larry Sabo]

I have prepared a Linux cd, thats already on my to do list once I return to the office.

That should have been done very early on (running a Linux live CD to triage between hardware and OS problem). Proposing to Refresh Windows before such a fundamental step is completed is bass ackwards... er, putting the cart before the horse.

 

[Diggs]

As @nlinecomputers said, when diagnosing hardware from software problems, throw a Linux DVD in and boot. It'll help sort out your problems and give you another set of tools.

 

[redagent001]

"We had to destroy the village in order to save it."

Now where have I heard that before?

Despite its fluffy name a Windows Refresh is about the most destructive thing you can do to a computer short of a nuke and pave and should be treated as a last-ditch method that you only use once everything else has failed. It's an admission of defeat - please don't do that.

Windows Refresh is also a nice example of how Microsoft is reducing all personal computers to the level of disposable tablets - if it doesn't work right, wipe and reinstall or throw it away and buy a new one. Don't think, just spend!

No no. Don't get me twisted. I hate doing the nuke. DONT WANT TO. Its always my last thing on the list. Its too much of a hassle to refresh or nuke. But I always consider it no matter what but I will do what ever it takes before that ever happens. I know there is a solution.

 

[redagent001]

That should have been done very early on (running a Linux live CD to triage between hardware and OS problem). Proposing to Refresh Windows before such a fundamental step is completed is bass ackwards... er, putting the cart before the horse.

Again. I don't nuke or refresh before I try anything. I initially thought it was a simple program issue with the keyboard/corsair and some dumb macro but that may not be the case. Now i did not think to use Linux to test first. My bad on that.

I enjoy the process of investigating issues to learn how to fix them instead to just redo system. I will admit a nuke or refresh is just that last resolution I consider. Depending on time. Back ups are ready whenever.

 

[katz]

Again. I don't nuke or refresh before I try anything. I initially thought it was a simple program issue with the keyboard/corsair and some dumb macro but that may not be the case.

If this would happen to be something like a rootkit, it would most likely survive a refresh anyway. It would be beneficial, required really, to set up a coordinated plan of diagnosis, create a troubleshooting flowchart, etc.. When I bring a system into the shop, they all get the same treatment/repair to insure that nothing is overlooked/missed, or that I don't waste precious time going over the same steps, or spend time throwing different tools/fixes at it willy nilly.

As Larry stated earlier, a boot disk should have been one of the first things in troubleshooting. If a pc is more than a year old, I usually will remove the back (laptop), even tear it completely down & clean/re-seat everything, reapply thermal paste, etc. Nothing like starting with a fresh system to rule out any hardware issues, low cmos batt., ,and so forth.

 

[Larry Sabo]

... or "Throw it against the wall a few times until there is clearly something that needs fixing."