08-22-2007 11:33 AM - last edited on 01-01-2014 06:50 PM by Lisa198503
I get a bluescreen whenever I power on the (multiport W200) WLAN on a Compaq Evo N600c. I swapped the hardware, same result. Any ideas?
P.S. This thread has been moved from Notebook - HP ProBook, EliteBook, Compaq, Slate/Tablet PC, Armada, LTE to Notebook PC - Omnibooks, EVO. -HP Forum Moderator
08-22-2007 11:53 AM
What operating system? If the OS was recently re-installed, make sure all hardware specific drivers are installed, especially the Chipset Support. See my two replies in this thread for a general idea of what driver installation order to use:
08-23-2007 02:23 AM
08-23-2007 01:59 PM
Also, check the event logs for any clues as to what might cause the BSOD's. Although a BSOD typically won't allow time for an entry to the log, something previous to the BSOD might have been noted.
08-24-2007 09:19 AM
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.
Arg1: 61565a40, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804dbc8e, address which referenced memory
Stop 0x1000000A (aka Stop 0x0A) is not uncommon and generally due to faulty or improper drivers. Which drivers are you using for the W200? There are two sets, both of which are now near impossible to find via HP's search engine. They're still available via FTP...just not easy to find.
What I would do is to uninstall all traces of the W200, including the appropriate OEM.INF file in c:\windows\inf, then reboot (with the W200 turned off). To find the right OEM.INF to delete, you'll need to open each one and find the one(s) specific to the W200 - delete it and the matching .PNF file. After booting, turn on the W200 and see if Windows goes through the "new hardware detected" wizard. If it gets this far without the drivers installed, then the drivers are faulty (or some other driver/all is causing the driver to fail).
I posted links to the two W200 drivers on the FTP site. Let me see if I can find them while you delete the existing drivers.
p.s. In your next message, post a different dump file - having more than one helps narrow down the issue. Again, if you have a ZIP utility, zip a few into one file.
08-28-2007 03:50 AM
08-28-2007 03:52 AM
08-28-2007 07:02 AM
The most recent drivers for the W200 is v126.96.36.19908 dated 11/2004. The Softpaq number is 29165 (SP29165). Here are some links:
The first link is to a support page. The second and third links are direct to the old Compaq FTP site - these links may get broken by the forum software - if so, go to this link and scroll down to SP29165:
The .exe file is the actual Softpaq an the other two files (.html and .txt) are the readme.
If this driver doesn't work, it's possible there's something wrong with the W200 or the Multiport itself.
And, going back one step, since this was an OS re-install, make sure the drivers were installed in proper order (as mentioned earlier). Driver installation order is extremely important on a laptop in order to make sure everything runs as expected.
08-28-2007 09:03 PM
This problem came up only a few days ago in my system, but has persisted even though I have done a clean install of XP. I've not gotten to the point of Windows Updates yet because I can't get past this Wireless card driver issue.
Any other suggestions?
08-29-2007 01:41 AM
08-29-2007 03:55 AM
I haven't tried rolling back the driver yet because the new driver fixes problems with the card losing connection and thoroughput inconsistencies. Then again, what does it matter if I can't even use my wireless, right?
How reasonable is it to expect HP or Microsoft to come out with a fix some time soon?
01-13-2008 01:55 PM
I am having the same problem with a BSOD when my w200 is enabled. The BSOD says IRQ_NOT_LESS_OR_EQUAL. I have found that if I go through my device manager in Safe Mode and disable either the W200 network device or the W200 Packet Scheduler Miniport I am able to start my computer normally without the BSOD. The only catch is that I am unable to connect to any wireless network without the Packet Scheduler Miniport enabled so must compute without a wireless internet connection. I've done some poking around and it seems the problem is with the W200 driver in that is basically out of date and unable to handle more advanced networks such as those found in airports. Furthermore, it seems as though the chances of a driver update is slim to none. So, unless anyone can think of a workaround, I think all who are experiencing this issue are up crap creek.
Here are some links on the problem:
02-06-2008 01:57 PM
Sorry, it's not a real "fix" - HP doesn't seem to care about it.
02-07-2008 09:44 AM
02-11-2008 02:11 PM
Also I have read that some people were able to change the radio modes on their APs to different settings to get it to work as well. This seems to be a very common issue with the W200 card. A quick google search found several instances of other laptops with this card having the same problem and blue screen error message. So basically just experiment with changing settings on your Wireless AP or Router and see if you have any luck. Look especially for a "radio mode" option and try changing that setting.
Hope this helps.
03-08-2008 07:28 AM
03-09-2008 06:02 AM
04-06-2008 07:21 AM
04-29-2008 07:03 AM
The only laptop that will not work is equiped with the W200 and driver 188.8.131.5208. Enabling wireless will lead to a IRQL_NOT_LESS_OR_EQUAL blue screen.
Since I do not believe HP is still supporting this Compaq WLAN Multiport W200 (old Compaq equipment) here is only one solution if you are using the N wireless settings.
Install a PCMCIA wireless G/N and disable the internal W200 with Fn F2 or remove the W200 option.
08-03-2008 12:32 PM
I too am suffering the same problem on my evo n620c, and the only way I can get the w200 wlan to work was to use an earlier version driver SP23031. Using this driver the evo wlan will work quite happily with my new belkin N router but only with 128bit wep security.
When loading any driver always set a restore point first, then check the earliest that will work with your machine and start from there, if it works then update to the next untill it crashes.When it does just power of and restart press F8 load safe mode and when loaded go to restore and go back to your previous restore point. When restarted load the last driver that worked. This worked for me hope it works for you.
All I want to know is why the two later revisions won`t work on my N620c.
Anybody got any ideas.
08-05-2008 01:34 PM