W200 cause a blue screen

Yes you have to go to your internet's routers web setting page and change your settings from whatever you have now to WEP and follow these instructions.
Sup guys i found the cure to this horroble blue screen death for this N610c. Ok i called hp and they wanted $69.99 for tech support well just imagine what i told them to do lol. Anyway i did my research and guess what i found out. That the updated driver is made to screw up your connection so that you have to call tech support and they can steal your money.
Im a computer technician since 1990 and what i discover was that beautiful driver that works here is a list of drivers that cannot be used on the Evo N610C because it causes conflits that no one can fix i know for sure.
List of the no no drivers are:
These drivers will make your screen go from windows to BLUE.
sp29156
sp28252
sp29156
Here is how i fixed the problem i deleted everything that had to do with LANMultiport drivers every single one then i searched my laptop to remove the rest of the lost files.
Once that was done the i installed this driver (sp23031)
Once that was installed and the puter rebooted the wifi card found my wireless connection and asked me to input my Network Key and walla it works great now without any problems.
Im using windows XP Home i just bought memory cause im installing windows 7 32 bit.

Finally the key is this driver (sp23031) for both home and pro eddition.
Here is the link to download your driver:

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=hb-13082-1&lc=en&cc=fr&dlc=en&os=228&product=235687&lang=en

It works! Please hit me up a feedback

There are a lot of possible causes for blue screen errors, but most of them relate to the computer hardware. The cause of a BSOD error can be a temperature problem, a timing error, a resource conflict, hardware failure, a corrupt registry, a virus or simply a device incompatibility or driver error.
How to analyze blue screen errors The first thing to do to analyze a blue screen error is to check the meaning of the STOP error code. You need to stop Windows from rebooting when a STOP error is encountered. Once the blue screen of death is shown, you can check the meaning of the STOP error code. Together with the filename of the driver or module, this will give an indication of the error cause.
Another option to analyze the cause of the blue screen error is to look at the Windows system event log or to debug the memory dump (minidump) that Windows created when the error occurred. The event log can be viewed using the event viewer. Right-click Computer in the Start menu, and then select Manage. In the Computer Management window select Event Viewer. The information in the event log can be of great help to isolate the cause of the blue screen error.
Reading the minidump requires a bit more technical knowledge, but Microsoft has tools to read the minidump.
The most common cause of blue screen errors In reality, the most common cause of blue screen errors is a device driver problem. Outdated, incorrect or corrupt drivers can cause the system to encounter a STOP error, resulting in the BSOD.
So the easiest way to try and fix a blue screen error is to reinstall and update your system's device drivers. This will ensure that all driver bugs are fixed and that all hardware has the correct driver.
If you know which device caused the error, you can update or reinstall that driver first. The file name in the blue screen of death can help identify the driver. Look for a file with the .SYS extension and search for that file name.
If you do not have the drivers for all devices, or are not comfortable updating your PC's drivers manually, you can use a driver update tool to find, download and update all device drivers for you. Such tools will accurately identify your computer hardware, including any device causing an error, and automatically install the latest drivers for it.
In most cases updating or reinstalling drivers will solve your blue screen errors.
Other causes of blue screen errors However, if updating device drivers does not fix the blue screen error, there are a number of additional things to try:

• Load the default BIOS values - resource conflicts and timing issues can be caused by incorrect BIOS settings.
• Update the BIOS - especially after adding new hardware or installing a Windows service pack this can help fix issues.
• Update Windows - missing updates, including service packs can be a source of stop errors.
• Check your system - run a virus scan and spyware scan after updating your definition files.
• Driver rollback - if you have recently updated a driver, you can use the driver rollback to revert back to the previous driver version.

List of STOP Errors Causing BSOD:

• Stop 0×00000003 UNSYNCHRONIZED_ACCESS
• Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL
• Stop 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
• Stop 0×00000023 FAT_FILE_SYSTEM
• Stop 0×00000024 NTFS_FILE_SYSTEM
• Stop 0x0000002E DATA_BUS_ERROR
• Stop 0x0000003F NO_MORE_SYSTEM_PTES
• Stop 0×00000044 MULTIPLE_IRP_COMPLETE_REQUESTS

Here are 2 solutions:
Solution #1 Scan your registry for errors.
A Registry Cleaner scans your computer for errors in your PC's registry. Your computer's registry contains information about your Windows XP operating system, including driver, printer, software information. Over time, your computer's registry may start to contain obsolete data. A corrupt registry will easily slow down the speed of your computer because applications and drivers are loaded even though they're not in use. Fixing your registry of errors will not only prevent the Windows XP Blue Screen Of Death, it'll allow your computer to boot faster, open up multiple folders quicker. A listing of registry cleaners can be found here.
Solution #2 Process of Elimination
When the CPU calls certain functions from the RAM, or Random Access Memory, and the data rests in a faulty section of the RAM, this will cause the blue screen to appear. I recall a time whenever my computer booted up and started loading the Norton Anti Virus program, the blue screen error message would appear. This happens because the CPU is accessing data from faulty locations within the RAM when loading the anti virus software.
This method involves having 2 sticks of RAM. Remove 1 stick of RAM and wait to see if the blue screen surfaces, do the same for the other.
Through process of elimination, you'll find the cause of the Windows XP blue screen of death error.
Because getting into the hardware can be a little techy for computer hardware "adverse" readers, a simple 2 step plan is to first clear your PC of any registry errors. Then if the blue screen of death goes away, we would have saved ourselves the trouble of having to open up the PC casing and touching the hardware components

Blue screen errors, or blue screen of death (BSOD) errors, are the most severe errors Windows can encounter. Since Windows can not recover from this kernel level error, a blue screen is displayed with the error details. The error details contain a STOP error code, which indicates the type of error.

