Hello, your dumps are pointing to the culprit L1C62x64.sys, which is the Atheros NIC driver. Update it here.
Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Icarus\Downloads\Windows_NT6_BSOD_jcgriff2\033112-28953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e5c000 PsLoadedModuleList = 0xfffff800`030a0650
Debug session time: Fri Mar 30 22:35:06.894 2012 (UTC - 4:00)
System Uptime: 7 days 11:17:35.476
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff880021d3ec0, 2, 0, fffff80002edae40}
Unable to load image \SystemRoot\system32\DRIVERS\L1C62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L1C62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1C62x64.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : L1C62x64.sys ( L1C62x64+5534 )
Followup: MachineOwner
---------
4: 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: fffff880021d3ec0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002edae40, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310a100
fffff880021d3ec0
CURRENT_IRQL: 2
FAULTING_IP:
nt!RtlCopyMemoryNonTemporal+40
fffff800`02edae40 4c8b0c11 mov r9,qword ptr [rcx+rdx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88003384ab0 -- (.trap 0xfffff88003384ab0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000040 rbx=0000000000000000 rcx=fffff88009bb7ec0
rdx=fffffffff861c000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002edae40 rsp=fffff88003384c48 rbp=0000000000000002
r8=0000000000000020 r9=0000000000000000 r10=fffffa80079e9180
r11=fffff88003384c30 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!RtlCopyMemoryNonTemporal+0x40:
fffff800`02edae40 4c8b0c11 mov r9,qword ptr [rcx+rdx] ds:0002:fffff880`021d3ec0=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ed82e9 to fffff80002ed8d40
STACK_TEXT:
fffff880`03384968 fffff800`02ed82e9 : 00000000`0000000a fffff880`021d3ec0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03384970 fffff800`02ed6f60 : 00000000`00000000 00000000`00000000 00000000`00000014 fffff880`021d3ec0 : nt!KiBugCheckDispatch+0x69
fffff880`03384ab0 fffff800`02edae40 : fffff800`02e15e08 fffff880`021d3ec0 00000000`00000002 fffffa80`11d4b7c0 : nt!KiPageFault+0x260
fffff880`03384c48 fffff800`02e15e08 : fffff880`021d3ec0 00000000`00000002 fffffa80`11d4b7c0 fffff800`02e3fc60 : nt!RtlCopyMemoryNonTemporal+0x40
fffff880`03384c50 fffff800`02e15593 : fffffa80`079e9180 fffffa80`079e9100 00000000`00000ec0 00000000`00000000 : hal!HalpDmaSyncMapBuffers+0x1b0
fffff880`03384d00 fffff800`02e184fb : fffffa80`0fd43988 fffffa80`079e9180 fffffa80`11d4b7c0 fffff880`01749cda : hal!HalpDmaMapScatterTransfer+0xa3
fffff880`03384d50 fffff800`02e18472 : fffffa80`0fd43988 fffffa80`0fd43980 00000000`00000060 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`03384de0 fffff800`02e1794f : 00000000`00000000 fffff800`02e1501e 00000000`00000000 00000000`00000001 : hal!IoMapTransfer+0x8e
fffff880`03384e20 fffff800`02e1813d : fffffa80`08282050 fffffa80`079e9180 fffffa80`079e9101 00000000`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`03384ec0 fffff800`02e1771f : fffffa80`0fd43940 00000000`00000060 fffffa80`079e9180 fffffa80`11d4b7c0 : hal!HalAllocateAdapterChannel+0x101
fffff880`03384f00 fffff880`014a67c1 : fffffa80`0854f160 fffffa80`0854f160 00000000`000000a0 00000000`00000001 : hal!HalBuildScatterGatherList+0x2f3
fffff880`03384f70 fffff880`0962a534 : fffffa80`082821a0 00000000`00000000 fffffa80`0fcb8320 fffffa80`0854f160 : ndis!NdisMAllocateNetBufferSGList+0x181
fffff880`03385010 fffffa80`082821a0 : 00000000`00000000 fffffa80`0fcb8320 fffffa80`0854f160 fffffa80`0fd43940 : L1C62x64+0x5534
fffff880`03385018 00000000`00000000 : fffffa80`0fcb8320 fffffa80`0854f160 fffffa80`0fd43940 fffffa80`000001c0 : 0xfffffa80`082821a0
STACK_COMMAND: kb
FOLLOWUP_IP:
L1C62x64+5534
fffff880`0962a534 ?? ???
SYMBOL_STACK_INDEX: c
SYMBOL_NAME: L1C62x64+5534
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: L1C62x64
IMAGE_NAME: L1C62x64.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49d2f6fd
FAILURE_BUCKET_ID: X64_0xA_L1C62x64+5534
BUCKET_ID: X64_0xA_L1C62x64+5534
Followup: MachineOwner
---------
Quote