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: BSOD occurring at random in ntoskrnl.exe, error code: 0x0000003b

04 Jan 2012   #11
littleraskol

Windows 7 Home Premium 64 bit
 
 

Another BSOD, same error type and code, this morning at 3:35 AM. I had followed the steps for fixing USB issues when writhziden recommended it, but I guess that didn't work. It might be worth listing the USB peripherals I have attached:

Everything is connected to the computer by a Rosewill 7 port USB 2.0 hub. I think I may have plugged it into a USB 3.0 port if that matters.
  • WD 500 GB external hard drive, usually unplugged unless I need backup files
  • Netgear RangeMax Wireless-N USB 2.0 wireless adapter
  • Logitech mouse
  • APC Backup UPS ES550, USB connection allows UPS status info collection, which I don't think I actually use anymore
  • Brother HL-2040 printer, usually turned off
  • A simple USB to micro USB cable for my phone
  • One port left empty
Something of note is that yesterday I moved everything into a new case and attached a Seagate Momentus XT 500GB hybrid drive. This is going to be the destination for my Windows 7 OS and applications partitions, I plan to migrate it today using Backup and Restore, per these directions: How to move windows 7 to a new or larger hard drive using Backup and Restore

I've attached the most recent info. Eventually I may just have to re-install everything, but I'm hoping that can be a last resort...


My System SpecsSystem Spec
.
04 Jan 2012   #12
writhziden

Windows 7 Home Premium 64 Bit
 
 

