Solved

Linksys WMP54G wireless network adapter driver RT2500.sys causes BSOD.

Posted on 2007-11-28
16
14,807 Views
Last Modified: 2013-11-09
Have had a Linksys WMP54G wireless network adapter in my computer for about 1 year -- worked fine.  Lately I'm getting BSODs saying "driver irql not less or equal"  (error D1) and blaming RT2500.sys which is a RAlink driver for the WMP54G.  I reinstalled the card and software -- no help.  Anyone had this trouble or know what to do?
0
Comment
Question by:ssmyer
  • 8
  • 5
  • 2
  • +1
16 Comments
 
LVL 2

Expert Comment

by:JJB-Zenful
ID: 20370871
Have you installed any new cards or devices that may be causing an IRQ conflict which in turn is causing a "BSOD"?

Before reinstalling the driver and software for the card did you uninstall the driver for the device to make sure its completely removed before the re-installation?
0
 

Author Comment

by:ssmyer
ID: 20371298
Hi,
Thanks for the help!  No new cards or devices.  It is the only thing on IRQ11.  I did uninstall the card in Device Manager and the software in Control Panel-Add/Remove Programs.
 
Tonight, I disabled the card and the computer has been fine all night.

I have tested the memory for almost 21 hours with Microsoft Memory Diagnostic Test (it passed) and taken the 2 memory boards out one at a time - no help.

0
 

Author Comment

by:ssmyer
ID: 20373356
Thinking back, I think the BSODs started after a Windows Update awhile back.
0
 
LVL 2

Expert Comment

by:JJB-Zenful
ID: 20377548
You may want to uninstall that update, and install pieces of the update one by one until the error has reoccurred.

You would then obviously uninstall that singular update as its causing a conflict for some reason.  Then you can check with manufacturer to see if they offer any solution to the problem so you can reinstall the update.
0
 

Author Comment

by:ssmyer
ID: 20378723
I'm not sure when this started or what the update was.
0
 
LVL 2

Expert Comment

by:JJB-Zenful
ID: 20379086
Have you searched through your Event Viewer to see when the errors happen?

You can find the event view by going to Control Panel > Administrative Tools > Event Viewer.

It would be under System events.

Hopefully your logs will go back far enough to view when the errors started to happen.
0
 

Author Comment

by:ssmyer
ID: 20424916
Event Viewer doesn't show any errors having to do with networking.
0
 
LVL 2

Expert Comment

by:JJB-Zenful
ID: 20427330
Are you using the Linksys software or Windows Wireless Configuration tool to handle your Wireless Connection?  

Please make sure only one application is managing your wireless.  

You also may want to switch between the two applications.
0
Network it in WD Red

There's an industry-leading WD Red drive for every compatible NAS system to help fulfill your data storage needs. With drives up to 8TB, WD Red offers a wide array of solutions for customers looking to build the biggest, best-performing NAS storage solution.  

 

Author Comment

by:ssmyer
ID: 20449607
I'm using the Linksys software only.  

I disabled the wireless networking altogether and ran a cable to my router from the network plug on the motherboard.  I still get BSODs.  Is there some way to know what all the drivers, etc. are that have to do with networking, so I can replace them all?

I also wonder if I should do a Windows XP repair install, because even with ALL networking disabled I still get BSODs once in a while.  It just seems like there are a lot of things wrong with my software.
0
 
LVL 2

Assisted Solution

by:JJB-Zenful
JJB-Zenful earned 300 total points
ID: 20450463
You may in fact have multiple issues with your Windows XP installation.  What are the error messages saying?  There are a few things that could be wrong including but not limited to faulty system files, bad memory, etc.

To repair your Windows XP install (BACK UP YOUR DATA FIRST)

Insert the Windows XP CD.  Boot the system from the CD.  Press enter at the first option to load Windows XP.  Then agree to the license.  If there is a Windows XP install to be repaired, you can press "R" to repair the install.  This repairs your installation, some programs may not function properly after the repair, reinstalling them takes care of that.  All data should remain on the disk, but it is important that you backup any valuable data.
0
 
