First BSOD, would like to know what it stemmed from

[TheUnion]

I've attached the minidump file View attachment 204115

 

[writhziden]

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\TheUnion\032412-23010-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c16000 PsLoadedModuleList = 0xfffff800`02e5a650
Debug session time: Sat Mar 24 11:39:58.121 2012 (UTC - 6:00)
System Uptime: 0 days 0:13:17.323
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800bc54041, fffff880097fda28, fffff880097fd280}

Probably caused by : athurx.sys ( athurx+31041 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800bc54041, The address that the exception occurred at
Arg3: fffff880097fda28, Exception Record Address
Arg4: fffff880097fd280, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
athurx+31041
fffff880`0bc54041 ff9060050000    call    qword ptr [rax+560h]

EXCEPTION_RECORD:  fffff880097fda28 -- (.exr 0xfffff880097fda28)
ExceptionAddress: fffff8800bc54041 (athurx+0x0000000000031041)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000560
Attempt to read from address 0000000000000560

CONTEXT:  fffff880097fd280 -- (.cxr 0xfffff880097fd280)
rax=0000000000000000 rbx=fffffa8007404b60 rcx=0000000000000000
rdx=0000000000000008 rsi=fffffa80066cd040 rdi=0000000000000001
rip=fffff8800bc54041 rsp=fffff880097fdc60 rbp=0000000000000080
 r8=0000000000000000  r9=0000000000000f44 r10=fffff80002c16000
r11=0000000000000000 r12=fffffa80078ca030 r13=fffff8800bc29e20
r14=0000000000000000 r15=fffff880009eef40
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
athurx+0x31041:
fffff880`0bc54041 ff9060050000    call    qword ptr [rax+560h] ds:002b:00000000`00000560=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000560

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec4100
 0000000000000560 

FOLLOWUP_IP: 
athurx+31041
fffff880`0bc54041 ff9060050000    call    qword ptr [rax+560h]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80002e0b728 to fffff8800bc54041

STACK_TEXT:  
fffff880`097fdc60 fffff800`02e0b728 : fffff800`02e0b728 3ebec9a9`2a6ae9f9 00000000`00000000 fffffa80`07404b60 : athurx+0x31041
fffff880`097fdc68 fffff800`02e0b728 : 3ebec9a9`2a6ae9f9 00000000`00000000 fffffa80`07404b60 fffff880`0bc29ef3 : nt!KiInitialPCR+0x3a28
fffff880`097fdc70 3ebec9a9`2a6ae9f9 : 00000000`00000000 fffffa80`07404b60 fffff880`0bc29ef3 fffffa80`06d7c030 : nt!KiInitialPCR+0x3a28
fffff880`097fdc78 00000000`00000000 : fffffa80`07404b60 fffff880`0bc29ef3 fffffa80`06d7c030 fffffa80`07404b60 : 0x3ebec9a9`2a6ae9f9


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  athurx+31041

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athurx

IMAGE_NAME:  athurx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4cb2d4a1

STACK_COMMAND:  .cxr 0xfffff880097fd280 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_athurx+31041

BUCKET_ID:  X64_0x7E_athurx+31041

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

Simple. It was due to your Atheros Wireless Network Adapter driver. I do not know which model, but you should be able to determine it through device manager. Start Menu -> Right click Computer -> Manage -> Device Manager from the list on the left -> Expand Network Adapters

It can be updated from ATHEROS drivers for Microsoft Windows (Atheros?????)


I note an out of date driver that may also be related to the crash:

jswpslwfx	fffff880`08cfe000	fffff880`08d0b000	Thu May 15 04:28:50 2008 (482c1062)	00011e66		jswpslwfx.sys

jswpslwfx.sys

Wireless USB network adapters that have out of date drivers often cause crashes with Windows 7.