Question the seasonal, unpredictable BSOD

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Dec 26, 2021
17
0
10
0
Apr 25 2014HpqKbFiltr64.sysHP Quick Launch Buttons driver
remove that or update it if there is a version that is from the last 2 years or so.

It was cause of the last BSOD. See if that fixes your problem, or not.

I fell over on 10th December. I have bruised ribs, and if I am not on pain killers, its really hard to sleep at night, and my hand also aches - it was injured at time but I can't normally tell. I now have a month off to recover.
HP Quick Launch Buttons driver is no where to be found in my pc, nothing, i CCleaner and revo installer couldn't find it, however i found the driver itself in C:\Windows\System32\drivers, do i just delete it normally ?

EDIT: its called HP hotkey support not HP Quick Launch Buttons driver, last modified date is the same day i bought this laptop, also couldn't find it installed anywhere, the driver is the only visible thing.
 
Dec 26, 2021
17
0
10
0
No. Use AutoRuns. Be careful with AutoRuns and don't disable anything else. There is a "drivers" tab in AutoRuns.
i can't delete anything with autoruns. it always say "failed to delete HpqKbFiltr64", i tried to delete iocbios2.sys as a test but it also failed (i ran it as administrator)
 

gardenman

Distinguished
Moderator
I think newer versions of AutoRuns are buggy, and that is what is causing the issue. Source: https://docs.microsoft.com/en-us/answers/questions/532031/autoruns-v14-can39t-disable-or-delete-entries.html

Apparently version 13.98 works correctly, if you can find a good copy of it from a legitimate source. Be careful about downloading it from questionable sources. I have a original copy of 13.98 but it's discouraged for us to share files with users on here (for obvious security purposes).

They remove the older versions, but after several minutes of searching I finally found a link to 13.98. Give it a try.
https://web.archive.org/web/20201112005659/https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
 
Dec 26, 2021
17
0
10
0
I think newer versions of AutoRuns are buggy, and that is what is causing the issue. Source: https://docs.microsoft.com/en-us/answers/questions/532031/autoruns-v14-can39t-disable-or-delete-entries.html

Apparently version 13.98 works correctly, if you can find a good copy of it from a legitimate source. Be careful about downloading it from questionable sources. I have a original copy of 13.98 but it's discouraged for us to share files with users on here (for obvious security purposes).

They remove the older versions, but after several minutes of searching I finally found a link to 13.98. Give it a try.
https://web.archive.org/web/20201112005659/https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns
ok so i deleted it via the autoruns that you linked me, it disappeared from the driver tab but the driver is still present at C:\Windows\System32\drivers , is there something i'm not noticing or it will be removed later ?
 

gardenman

Distinguished
Moderator
As long as it's unchecked in Autoruns, and the software that previously loaded it is nowhere to be found on your system, then it's very unlikely that the driver is being loaded at all. Which is what we want. It can stay right where it's at and not be an issue.

Watch for additional BSODs. If you have them, upload the dumps. If the dumps show the driver is still being loaded, then we'll consider removing it at that point. For now, leave it be.
 
Dec 26, 2021
17
0
10
0
As long as it's unchecked in Autoruns, and the software that previously loaded it is nowhere to be found on your system, then it's very unlikely that the driver is being loaded at all. Which is what we want. It can stay right where it's at and not be an issue.

Watch for additional BSODs. If you have them, upload the dumps. If the dumps show the driver is still being loaded, then we'll consider removing it at that point. For now, leave it be.
ok horrible news, every time i get rid of it, my mouse and touchpad does not work + it goes through boot loop cycle, the only thing that saved me is the point restoration that i made before making this post, this is an official bruh moment
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
55,450
4,333
160,590
10,080
I wonder if windows auto installs that driver,
catch 22 if you need driver but it also causes BSOD if its there.

wonder what version number it is, might let me work out if there is a newer one

Can you download and run Driverview - http://www.nirsoft.net/utils/driverview.html

All it does is looks at drivers installed; it won't install any (this is intentional as 3rd party driver updaters often get it wrong)

When you run it, go into view tab and set it to hide all Microsoft drivers, will make list shorter.

Can you take a screenshot from (and including)Driver name to (and including)Creation date.

upload it to an image sharing website and show link here

it will show me the version number.
 
Dec 26, 2021
17
0
10
0
Colif something funny happen now, it seems the BSOD is gone (not entirely sure if it gonna come back, hopefully not) after i did a entire wipe of the system drive (the drive where i store my files, games..etc is still intact), fast forward few weeks later and then my laptop shuts off while i was watching a youtube video, restarts and boot up, the thing is that majority of my stuff are gone (i can do a restore point and recover, no worries here), not all of them, some remained and some disappeared, but it did produce a minidump file, i opened the minidump folder to check and i was surprised that there was a dump file, i have no idea if the BSOD that i keep encountering and this problem that i got now are related but i hope i can resolve this issue.

here's the dumpfile :

 

gardenman

Distinguished
Moderator
I ran the dump file through the debugger and got the following information: https://jsfiddle.net/aguxwzs4/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:012622-10218-01.dmp (Jan 26 2022 - 06:30:05)
Bugcheck:VIDEO_TDR_ERROR (116)
Driver warnings:*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:memory_corruption (Process running at time of crash: System)
Uptime:0 Day(s), 14 Hour(s), 15 Min(s), and 57 Sec(s)

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

ASK THE COMMUNITY

TRENDING THREADS