BSOD occurring at random in ntoskrnl.exe, error code: 0x0000003b

Well, it's still happening... I'm going to try the USB fix steps one more time and uninstall anything that looks like a network device and restart. I kinda feel like I am doing the same thing over and over and expecting a different result.

Odd thing about this one: still a 0x0000003b SYSTEM_SERVICE_EXCEPTION, but the cause seems to be "dxgmms1.sys" Another odd thing is that often when this happens, the AMD Catalyst software updater runs. Could just be because it only checks on restarts or something, maybe. A search on google seems to indicate this file/program is a common BSOD issue. According to this it is often thought to be a display driver issue, but it's not always.

Code:

AODDriver2	fffff880`07ed1000	fffff880`07f02000	Wed Jun 15 02:38:35 2011 (4df86f8b)	00012df4		AODDriver2.sys

The above driver is known to cause blue screen crashes. Can you install just the drivers for your graphics card without the software? If not, refer to my post #30 in BSOD Windows 7 - ntoskrnl.exe+7cc40.

Your crash report still suggests a USB issue; where did you see the DirectX driver for the crash?

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\littleraskol\Windows_NT6_BSOD_jcgriff2\022312-21840-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0365b000 PsLoadedModuleList = 0xfffff800`038a0670
Debug session time: Thu Feb 23 05:01:12.557 2012 (UTC - 7:00)
System Uptime: 3 days 12:36:56.102
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff800036cfb65, fffff88008971cd0, 0}

Probably caused by : hidusb.sys ( hidusb!HumGetStringDescriptor+10a )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800036cfb65, Address of the instruction which caused the bugcheck
Arg3: fffff88008971cd0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExpInterlockedPopEntrySListFault16+0
fffff800`036cfb65 498b08          mov     rcx,qword ptr [r8]

CONTEXT:  fffff88008971cd0 -- (.cxr 0xfffff88008971cd0)
rax=00000001bd960003 rbx=0000000000000001 rcx=fffff88002fd6060
rdx=0046002057004601 rsi=0000000000000012 rdi=0000000000000000
rip=fffff800036cfb65 rsp=fffff880089726b0 rbp=fffff88002fd6060
 r8=0046002057004600  r9=fffff8000365b000 r10=fffff88002fd6060
r11=fffff88008972800 r12=fffff80003862340 r13=0000000000000000
r14=0000000000000002 r15=0000000055646948
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
nt!ExpInterlockedPopEntrySListFault16:
fffff800`036cfb65 498b08          mov     rcx,qword ptr [r8] ds:002b:00460020`57004600=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  mainserv.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800038061de to fffff800036cfb65

STACK_TEXT:  
fffff880`089726b0 fffff800`038061de : fffffa80`09969168 fffff800`036dcf32 fffffa80`0c1f6c10 fffff800`036e989c : nt!ExpInterlockedPopEntrySListFault16
fffff880`089726c0 fffff880`06eeab4e : 00000000`0000000a 00000000`00000001 fffffa80`08bb2cf0 fffff880`06ee2d2d : nt!ExAllocatePoolWithTag+0xfe
fffff880`089727b0 fffff880`06ee2f2f : fffffa80`00000106 fffffa80`0ca15778 fffffa80`0ca15730 fffffa80`08eaf060 : hidusb!HumGetStringDescriptor+0x10a
fffff880`08972830 fffff880`06ef302f : fffffa80`0b773801 fffffa80`0ca15778 00000000`00000001 fffffa80`08eaf1d0 : hidusb!HumInternalIoctl+0x10b
fffff880`089728a0 fffff880`06ef2dd0 : fffffa80`0ca15778 fffff880`06efb4a0 fffffa80`08ec8910 00000000`000b01be : HIDCLASS!HidpGetDeviceString+0x8b
fffff880`089728e0 fffff880`06ef18d3 : fffff880`06efc301 fffffa80`0ca15420 fffffa80`08ec8910 00000000`000b01be : HIDCLASS!HidpIrpMajorDeviceControl+0xb2c
fffff880`08972970 fffff880`06f1f83f : 00000000`c00000bb 00000000`c00000bb fffff880`08972ca0 fffffa80`0ca15420 : HIDCLASS!HidpMajorHandler+0x1c3
fffff880`089729e0 fffff800`039f2a97 : fffffa80`0c270b00 fffffa80`0c270b00 fffffa80`0ca157c0 fffffa80`0ca15420 : HidBatt!HidBattIoControl+0x87
fffff880`08972a10 fffff800`039f32f6 : 00000000`0128f100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`08972b40 fffff800`036d6ed3 : 00000000`73352450 00000000`0128f170 00000000`0128fd20 00000000`7efaa000 : nt!NtDeviceIoControlFile+0x56
fffff880`08972bb0 00000000`73352e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0128f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73352e09


FOLLOWUP_IP: 
hidusb!HumGetStringDescriptor+10a
fffff880`06eeab4e 4889842488000000 mov     qword ptr [rsp+88h],rax

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  hidusb!HumGetStringDescriptor+10a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hidusb

IMAGE_NAME:  hidusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a665

STACK_COMMAND:  .cxr 0xfffff88008971cd0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

BUCKET_ID:  X64_0x3B_hidusb!HumGetStringDescriptor+10a

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

Yeah when going through the USB fix steps I noticed that I had done some of them wrong... I didn't notice any missing devices because I forgot to apply that setting. So maybe now things will work.

I saw "dxgmms1.sys" in BlueScreenView. I'll upload a screenshot of what it shows:



I'll see what I can do about that driver.

Sorry for the very late reply. Since purging the system of all USB wireless adapter drivers, I've had no BSODs.

Good news! Thanks for posting back.