BSOD due to utorrent

[ratgar]

I have a BSOD that happens because of utorrent, since it happens not long after I start it up. I read a little about this before and it seems that some driver is crappy and there's too many connection going on. It's really annoying having this happen, I practically can't use utorrent now. Also, my wireless adaptor is a ZyXel G-220 v2, with driver up to date (that version -> http://preview.tinyurl.com/yj63p2v) Help!

 

[ratgar]

I realized it might be a good idea to put all the dumps in the zip... so here:

 

[Jonathan_King]

Welcome!

It looks like WlanGZG.sys is the cause. I can't find much info at all about that driver, but it is obvious to me that is a network driver. Try updating your network card drivers in Device Manager.

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp1_Minidump.zip\040610-17862-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c55000 PsLoadedModuleList = 0xfffff800`02e92e50
Debug session time: Tue Apr  6 14:59:02.304 2010 (GMT-4)
System Uptime: 0 days 2:59:06.161
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\WlanGZG.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WlanGZG.sys
*** ERROR: Module load completed but symbols could not be loaded for WlanGZG.sys
Probably caused by : WlanGZG.sys ( WlanGZG+76841 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000ba2838 -- (.exr 0xfffff80000ba2838)
ExceptionAddress: fffff880024b9841 (WlanGZG+0x0000000000076841)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff80000ba28e0 -- (.trap 0xfffff80000ba28e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000fa800459d8d9 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa800450e030 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880024b9841 rsp=fffff80000ba2a70 rbp=0000000000000000
 r8=fffffa80044e5208  r9=0000000000000000 r10=000000000010de80
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
WlanGZG+0x76841:
fffff880`024b9841 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cbec2e to fffff80002cc6ed0

STACK_TEXT:  
fffff800`00ba1918 fffff800`02cbec2e : fffffa80`044b91a0 fffff880`02455993 fffff800`00ba2090 fffff800`02cf3e28 : nt!KeBugCheck
fffff800`00ba1920 fffff800`02cecbed : fffff800`02ed3c24 fffff800`02e0ca3c fffff800`02c55000 fffff800`00ba2838 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00ba1950 fffff800`02cf4250 : fffff800`02e14a88 fffff800`00ba19c8 fffff800`00ba2838 fffff800`02c55000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00ba1980 fffff800`02d011b5 : fffff800`00ba2838 fffff800`00ba2090 fffff800`00000000 fffffa80`02c46770 : nt!RtlDispatchException+0x410
fffff800`00ba2060 fffff800`02cc6542 : fffff800`00ba2838 fffffa80`02c4691b fffff800`00ba28e0 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`00ba2700 fffff800`02cc4e4a : 00000000`00000000 fffff880`01520173 fffffa80`04567a20 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff800`00ba28e0 fffff880`024b9841 : fffff880`0148f110 fffffa80`055272e0 00000000`00000282 fffff880`02454340 : nt!KiGeneralProtectionFault+0x10a
fffff800`00ba2a70 fffff880`0148f110 : fffffa80`055272e0 00000000`00000282 fffff880`02454340 00000000`00000000 : WlanGZG+0x76841
fffff800`00ba2a78 fffffa80`055272e0 : 00000000`00000282 fffff880`02454340 00000000`00000000 fffffa80`055272e0 : ndis!WPP_GLOBAL_Control
fffff800`00ba2a80 00000000`00000282 : fffff880`02454340 00000000`00000000 fffffa80`055272e0 00000000`00000000 : 0xfffffa80`055272e0
fffff800`00ba2a88 fffff880`02454340 : 00000000`00000000 fffffa80`055272e0 00000000`00000000 fffff880`0247f3f1 : 0x282
fffff800`00ba2a90 00000000`00000000 : fffffa80`055272e0 00000000`00000000 fffff880`0247f3f1 00000001`04a3c020 : WlanGZG+0x11340


STACK_COMMAND:  kb

FOLLOWUP_IP: 
WlanGZG+76841
fffff880`024b9841 ??              ???

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  WlanGZG+76841

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: WlanGZG

IMAGE_NAME:  WlanGZG.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  468c5e5a

FAILURE_BUCKET_ID:  X64_0x1E_WlanGZG+76841

BUCKET_ID:  X64_0x1E_WlanGZG+76841

Followup: MachineOwner
---------

 

[ratgar]

It is up to date. Does that mean I should get a different wireless adapter if I want to continue using utorrent?

 

[Jonathan_King]

That driver is from 2007. Go here and select your machine: eMachines Support: Drivers and Downloads

I saw a driver form 2009.

 

[ratgar]

That driver is from 2007. Go here and select your machine: eMachines Support: Drivers and Downloads

I saw a driver form 2009.

I tried uninstalling the driver for the G-220 and installing it with the one I downloaded (Wireless LAN Pro-Nets Wireless LAN Driver 6.1070.0123.2007 264.2 KB 2009/09/09), but it didn't find a valid driver in the folder, so I reinstalled the driver from Zyxel from 2007.

 

[Jonathan_King]

Extract the zip folder, and then run the setup.exe file found inside.

 

[ratgar]

There is no exe.

btw, this is the zip i have. Just to make sure it's the one I'm supposed to have.

 

[Jonathan_King]

Go to Device Manager, right-click on your card, and select Update Driver Software.

Then tell it to manually look in the location you saved the folder to.

 

[ratgar]

Go to Device Manager, right-click on your card, and select Update Driver Software.

Then tell it to manually look in the location you saved the folder to.

I did that, but it said that the driver is up to date. I uninstalled the driver and tried it again, but it said it didn't find a valid driver in the folder.