It does seem like a network driver error, but I also wonder if sptd.sys is the cause. Sptd.sys is a driver used by many virtualization programs, such as Daemon Tools and Alcohol 120%. It is notorious for causing BSODs.
I recommend completely uninstalling any such tools you may have, in addition to updating your network drivers.
Code:
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\Temp2_Desktop.zip\041910-19312-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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a4c000 PsLoadedModuleList = 0x82b94810
Debug session time: Mon Apr 19 07:54:35.722 2010 (GMT-4)
System Uptime: 1 days 22:11:45.030
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {42, 2, 0, 91958d1f}
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
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : WlanGZG.sys ( WlanGZG+5ed1f )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000042, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 91958d1f, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from 82bb4718
Unable to read MiSystemVaType memory at 82b94160
00000042
CURRENT_IRQL: 2
FAULTING_IP:
WlanGZG+5ed1f
91958d1f 8b5124 mov edx,dword ptr [ecx+24h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: 82b729e8 -- (.trap 0xffffffff82b729e8)
ErrCode = 00000000
eax=00000001 ebx=00000000 ecx=0000001e edx=00000001 esi=85d2a020 edi=856e4247
eip=91958d1f esp=82b72a5c ebp=82b72ac8 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
WlanGZG+0x5ed1f:
91958d1f 8b5124 mov edx,dword ptr [ecx+24h] ds:0023:00000042=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 91958d1f to 82a9285b
STACK_TEXT:
82b729e8 91958d1f badb0d00 00000001 00000000 nt!KiTrap0E+0x2cf
WARNING: Stack unwind information not available. Following frames may be wrong.
82b72ac8 91958b14 85d2a020 856e4168 85b8fb40 WlanGZG+0x5ed1f
82b72af4 91950c66 85d2a020 85ced000 85ca092c WlanGZG+0x5eb14
82b72b1c 91950d72 85c9e020 82b72b3c 91953e12 WlanGZG+0x56c66
82b72b28 91953e12 85ca07b8 85ca0898 85ca07b8 WlanGZG+0x56d72
82b72b3c 82ab4c13 00000000 856e4168 85ca0898 WlanGZG+0x59e12
82b72b84 8d327868 82a8c374 8449c138 00000000 nt!IopfCompleteRequest+0x128
82b72bb4 8d328178 85bdc2c0 856e4168 85b4e070 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
82b72be0 8d32b9af 85653028 856530f0 85653a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
82b72c08 8d325d18 85653028 85653a98 85653002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
82b72c2c 8709dba0 85653aa4 85653002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
82b72c78 82ab44b5 85653aa4 85653a98 00000000 sptd+0x11ba0
82b72cd4 82ab4318 82b75d20 82b7f280 00000000 nt!KiExecuteAllDpcs+0xf9
82b72d20 82ab4138 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
82b72d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
WlanGZG+5ed1f
91958d1f 8b5124 mov edx,dword ptr [ecx+24h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: WlanGZG+5ed1f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: WlanGZG
IMAGE_NAME: WlanGZG.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 468c5e30
FAILURE_BUCKET_ID: 0xD1_WlanGZG+5ed1f
BUCKET_ID: 0xD1_WlanGZG+5ed1f
Followup: MachineOwner
---------
Quote