Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Hidclass.sys bsod


07 Aug 2011   #1

Windows Home Premium 64-bit
 
 
Hidclass.sys bsod

Current OS -Windows 7 Home Premium SP164bit
Version (OEM/Retail) - Retail Upgrade (FULLY CLEAN INSTALL)
OEM OS - Windows Vista 32bit
System Age - 4yrs (2007)
OS Age - Installed 1/19/2010

I am getting this Warning Event in Event Viewer:

Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 8/6/2011 3:10:11 PM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: LINUS
Description:
The driver \Driver\WUDFRd failed to load for the device USB\VID_BEEF&PID_0006\AAAAAAAAAAAAAAAAAAAA.
Event Xml:
<Event xmlns="Error">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>219</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>212</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2011-08-06T21:10:11.472829800Z" />
<EventRecordID>385215</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="44" />
<Channel>System</Channel>
<Computer>LINUS</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DriverNameLength">42</Data>
<Data Name="DriverName">USB\VID_BEEF&amp;PID_0006\AAAAAAAAAAAAAAAAAAAA</Data>
<Data Name="Status">3221226341</Data>
<Data Name="FailureNameLength">14</Data>
<Data Name="FailureName">\Driver\WUDFRd</Data>
<Data Name="Version">0</Data>
</EventData>
</Event>

I ran verifier.exe and got BSOD indicating HIDCLASS.SYS error (See attached image and DATA.ZIP files). I've ran onboard diagnostics with no errors but I did not do the extended memory tests. Had to install 64 bit driver for my smartcard reader (CAB-200 19-1 Media Card Reader with Integrated Bluetooth Receiver) in Vista Comaptibility mode.
I have two listings under Bluetooth Radios in Device Manager showing Dell Wireless 355C Bluetooth 2.0 + EDR module and Microsoft Bluetooth Enumerator. Also in Device Manager I have Disabled two "Bluetooth Peripheral Devices" that appear under the heading Other Devices that windows could not find drivers for. However in Control Panel under Devices I have "BT Mini-Receiver" and "CAB-200" Devices that show as working properly. I originally had a Bluetooth Enabled Logitec Mouse and Keyboard that came with the machine but I have since opted to use a Microsoft Wireless USB Mouse and Keyboard that I got for Christmas a few years back. I have removed the original BT Mouse and BT Keyboard devices in Control Panel/Devices. With HIDCLASS.SYS being a USB driver and having so many USB peripherals is making it hard to diagnose this issue. Any help would be greatley appreciated.

My System SpecsSystem Spec
.

07 Aug 2011   #2

Microsoft Windows 7 Ultimate: x64 (SP1)
 
 

Hello markmandyderek & Welcome to SevenForums!

BSOD Summary
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Frederik\AppData\Local\Temp\Rar$DI00.947\080611-11887-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`0525e000 PsLoadedModuleList = 0xfffff800`054a3650
Debug session time: Sun Aug  7 06:11:50.795 2011 (UTC + 2:00)
System Uptime: 0 days 0:00:31.356
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, fffff8800734e710, fffff9800be52990, fffffa800c3ce540}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000220, IRP_MJ_SYSTEM_CONTROL has been completed by someone other than the ProviderId.
	This IRP should either have been completed earlier or should have been passed
	down.
Arg2: fffff8800734e710, The address in the driver's code where the error was detected.
Arg3: fffff9800be52990, IRP address.
Arg4: fffffa800c3ce540, ProviderId.

Debugging Details:
------------------


BUGCHECK_STR:  0xc9_220

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  220

FAULTING_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`0734e710 48895c2410      mov     qword ptr [rsp+10h],rbx

FOLLOWUP_IP: 
HIDCLASS!HidpMajorHandler+0
fffff880`0734e710 48895c2410      mov     qword ptr [rsp+10h],rbx

IRP_ADDRESS:  fffff9800be52990

DEVICE_OBJECT: fffffa800cc68050

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LOCK_ADDRESS:  fffff800054d9b60 -- (!locks fffff800054d9b60)

