BF4 PC stops responding to mouse and keyboard input

I'm having the exact same problem.

I think it's the BF4 window that releases the mouse or "fullscreen input lock". Because, when this happens my cursor can be dragged on to my second monitor. That could explain why the character keeps on walking. I've seen this kind of behavior in other games as well, when you tab out.

• I'm on the latest drivers
• Switching between the different window modes did not help
• Turning 'raw mouse input' didn't work either

did you ever find a solution? this bug makes me rage like no other =/

Bumping the Topic.

There's a workaround that decreases the likelihood of it happening, but doesn't get rid of it altogether and that is to close the browser when Battlelog says that the level is loading after logging into the server. I need some answers as to why this is happening in the first place. Is it due to a bug, network issues, graphics drivers, my system...?

I am having the same issue. I have noticed that when I play certain maps it can be worse then other maps. I use a 705 a k750 and a wireless logitech headset. I am stumped as to why this is happening.

I'm not sure if this will help but I'll take a stab at it.

I have encountered this problem in the past in BF3 and Planetside 2.  For me my CPU was capping at 100% which would in turn cause my mouse / keyboard input to stop.  After a few seconds it would finally respond but during the time my character would either be sitting in place or running in the direction I last sent it.

I recently upgraded from a core 2 quad to an i7 and I no longer have these issues.

Have you checked your cpu load during the time it's not responding?

I haven't noticed any CPU spikes. The framerate doesn't seem to drop when it's happening and everything else seems normal ie you can see the other players happily moving about and shooting each other. If the CPU was maxing out, there would also be a drop in framerate(as was evident the last time I played PS2) as well as a failure to respond to inputs. I have an AMD x6 1090T and very few things can max out my CPU. I run quite CPU-hungry audio apps and run a ridiculous amount of FX, and my RAM is maxed out way before my CPU. I also sometimes run number-crunching tasks for CERN and protein-folding simulations which are also capable of maxing out my CPU. I somehow doubt that BF4 is as CPU-intensive as those. If it is, then it's likely to be due to a bug. I will check when I next play as I'm not sure it isn't due to CPU load.

[edit] just played with the browser open and while there were some small CPU spikes, none of them were suffcient to max out the CPU and the load was balanced fairly evenly across cores. The game froze when I spawned in and there was a RAM spike that occurred for about a second and the RAM used decreased steadily after that, but the game failed to respond to any input for about 10 seconds. I don't know that the RAM spike was the cause of the problem, but it could be the culprit. I will try again to see if there is any connection between the RAM and the freezing issue.

It's taken me a while to get the problem to occur again, but this time I noticed that there was a very clear 100% CPU spike for a very brief time ie every core was showing 100% usage, but the game did not start responding again for about 10 seconds. The RAM usage was also very high, but it didn't look as if anything unusual was going on. Again, there was no obvious drop in framerate, probably because of the short time it took for the spike to occur.

Well I'm glad to have given a little insight.  It took me forever to figure out why my machine was doing that but I was easily able to duplicate the problem while attempting to stream.  

I haven't been keeping up with things to know if there are any optimizations in the works but hopefully your problem is being looked at.  If not you might want to try and find other players who share your problem and band together to move it up the chain.

Good luck!

I have a 360 controller also hooked up to my PC also, and was able to instantly fix the behavior by tapping the controller (which never stopped working) and then going back to the mouse (which suddenly started working again.