This crash was probably caused by nwifi.sys which is part of win 7's wifi setup
I would run a system file check
type cmd in search>right click and run as admin>sfc /scannow (note the space between sfc and "/"
Let us know if you need help
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\032310-8468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4b000 PsLoadedModuleList = 0xfffff800`02e88e50
Debug session time: Tue Mar 23 12:33:46.600 2010 (GMT-4)
System Uptime: 0 days 6:17:28.553
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4dd951, 2, 8, fffff88001e3e956}
Unable to load image \SystemRoot\system32\DRIVERS\netr7364.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netr7364.sys
*** ERROR: Module load completed but symbols could not be loaded for netr7364.sys
Probably caused by : nwifi.sys ( nwifi!Pt6RepackRecvNBL+2f2 )
Followup: MachineOwner
---------
2: 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: 00000000004dd951, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff88001e3e956, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef30e0
00000000004dd951
CURRENT_IRQL: 2
FAULTING_IP:
nwifi!Pt6RepackRecvNBL+2f2
fffff880`01e3e956 488b4b10 mov rcx,qword ptr [rbx+10h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: milkyway_0.19_
TRAP_FRAME: fffff88002f924e0 -- (.trap 0xfffff88002f924e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88002f92610
rdx=0000000000cbd7c8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001e3e956 rsp=fffff88002f92670 rbp=0000000000000000
r8=0000000000000000 r9=fffffa8006457e4c r10=1052197c4aa4969a
r11=fffffa8006457850 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nwifi!Pt6RepackRecvNBL+0x2f2:
fffff880`01e3e956 488b4b10 mov rcx,qword ptr [rbx+10h] ds:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cbc469 to fffff80002cbcf00
STACK_TEXT:
fffff880`02f92398 fffff800`02cbc469 : 00000000`0000000a 00000000`004dd951 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02f923a0 fffff800`02cbb0e0 : fffffa80`07986010 fffffa80`079aeeb0 fffff880`01e76500 fffff880`03e6454a : nt!KiBugCheckDispatch+0x69
fffff880`02f924e0 fffff880`01e3e956 : fffffa80`07978010 00000000`000005fc fffffa80`079aeeb0 fffff880`00000000 : nt!KiPageFault+0x260
fffff880`02f92670 fffff880`01e3f6c8 : fffffa80`065c01a0 fffff880`03e6454a fffffa80`065c0100 fffffa80`07978010 : nwifi!Pt6RepackRecvNBL+0x2f2
fffff880`02f92770 fffff880`0146e9e9 : fffffa80`074a3c90 00000000`00000000 00000000`00000001 fffff880`03e65a95 : nwifi!Pt6Receive+0x170
fffff880`02f927d0 fffff880`0146e980 : fffffa80`074a7028 fffff880`03cbc0c7 fffff880`03cbd340 fffff880`03e58f79 : ndis!ndisFilterIndicateReceiveNetBufferLists+0x29
fffff880`02f92810 fffff880`03cb89c0 : fffff880`03cbf110 00000000`00000000 00000000`00000001 fffffa80`074a7a78 : ndis!NdisFIndicateReceiveNetBufferLists+0x50
fffff880`02f92850 fffff880`014862b7 : fffffa80`06b5e1a0 fffffa80`06f4fd50 fffffa80`06f4fd50 00000000`00000001 : vwififlt!FilterReceiveNetBufferLists+0x158
fffff880`02f928b0 fffff880`01e961cf : fffffa80`06f22ac0 00000000`00000000 fffffa80`0711502e 00000000`00000000 : ndis! ?? ::FNODOBFM::`string'+0xccef
fffff880`02f92900 fffffa80`06f22ac0 : 00000000`00000000 fffffa80`0711502e 00000000`00000000 fffffa80`00000002 : netr7364+0x51cf
fffff880`02f92908 00000000`00000000 : fffffa80`0711502e 00000000`00000000 fffffa80`00000002 fffffa80`06e91660 : 0xfffffa80`06f22ac0
STACK_COMMAND: kb
FOLLOWUP_IP:
nwifi!Pt6RepackRecvNBL+2f2
fffff880`01e3e956 488b4b10 mov rcx,qword ptr [rbx+10h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nwifi!Pt6RepackRecvNBL+2f2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nwifi
IMAGE_NAME: nwifi.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc3b
FAILURE_BUCKET_ID: X64_0xD1_nwifi!Pt6RepackRecvNBL+2f2
BUCKET_ID: X64_0xD1_nwifi!Pt6RepackRecvNBL+2f2
Followup: MachineOwner
---------