Resource @ nt!PiEngineLock (0xfffff800054d9b60)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
	Lock address  : 0xfffff800054d9b60
	Thread Count  : 0
	Thread address: 0x0000000000000000
	Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800057643dc to fffff800052ddd00

STACK_TEXT:  
fffff880`035ef0b8 fffff800`057643dc : 00000000`000000c9 00000000`00000220 fffff880`0734e710 fffff980`0be52990 : nt!KeBugCheckEx
fffff880`035ef0c0 fffff800`0576e47a : fffff800`057629f0 fffff880`0734e710 fffff980`0be52990 fffffa80`0c3ce540 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`035ef100 fffff800`0576f0ff : 00000000`00000220 fffffa80`0c3ce540 fffff980`0be52990 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`035ef150 fffff800`057746a7 : fffff980`0be52f28 fffff880`0734e710 00000000`00000000 00000000`000001f1 : nt!VfErrorReport10+0x6f
fffff880`035ef230 fffff800`0576404e : fffffa80`0b80ce90 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfWmiVerifyIrpStackUpward+0x67
fffff880`035ef260 fffff800`05770b2d : fffffa80`0c4011e0 fffffa80`0b80c5d0 fffff980`0be52990 fffff980`0be52990 : nt!VfMajorVerifyIrpStackUpward+0x6e
fffff880`035ef2a0 fffff800`0578250d : fffff980`0be52f28 fffff880`035ef480 00000000`c0000010 fffff980`0be52f28 : nt!IovpCompleteRequest2+0xad
fffff880`035ef310 fffff800`052e1091 : fffff980`0be52f2b fffff800`00000000 00000000`000000ff fffff880`00000005 : nt!IovpLocalCompletionRoutine+0x9d
fffff880`035ef370 fffff800`0577a19f : fffff980`0be52990 fffff880`07358400 fffffa80`0cc68100 00000000`00000000 : nt!IopfCompleteRequest+0x3b1
fffff880`035ef450 fffff800`052c38c2 : fffff880`00000013 fffff880`035ef578 fffff980`0be52f28 fffffa80`0cc681a0 : nt!IovCompleteRequest+0x19f
fffff880`035ef520 fffff880`0734ea0f : 00000000`00000000 fffffa80`0cc681a0 00000000`00000001 00000000`00000017 : nt!IopInvalidDeviceRequest+0x16
fffff880`035ef550 fffff880`0734e7fb : 00000000`00000000 fffffa80`0cc681a0 fffff980`0be52990 fffff880`035ef600 : HIDCLASS!HidpIrpMajorDefault+0x8b
fffff880`035ef590 fffff800`05780c16 : fffff980`00000002 fffff980`0be52990 00000000`00000002 fffff800`0577c37e : HIDCLASS!HidpMajorHandler+0xeb
fffff880`035ef600 fffff800`0577fc42 : fffff980`0be52f70 00000000`00000002 fffffa80`0c3e51e0 fffffa80`0c384d30 : nt!IovCallDriver+0x566
fffff880`035ef660 fffff800`05780c16 : fffff980`0be52990 00000000`00000002 fffffa80`0c3e5090 00000000`00000000 : nt!ViFilterDispatchPower+0x62
fffff880`035ef690 fffff800`0577fd58 : fffff980`0be52990 fffffa80`0c3e5090 00000000`00000000 fffffa80`0c395900 : nt!IovCallDriver+0x566
fffff880`035ef6f0 fffff800`0577fe42 : fffffa80`0c3ce540 fffffa80`076703f0 fffffa80`0c3ce540 00000000`00000017 : nt!VfIrpSendSynchronousIrp+0xe8
fffff880`035ef760 fffff800`0576cfaf : fffffa80`0c3ce270 00000000`000007ff fffff800`054145b8 fffff800`05670a89 : nt!VfWmiTestStartedPdoStack+0x72
fffff880`035ef800 fffff800`05387a22 : fffffa80`0c3ce270 00000000`00000000 00000000`00000000 00000000`00000000 : nt!VfMajorTestStartedPdoStack+0x5f
fffff880`035ef830 fffff800`056c504c : fffffa80`0c3ce270 fffffa80`076703f0 00000000`00000001 01535242`00000010 : nt!PpvUtilTestStartedPdoStack+0x12
fffff880`035ef860 fffff800`056c6c44 : fffffa80`0c3ce270 fffffa80`0c3ce270 fffffa80`076703f0 00000000`00000001 : nt!PipProcessStartPhase3+0x55c
fffff880`035ef950 fffff800`056c7208 : 00000000`00000000 00000000`00000000 00000000`00000010 fffff800`056c7170 : nt!PipProcessDevNodeTree+0x264
fffff880`035efbc0 fffff800`053d7927 : 00000001`00000003 00000000`00000000 00000000`00000001 fffffa80`00000084 : nt!PiProcessReenumeration+0x98
fffff880`035efc10 fffff800`052e8021 : fffff800`053d7600 fffff800`055d4001 fffffa80`076a7100 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`035efcb0 fffff800`0557a32e : 00000000`00000000 fffffa80`076a71a0 00000000`00000080 fffffa80`07603890 : nt!ExpWorkerThread+0x111
fffff880`035efd40 fffff800`052cf666 : fffff880`009ee180 fffffa80`076a71a0 fffff880`009f8f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`035efd80 00000000`00000000 : fffff880`035f0000 fffff880`035ea000 fffff880`035eebc0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  HIDCLASS!HidpMajorHandler+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HIDCLASS

IMAGE_NAME:  HIDCLASS.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

FAILURE_BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0

BUCKET_ID:  X64_0xc9_220_HIDCLASS!HidpMajorHandler+0

Followup: MachineOwner
---------
The dump you attached is caused by your USB drivers. Uninstall them, and install a fresh copy.

Code:
HIDCLASS HIDCLASS.SYS Sat Nov 20 11:43:49 2010
Best Regards,
FredeGail
My System SpecsSystem Spec
07 Aug 2011   #3

Windows Home Premium 64-bit
 
 

How do I uninstall the USB drivers. This is the only way
I can communicate with my computer (USB). Any way I tried and windows keeps reinstalling them right after I uninstall them.
My System SpecsSystem Spec
.


22 Feb 2012   #4

Windows Home Premium 64-bit
 
 
Solved

The problem was with the little viewing screen attached to the top of my desktop case. The windows sideshow device. Once I disabled that device in the bios and in device manager I no longer recieved the WUDFrd Driver Warning in event viewer. I ran driver verifier again after disabling the View Screen and it crashed my system with a STOP error Identifying The HIDCLASS.SYS driver. It took a little investigation to find out this STOP message was caused by my Bluetooth drivers installed as part of my TEAC CAB-200 19-1 Media Card Reader with integrated bluetooth. I disabled the bluetooth radio shown in device manager as I no longer use the Bluetooth Mouse and Keyboard that shipped with my system back in 2007 and ran driver verifier once again.....this time with no BSOD's. And no more errors or warnings in event viewer upon booting
My System SpecsSystem Spec
26 Dec 2013   #5

64 bit windows 7 home professional
 
 

HEY, I HAVE THE SAME PROBLEM.

hidclass.sys
i recently got a new mobo and it has 2x usb3 ports, i got a cd with the mobo with the drivers in there. i installed them but i think it messed up half way, could that be why i am having bsod's?
My System SpecsSystem Spec
Reply

 Hidclass.sys bsod




Thread Tools



Similar help and support threads for2: Hidclass.sys bsod
Thread Forum
BSOD Randomly win32k.sys Bad_Pool_Header HIDClass.sys BSOD Help and Support
HIDCLASS.SYS & ntoskrnl.exe Problem's BSOD Help and Support
hidclass.sys+2710 verifier bsod error BSOD Help and Support
HIDCLASS.sys BSOD and sound problems BSOD Help and Support
HidClass.sys BugCheck BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:49 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33