This situation is interesting, because it behaved like driver verifier is enabled even before you enabled DV yourself.
Code:
[COLOR=Red]BugCheck C4[/COLOR], {91, 2, fffff80003660cc0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+1bb8c5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[COLOR=Red]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/COLOR]
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
[COLOR=SeaGreen]Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
the operating system. The only supported way to extend a kernel
mode stack is by using KeExpandKernelStackAndCallout.[/COLOR]
Arg2: 0000000000000002
Arg3: fffff80003660cc0
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0xc4_91
CUSTOMER_CRASH_COUNT: 1
[COLOR=Blue]DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT[/COLOR]
PROCESS_NAME: System
CURRENT_IRQL: 2
TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0
LAST_CONTROL_TRANSFER: from fffff8000352d5ba to fffff800034d6c40
Two red lines indicate that DV is enabled. The blue line makes it sure that DV was not enabled. Then why it may occur? Most probable reason is a driver bug. And the green line indicates that there is a driver bug. What is to do in such a situation? First of all, better you shift to an older driver version, which is stable and bug free in the best of my knowledge.
If the stop 0xC4 continues with this version too, we will think it differently in the next time.
Now coming to the DV enabled HIDCLASS.sys BSODs.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {224, fffff88006cba710, fffff9802960a750, ffffffffc00000bb}
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
Followup: MachineOwner
---------
Hidclass.sys is the OS element, so it cannot be the real reason behind the crash. But it is keyboard/mouse related. So better you try to update these drivers:
DRIVER|NAME|LOCATION
lgbusenum | Logitech GamePanel Virtual Bus Enumerator Driver | c:\windows\system32\drivers\lgbusenum.sys Kerneltreiber
lgshidfilt | Logitech Gaming KMDF HID Filter Driver | c:\windows\system32\drivers\lgshidfilt.sys Kerneltreiber Ja
lgvirhid | Logitech Gamepanel Virtual HID Device Driver | c:\windows\system32\drivers\lgvirhid.sys Kerneltreiber
They all are somehow old. Update them from
Logitech - Support & Software Downloads.
Daemon Tools, Alcohol 120% and Power Archiver Pro uses
SCSI Pass Through Direct (
SPTD), which is a well known BSOD causer. Uninstall
Daemon Tools at first. Then download SPTD standalone installer from
Disk-Tools.com, and execute the downloaded file as guided below :
- Double click to open it.
- Click this button only:
-
- If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
Uninstall these bloatware
Code:
Start Menu\Programs\ASUS
Start Menu\Programs\ASUS\AI Suite II
Uninstall Avast using
Avast Uninstall Utility. Use
Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and
free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.
Let us know the results.
