Unsolved
This post is more than 5 years old
23 Posts
0
30600
June 29th, 2005 22:00
BSOD/Stop error: DRIVER_IRQL_NOT_LESS_OR_EQUAL: w22n51.sys
It says:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
w22n51.sys - Address F6BBCB98 base at F6B49000, DateStamp 40054b01
What I did was I tried to run a scan using software which finds game servers for you called All Seeing Eye. This software has not caused problems on my desktop.
There must be something wrong with my networking on this laptop, because I also get a similar error when I use Telnet to access an email account. I can open up Telnet and connect to a server but as soon as I send the USER command it crashes to the same kind of BSOD.
It is an Inspiron 8600 with the following network card:
K3444 CARD (CIRCUIT), NETWORK, MINI PCI CARD, INTEL2200, NOT APPLICABLE
or in other words, an Intel Pro 2200 BG Wireless card
and I use the Intel PRO Set software to manage my network.
Please help me solve this problem
DRIVER_IRQL_NOT_LESS_OR_EQUAL
w22n51.sys - Address F6BBCB98 base at F6B49000, DateStamp 40054b01
What I did was I tried to run a scan using software which finds game servers for you called All Seeing Eye. This software has not caused problems on my desktop.
There must be something wrong with my networking on this laptop, because I also get a similar error when I use Telnet to access an email account. I can open up Telnet and connect to a server but as soon as I send the USER command it crashes to the same kind of BSOD.
It is an Inspiron 8600 with the following network card:
K3444 CARD (CIRCUIT), NETWORK, MINI PCI CARD, INTEL2200, NOT APPLICABLE
or in other words, an Intel Pro 2200 BG Wireless card
and I use the Intel PRO Set software to manage my network.
Please help me solve this problem
No Events found!


tbsteph
51 Posts
0
June 30th, 2005 03:00
Well, the BSOD certainly looks like a driver problem. I am not familiar with "All Seeing Eye" but my 6000D has the same wireless card.
In the Networking forum, there is a thread discussing a new generic driver for the Pro 2200 available from the Intel website. I would suggest trying this driver and see if it solves your problem.
Good Luck!
bacillus
2 Intern
•
14.4K Posts
0
June 30th, 2005 09:00
4fluke
354 Posts
0
June 30th, 2005 11:00
SpamFilter
23 Posts
0
June 30th, 2005 13:00
I decided to first try and disable Intel's PRO Set software and see how Windows manages the network. IT worked! I fired up telenet, connected to my email server and punched in my username bracing for the BSOD... and it didn't happen! Checked my mail everything went OK. Then I launched All Seeing Eye and clicked the search button which produced a BSOD last time (it pings all active servers and gets some information about them) and that went fine as well.
Conclusion: Intel makes lousy drivers.
bacillus
2 Intern
•
14.4K Posts
0
June 30th, 2005 13:00
SpamFilter
23 Posts
0
June 30th, 2005 14:00
bacillus
2 Intern
•
14.4K Posts
0
June 30th, 2005 18:00
4fluke
354 Posts
0
July 1st, 2005 16:00
bacillus
2 Intern
•
14.4K Posts
0
July 1st, 2005 17:00