Please help! i got blue screen while iam executing programs that require admin rights and sometimes when iam gaming.
dunno what to do...
repot and dump files attached.
x64
the original installed OS on the system? yes
- an OEM or full retail version? full retail
- What is the age of system (hardware)? about an year
- What is the age of OS installation (have you re-installed the OS?) about an year
All of these were virtually identical and caused by your atheros driver (athrx.sys). It is old and needs to be updated and re-installed
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\Windows_NT6_BSOD_jcgriff2\022211-18002-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
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`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Tue Feb 22 21:08:00.225 2011 (GMT-5)
System Uptime: 0 days 0:32:20.253
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {44, 2, 0, fffff880048988c1}
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+5c8c1 )
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: 0000000000000044, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880048988c1, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebf0e0
0000000000000044
CURRENT_IRQL: 2
FAULTING_IP:
athrx+5c8c1
fffff880`048988c1 8b4044 mov eax,dword ptr [rax+44h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff88002f1b3e0 -- (.trap 0xfffff88002f1b3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8003f05a8c
rdx=fffffa8003f05a8c rsi=0000000000000000 rdi=0000000000000000
rip=fffff880048988c1 rsp=fffff88002f1b570 rbp=0000000000000000
r8=0000000000000000 r9=fffffa80050f393c r10=0000000000da7a64
r11=00000000001d9b16 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
athrx+0x5c8c1:
fffff880`048988c1 8b4044 mov eax,dword ptr [rax+44h] ds:8d20:00000000`00000044=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002c88469 to fffff80002c88f00
STACK_TEXT:
fffff880`02f1b298 fffff800`02c88469 : 00000000`0000000a 00000000`00000044 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f1b2a0 fffff800`02c870e0 : fffffa80`0547eb10 00000000`00000000 fffffa80`0547eb10 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f1b3e0 fffff880`048988c1 : fffffa80`03f05a8c 00000000`00000000 fffffa80`0572cb60 fffffa80`04c56030 : nt!KiPageFault+0x260
fffff880`02f1b570 fffffa80`03f05a8c : 00000000`00000000 fffffa80`0572cb60 fffffa80`04c56030 fffffa80`00000018 : athrx+0x5c8c1
fffff880`02f1b578 00000000`00000000 : fffffa80`0572cb60 fffffa80`04c56030 fffffa80`00000018 fffff800`02c943b7 : 0xfffffa80`03f05a8c
STACK_COMMAND: kb
FOLLOWUP_IP:
athrx+5c8c1
fffff880`048988c1 8b4044 mov eax,dword ptr [rax+44h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: athrx+5c8c1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athrx
IMAGE_NAME: athrx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a2ea4b9
FAILURE_BUCKET_ID: X64_0xD1_athrx+5c8c1
BUCKET_ID: X64_0xD1_athrx+5c8c1
Followup: MachineOwner
---------
1: kd> lmvm athrx
start end module name
fffff880`0483c000 fffff880`04994000 athrx T (no symbols)
Loaded symbol image file: athrx.sys
Image path: \SystemRoot\system32\DRIVERS\athrx.sys
Image name: athrx.sys
Timestamp: Tue Jun 09 14:06:49 2009 (4A2EA4B9)
CheckSum: 0015FE99
ImageSize: 00158000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
ALSO, old driver needing update
Code:
SmSerl64.sys 9/26/2008 3:45:56 0x48dca144 fffff880`058bb000 fffff880`059f5000 0x0013a000
Rt64win7.sys 2/26/2009 4:04:13 0x49a65b0d fffff880`0456a000 fffff880`0459c000 0x00032000
igdkmd64.sys 5/6/2009 13:22:19 0x4a01d55b fffff880`03c04000 fffff880`041d7500 0x005d3500
spldr.sys 5/11/2009 11:56:27 0x4a0858bb fffff880`015db000 fffff880`015e3000 0x00008000
amdxata.sys 5/19/2009 12:56:59 0x4a12f2eb fffff880`00de0000 fffff880`00deb000 0x0000b000
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads