Solved BSOD Playing WoW, Several Errors

[cshaw419]

Hi, I just built my new computer on Saturday. The first day everything seemed fine and I had no issues. The following night I got my first BSoD and have been getting them virtually every time I play WoW. I have tried trouble shooting myself. Here is what I have done:

1. Ran memtest86: 8 tests/no errors
2. Ran FurMark burn-in: Ran for over an hour with GPU at 99%, temps stayed at 49-54 C. No crashes.
3. Ran AoD stability test for 1 hour: No errors.
4. Ran Windows Memtest: No errors after 2 tests.
5. Used DriverFusion in safe mode to remove graphic drivers, updated drivers from Gigabyte's website: Drivers specific to my card model.
6. Googled Nirsoft BlueScreenView bug checks: Found nothing relevant.

I come to you as I am at my wits end. From all my tests it seems pretty clear to me that my hardware is working fine. Windows is telling me all my drivers are up to date. I am not having problems browsing or watching videos, and when I am in WoW everything seems to be running fantastically until the BSoD pops up.

I assume all relevant information that anyone needs will be found in this post and my attachment. I will be monitoring this thread closely. Any help would be appreciated.

 

[Arc]

Hello cshaw419.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {57ff6aae5a8, 2, 1, fffff88005408a9f}

*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
[COLOR=Red]Probably caused by : athurx.sys[/COLOR] ( athurx+3a9f )

Followup: MachineOwner
---------
fffff880`05405000 fffff880`055e2000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
 [COLOR=Red]   Image name: athurx.sys
    Timestamp:        Mon Oct 11 14:40:57 2010 [/COLOR](4CB2D4A1)
    CheckSum:         001D77E1
    ImageSize:        001DD000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The Atheros AR9271 Wireless Network Adapter driver is very old here. Update it from ATHEROS drivers for Microsoft Windows (Atheros?????)

Also, some memory related errors are there, too.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, fffff80002f1c0f0}
[COLOR=Red]
Probably caused by : memory_corruption [/COLOR]( nt!MiFindNodeOrParent+0 )

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

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Let us know the results. And next time upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

 

[cshaw419]

Thanks for looking at this. As I said in the OP, I ran memtest 8 times (seeing that it was highly recommended in virtually every BSoD thread) and I had no errors. I'll run it again after I post this.View attachment 253871

 

[cshaw419]

Finished the memtest with 0 errors, installed atheros drivers that you suggested.

 

[Arc]

OK, let us know if there are any further crashes, and if so, dont forget to upload the msinfo32.nfo file that time.

 

[cshaw419]

I have played about 3 hours without a crash. I'll let you know if I do end up crashing. And if I go a few days without a crash I'll certainly come back and tell you my issue is fixed. I just have one question if you don't mind, why did I need atheros drivers when my wireless card is Realtek on the Gigabyte 970a-d3? Does realtek use the atheros chipsets? And if so, why didn't upgrading the realtek drivers that were on gigabytes website also update the atheros drivers? I know this question isn't really that important, if it worked it worked, but I'd still like to know.

When I looked through the logs I noticed that was an atheros issue, but since I don't know that much I just assumed that wasn't something I needed to be concerned with, although I am now assuming that Realtek is using the atheros chipset. I also wonder why that driver would casue so many crashes when I had the onboard wireless disabled. I use a wireless card from netgear.

(really just trying to inform myself, if it is a bother to answer these questions feel free to ignore them and I'll update this thread the next time I see a BSoD or in a few days if everything is still clear)

 

[cshaw419]

So last night I played for at least 3 hours, no problems. The game even ran for another 2-3 hours throughout the night when I wasn't playing. Computer was on all night and today without crashing. Tonight I get on and start to play and I am crashing regularly again.

View attachment 254070
View attachment 254071

 

[cshaw419]

Still crashing, still only crashing while playing WoW. What has happened the last 2 days is that I will crash 2-3 times, then after that it plays all night without any issues. When it does crash, I don't have to be doing anything, I can just be idle and I get a BSoD. here's more info:

View attachment 254330
View attachment 254331

 

[cshaw419]

Well, after posting the last entry I decided to try Prime95 to test the system. For the first time, I was able to get a BSoD without it being caused by WoW. After the first crash I moved my ram to the other dual channel slots. It crashed again. I haven't changed anything else since my last post so I'll only post the dumps. The last 2 dumps are both from running Prime95 and the only difference is that the RAM was in different slots.

View attachment 254335

 

[cshaw419]

I think I may have figured out the problem (knock on wood). I think I have a bad stick of RAM. After running Prime95 and figuring out that I could get my system to BSoD on command, I took out one stick of RAM and ran the test again. It stayed stable for 30 mins. I took that stick out and put the other stick into the same socket. Crashed in under 30 seconds. Plugged the first stick back into the same socket and ran the test again, so far it's been running for 10 mins without a crash. I understand this forum is for reading logs, but this seems like an obvious case of a bad stick of RAM. If anyone would like to chime in and reassure me that I'm right here, I would be much appreciated.

 

[cshaw419]

You can mark this as solved if you would like. Was certainly the 1 bad stick of RAM. Took it out, haven't crashed in 3 days. Just got some new sticks today, installed, haven't crashed in 4 hours. Everything is right with the world.

 

[Arc]

Good news.
Marking solved or otherwise is on the user. If you like, you may click the green button on quick reply box to mark it as solved.