For those who spent hours to solve this Blue Screen of death..
Yesterday I spent like 8 hours or more to find out why my sick old laptop crash when I turn on the wireless radio switch..
The problem is: w22n51.sys
Even tough at first it said ndis.sys, but when I turned all services off the BSOD still happens and said w22n51.sys instead.
Many people couldnt solve this because everywhere on the internet they share the old buggy driver, even on the laptop manufacturer website (mine is acer)..
Intel have fixed this bug on 2009, and post the driver on their website.. So if you have same problem with mine, just go to intel websites and search for new driver for this Intel PRO/Wireless 2200BG and try it..
http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&keyword=%22w22n51%22
For me it solved my problem, no more bsod when I turned on the wireless device..
NOTE:
- many ndis.sys BSOD is simply solved by switching hardware slots (mostly memory)
- many ndis.sys BSOD is actually a different driver problem, so try turn off all windows services and see if the BSOD still happens and caused by other thing.
- turned off all services is done from msconfig (start->run->msconfig), on services tab click disable all services
good luck
.zoc
Tuesday, October 12, 2010
Subscribe to:
Post Comments (Atom)
4 comments:
Hero, thanks.
I actually bought another 2nd hand 2200BG as drivers from Acer couldn't help me either.
Only after trying yet another driver I noticed the w22n51.sys message. Any reboots and BSOD beyond that didn't display W22n51.
Googling that got me here and solved it for me also. Another $15 and 20 hrs down the drain for the wifi-card...
While googling i came across your blog, and i think you have done a good job to list this blog.
This has help me solve my laptop problem.
Thanks.
Hey I have this same wifi adapter with the smae drivers from a 6 year old laptop for a user, it is an Compaq nc6000 with Wifi Intel 2200BG drivers from 2004. I noticed as well the computer would blue screen on wifi turn "on-age" so I googled a bit and came to this post. I did indeed use the w22n51.sys driver but now it uses:
w29n51.sys
Netw2c32.dll
Netw2r32.dll
With a driver fileversion of 9.0.4.39 andI have been able to turn it on no problem.
Just thought I would update for anyone else having problems
Post a Comment