Emin

New Member
Joined
May 15, 2015
Messages
13
I recently bought a new USB keyboard (GK-004 Silvio) and a new USB Mouse (Dragon War Thor), and I seem to be experiencing BSODs with my new keyboard. (had been using PS/2 keyboard and mouse before with no problems till date). I then updated all of my drivers using Driver Booster, and the problem stopped, until I restarted for the next time. Now as soon as I press a key after logging in, it gives me a BSOD right away and it doesn't let me see the message (as it did for the very first time, and it also restarts too just right after the BSOD). I got lucky one time and saw that the message was:
"DRIVER_IRQL_NOT_LESS_OR_EQUAL" due to 'kbdclass.sys'

1. I've run for a virus scan and I couldn't find any threats.
2. I've cross checked that all my drivers are up to date. There were no specific keyboard drivers/softwares included with my keyboard nor could I find any online.
3. I've been self-logging myself with the help of Spyrix for a few days due to personal reasons. The BSOD occurs irrespective of Spyrix logging/running and as I mentioned, it worked perfectly fine for a whole day until I restarted during which Spyrix was working. (It doesn't crash with my old PS/2 keyboard)
4. I've run TDSSKiller and found no threats.
5. My USBs currently include: Speakers, XBox 360 Controller, New USB Mouse (which seems to be working without any problem)...I don't suppose any of those could cause any problems.
6. I've done a sfc /scannow, it said that it found some corrupt files and was unable to repair them. Maybe I should do it in safemood or with a W7 DVD inserted? After the restart, the issue wasn't resolved.
7. The keyboard works fine in Safe Mood.
8. There are currently no dumps in my minidump folder.

Below is a link to dm_log_collector log..hope it helps. Thanks. (:
db.tt/pWUvFyl9
 


Solution
Some of these driver updating software tools are garbage. You need to re-verify your drivers. The issue is likely caused by memory corruption caused by a bad driver. There are methods to solve your problem using the Driver Verifier option in Windows as well as analysis of the BSOD Mini Dumps. I see @kemical has posted before I replied, so please try to follow his advice. If you have system restore, try to go back before you installed your mouse/keyboard software, and revert the changes you made with "Driver Booster". This may, at least, allow you to run your system with Microsoft compatibility drivers until it can be determined what is causing your problem. The idea here is that if you make incremental changes and not major ones...
Sorry Emin I didn't see your edit from Tuesday.

Hmm.. your options are getting smaller. Personally I'd have re-installed ages ago but then again I keep a lot of stuff backed up so for me it's relatively simple. I'm trying to think of a way you could try and remove these drivers.... Check and see if there is still an Evolve folder in the Program files (x86) if there is, see if you can find the relevant drivers (outlined in the task manager above) and rename them to something like Evokbfilter.old. Regardless of what the driver is called just rename it so it has .old at the end.
I'd create a system repair point first as well as making a backup of the files your going to change (just make a copy of each driver in say your documents folder) just in case it doesn't work and you need to go back.
 


I'm sorry, I've been kind of busy the past two weeks.
The drivers can be located at "C:\Windows\system32\drivers". Earlier I tried disabling those driver services which rendered my mouse and keyboard unusable. I tried recreating my 'infcache' (but I didn't delete all the greyed out USBs, there were too many) but it didn't seem to work either. I could try that again though.

In short: I've uninstalled Evolve completely yet the drivers remain in the system32/drivers folder. Tried rebuilding infcache, tried your SP1 update and then installed all the windows updates. I could try renaming it although it's still in use as reported by the task manager. Tips?
 


Try different USB ports as some are different. In fact if you still have the old keyboard you could pop that back on and then remove those evolve drivers. If you try the USB keyboard again try a different USB port than the one it was originally in.
If you don't have your old k'board then make copies of the evolve drivers and then try and break them by renaming so that '.old' is at the end. If it doesn't work you can always pop the copies back in their place although you might have to boot into safe mode to do so.
 


Sorry for the late reply once again, been kind of busy.
I've tried different USB ports.
Yes, I still have my old keyboard which is a PS/2 keyboard and I'm still using it at this very moment.
I could try renaming the drivers, I just hope it doesn't render my keyboard useless as the last time I disabled it's service, my keyboard didn't work. I'll let you know about it.
 


Just remember to create a restore point and/or back up the original files.
 


Back
Top