There are a lot of possible causes for blue screen errors, but most of them relate to the computer hardware. The cause of a BSOD error can be a temperature problem, a timing error, a resource conflict, hardware failure, a corrupt registry, a virus or simply a device incompatibility or driver error.

How to analyze blue screen errors

The first thing to do to analyze a blue screen error is to check the meaning of the STOP error code. You need to stop Windows from rebooting when a STOP error is encountered. Once the blue screen of death is shown, you can check the meaning of the STOP error code. Together with the filename of the driver or module, this will give an indication of the error cause.

Another option to analyze the cause of the blue screen error is to look at the Windows system event log or to debug the memory dump (minidump) that Windows created when the error occurred. The event log can be viewed using the event viewer. Right-click Computer in the Start menu, and then select Manage. In the Computer Management window select Event Viewer. The information in the event log can be of great help to isolate the cause of the blue screen error.

Reading the minidump requires a bit more technical knowledge, but Microsoft has tools to read the minidump.

The most common cause of blue screen errors

In reality, the most common cause of blue screen errors is a device driver problem. Outdated, incorrect or corrupt drivers can cause the system to encounter a STOP error, resulting in the BSOD.

So the easiest way to try and fix a blue screen error is to reinstall and update your system's device drivers. This will ensure that all driver bugs are fixed and that all hardware has the correct driver.

If you know which device caused the error, you can update or reinstall that driver first. The file name in the blue screen of death can help identify the driver. Look for a file with the .SYS extension and search for that file name.

If you do not have the drivers for all devices, or are not comfortable updating your PC's drivers manually, you can use a driver update tool to find, download and update all device drivers for you. Such tools will accurately identify your computer hardware, including any device causing an error, and automatically install the latest drivers for it.

In most cases updating or reinstalling drivers will solve your blue screen errors.

Other causes of blue screen errors

However, if updating device drivers does not fix the blue screen error, there are a number of additional things to try:

Load the default BIOS values - resource conflicts and timing issues can be caused by incorrect BIOS settings.

Update the BIOS - especially after adding new hardware or installing a Windows service pack this can help fix issues.

Update Windows - missing updates, including service packs can be a source of stop errors.

Check your system - run a virus scan and spyware scan after updating your definition files.

Driver rollback - if you have recently updated a driver, you can use the driver rollback to revert back to the previous driver version.

hope it helps, if so rate the solution

All drivers webcam : with "Cam-Drivers" download link: http://www.filefront.com/16785445/Cam-Drivers.exe

Sup guys i found the cure to this horroble blue screen death for this N610c. Ok i called hp and they wanted $69.99 for tech support well just imagine what i told them to do lol. Anyway i did my research and guess what i found out. That the updated driver is made to screw up your connection so that you have to call tech support and they can steal your money.
Im a computer technician since 1990 and what i discover was that beautiful driver that works here is a list of drivers that cannot be used on the Evo N610C because it causes conflits that no one can fix i know for sure.
List of the no no drivers are:
These drivers will make your screen go from windows to BLUE.
sp29156
sp28252
sp29156
Here is how i fixed the problem i deleted everything that had to do with LANMultiport drivers every single one then i searched my laptop to remove the rest of the lost files.
Once that was done the i installed this driver (sp23031)
Once that was installed and the puter rebooted the wifi card found my wireless connection and asked me to input my Network Key and walla it works great now without any problems.
Im using windows XP Home i just bought memory cause im installing windows 7 32 bit.

Finally the key is this driver (sp23031) for both home and pro eddition.
Here is the link to download your driver:

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=hb-13082-1&lc=en&cc=fr&dlc=en&os=228&product=235687&lang=en

It works! Please hit me up a feedback

dear sir good day this problem used to appear when a bad driver is installed or a damaged windows in near so reinstall your system as Microsoft says in this article http://technet.microsoft.com/en-us/library/cc957609.aspx thank you

http://www.fixya.com/support/t612983-blue_screen_hp_wlan_multiport_w200 seems to have the solution.

It says:

Rollback the W200 driver to version 1.00C. Subsequent drivers are incompatible with XP SP2.

Unfortunately, WPA support came in version 1.00E, so W200 + XpSp2 = no WPA support. :(


I removed my wirelss drivers and compaq wireless client software, then installed the older driver from http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=hb-13082-1&lc=en&cc=fr&dlc=en&os=228&product=235687&lang=en which is sp23031. This seems to have worked.

ftp://ftp.hp.com/pub/softpaq/sp29001-29500/sp29156.exe
Here is the SP29156 that includes W200 drivers.
1. Delete the W200 in the device manager.
2. With the computer turned off, remove the W200 from the cover mounting( 1 screw).
3. Reboot with the W200 removed. Reinstall the Sp29156 Drivers to the system.
4. Reboot the system twice, with the W200 UNINSTALLED. Shutdown system.
5. Now replace the W200 in it's mounting area and secure with screw.
6. Now, reboot the system, it should again recognize PNP-new hardware and install itself with the correct IRQ's and drivers.
7. Save SP29156 in a safe place for use at a later date if needed.
8. Enjoy your now functional W200 module.
later...

Anyone who has this problem: the problem is with the W200 driver that HPclaims you should use. Download this driver instead and your problems should be fixed:

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=hb-13082-1&lc=en&cc=fr&dlc=en&os=228&product=235687&lang=en

This will be happening because of a driver conflict. Uninstall all drivers to do with adapter, then re- install your Zyair software and then plug in your adapter, but force windows to look where you have downloaded the driver in other words not automatically install but manually when the option pops up. It may be you have to connect your adapter first then install drivers.