New
#11
Caused by driver verifier (which is a good thing). Points to Human Interface Devices (USB, Bluetooth, keyboard, mouse, gaming devices, etc). Disable Verifier for the time being. Start with USB Driver - General Fix for Problems to fix any USB related conflicts. Once finished with those steps, re-enable Verifier as before.Code:Loading Dump File [F:\Kingston\BSODDmpFiles\beagrie07\Windows_NT6_BSOD_jcgriff2\020512-54272-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03298670 Debug session time: Sun Feb 5 15:07:45.438 2012 (GMT-7) System Uptime: 0 days 0:01:57.312 Loading Kernel Symbols ............................................................... ................................................................ ................................................ Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {224, fffff88006d47710, fffff9801799a9d0, ffffffffc00000bb} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9) The IO manager has caught a misbehaving driver. Arguments: Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the IRP's IoStatus.Status field. Arg2: fffff88006d47710, The address in the driver's code where the error was detected. Arg3: fffff9801799a9d0, IRP address. Arg4: ffffffffc00000bb, Expected status code. Debugging Details: ------------------ BUGCHECK_STR: 0xc9_224 DRIVER_VERIFIER_IO_VIOLATION_TYPE: 224 FAULTING_IP: HIDCLASS!HidpMajorHandler+0 fffff880`06d47710 48895c2410 mov qword ptr [rsp+10h],rbx FOLLOWUP_IP: HIDCLASS!HidpMajorHandler+0 fffff880`06d47710 48895c2410 mov qword ptr [rsp+10h],rbx IRP_ADDRESS: fffff9801799a9d0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP PROCESS_NAME: ts3client_win6 CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800035593dc to fffff800030cfc40 STACK_TEXT: fffff880`0a1ae638 fffff800`035593dc : 00000000`000000c9 00000000`00000224 fffff880`06d47710 fffff980`1799a9d0 : nt!KeBugCheckEx fffff880`0a1ae640 fffff800`0356347a : fffff800`035579f0 fffff880`06d47710 fffff980`1799a9d0 ffffffff`c00000bb : nt!VerifierBugCheckIfAppropriate+0x3c fffff880`0a1ae680 fffff800`035643f3 : fffff880`06d47710 fffffa80`0a7270c8 ffffffff`c00000bb 00000000`ffffffff : nt!ViErrorFinishReport+0xda fffff880`0a1ae6d0 fffff800`0356f759 : 00000000`00000008 fffffa80`0a727010 fffffa80`0a7270c8 00000000`00000000 : nt!VfErrorReport4+0x83 fffff880`0a1ae7c0 fffff800`0356fb63 : fffffa80`0a727010 00000000`00000002 fffffa80`096f3b70 fffff980`1799a9d0 : nt!IovpCallDriver2+0x179 fffff880`0a1ae820 fffff800`03575c2e : fffff980`1799a9d0 fffff980`1799a9d0 00000000`00000002 fffffa80`096f3b70 : nt!VfAfterCallDriver+0x353 fffff880`0a1ae870 fffff800`033eaa97 : fffffa80`08708850 fffff880`0a1aeb60 fffffa80`08708850 fffffa80`0a727010 : nt!IovCallDriver+0x57e fffff880`0a1ae8d0 fffff800`033eb2f6 : fffff683`ff7d7590 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`0a1aea00 fffff800`030ceed3 : fffffa80`0a4f89d0 0000007f`ffffffff fffffa80`0a644060 00000980`00000000 : nt!NtDeviceIoControlFile+0x56 fffff880`0a1aea70 00000000`7767138a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`05e6e5c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7767138a 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_224_VRF_HIDCLASS!HidpMajorHandler+0 BUCKET_ID: X64_0xc9_224_VRF_HIDCLASS!HidpMajorHandler+0 Followup: MachineOwner ---------
Last edited by writhziden; 05 Feb 2012 at 17:56. Reason: Re-enable Verifier after resolving USB conflicts.