LVL 5

Assisted Solution

by:dclive
dclive earned 200 total points
ID: 20594803
Don't reinstall Windows!

Instead, read my guide (http://bluescreens.homeserver.com/BSOD) and learn how to debug your memory dumps (created whenever the box BSODs).  It should take about 5 minutes to install the debugger, configure it, and then do an '!analyze -v' on your memory dump.  Once you've done that, post the output of that result (that !analyze -v command) here, and we'll help you figure out what the real problem is.  

Again - read http://bluescreens.homeserver.com/BSOD, read the debugging guide, and then do the listed steps, and then post the output of !analyze -v here.  
0
 

Author Comment

by:ssmyer
ID: 20605155
Thanks for joining, dclive.  That's a good site.  I have been doing the debugger for a while and it has pointed to various files as the problem including win32k.sys, klif.sys, sspipes.scr, ntoskrnl.exe, and nv4_disp.dll.  What do you make of so many different filoes being the problem?  I have vacuumed out the computer, tested memory for days at a time and swapped memory and used one memory board at a time.  For awhile it seemed that disabling the wireless network card was the answer (thus this thread) but that isn't working anymore.  Sometimes it will be good for days at a time, sometimes it will BSOD 2 or 3 times in a short period of time.  I also sent the whole motherboard back to the factory and they tested it and found it OK.  I'm ready to remove one board at a time and see if it is a bad board -- I'm stumped.

Here are 2 debugs:

----------- #1 -----------
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini123107-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Program Files\Debugging Tools for Windows\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Dec 31 01:08:37.052 2007 (GMT-5)
System Uptime: 4 days 22:06:04.748
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {0, 2, 1, 80513a3d}



Probably caused by : ntoskrnl.exe ( nt!`string'+1d )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
      bit 0 : value 0 = read operation, 1 = write operation
      bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80513a3d, address which referenced memory

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




WRITE_ADDRESS:  00000000

CURRENT_IRQL:  2

FAULTING_IP:
nt!`string'+1d
80513a3d 890a            mov     dword ptr [edx],ecx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  dfrgntfs.exe

LAST_CONTROL_TRANSFER:  from 8050c1f5 to 80513a3d

STACK_TEXT:  
b9af94e4 8050c1f5 84ec009c b9af95b8 00000000 nt!`string'+0x1d
b9af950c 804e36a5 84ec0070 00000001 00000000 nt!RtlVerifyVersionInfo+0x1f3
b9af9520 00000000 856ae6e0 e40ebd20 00000001 nt!__from_strstr_to_strchr+0x23


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!`string'+1d
80513a3d 890a            mov     dword ptr [edx],ecx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!`string'+1d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  45e53f9c

FAILURE_BUCKET_ID:  0xA_W_nt!_string_+1d

BUCKET_ID:  0xA_W_nt!_string_+1d

Followup: MachineOwner
___________________________________________________________________________________

------------- #2 --------------------

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


Loading Dump File [C:\WINDOWS\Minidump\Mini123107-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\Program Files\Debugging Tools for Windows\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805533a0
Debug session time: Mon Dec 31 19:59:10.008 2007 (GMT-5)
System Uptime: 0 days 10:24:19.697
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
.............................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {80000003, bfb29a8f, b98608fc, 0}



Probably caused by : nv4_disp.dll ( nv4_disp!CPixelShaderTSSFP::compileDefaultShader+af )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: bfb29a8f, The address that the exception occurred at
Arg3: b98608fc, Trap Frame
Arg4: 00000000

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




EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
nv4_disp!CPixelShaderTSSFP::compileDefaultShader+af
bfb29a8f cc              int     3

TRAP_FRAME:  b98608fc -- (.trap 0xffffffffb98608fc)
ErrCode = 00000000
eax=00000006 ebx=00000006 ecx=e18b4800 edx=00000400 esi=00000007 edi=ff000000
eip=bfb29a90 esp=b9860970 ebp=ffffffff iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000246
nv4_disp!CPixelShaderTSSFP::compileDefaultShader+0xb0:
bfb29a90 a1a02aecbf      mov     eax,dword ptr [nv4_disp!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_disp+0x4edaa0) (bfec2aa0)] ds:0023:bfec2aa0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  sspipes.scr

LAST_CONTROL_TRANSFER:  from b9860c20 to bfb29a90

STACK_TEXT:  
b98609b8 b9860c20 e184d714 e229e100 e229f2c0 nv4_disp!CPixelShaderTSSFP::compileDefaultShader+0xb0
WARNING: Frame IP not in any known module. Following frames may be wrong.
b98609c0 e229e100 e229f2c0 00000000 e18b4800 0xb9860c20
b98609c4 e229f2c0 00000000 e18b4800 00000001 0xe229e100
b98609c8 00000000 e18b4800 00000001 01020000 0xe229f2c0


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
nv4_disp!CPixelShaderTSSFP::compileDefaultShader+af
bfb29a8f cc              int     3

SYMBOL_NAME:  nv4_disp!CPixelShaderTSSFP::compileDefaultShader+af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  470588d1

FAILURE_BUCKET_ID:  0x8E_nv4_disp!CPixelShaderTSSFP::compileDefaultShader+af

BUCKET_ID:  0x8E_nv4_disp!CPixelShaderTSSFP::compileDefaultShader+af

Followup: MachineOwner


0
 
LVL 5

Expert Comment

by:dclive
ID: 20605457
Remove the nVidia card, and put in an ATI card.

Can you repro the problem?
0
 

Author Comment

by:ssmyer
ID: 20620712
I can't reproduce the problem at will -- it is random.

I have an old ATI All-In-Wonder card which I will try, although my Hauppage video recording card doesn't like it so it won't be a permanent solution.

Here's my plan:
1.  As a first step, I uninstalled my nVidia card drivers, ran Driver Cleaner Pro to get rid of residual driver garbage, installed the latest nVidia drivers, and cleaned out the registry of leftovers.

2.  If I get a blue screen, I will repeat the step 1 uninstall/cleanup parts and install my ATI card, only as a graphics card (not as a video recorder -- maybe the Hauppage will like it).  Then we'll see what happens.  

Since my BSODs are random this testing could all take a few days.  I'll give you updates.  

 
0
 

Accepted Solution

by:
ssmyer earned 0 total points
ID: 20950952
I have gotten BSODs blaming various programs.  The problems started getting worse and I was finally able to figure out that it was my memory -- even though I had tested it numerous times with 2 different programs and for many hours each time, and tried swapping the 2 memory cards in my memory slots.

I put in new memory cards and everything has been fine for weeks.  It's amazing that the memory was passing the tests with flying colors, but it had a problem.
0
 

Expert Comment

by:vklen
ID: 21551035
Amazingly, I had exactly the same BSOD with the Debugger showing RT2500.sys as the faulting driver. What solved the issue for me was unistalling the most recent Windows Updates. Scary, but the only way that could do it.

Is there a good thread that discusses how to deal with the Wiindows Update bugs that cause BSODs?
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Suggested Solutions

MAC Filtering: MAC filtering is like handing a list of names to a doorman. If someone comes to the door and mentions a name, this name is checked by the doorman on his list and granted or denied access by this. This means that if someone menti…
Last Mile Wireless The term last mile wireless is a bit deceptive as it can be much more than a mile. It is also called WiMax and 802.16. It generally refers to relatively short distance point-to-point / point-to-multipoint secure wireless connecti…
This Micro Tutorial will show you how to maximize your wireless card to its maximum capability. This will be demonstrated using Intel(R) Centrino(R) Wireless-N 2230 wireless card on Windows 8 operating system.
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…

747 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now