Bsod

Hi,
It seems Atheros Extensible Wireless LAN driver is the caused.
Do you use proper driver for the Wireless LAN device?
I see from MSinfo that you use D-Link Adapter, but why Atheros driver was shown up when crashing?

Code:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a12000 PsLoadedModuleList = 0xfffff800`02c57650
Debug session time: Mon Jul  4 00:15:31.725 2011 (GMT-8)
System Uptime: 0 days 0:03:04.911
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {c, 2, 0, fffff880044fb99d}

Unable to load image \SystemRoot\system32\DRIVERS\athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+8b99d )

Followup: MachineOwner
---------

3: 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: 000000000000000c, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880044fb99d, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc1100
 000000000000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
athrx+8b99d
fffff880`044fb99d 8b480c          mov     ecx,dword ptr [rax+0Ch]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88009f104b0 -- (.trap 0xfffff88009f104b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8005944f94
rdx=0000000000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044fb99d rsp=fffff88009f10640 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffffa800580ea70
r11=0000000000000018 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
athrx+0x8b99d:
fffff880`044fb99d 8b480c          mov     ecx,dword ptr [rax+0Ch] ds:7000:00000000`0000000c=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a912a9 to fffff80002a91d00

STACK_TEXT:  
fffff880`09f10368 fffff800`02a912a9 : 00000000`0000000a 00000000`0000000c 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`09f10370 fffff800`02a8ff20 : fffffa80`05944e9c fffffa80`05325a00 fffffa80`06c5d680 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`09f104b0 fffff880`044fb99d : fffffa80`05944f94 fffffa80`05944f94 fffffa80`0595d660 0000005d`00000000 : nt!KiPageFault+0x260
fffff880`09f10640 fffffa80`05944f94 : fffffa80`05944f94 fffffa80`0595d660 0000005d`00000000 fffffa80`06427064 : athrx+0x8b99d
fffff880`09f10648 fffffa80`05944f94 : fffffa80`0595d660 0000005d`00000000 fffffa80`06427064 fffffa80`058d9040 : 0xfffffa80`05944f94
fffff880`09f10650 fffffa80`0595d660 : 0000005d`00000000 fffffa80`06427064 fffffa80`058d9040 00000018`00000008 : 0xfffffa80`05944f94
fffff880`09f10658 0000005d`00000000 : fffffa80`06427064 fffffa80`058d9040 00000018`00000008 fffffa80`0534e030 : 0xfffffa80`0595d660
fffff880`09f10660 fffffa80`06427064 : fffffa80`058d9040 00000018`00000008 fffffa80`0534e030 00000078`09f10860 : 0x5d`00000000
fffff880`09f10668 fffffa80`058d9040 : 00000018`00000008 fffffa80`0534e030 00000078`09f10860 00000000`00000000 : 0xfffffa80`06427064
fffff880`09f10670 00000018`00000008 : fffffa80`0534e030 00000078`09f10860 00000000`00000000 fffffa80`05817780 : 0xfffffa80`058d9040
fffff880`09f10678 fffffa80`0534e030 : 00000078`09f10860 00000000`00000000 fffffa80`05817780 00000000`00000000 : 0x18`00000008
fffff880`09f10680 00000078`09f10860 : 00000000`00000000 fffffa80`05817780 00000000`00000000 fffffa80`05817890 : 0xfffffa80`0534e030
fffff880`09f10688 00000000`00000000 : fffffa80`05817780 00000000`00000000 fffffa80`05817890 00000000`044ec1ac : 0x78`09f10860


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+8b99d
fffff880`044fb99d 8b480c          mov     ecx,dword ptr [rax+0Ch]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrx+8b99d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a2ea4b9

FAILURE_BUCKET_ID:  X64_0xD1_athrx+8b99d

BUCKET_ID:  X64_0xD1_athrx+8b99d

Followup: MachineOwner
---------

Jrdn23 said:

I have the d-link drivers installed, I have no idea what the Atheros is.

Have you tried to update its driver?
Also what is the model of your D-Link adapter?