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: Issue with Netgear RangeMax wireless USB adapter drivers

04 Jan 2012   #1

Windows 7 Home Premium 64 bit
 
 
Issue with Netgear RangeMax wireless USB adapter drivers

This is a continuation of my questions in this thread about a random BSOD I have been getting over the past month. writhziden was kind enough to help me out and his last diagnosis located the problem in a set of drivers:

Quote   Quote: Originally Posted by writhziden View Post
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
I looked into this and found number of strange things.

"jswpslwfx" 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. The Netgear driver directory also had the actual files for this driver: jswpslwfx.sys, jswpslwfx.cat, and jswpslwfx.inf. 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 don't feel comfortable trying to update that until I understand what's going on better.

There's a similar odd issue with the "PCASp50a64" driver. This is 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. Meanwhile, on my computer, the PCAUSA driver is only refered to in the above file (W32N55.INI):

Code:
[SinglePacket.amd64]
NDIS50=PCASp50a64
NDIS60=PCASp50a64
There is no PCASp50a64.sys or anything similar, so now I don't even know what to update, or how a nonexistent driver could be causing a BSOD.

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. I throw myself on the mercy of this forum for figuring out how to update these things, unless I just buy a wireless card first.

Quote   Quote: Originally Posted by System Specs
System Manufacturer/Model Number: Custom Built
OS: Windows 7 Home Premium 64 bit (OEM disc)
CPU: AMD Phenom II X4 965 3.4 GHz
Motherboard: Asus M4A88T-V EVO
Memory: G.SKILL Ripjaws 8 GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333
Graphics Card(s): Asus ATI Radeon HD6870 1GB DDR5
Sound Card: Integrated
Monitor(s) Displays: Acer AL1912 19"
Screen Resolution: 1280x1024
Hard Drives: SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5", Seagate Momentus XT 500GB hybrid drive 2.5"
PSU: CORSAIR Enthusiast Series TX750 V2 750W ATX12V v2.31
I have attached the BSOD info file as requested in the BSOD posting instructions, just in case.




Attached Files
File Type: zip BSOD.zip (1.16 MB, 17 views)
My System SpecsSystem Spec
.

04 Jan 2012   #2

Windows 7 Home Premium 64 bit
 
 

Crossposting due to potential relevance:

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?


Attached Files
File Type: zip BSOD.zip (1.30 MB, 27 views)
My System SpecsSystem Spec
10 Jan 2012   #3

Windows 7 Home Premium 64 bit
 
 

So, er, any thoughts?
My System SpecsSystem Spec
.


Reply

 Issue with Netgear RangeMax wireless USB adapter drivers




Thread Tools



Similar help and support threads for2: Issue with Netgear RangeMax wireless USB adapter drivers
Thread Forum
NETGEAR RangeMax NEXT WN311T Issue Hardware & Devices
Solved NETGEAR Wireless USB Adapter Connectivity Issue. Network & Sharing
NETGEAR RangeMax PCI wireless adapter issues Hardware & Devices
Netgear Wireless RangeMax N PCI driver Drivers
netgear rangemax wireless n usb (v2) cant find network Network & Sharing
USB RangeMax Wireless N Adapter constantly crashing Hardware & Devices
Need drivers for NetGear WG111v3 wireless usb adapter Drivers

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 11:31 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