BSOD on New AMD Board

I have been having these random BSOD, which has occurred twice thus far on my new ASUS M4A79XTD EVO motherboard. I have a clean installation of windows which I installed about 2 weeks ago, and at the moment I am clueless of why this BSOD is happening. I am assuming it is the Video Card, but I could be wrong. Any assitance would be of great help.

Computer Hardware Details (All purchased in May 2011, except Video Card)
===========================================================
ASUS M4A79XTD EVO AM3 AMD 790X ATX AMD
AMD Phenon(tm) II X6 1090T Processor 3.20 GHz
CORSAIR Vengeance 8GB (2 x 4GB)
NVIDIA GeForce 8800 GTS *****(Video Card from old computer I had)*****
1.) Western Digital Caviar Blue WD3200AAKS 320GB 7200 RPM
2.) Western Digital Caviar Black WD6401AALS 640GB 7200 RPM
3.) Western Digital Caviar Black WD6401AALS 640GB 7200 RPM
===========================================================

OS: Windows 7 Professional x64
Verion: 6.1.7601 Service Pack 1 Build 7601

**If it helps I slipstreamed SP1 to Windows 7 Pro x64***

Thanks

lealr said:

I have been having these random BSOD, which has occurred twice thus far on my new ASUS M4A79XTD EVO motherboard. I have a clean installation of windows which I installed about 2 weeks ago, and at the moment I am clueless of why this BSOD is happening. I am assuming it is the Video Card, but I could be wrong. Any assitance would be of great help.

Computer Hardware Details (All purchased in May 2011, except Video Card)
===========================================================
ASUS M4A79XTD EVO AM3 AMD 790X ATX AMD
AMD Phenon(tm) II X6 1090T Processor 3.20 GHz
CORSAIR Vengeance 8GB (2 x 4GB)
NVIDIA GeForce 8800 GTS *****(Video Card from old computer I had)*****
1.) Western Digital Caviar Blue WD3200AAKS 320GB 7200 RPM
2.) Western Digital Caviar Black WD6401AALS 640GB 7200 RPM
3.) Western Digital Caviar Black WD6401AALS 640GB 7200 RPM
===========================================================

OS: Windows 7 Professional x64
Verion: 6.1.7601 Service Pack 1 Build 7601

**If it helps I slipstreamed SP1 to Windows 7 Pro x64***

Thanks

These were related to yoiur athrux.sys Atheros wifi driver. Re-install it with newest.

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\060511-30310-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02ca7650
Debug session time: Sun Jun  5 01:56:18.757 2011 (GMT-4)
System Uptime: 0 days 5:07:47.360
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80000007f4e, 8, fffff80000007f4e, 0}

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

Could not read faulting driver name
Probably caused by : athurx.sys ( athurx+9bf7b )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80000007f4e, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80000007f4e, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d11100
 fffff80000007f4e 

FAULTING_IP: 
+624c952f02ebdf20
fffff800`00007f4e ??              ???

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007a29a30 -- (.trap 0xfffff88007a29a30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000032d900000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000007f4e rsp=fffff88007a29bc0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000f44 r10=fffff80002a62000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fffff800`00007f4e ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002a8da0c to fffff80002ae1d00

STACK_TEXT:  
fffff880`07a298c8 fffff800`02a8da0c : 00000000`00000050 fffff800`00007f4e 00000000`00000008 fffff880`07a29a30 : nt!KeBugCheckEx
fffff880`07a298d0 fffff800`02adfe2e : 00000000`00000008 fffff800`00007f4e 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4621f
fffff880`07a29a30 fffff800`00007f4e : 00000000`40350089 fffff880`052a8f7b fffffa80`00000000 00000000`00004048 : nt!KiPageFault+0x16e
fffff880`07a29bc0 00000000`40350089 : fffff880`052a8f7b fffffa80`00000000 00000000`00004048 fffff880`00000000 : 0xfffff800`00007f4e
fffff880`07a29bc8 fffff880`052a8f7b : fffffa80`00000000 00000000`00004048 fffff880`00000000 00000000`00000000 : 0x40350089
fffff880`07a29bd0 fffffa80`00000000 : 00000000`00004048 fffff880`00000000 00000000`00000000 00000000`00000000 : athurx+0x9bf7b
fffff880`07a29bd8 00000000`00004048 : fffff880`00000000 00000000`00000000 00000000`00000000 fffffa80`07fa8030 : 0xfffffa80`00000000
fffff880`07a29be0 fffff880`00000000 : 00000000`00000000 00000000`00000000 fffffa80`07fa8030 00000000`00000001 : 0x4048
fffff880`07a29be8 00000000`00000000 : 00000000`00000000 fffffa80`07fa8030 00000000`00000001 fffffa80`06a0c040 : 0xfffff880`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athurx+9bf7b
fffff880`052a8f7b ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  athurx+9bf7b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athurx

IMAGE_NAME:  athurx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b42b0a4

FAILURE_BUCKET_ID:  X64_0x50_athurx+9bf7b

BUCKET_ID:  X64_0x50_athurx+9bf7b

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

Appreciate the help zigzag3143.. You saved my life from having to wonder what the actual problem was. Many thanks to you once again.

lealr said:

Appreciate the help zigzag3143.. You saved my life from having to wonder what the actual problem was. Many thanks to you once again.

My pleasure and let us know if you need help. I know how frustrating these things can be.

I managed to download the latest driver for my wireless card directly from the website. But today I managed to get that BSOD once again, so I am not too sure what I might be doing wrong. I am using a TP-Link: Model No. TL-WN722N, 150 High Gain Wireless USB Adapter. On the box it states that it is Compatible with Windows 7, but when I look at the driver date it has 1/4/2010. Even the one I download from the manufacture website, which has a publishing date of 6/29/2010, still shows driver date: 1/4/2010 when I check it on device manager. Any ideas what I might be doing wrong?

I am attaching the dump files which were generated today for reference. Would appreciate the help once again.

On a side note, I have the wireless usb connected to the monitor and not the actual desktop, being that the monitor has USB ports on it. Not sure if this might cause the issue.

lealr said:

I managed to download the latest driver for my wireless card directly from the website. But today I managed to get that BSOD once again, so I am not too sure what I might be doing wrong. I am using a TP-Link: Model No. TL-WN722N, 150 High Gain Wireless USB Adapter. On the box it states that it is Compatible with Windows 7, but when I look at the driver date it has 1/4/2010. Even the one I download from the manufacture website, which has a publishing date of 6/29/2010, still shows driver date: 1/4/2010 when I check it on device manager. Any ideas what I might be doing wrong?

I am attaching the dump files which were generated today for reference. Would appreciate the help once again.

On a side note, I have the wireless usb connected to the monitor and not the actual desktop, being that the monitor has USB ports on it. Not sure if this might cause the issue.

Still blamed on the same driver and still the same date on that driver did you update it?

its from 1/10/2010 so over a year old.


Having the USB plugged elsewhere shouldnt matter but is an easy thing to check. Plug the device directly into the PC to see.

I managed to update the driver using the Windows 7 update driver option, and it stated it already has the latest driver installed. I also went to the manufactures website to get the latest driver but even after using that updated driver, which has a publishing date of 6/29/2010 it still states 1/4/10 on device manager. Am not sure if they have created a 2011 driver.

I will try connecting it directly to the PC and see if that helps. But for the time being I am not sure if the manufacture will make an updated driver anytime soon. I might just have to get an internal wireless card.

It seems that the problem has stopped for now. So it might be fixed, I will continue to monitor the issue and see how things turn up. Appreciate the help zigzag3143.

lealr said:

It seems that the problem has stopped for now. So it might be fixed, I will continue to monitor the issue and see how things turn up. Appreciate the help zigzag3143.

My pleasure and let us know if you need help.

Ken

Unfortunately I am still having the same issue. Am not sure what to do now. Should I get a new internal Wireless card instead of using this USB Wireless Adapter? So far the Manufacture's website does not have a 2011 driver, only the driver from last year January.

I have attached the dump file once more. I wonder if all these BSOD would damage my HDD, am a bit worried now, and probably should get an internal wireless card. I hope someone can give me some good advice, since am a bit frustrated with the on going problem.