Keyboard Lockup

[Avien]

Been experiencing this problem since every build after 7229. Whenever I am playing a game, sometimes i will notice that my keyboard will act rather funny. I can no longer jump, hitting ctrl, i can no longer type while in game, after hitting y, and whenever I hit esc my game minimizes to desktop. The only way I have found to fix this problem is by either restarting or hitting, ctl + alt + del. I have also noticed that while the game is minimized and in this locked state, I can not type in any application I use, including internet browsers, office, anything.

The game that I experience this in is TF2, which uses Steam if it matters. I have only experienced this as a heavy possibly due to having to hold mouse 2 to spool the gun.

I have turned off all filter keys, mouse keys, sticky keys, language toolbar, high contrast keys, everything I can think of to get rid of the problem, yet nothing seems to fix it but going back to build 7229. Again, I never really noticed it in 7229, but maybe it was there too.


I use a MX518 mouse and an Logitech Elite keyboard.

Any ideas?

 

[zigzag3143]

keyboard driver

Been experiencing this problem since every build after 7229. Whenever I am playing a game, sometimes i will notice that my keyboard will act rather funny. I can no longer jump, hitting ctrl, i can no longer type while in game, after hitting y, and whenever I hit esc my game minimizes to desktop. The only way I have found to fix this problem is by either restarting or hitting, ctl + alt + del. I have also noticed that while the game is minimized and in this locked state, I can not type in any application I use, including internet browsers, office, anything.

The game that I experience this in is TF2, which uses Steam if it matters. I have only experienced this as a heavy possibly due to having to hold mouse 2 to spool the gun.

I have turned off all filter keys, mouse keys, sticky keys, language toolbar, high contrast keys, everything I can think of to get rid of the problem, yet nothing seems to fix it but going back to build 7229. Again, I never really noticed it in 7229, but maybe it was there too.


I use a MX518 mouse and an Logitech Elite keyboard.

Any ideas?

Hey Avien long time no hear. could you go into device manager (devmgmt.msc into search) and right click the keyboard get the properties and tell us if its working

Thanks in advance

Ken

 

[Avien]

Its been a while. Since there is real no more news about RTM till the 6th, I am taking a break from all the action until then. Need to rest up until all hell breaks loose.

Yes it is working. Otherwise I couldn't type this. Again, when it locks up I can't do really anything. Arrow keys still work, shift still works, and all the mouse buttons work. Once i unlock it, everything works fine. I can type ingame/out of the game, etc... It only seems to lock up while playing TF2, as I have not experienced the problem while browsing the internet or watching movies, etc..



It is using the default MS driver, and MS recognizes it as a Logitech US Keyboard. Either way, this is the same as in 7229.

 

[DJG]

OK, this could make it better or it could make it worse - have you tried using the Logitech Setpoint software? Out of desperation?

 

[Zidane24]

OK, this could make it better or it could make it worse - have you tried using the Logitech Setpoint software? Out of desperation?

I was going to reccomend the same...try setpoint and see if things go okay

 

[Avien]

Setpoint does not work with my keyboard. I don't think it is driver related, as I said it worked fine with 7229, but anything later then that and it locks up. I would have to use iTouch, but they only made that for XP and it was like 2 years ago. Vista and Windows 7 do not require any drivers according to Logitech for my keyboard.

 

[DJG]

Oh, right! I just noticed it's not a Setpoint-managed device. I saw how they dress up their non-support by stating "the basic functionality of your devices will be provided by the Windows native driver", operative word being "basic" .

It's true - I have an Edge and I can use it without Setpoint, but I get to customize it with Setpoint and it does install a Logitech driver. Oh well, just a thought.

What about checking the power aspect in the Device Manager? I noticed different ports in my MB seem to have different capacities - have you tried different ports? I know, it's a shot in the dark, but what the hell if there's nothing else left to try?

 

[Avien]

I havent touched anything since doing a clean install of 7600-16384 from 7229. Even then when going to 7264 i had the same problem. Like I said I have checked all the power settings and anything related to the keyboard and turned everything off. As far as I know there is no error to report when it locks up as nothing crashes, it just seems to be in a locked state waiting for a key to be hit to do some type of hotkey or shortcut type thing. I almost thought it was filter keys, but I have that completely disabled.

 

[DJG]

I was having this image of you going into a gaming frenzy pounding the keyboard so quickly that the power usage would climb way high and starve the USB circuit . That's why I thought if some other USB ports handle higher capacities, switching might help.

 

[Avien]

Well I am already using the ones that should be given the highest power, since they are straight into the motherboard. According to my manual, all the USB ports are the same. If it was a power issue, why would only some keys work, but then all of them work after I hit ctrl alt del? Either way I tried it and it did not work.

I am not even doing anything amazing when it occurs. I might hit ctrl a few times, or hold my mouse button for say 30 seconds while moving the mouse or using the arrow keys to move back and forth. I have noticed that occasionally i will lock in one position and start moving that way even when I am not holding any buttons down, kind of like it is stuck holding a key down. Getting out of that just requires me to hit a bunch of random keys.

Think it might have anything to do with the keyboard buffer limit?

 

[DJG]

I doubt it - try letting the auto-repeat fill it and see if you can make it lock up. But I wonder if it's some interrupt handling thing. Do you have a PS2 adapter so you could try that input and see if you get the same results? Just grasping at straws here .

 

[Avien]

I can try, but it is not always done the same way. Sometimes I play all day without it happening. I installed 7600 last week, and it only locked up yesterday once. The entire week before that it never did it once.

It is strange.


I am going to go back to 7229 and see if I can get it to do it there. Will post back if I find anything out. Seeing as RTM really hasn't been leaked yet, I am still going to test crap out.

 

[johngalt]

Try visiting the Logitech W7 RC forums and seeing if there is anything there - perhaps someone else has experienced your problem?

FWIW, I *just* bought a G15 (like 2 months ago from BestBuy) and although the driver does not *specifically* state W7 compatibility, I a using it without a hitch.

Windows 7 (RC) Discussion Topics - Logitech Forums

 

[Avien]

Well the driver wasn't even made for vista. It was made like a year before SP2 for XP came out. I'll ask in the Logitech forums soon as well. I just want to try 7229 again and see if i can get it to lock up.

 

[DJG]

Another thought - are you OC'ing. I had a strange experience. When I first moved to 385, after a day I got a BSOD. Then another. They started to happen now and then. I thought it was 385 so I restored my 7232 image, and things were fine. Then got a BSOD, which had never happen in about 2-3 weeks of 7232. Then got another.

Bottom line, although I had had no problems with my OC settings for a long time, apparently the HW must have slightly shifted its parameters. I re-balanced my OC parameters and no more BSOD in 7000/385 or 7232.

 

[SquonkSC]

Maybe it's Pizza related?

 

[DJG]

You mean like, gooey cheese behind the keys? Don't know ... could be a possibility

 

[Avien]

I have not OCed my computer at all. It is only 2 months old, though this keyboard is probably like 8 yrs old. It is also not pizza related either as I normally do a thorough cleaning of my entire computer and keyboard/mouse once every 3-4 months.

 

[johngalt]

Cleaning won't, however, fix things like shorts in the wiring and / or KB itself, which is another possibility....

 

[Avien]

How would going from 7229 to anything higher causing the problem be due to shorts? 7229 never seemed to have the problem, but I am back on 7229 waiting for it to happen again.