Plausible that the keyboard driver is using a call which has been deprecated in that KB, or the values the call are expecting are invalid. The best course of action here is to reach out to the keyboard vendor and inform them of the issue, so they can update their driver.
From the release note text on that KB
Updates to improve security when using input devices (such as a mouse, keyboard, or stylus).
This is most likely the root-cause.