New
#1
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:
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:
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.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)"
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.
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:; 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)"
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.Code:[SinglePacket.amd64] NDIS50=PCASp50a64 NDIS60=PCASp50a64
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.
I have attached the BSOD info file as requested in the BSOD posting instructions, just in case.System Specs said: