BSOD STOP 0xc9

[martinlest]

Suddenly had a BSOD this morning... the advice was to remove new devices or drivers, but I have changed nothing. I rebooted but every time I got a blue screen. Spent half the morning on my other PC looking for ideas, but nothing really helped. I unplugged all my peripherals, but could only boot in Safe Mode. I could also boot OK into Windows 10 (the PC dual boots, Windows 7 set as default)...

In the end, I had to try System Restore from within Safe Mode - after which the PC boots into Win7 again. Unfortunately the minidumps have gone in the process (nothing now in the Windows minidump folder - I should have copied them and saved them. Too late now).

I did however copy as much information as I found. Don't know if this helps (below). Be good to know what the problem was.. since the PC was unbootable into Win7, there was some serious issue (with a driver, I take it). But as I say, as I had changed nothing since I last used the PC, just last night, I am at a loss to imagine what the cause might have been. Also, concerned that the same thing may happen again some time soon...

Any insights into what the information might mean appreciated. Thanks!

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.768.3
  Locale ID:	2057

Additional information about the problem:
  BCCode:	c9
  BCP1:	0000000000000220
  BCP2:	FFFFF8800441B710
  BCP3:	FFFFF980079B2CF0
  BCP4:	FFFFFA800E9BE5B0
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	768_1

  C:\Windows\Minidump\052520-4414-01.dmp
  C:\Users\Martin\AppData\Local\Temp\WER-6177-0.sysdata.xml

-----------------------------------


--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.61
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution. 

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice. 

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available. 

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. 

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: MARTIN-FSPC
Windows version: Windows 7 Service Pack 1 , 6.1, build: 7601
Windows dir: C:\Windows
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., H97I-PLUS
CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 17119162368 bytes (15.9GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. 

Crash dump directories: 
C:\Windows
C:\Windows\Minidump

On Mon 25/05/2020 12:22:58 GMT your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-4414-01.dmp
This was probably caused by the following module: hidclass.sys (0xFFFFF8800441B710) 
Bugcheck code: 0xC9 (0x220, 0xFFFFF8800441B710, 0xFFFFF980079B2CF0, 0xFFFFFA800E9BE5B0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION 
file path: C:\Windows\system32\drivers\hidclass.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hid Class Library
Bug check description: This is the bug check code for all Driver Verifier crashes. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Mon 25/05/2020 08:47:13 GMT your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052520-6630-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93EA0) 
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4030015, 0xFFFFFA8012463550)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[martinlest]

Meant to mention above that, in Device Manager, there was the 'infamous' issue of AMDA00 Interface, with a yellow exclamation mark. Does the following sound about right (from another forum)? I should have tried this before going for System Restore, but for the future.. Could this be the reason for the BSOD? (The AMDA00 Interface entry is now OK in DM).

1. Go to "manage devices" in "computer". Find that nasty AMD00 yellow triangle or just look for the AMD00 driver. (Sometimes it will even disguise itself as "unknown driver". Uninstall it.

Do not "disable", do not "update", do not "fix". Just uninstall it.

2. Go to Program Files and look for the ATI technologies file in case you happen to have one. Delete the entire folder.

Now this assumes that you are not using an ATI gpu but even if you are you can always reinstall your "Catalyst Control Center" pain-in-the-buttocks program later, when you've finished ridding yourself of his corrupt driver.

3. Reboot your PC and then run PC CLEANER, ADVANCED SYSTEM CARE, or whatever program you use for cleaning out old registry entries you no longer need.

*note* Malware Bytes may help somewhat but it likely will not get all unnecessary garbage that behaves like malware.

4, Reboot your PC again. You'll likely no longer encounter any blue screens caused by this very faulty driver that I've caught messing up more PCs than I care to recall having to deal with.

 

[torchwood]

Hi

Hidclass drivers tend to relate to PNP devices, ie USB connected devices keyboard/mouse etc

run sfc /scannow

it should repair it.


Roy

 

[martinlest]

Ok, I will try that, thanks. But the two BSODs (there were several, each time I rebooted into Win7 - I should have recorded them all: too late now after a system restore) show completely different causes.

Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\hidclass.sys

Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe