doug
Is this a recent installation? Are you overclocking? All three dumps are virtually identical. the faulting module is netio.sys.
I suggest you run a system file check to verify & tepair system files. to run go to start?search>type cmd> rightclick and run as admin>type syc /scannow.
hope this helps
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\093009-26317-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
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`02c0d000 PsLoadedModuleList = 0xfffff800`02e4ae50
Debug session time: Wed Sep 30 16:30:03.605 2009 (GMT-4)
System Uptime: 3 days 1:31:23.306
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8, 2, 1, fffff88001786673}
Probably caused by : NETIO.SYS ( NETIO!WfppIncrementIndexAndPurgeEntries+93 )
Followup: MachineOwner
---------
1: 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: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001786673, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb50e0
0000000000000008
CURRENT_IRQL: 2
FAULTING_IP:
NETIO!WfppIncrementIndexAndPurgeEntries+93
fffff880`01786673 48897008 mov qword ptr [rax+8],rsi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff880031c7940 -- (.trap 0xfffff880031c7940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8002c60770
rdx=000000000000003a rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001786673 rsp=fffff880031c7ad0 rbp=fffffa8002c60768
r8=fffff880031c7b18 r9=0000000000000000 r10=fffffffffffffffd
r11=0000000000000004 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
NETIO!WfppIncrementIndexAndPurgeEntries+0x93:
fffff880`01786673 48897008 mov qword ptr [rax+8],rsi ds:00000000`00000008=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c7e469 to fffff80002c7ef00
STACK_TEXT:
fffff880`031c77f8 fffff800`02c7e469 : 00000000`0000000a 00000000`00000008 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`031c7800 fffff800`02c7d0e0 : 00000000`00000000 fffff880`0197b180 00000000`00000000 fffff880`00eeb282 : nt!KiBugCheckDispatch+0x69
fffff880`031c7940 fffff880`01786673 : fffff880`0197b180 fffff880`0197b910 fffff880`0197b180 fffff880`0197b910 : nt!KiPageFault+0x260
fffff880`031c7ad0 fffff880`01786799 : 00000000`00000004 fffff880`0197b1c0 fffff880`0197b910 fffff880`0197b180 : NETIO!WfppIncrementIndexAndPurgeEntries+0x93
fffff880`031c7b40 fffff880`0178627f : fffff880`0197b5d0 fffffa80`024e9680 fffff880`0197b1c0 00000000`00000000 : NETIO!WfppLeastRecentlyUsedTimerRoutine+0x19
fffff880`031c7b90 fffff880`0178698e : 00000000`000000ff 00000000`00000000 fffff880`0197b840 fffffa80`024e9680 : NETIO!WfpTimerWheelTimeoutHandler+0xff
fffff880`031c7c10 fffff800`02f78527 : fffffa80`033eabc0 fffffa80`05543b90 fffffa80`05543b90 fffffa80`024e9680 : NETIO!WfpSysTimerPassiveCallback+0x2e
fffff880`031c7c40 fffff800`02c8c161 : fffff800`02e22500 fffff800`02f78504 fffffa80`024e9680 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031c7c70 fffff800`02f22166 : 004c0044`002e0030 fffffa80`024e9680 00000000`00000080 fffffa80`02454890 : nt!ExpWorkerThread+0x111
fffff880`031c7d00 fffff800`02c5d486 : fffff880`009e8180 fffffa80`024e9680 fffff880`009f2f40 11477982`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`031c7d40 00000000`00000000 : fffff880`031c8000 fffff880`031c2000 fffff880`031c79b0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!WfppIncrementIndexAndPurgeEntries+93
fffff880`01786673 48897008 mov qword ptr [rax+8],rsi
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: NETIO!WfppIncrementIndexAndPurgeEntries+93
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc18a
FAILURE_BUCKET_ID: X64_0xD1_NETIO!WfppIncrementIndexAndPurgeEntries+93
BUCKET_ID: X64_0xD1_NETIO!WfppIncrementIndexAndPurgeEntries+93
Followup: MachineOwner
---------
ken
), so don't hold back on what I should try. I just didn't have time to get my debugger working before my conference, leaving tomorrow morning at 7am PST...