It looks like your network drivers are causing the issue. Try updating them, and run a system files check. Open an elevated command prompt and enter sfc /scannow.
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\Temp1_dumpfiles.zip\040510-21294-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Mon Apr 5 10:10:08.342 2010 (GMT-4)
System Uptime: 0 days 1:36:23.965
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff80002ad0d4f}
Unable to load image \??\C:\Windows\system32\drivers\PktIcpt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PktIcpt.sys
*** ERROR: Module load completed but symbols could not be loaded for PktIcpt.sys
Probably caused by : NETIO.SYS ( NETIO!WfpExpireEntryLru+17 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ad0d4f, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfd0e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+4f
fffff800`02ad0d4f 488713 xchg rdx,qword ptr [rbx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880033af650 -- (.trap 0xfffff880033af650)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80039ee040 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff880033af850 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ad0d4f rsp=fffff880033af7e0 rbp=fffffa800707f140
r8=fffff880033af850 r9=0000000000000000 r10=0000000000000002
r11=0000000000000006 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f:
fffff800`02ad0d4f 488713 xchg rdx,qword ptr [rbx] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ac6469 to fffff80002ac6f00
STACK_TEXT:
fffff880`033af508 fffff800`02ac6469 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`033af510 fffff800`02ac50e0 : 00000000`00000010 00000000`00000000 fffffa80`00000003 00000000`c0a80168 : nt!KiBugCheckDispatch+0x69
fffff880`033af650 fffff800`02ad0d4f : 00000000`00000003 00000000`00000002 00000000`00000003 00000000`00000002 : nt!KiPageFault+0x260
fffff880`033af7e0 fffff880`0192d557 : fffffa80`0707f140 fffff880`033afac0 00000000`00006c07 fffff880`018113de : nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x4f
fffff880`033af830 fffff880`01ae47bd : fffffa80`04293a50 00000000`00000002 fffffa80`062ff010 fffff880`033afac0 : NETIO!WfpExpireEntryLru+0x17
fffff880`033af880 fffff880`01aa2d26 : 00000000`00000004 fffffa80`00000030 00000000`00000000 00000000`00000001 : tcpip!WfpAleCloseRemoteEndpointConnection+0x2d
fffff880`033af8b0 fffff880`01b245bb : fffffa80`04293a50 fffffa80`04129c5a 00000000`00000000 fffffa80`04293a50 : tcpip! ?? ::FNODOBFM::`string'+0x22592
fffff880`033afa00 fffff880`01b24942 : fffff8a0`0a7f9ad0 fffffa80`04129b90 00000000`00000001 00000000`00000000 : tcpip!WfpAleHandleSendCompletion+0xeb
fffff880`033afb20 fffff880`01b2eac2 : fffffa80`07c9d9c8 fffff880`04980ec3 fffffa80`043b1240 00000000`00000001 : tcpip!WfpAlepAuthorizeSendCompletion+0x32
fffff880`033afb70 fffff880`01992af2 : 00000000`00000000 fffffa80`043b1240 fffffa80`043b1240 00000000`00000000 : tcpip!WfpAleCompleteOperation+0x162
fffff880`033afc10 fffff880`0497e618 : 00000000`00000000 fffffa80`043b1240 ffffffff`00000010 00000002`00000005 : fwpkclnt!FwpsCompleteOperation0+0x1e
fffff880`033afc40 00000000`00000000 : fffffa80`043b1240 ffffffff`00000010 00000002`00000005 fffffa80`07c9d9c0 : PktIcpt+0x2618
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!WfpExpireEntryLru+17
fffff880`0192d557 488b4310 mov rax,qword ptr [rbx+10h]
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: NETIO!WfpExpireEntryLru+17
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0xA_NETIO!WfpExpireEntryLru+17
BUCKET_ID: X64_0xA_NETIO!WfpExpireEntryLru+17
Followup: MachineOwner
---------
Quote