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?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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.
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.
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.
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.
Don't reinstall Windows!
Instead, read my guide (http://bluescreens.homese
Again - read http://bluescreens.homeser
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\Mini1
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+0x
b9af9520 00000000 856ae6e0 e40ebd20 00000001 nt!__from_strstr_to_strchr
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:
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\Mini1
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
Followup: MachineOwner
---------
kd> !analyze -v
**************************
* *
* Bugcheck Analysis *
* *
**************************
KERNEL_MODE_EXCEPTION_NOT_
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
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
bfb29a90 a1a02aecbf mov eax,dword ptr [nv4_disp!_NULL_IMPORT_DES
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
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
bfb29a8f cc int 3
SYMBOL_NAME: nv4_disp!CPixelShaderTSSFP
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nv4_disp
IMAGE_NAME: nv4_disp.dll
DEBUG_FLR_IMAGE_TIMESTAMP:
FAILURE_BUCKET_ID: 0x8E_nv4_disp!CPixelShader
BUCKET_ID: 0x8E_nv4_disp!CPixelShader
Followup: MachineOwner
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.
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.
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?
Business Accounts
Answer for Membership
by: JJB-ZenfulPosted on 2007-11-28 at 18:25:28ID: 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?