Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have the strangest problem that started 2 days ago (Windows7, 64bit). SOMETHING causes my F5 key to be constantly pressed. Rebooting helps, but only for a while, it keeps coming back to that.

So far I've tried to disconnect and reconnect the keyboard (physically), however, disconnecting the keyboard doesn't actually do anything. Reconnecting it back again, causes the F5-pressing to stop, but not for very long (seconds/minutes).

I'd really like to avoid a binary search for the programs (process closing/keyboard switching/etc) before I can, at the very least, identify the source of the keypress. Is there an application that can show me what is causing a key press? E.g is it the keyboard driver, or some process that executes SendKey repeatedly for reasons unknown.


P.S FYI, having F5 causes the strangest side effects. Task Manager refreshes very very quickly (as F5 is refresh), the desktop is constantly flickering and all the browsers stop working as they keep trying to refresh. I was lucky to find out what the heck is happening only because I started notepad and saw that current date/time started to appear constantly. If not that, I'd still be wondering.

P.S.S Another tidbit that might turn useful for anyone experiencing a similar issue: The problem described, turned my workstation effectively unworkable, as you can understand from the symptoms described above, the best solution I found so far is using AutoHotKey with the following script:


Which effectively disabled F5 key system-wide. It works great and almost without any CPU loss, still, of course, I have to get the issue solved.

share|improve this question
Similar question:… – Hugh Allen May 24 '10 at 2:11

Have you tried a replacement keyboard?

share|improve this answer
I will try that. Will let you know how it went. I wanted to avoid it as I had no near keyboard replacement. Thanks! – VitalyB May 25 '10 at 11:14

I had a Konica Minolta Printer driver do something like this. It was a 'Universal' driver. needless to say we restored the original driver that came with the device.

share|improve this answer
Hmmm.. Strange. How did you discover it was that driver? – VitalyB May 25 '10 at 11:14
It was the only thing changed on the server before the strangeness started. You even hear the click. Procmon from sysinternals confirmed the finding. – ggonsalv May 25 '10 at 16:38
Confused. How can I use process monitor to monitor which process/driver presses a key? – VitalyB May 26 '10 at 20:04
We noticed when the screen refreshed, what processes were actually running. We could NOT see the keyboard buffer since most of those utilities get detected a keyboard loggers in our anitvirus program. – ggonsalv May 26 '10 at 21:07
up vote 0 down vote accepted

Well, turns out it WAS a hardware problem. As I said before, the problem persisted when I plugged out the keyboard, HOWEVER, I forgot I have more than 1 keyboard connected - I have a second media keyboard which sits under the table and is wireless. Apparently the cat pressed the button sometime during the night and it got stuck =\.

Thanks for trying to help everyone.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .