Troubleshooting advice needed

Associate
Joined
21 Feb 2011
Posts
128
Hi Guys,

Happy Xmas.

I have a recurring crash on my rig that I've been unable to get to the bottom of and I've now reached the limit of my technical expertise, so looking for kind advice on what to do now.

The problem:
About 1 or 2 blue screen crashes per hour. There appears to be no pattern and it happens regardless of load on the CPU or GPUs. However, if I run the system overnight to download something it rarely crashes, so the problem mainly occurs when running games, but also sometimes at shutdown.
I don't have the fault code to hand, but from looking on the web it's a generic, non-specific code.
A consequence of the crash has been to lose game saves but in some games have gone missing from the system altogether. Not sure if that is relevant.

My rig is in my sig below, plus I now have a second 7950.

Actions taken so far:
Checked core temps - CPU and GPUs are all well within safe operating temps.
Removed overclock - no effect
Flashed bios - seemed improved for 2 days, then back to normal
Took it off X-fire and swapped the main card to my newest one - no effect
Checked firmware on SSD - up to date
Bought a new SSD - no effect (but noteworthy that it's the same Sandisk model)
Reseated GPUs and RAM - no effect

I'd be grateful for any ideas for next steps and advice on whether you can get diagnostic/logging software that will help ID the problem.

When I get home I will attach the error code.

Ta
 
1st stick of RAM out and it still crashes. Now to see whether it stays stable with only the other stick in...

Failing that, I will try some other RAM from a family member's rig to see if that solves it.
 
Taking individual RAM sticks out had no effect so I will try someone else's RAM in mine.

Here is the fault code, in case that gives any hints:

STOP: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF88004638BCD, 0xFFFFF88003CD1138, 0xFFFFF88003CD0990)

Athurx.sys - Address FFFFF88004638BCD base at FFFFF8800462F000

I've searched theweb for ideas, but tbh I don't know how to interpret the code and which bits are critical.
 
If it still blue-screens with replacement ram I'd be inclined to start looking at the power supply as a possible culprit. Either swap it out for a good one, get a multimeter on it and check the voltages or simply check the BIOS reported voltages (although this is not always reliable)
 
If it still blue-screens with replacement ram I'd be inclined to start looking at the power supply as a possible culprit. Either swap it out for a good one, get a multimeter on it and check the voltages or simply check the BIOS reported voltages (although this is not always reliable)

Thanks.

You mention about swapping the PSU for a good one - do you mean that the one I have is not a reliable unit?

At what location should I take the multimeter reading?
 
All power supplies can be prone to failure. Your XFX 850W is made by Seasonic so it's a good unit, but it'd be prudent to check it anyway. Rules it out of any further testing and doesn't cost anything to do, assuming you have a multimeter.

Here's how
 
Right, I've finally managed to lay my hands on a). A multimeter and b). Spare time, and finally got around to testing my PSU.

After weeks of trying to work out the reason for the crashes I kinda hoped it was the PSU but it's not to be and the thing is solid as a rock. Voltages on all rails barely moved under load, well-within tolerances.

Any suggestions on what to try next?
 
From looking at the bsod codes list it says this about that error.

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

Though i think i had this a few weeks back with a faulty memory kit. 2400mhz patriot venom. It wouldnt run at its xmp rated speed and timings but worked ok at 1600mhz. Have you tried running memtest86 with the ram set to its rated 2133mhz, voltage and timings?
 
From looking at the bsod codes list it says this about that error.

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

Though i think i had this a few weeks back with a faulty memory kit. 2400mhz patriot venom. It wouldnt run at its xmp rated speed and timings but worked ok at 1600mhz. Have you tried running memtest86 with the ram set to its rated 2133mhz, voltage and timings?

I've not tried running scannow or chkdsk - I'll give that a go.

I did try running my memory at lower speeds and that did not seem to help. Nevertheless, I can't help but think this is memory related. I still need to try swapping my memory with someone else's to see if that solves it.
 


I installed this last night and wished I'd done so sooner. It showed that every crash in the dump, except 1, was the result of the driver for my wireless adapter. A quick sqizz on the internet shows that it's a very common problem.

I've removed the adapter and rogue driver and so far I've had no crashes. Still need to spend a few more crash-free hours to confirm that I've finally found the culprit, but optimistic that my rig is on the mend :D

Cheers
 
Back
Top Bottom