-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Boot and Lockup
- BSOD says Device Driver Attempting to Corrupt the system

Create an account on the HP Community to personalize your profile and ask a question
03-18-2019 03:39 AM
HP p6710f running Win 7 64 bit.
Getting BSOD saying " A device driver attempting to corrupt the system has been caught. The faulty driver currently on the kernel stack must be replaced with a working version."
Unfortunately I have no idea how to identify a faulty driver, or how to replace it.
I have a log of the MiniDump and other files, but do not see any way to attach it to this post. Thank you.
03-18-2019 09:14 AM
Hi
Could you start in Safe Mode with minimal drivers and see if that has excluded the dodgy driver?
In W10, and allegedly W7, you can list all the drivers and pipe the output to a Text or whatever...
C:\>driverquery /?
DRIVERQUERY [/S system [/U username [/P [password]]]]
[/FO format] [/NH] [/SI] [/V]
Description:
Enables an administrator to display a list of
installed device drivers.
Parameter List:
/S system Specifies the remote system to connect to.
/U [domain\]user Specifies the user context
under which the command should execute.
/P [password] Specify the password for the given
user context.
/FO format Specifies the type of output to display.
Valid values to be passed with the
switch are "TABLE", "LIST", "CSV".
/NH Specifies that the "Column Header"
should not be displayed. Valid for
"TABLE" and "CSV" format only.
/SI Provides information about signed drivers.
/V Displays verbose output. Not valid
for signed drivers.
/? Displays this help message.
Examples:
DRIVERQUERY
DRIVERQUERY /FO CSV /SI
DRIVERQUERY /NH
DRIVERQUERY /S ipaddress /U user /V
DRIVERQUERY /S system /U domain\user /P password /FO LIST
i used the CSV and signed drivers may provide more clues.
The list could be a coupla hundred items long.
03-19-2019 05:04 AM
Thank you for your reply. I am currently running in Safe Mode, that is the only way I can launch.
I did not see in your message any information about how to IDENTIFY AND REPLACE the bad driver.
Sorry if I am just slow/stupid.
I have Minidump and Event Viewer logs, but do not see any way to attach them here.
03-19-2019 07:20 AM
Hi
I didn't post any.
driver query and list all the drivers as a CSV.
Then filter for signed drivers.
Deduct signed from all and you have a shortlist.
Then make a backup of everything and reformat and reinstall.
As you rebuild the dodgy driver will be flagged by its install date.
Just do a rollback and voila.