kbdclass.sys BSODs

[Urfe]

Hey there, I’m creating this post over here, because I’m unable to create one in the BSOD-proper section.
[ATTACH type=“full” alt=“1714857711288.png”]13670[/ATTACH]
[HEADING=1]I have recently bought a new laptop - GIGABYTE G7 KF (RTX4060, 16GB RAM, I5 12500H) - x64 system
And since the time of purchase I have been encountering BSOD’s - DRIVER_IRQL_NOT_LESS_OR_EQUAL relating to the kbdclass.sys driver.
As far, the BSODs are occuring roughly once a day/once two days, while playing games (both less and more demanding titles).
So far, I have resulted myself to:
Reinstalling all Keyboard/related drivers
Reinstalling motherboard drivers
Reinstalling USB/HID drivers
Removed Hotkey/Keybind software
Tried to disable referring to kbdclass.sys via register edit. (DETAILS BELOW)
As according, to one of the online posts i’ve found regarding the same issue, it was apparently that HKKbdFltr tried sending data that kbdclass.sys could not process, resulting in BSOD.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class{4d36e96b-e325-11ce-bfc1-08002be10318} - in the “upper filters” config file, i’ve removed the HKKbdFltr line from it.[/HEADING]
I’m also attaching .speccy file in the archive.
(SysnativeFile uploaded on google drive, because it was too big).
[MEDIA=googledrive]1hA8WB_Kuh_iihr9ycd4422BFIYv-tb3T[/MEDIA]

[phillpower2]

Download then run Speccy ( free ) and post the resultant url for us, details here, this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s.

To publish a Speccy profile to the Web:

In Speccy, click File, and then click Publish Snapshot.

In the Publish Snapshot dialog box, click Yes to enable Speccy to proceed.

Speccy publishes the profile and displays a second Publish Snapshot. You can open the URL in your default browser, copy it to the clipboard, or close the dialog box.

[Urfe]

There you go, I forgot that this forum does not accept .speccy files.

https://speccy.piriform.com/results/ss4WxA2GUhJzvUEFraQ3Qna

[phillpower2]

Your crash dmps flag hot key drivers as being the cause and after looking at Speccy we can see that the notebook has not been set up correctly from day one, as to why is explained below but can I first of all mention a couple of other things.

If fast boot is enabled, disable it.
Power Profiles
[COLOR=rgb(184, 49, 47)]Active power scheme: Balanced
[COLOR=rgb(44, 130, 201)]Hibernation: Enabled
[COLOR=rgb(184, 49, 47)]Turn Off Monitor after: (On AC Power): 1 min
Turn Off Monitor after: (On Battery Power): 1 min
Turn Off Hard Disk after: (On AC Power): 20 min
Turn Off Hard Disk after: (On Battery Power): 10 min
Suspend after: (On AC Power): Never
Suspend after: (On Battery Power): Never
Screen saver: Disabled

Change your Windows Power Plan to High Performance when gaming or watching videos, your dedicated GPU will not get the power that it needs to be able to function properly if you don`t, you must also power the notebook using the AC adaptor and mains power for the same reason.

If only while troubleshooting change all those in red to Never, no point in trying to fix things only for one of those settings tripping the system up.

Disable the problematic Hibernation setting, it not only causes stability issues but also uses up a chunk of resources such as the RAM.

To disable Hibernation:

1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt
2. Type in “powercfg.exe /h off” without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input
3. Now just exit out of command prompt

Now your explanation;
Once Windows has been clean installed you must then install first the MBs chipset drivers then the storage/SATA drivers and third the graphics drivers, the drivers can either come from a disk provided by the motherboard manufacture[COLOR=rgb(184, 49, 47)]r ** or downloaded from their site and saved to a flash drive etc, this is a must and Windows should not be allowed to check for updates before it has been done as more often than not Windows installs the wrong drivers or in the incorrect order and this can cause all sorts of problems.

The reason why this procedure is so important, the chipset is what enables the MB to be able to communicate with all the hardware + are the first drivers that Windows looks for on boot.

[COLOR=rgb(184, 49, 47)]** For OEM computers/notebooks such as Acer, Dell, HP and Lenovo etc you must only download drivers from their support page, OEMs may sometimes redirect users to a third party site such as AMD or Nvidea to obtain the latest drivers for their GPUs, this tends to be for high end gaming notebooks and desktops though.[/COLOR][/COLOR][/COLOR][/COLOR][/COLOR]

[Urfe]

Okay, I have followed your instructions regarding power profiles, disabled hypernation. [Fast boot has been disabled already] - Thanks for the advice.

First thing - regarding the hot keys, I was guessing it’d be one of the possible issues. I’m pretty confident that the culprit is pre-installed software CLEVOCO CONTROL CENTER (as it provides hotkey editing). I’d love to get rid of this software, but unfortunately, it’s the only one that is able to manage my fan speed in the laptop, so i’m kind of stuck. (Tried argus monitor and fan control, did not work) - i’m open for any ideas, in that case.

But, about the hotkeys, is there any particular imput/prompt that causes the BSOD? As far as I noticed, the bluescreen always appeared whenever I was holding buttons, but I haven’t seen any pattern of it, initially thought it might be while holding a shift, but most recent one proved me wrong on it.

As far I’ve checked the internet, the similar GIGABYTE models had this issue with keyboard drivers BSODs and in most cases ditching the control centre was the working solution. Also - updating the control center itself from GIGABYTE website (as I had slightly outdated at the time) did not help at all.
At this point, it’s a no-brainer to just uninstall it, unless there might be a workaround?

[phillpower2]

Apologies for the delay, will get back to you after work today.

[COLOR=rgb(44, 130, 201)]Edit to add: Uninstall the problematic Gigabyte program then download MSI Afterburner which works with most if not all other brands of hardware, of particular interest for you will be Step 3: Creating Your Custom GPU Fan Curve Using MSI Afterburner in the tutorial here[/COLOR]

[Urfe]

I think I’ve got a good news.
Remember when I mentioned the pre-installed software - CLEVO CONTROL CENTER?
For a started I uninstalled it and reinstalled again, turns out, it has installed two control centers, while both functional and almost identical, one is much more feature-stripped and outdated than the other one.
Initially I thought that is an extension of the default program, but no, the bottom one runs independently and without any problems after uninstalling the old
one. Also from now on, it actually displays the CPU clock rate properly (it used to show -1 clock rate), meaning that those two programs were most likely overriding one with the other.
I have uninstalled it yesterday and as of now, everything looks good.

If any BSODs will occur, i’ll ditch the other program too.

I use MSI Afterburner on the daily basis (For the OSD), unfortunely fan management option is locked out from me and does not work even via config file. (screen below). The GPU built-in fans do work without software nonetheless.
Side note: The software is only responsible only for exhaust fans, which after uninstalling the program are dead silent.

[ATTACH type=“full” alt=“1715106118940.png”]13688[/ATTACH]
[ATTACH type=“full”]13689[/ATTACH]

[phillpower2]

Looks promising, good work on your behalf and thank you for sharing the information for the benefit of others (y)

[Urfe]

Thank You, took me two months of work to get to it, but in the end managed to finally find a solution. Which wow, cannot believe it was THAT simple.
I appreciate all the help provided and time spent on helping me out.
I hope that all the issues that people come with here are as easy to fix as this one, now I can finally sleep easy knowing, that everything is alright.

The thread can be considered solved = )

[phillpower2]

The thread can be considered solved = )

Great and thank you for the follow up (y)