BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL (kbdclass.sys)" error with new Desktop Keyboard and Mouse

Original Title[kbdclass.sys BSOD with new Microsoft Keyboard]

I just bought a new Microsoft L5V-00001 Sculpt Ergonomic Desktop Keyboard and Mouse which worked fine out of the box for a few days but now crashes me to BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL (kbdclass.sys)" upon first keystroke.

I read through post after post and it seems providing the crash dmp and msinfo is the best way to receive the correct advise:

Accordingly I've uploaded the dmp and msinfo to the following DROPBOX folder to be referenced by anyone who feels capable of helping.

https://www.dropbox.com/sh/jf11fvx7r0g3fkg/AABRVrgHnO3nu4mPRnhEpwoja?dl=0    <----DROPBOX WITH DMP AND MSINFO

Thanks in advance for anyone who can advise on a solution.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello,

Welcome to Microsoft Community.

This bug check is usually caused by drivers that have used improper addresses.

I suggest you to follow the article below and check if it helps:

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Hope the above information helps. Reply with necessary information and the result to help you further.

Thank you.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Anju,

While I appreciate the same day response the link you provided left me with 2 options:

  1. To check for updates which I did and was notified that my keyboard drivers were already up to date.
  2. Remove the hardware... Which wont work as I need my keyboard.

I attempted to roll back my keyboard driver and still have the same problems.

I've been using my old keyboard in my attempts to make changes to the drivers but as soon as I swap the USB dongle to the new keyboard it crashes on the first few keystrokes.

As I mentioned in the original post, I uploaded the dmp files and MSINFO to the dropbox for reference.

Could you or someone reference them to identify my issue?

Is there someone who is familiar with Microsoft L5V-00001 keyboard driver issues who can assist?

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi,

I don't believe the issue is with the keyboard.

The dump files you provided reference the WirelessKeyboardFilter.sys :

BugCheck D1, {0, 2, 1, fffff801f0122eeb}

*** WARNING: Unable to verify timestamp for WirelessKeyboardFilter.sys
*** ERROR: Module load completed but symbols could not be loaded for WirelessKeyboardFilter.sys
Probably caused by : kbdclass.sys ( kbdclass!memcpy+2b )

The WirelessKeyboardFilter.sys is from Microsoft and may have been recently updated as per the following article:

https://support.microsoft.com/en-us/kb/3152550

However another user has reported the same error in this topic and according to the dump files you both have the  WRkrn.sys (dated July 22, 2015) as a loaded driver.

The WRkrn.sys appears to be a component of Webroot SecureAnywhere.

Because of this similarity I might suggest to uninstall Webroot SecureAnywhere and see if the error resolves.

Afterwards you could reinstall Webroot SecureAnywhere using the latest version.

For security software consider using Windows built-in antivirus (Windows Defender) and firewall.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Has any body been able to prove that it is Webroot? Or has it occurring without Webroot? I have Webroot installed and can't remove b/c of IT :( But it could be a red herring too about driver load order and the issue could still be in kbdclass.sys. Certainly the crash occurs always while typing. Of course wrkrn.sys could have written over memory in kbdclass.sys.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I don't see any direct evidence that it is Webroot, just so far the wrkrn.sys is a common driver in two instances so far.

In this topic it seems uninstalling Webroot seems to be working.

I am still waiting for a reply here.

The issue could be a Microsoft driver but if that was the case I would suspect more users would be reporting the same error rather than a limited number of users.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have just experienced this same issue, but with the microsoft keyboard and mouse combo 5050.   I couldn't even get into the computer to removed webroot.  I had to removed the mouse/keyboard, then use my on screen keyboard to remove webroot.  Rebooted and now I can use the mouse and keyboard.  

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Exact same problem began affecting my Windows 10 Enterprise desktop system after installing the same Microsoft Sculpt Ergonomic Keyboard with wireless (USB) connection as reported in the original post on this topic.  System works fine with USB antenna device unplugged and a wired keyboard and mouse plugged in.  

Uninstalling WebRoot followed by a full reboot did not solve this problem.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Uninstalling webroot fixed mine but as soon as I reinstalled webroot the problem came right back. I have Geek squad support try a few things like update my bios but nothing. They did find that my motherboard battery was dead which he said can cause wired issues. I'm working on getting that done and will update from there. 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks everybody for the information. Removing webroot on my machine did work as well (no longer experiencing crashes). IT is going to re-enable webroot today to debug and we are going to see if there are any file locking issues with webroot (although I think the driver sys files should be system and signed properly so they shouldn't be an issue). 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Uninstalling WebRoot followed by a full reboot did not solve this problem.

Can you check that the WRkrn.sys  is no longer "active" on the system:

Windows Key + R > type msinfo32.exe in the "Open" box > OK > Software Environment > System Drivers

In the right window under "Name" scroll down and see if WRkrn is listed and if so what is the "State" of WRkrn?

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated February 12, 2023 Views 12,792 Applies to: