I have an nLite'd/Ryan'd/DriverPack'd XPSP2 install. It works on almost every piece of hardware my company has. The problem, is when I get a laptop with an Intel 2100B Wireless Integrated NIC, the machines ALWAYS get a GPF on the SVCHOST pertaining to the wzcsvc.dll file (which from what I can tell is the Wireless Zero Configuration Service).

I've tried disabling the service as well as the card, the laptops behave very slow, and once they get the GPF, the machine has to be hard powered off.

I've got every possible hotfix in the world for this that I'm aware of, and nothing fixes it. I've got the latest Intel driver for the WIFI card, nothing. Any thoughts?

Edited October 25, 200718 yr by GTOOOOOH

If you can, get the PID of the svchost containing that service, and then install the debugging tools and get a dump of that svchost process ID when it crashes.

Memory dump from an application/process that is CRASHING (not hanging):

1. Create a directory called c:\adplus

2. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is "C:\Program Files\Debugging Tools for Windows"

3. Type the following command in the command prompt:

cscript adplus.vbs -crash -p <PID> -quiet -o c:\adplus (replacing <PID> with the process ID (PID) of the svchost.exe instance that is crashing - you can run "tasklist /svc" from a command prompt to figure out which PID to use)

4. Once the debugger has finished (this can take some time), the command prompt window(s) will close, and you will have data in your C:\adplus folder that can be analyzed.

If you can, get the PID of the svchost containing that service, and then install the debugging tools and get a dump of that svchost process ID when it crashes.

Memory dump from an application/process that is CRASHING (not hanging):

1. Create a directory called c:\adplus

2. Open a command prompt and change to the directory where you installed the debugging tools. By default, this is "C:\Program Files\Debugging Tools for Windows"

3. Type the following command in the command prompt:

cscript adplus.vbs -crash -p <PID> -quiet -o c:\adplus (replacing <PID> with the process ID (PID) of the svchost.exe instance that is crashing - you can run "tasklist /svc" from a command prompt to figure out which PID to use)

4. Once the debugger has finished (this can take some time), the command prompt window(s) will close, and you will have data in your C:\adplus folder that can be analyzed.

What will this tell me?

It'll tell us what happened when the process crashed - once you are able to get a dump of the crash, upload it and post links so we can grab it and debug it for you, if you'd like. At this point, it'll be hard to say otherwise why this is occurring other than an educated guess saying the intel driver is at fault somehow.