Code:
  1. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\BSOD\Minidump\122911-15459-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*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`02e11000 PsLoadedModuleList = 0xfffff800`03056670 Debug session time: Thu Dec 29 03:47:13.801 2011 (GMT-7) System Uptime: 4 days 10:47:18.346 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002e85b65, fffff88007dd7cd0, 0} Probably caused by : hidusb.sys ( hidusb!HumGetStringDescriptor+10a ) Followup: MachineOwner --------- 0: 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: fffff80002e85b65, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88007dd7cd0, 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`02e85b65 498b08 mov rcx,qword ptr [r8] CONTEXT: fffff88007dd7cd0 -- (.cxr 0xfffff88007dd7cd0) rax=00000003583f0003 rbx=0000000000000001 rcx=fffff80003004d60 rdx=0042034c61004201 rsi=0000000000000012 rdi=0000000000000000 rip=fffff80002e85b65 rsp=fffff88007dd86b0 rbp=fffff80003004d60 r8=0042034c61004200 r9=fffff80002e11000 r10=fffff80003004d60 r11=fffff88007dd8800 r12=fffff80003018340 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`02e85b65 498b08 mov rcx,qword ptr [r8] ds:002b:0042034c`61004200=???????????????? 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 fffff80002fbc1de to fffff80002e85b65 STACK_TEXT: fffff880`07dd86b0 fffff800`02fbc1de : fffffa80`095e4558 fffff800`02e92f32 fffffa80`0ed6d8f0 fffff800`02e9f89c : nt!ExpInterlockedPopEntrySListFault16 fffff880`07dd86c0 fffff880`055b3b4e : 00000000`0000000a 00000000`00000001 fffffa80`08ecd0a0 fffff880`055abd2d : nt!ExAllocatePoolWithTag+0xfe fffff880`07dd87b0 fffff880`055abf2f : fffffa80`00000106 fffffa80`0ed6dc48 fffffa80`0ed6dc00 fffffa80`0ad059b0 : hidusb!HumGetStringDescriptor+0x10a fffff880`07dd8830 fffff880`055bc02f : fffffa80`0d791301 fffffa80`0ed6dc48 00000000`00000001 fffffa80`0ad05b20 : hidusb!HumInternalIoctl+0x10b fffff880`07dd88a0 fffff880`055bbdd0 : fffffa80`0ed6dc48 fffff880`055c44a0 fffffa80`0c34ab30 00000000`000b01be : HIDCLASS!HidpGetDeviceString+0x8b fffff880`07dd88e0 fffff880`055ba8d3 : fffff880`055c5301 fffffa80`0ed6d8f0 fffffa80`0c34ab30 00001f80`000b01be : HIDCLASS!HidpIrpMajorDeviceControl+0xb2c fffff880`07dd8970 fffff880`0547f83f : 00000000`c00000bb 00000000`c00000bb fffff880`07dd8ca0 fffffa80`0ed6d8f0 : HIDCLASS!HidpMajorHandler+0x1c3 fffff880`07dd89e0 fffff800`031a8a97 : fffffa80`0bf2cf20 fffffa80`0bf2cf20 fffffa80`0ed6dc90 fffffa80`0ed6d8f0 : HidBatt!HidBattIoControl+0x87 fffff880`07dd8a10 fffff800`031a92f6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`07dd8b40 fffff800`02e8ced3 : 00000000`73702450 00000000`0122f170 00000000`0122fd20 00000000`7efaa000 : nt!NtDeviceIoControlFile+0x56 fffff880`07dd8bb0 00000000`73702e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`0122f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73702e09 FOLLOWUP_IP: hidusb!HumGetStringDescriptor+10a fffff880`055b3b4e 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 0xfffff88007dd7cd0 ; kb FAILURE_BUCKET_ID: X64_0x3B_hidusb!HumGetStringDescriptor+10a BUCKET_ID: X64_0x3B_hidusb!HumGetStringDescriptor+10a Followup: MachineOwner ---------
  2. Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\littleraskol\BSOD\Minidump\010412-19141-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*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`02e17000 PsLoadedModuleList = 0xfffff800`0305c670 Debug session time: Wed Jan 4 01:19:39.034 2012 (GMT-7) System Uptime: 0 days 8:10:04.189 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002e8bb65, fffff88007d2bcd0, 0} Probably caused by : hidusb.sys ( hidusb!HumGetStringDescriptor+10a ) Followup: MachineOwner --------- 2: 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: fffff80002e8bb65, Address of the exception record for the exception that caused the bugcheck Arg3: fffff88007d2bcd0, 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`02e8bb65 498b08 mov rcx,qword ptr [r8] CONTEXT: fffff88007d2bcd0 -- (.cxr 0xfffff88007d2bcd0) rax=00000000312e0003 rbx=0000000000000001 rcx=fffff88002f65060 rdx=0042032061004201 rsi=0000000000000012 rdi=0000000000000000 rip=fffff80002e8bb65 rsp=fffff88007d2c6b0 rbp=fffff88002f65060 r8=0042032061004200 r9=fffff80002e17000 r10=fffff88002f65060 r11=fffff88007d2c800 r12=fffff8000301e340 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`02e8bb65 498b08 mov rcx,qword ptr [r8] ds:002b:00420320`61004200=???????????????? 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 fffff80002fc21de to fffff80002e8bb65 STACK_TEXT: fffff880`07d2c6b0 fffff800`02fc21de : fffffa80`096c3c68 fffff800`02e98f32 fffffa80`0b8e6780 fffff800`02ea589c : nt!ExpInterlockedPopEntrySListFault16 fffff880`07d2c6c0 fffff880`03b8cb4e : 00000000`0000000a 00000000`00000001 fffffa80`0885b830 fffff880`03b84d2d : nt!ExAllocatePoolWithTag+0xfe fffff880`07d2c7b0 fffff880`03b84f2f : fffffa80`00000106 fffffa80`0be60368 fffffa80`0be60320 fffffa80`08d7b330 : hidusb!HumGetStringDescriptor+0x10a fffff880`07d2c830 fffff880`03b9502f : fffffa80`0ae3a301 fffffa80`0be60368 00000000`00000001 fffffa80`08d7b4a0 : hidusb!HumInternalIoctl+0x10b fffff880`07d2c8a0 fffff880`03b94dd0 : fffffa80`0be60368 fffff880`03b9d4a0 fffffa80`08e14c80 00000000`000b01be : HIDCLASS!HidpGetDeviceString+0x8b fffff880`07d2c8e0 fffff880`03b938d3 : fffff880`03b9e301 fffffa80`0be60010 fffffa80`08e14c80 fffff800`000b01be : HIDCLASS!HidpIrpMajorDeviceControl+0xb2c fffff880`07d2c970 fffff880`03bc183f : 00000000`c00000bb 00000000`c00000bb fffff880`07d2cca0 fffffa80`0be60010 : HIDCLASS!HidpMajorHandler+0x1c3 fffff880`07d2c9e0 fffff800`031aea97 : fffffa80`099251c0 fffffa80`099251c0 fffffa80`0be603b0 fffffa80`0be60010 : HidBatt!HidBattIoControl+0x87 fffff880`07d2ca10 fffff800`031af2f6 : 00000000`010df100 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607 fffff880`07d2cb40 fffff800`02e92ed3 : 00000000`73752450 00000000`010df170 00000000`010dfd20 00000000`7efaa000 : nt!NtDeviceIoControlFile+0x56 fffff880`07d2cbb0 00000000`73752e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`010df0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73752e09 FOLLOWUP_IP: hidusb!HumGetStringDescriptor+10a fffff880`03b8cb4e 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 0xfffff88007d2bcd0 ; kb FAILURE_BUCKET_ID: X64_0x3B_hidusb!HumGetStringDescriptor+10a BUCKET_ID: X64_0x3B_hidusb!HumGetStringDescriptor+10a Followup: MachineOwner ---------
The following drivers should be updated or the components removed if they are no longer supported. Please refer to Driver Reference and Drivers and Downloads

Code:
PCASp50a64	fffff880`081e8000	fffff880`081f4000	Tue Nov 28 19:45:19 2006 (456cf43f)	000172df		PCASp50a64.sys
jswpslwfx	fffff880`03f56000	fffff880`03f63000	Thu May 15 04:28:50 2008 (482c1062)	00011e66		jswpslwfx.sys
My System SpecsSystem Spec
04 Jan 2012   #13
littleraskol

Windows 7 Home Premium 64 bit
 
 

Thanks once again! I will get on that.

ETA: both of these seem to be related to my USB wireless adapter, hmm...
My System SpecsSystem Spec
.

04 Jan 2012   #14
littleraskol

Windows 7 Home Premium 64 bit
 
 

Something strange about the "jswpslwfx" driver... This is apparently a D-Link USB wireless adapter driver. But my wireless adapter is not made by D-Link... The D-Link driver download site lists a bunch of devices and I was not sure what on my computer could be using it. I searched my C: drive for "D-Link" and found that a file in my Netgear driver directory (C:\Program Files (x86)\NETGEAR\WN111v2\Driver) had a reference to it: arusb_win7x.inf. The following lines give some details:

Code:
[Strings]

...

DLINK                        = "D-Link Corporation"

...

DWA160.DeviceDesc            = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A)"
DWA160A2.DeviceDesc          = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A2)"
The ellipses are omitted text that is not relevant. Does this mean that my Netgear adapter is using some D-Link software? There is a listing on the D-Link driver page for "DWA-160," but I really don't understand what's going on here... If there's a better forum for this, I'll ask there.
My System SpecsSystem Spec
04 Jan 2012   #15
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by littleraskol View Post
Something strange about the "jswpslwfx" driver... This is apparently a D-Link USB wireless adapter driver. But my wireless adapter is not made by D-Link... The D-Link driver download site lists a bunch of devices and I was not sure what on my computer could be using it. I searched my C: drive for "D-Link" and found that a file in my Netgear driver directory (C:\Program Files (x86)\NETGEAR\WN111v2\Driver) had a reference to it: arusb_win7x.inf. The following lines give some details:

Code:
[Strings]

...

DLINK                        = "D-Link Corporation"

...

DWA160.DeviceDesc            = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A)"
DWA160A2.DeviceDesc          = "D-Link DWA-160 Xtreme N Dual Band USB Adapter(rev.A2)"
The ellipses are omitted text that is not relevant. Does this mean that my Netgear adapter is using some D-Link software? There is a listing on the D-Link driver page for "DWA-160," but I really don't understand what's going on here... If there's a better forum for this, I'll ask there.
You could start a thread in the Drivers forum about it. I would have to do some research to find out more, but someone in there may already know the answer(s) to your question(s).
My System SpecsSystem Spec
04 Jan 2012   #16
littleraskol

Windows 7 Home Premium 64 bit
 
 

There's a similar odd issue with the "PCASp50a64" driver. This has something to do with a PCAUSA NDIS (Network Driver Interface Specification?) driver. Once again, a file in my Netgear directory has a reference: W32N55.INI in C:\Program Files (x86)\NETGEAR\WN111v2.

Code:
; Rawether for Windows OEM Customization File
; Copyright (c) 2003-2006 Printing Communications Assoc., Inc. (PCAUSA)
; All Rights Reserved.
; ------------------------------------------------------------------
;
[Manufacturer]
CompanyName="Printing Communications Assoc., Inc. (PCAUSA)"
LegalCopyright="Copyright (c) 1997-2006 Printing Communications Assoc., Inc. (PCAUSA)"
The PCAUSA site is a nightmare, I cannot figure out where, if anywhere, the driver downloads are (but I'll keep looking). Seems more and more like the easiest way to deal with this is to not use the USB adapter and get a real wireless card.

Side note, the D-Link driver has actual associated files in the Netgear driver directory: jswpslwfx.sys, jswpslwfx.cat, and jswpslwfx.inf. The PCAUSA driver is only refered to in the above file (W32N55.INI):

Code:
[SinglePacket.amd64]
NDIS50=PCASp50a64
NDIS60=PCASp50a64
So now I am doubly lost, because there doesn't even seem to be a PCASp50a64.sys or anything similar. I throw myself on the mercy of this forum for figuring out how to update these things, unless there's a better forum or I just buy a wireless card first.
My System SpecsSystem Spec
04 Jan 2012   #17
littleraskol

Windows 7 Home Premium 64 bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
You could start a thread in the Drivers forum about it. I would have to do some research to find out more, but someone in there may already know the answer(s) to your question(s).
Alright, cool, I will repost this stuff there. Thanks!
My System SpecsSystem Spec
04 Jan 2012   #18
littleraskol

Windows 7 Home Premium 64 bit
 
 

A troubling development: I have gotten a new kind of BSOD error, which has appeared once when resuming from hibernate and then again when entering hibernate. Both have the code 0x000000d1 and the string DRIVER_IRQL_NOT_LESS_OR_EQUAL. Attached is the ZIP file. Interestingly, both of these happened when a USB flash drive was plugged into the front panel USB port while shutting down/starting up. One of the BSODs is traced back to "WN111v2w7x.sys" which I think is a wireless driver?
My System SpecsSystem Spec
04 Jan 2012   #19
writhziden

Windows 7 Home Premium 64 Bit
 
 

Quote   Quote: Originally Posted by littleraskol View Post
A troubling development: I have gotten a new kind of BSOD error, which has appeared once when resuming from hibernate and then again when entering hibernate. Both have the code 0x000000d1 and the string DRIVER_IRQL_NOT_LESS_OR_EQUAL. Attached is the ZIP file. Interestingly, both of these happened when a USB flash drive was plugged into the front panel USB port while shutting down/starting up. One of the BSODs is traced back to "WN111v2w7x.sys" which I think is a wireless driver?
NETGEAR WN111v2 USB2.0 wifi driver to be exact. A very common problem during sleep and hibernation sequences. Basically, the system tells the device to turn off (go to sleep) when entering hibernation or sleep mode, then tells it turn on (wake up) when resuming from hibernation or sleep mode. The driver is supposed to turn the device off or on, and when it fails to do so (sometimes due to another driver interfering or because the driver itself has become corrupted), a blue screen results to protect your system.

Try uninstalling the device driver through device manager and re-installing the latest driver (start menu -> right click my computer/computer -> click manage -> click device manager [from the list on the left] -> expand network adapters -> right click the device -> click uninstall [do not hit ok in the dialog box that pops up after hitting uninstall] -> put a tick to delete driver software for the device and hit ok -> restart your computer and install the latest driver for the device when Windows starts up again).
My System SpecsSystem Spec
04 Jan 2012   #20
littleraskol

Windows 7 Home Premium 64 bit
 
 

Er, I think I might have caused this... I think I un-checked the "turn off on sleep" setting when I was messing around with the device properties. Still, wouldn't hurt to re-install the drivers anyway, all things considered. Thanks again.
My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD occurring almost daily, error 0x0000003b
I have been experiencing an random intermittent BSOD. I once was able to track it to the adobeflash player and disabling it seemed to improve things. However, the web without adobe flash is not as useful. I was hoping someone could give me a better analysis of what is going wrong. Problem...
BSOD Help and Support
BSOD error 0x0000003B occurring randomly & frequently
Lately I've been getting a BSOD with a stop: 0x0000003B error on my laptop. I've tried updating my graphics driver, running a sfc /scannow test, tried the applicable hotfix from the Microsoft website and nothing solves the issue. Here are the contents of my windows/minidump/ folder:...
BSOD Help and Support
BOSD Random Times/Applications, error 0x0000003B ntoskrnl.exe
My computer recently started blue screening with the error code 0x0000003B seeming to come from ntoskrnl.exe, I haven't installed any new software (to my knowledge) recently, and I've also been having Windows Explorer crash and freeze up right after I boot. I'm attaching my recent dump files and if...
BSOD Help and Support
Random BSOD error 0x0000003B ntoskrnl.exe
Hello :) I am having random BSOD issues, just recently i download blue screen view and at the top of the list it has ntoskrnl.exe that seemed to be causing the issue. I will upload the minidump file if that makes things easier, besides that i don't know much else to report on, help is...
BSOD Help and Support
BSOD Error Code 0x0000003B Random Timing
i have been getting random bluescreens all with error code 3B. ther has been no pattern. I have also uploaded here the SF diagnostic tool results. can someone help?
BSOD Help and Support
Random BSOD when playing games bug check code 0x0000003b
When I play games I randomly get blue screened can anyone help I'm running windows 7 ultimate 64 bit. All help is appreciated I've had this problem for I don't know how long
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 17:23.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App