[Crash&Client&Gameplay] Input lag of some kind & Crashes

Since the Azir update, I've noticed a bug with ability responsiveness that is NOT limited to Azir. So far, I've noticed Warwick's Q and ult, Kayle's ult, Ashe's ult, Soraka's entire kit, and occasionally the auto-attack command on Warwick occasionally being sluggish or completely unresponsive. This has put me in a lot of bad situations in duels AND teamfights, and as you might imagine I've also had to deal with an excessive amount of toxicity related to these failures. Warwick's Q is essential to his dueling power, delay on Ashe's ult throws it off completely, and delay on Kayle's ult ALWAYS gets someone killed. If anyone else has noticed this issue, please bump this thread and make a note; if anyone knows how I might fix this issue (I have reinstalled the game a few times and I'm certain my hardware is working, and it is consistently the same abilities and champions) I would also appreciate that greatly.

The second issue, I've only noticed since the most recent patch (4.17 at the time of writing). I initially thought it was an Azir animation bug, but I've had crashes to desktop with a bugsplat followup in the middle of several games- interestingly enough, Warwick is again the most consistent crashmaster, with some games crashing 2-3 times. I've also seen this bug on Nasus. I have no idea what could be causing it, but I have had several other players complaining about bugsplat CTDs as well- both on my team and the opposing team, seemingly at random. Riot please!

(P.S. : Bugsplat might be more efficient if it automatically sent a report or was at least a one-click send. Most players don't have time to fill out a form after a crash, as it's almost always at a high-pressure moment (with the greatest density of things to go wrong) that the player will want to get back to ASAP. When there's a set of boxes to fill in, it's reflex to hit 'don't send'.) (P.P.S. : Other players, please! Post if you've noticed either of these particular issues. The more comments on this thread, the more weight it will bear. Obviously, that increases the chances of the bugs being addressed by 4.18 )