BSOD playing FFXIV and browsing on chrome.

kwall · 14 Nov 2013

The BSOD problems started last night while playing FFXIV. I had a series of crashes but was thinking something was wrong with the game. That stopped when the computer blue screened. After restarting and getting back to the desktop, the Windows solution window popped up detailing that I had a WD-20130408-1733.dmp,
sysdata.xml, and WERInternalMetadata.xml error.

I began looking for solutions in chrome until having problems with websites crashing on me then chrome crashed all together. Reading that I might be a video card error, I went on to the AMD website and downloaded the newest graphic card drivers (AMD Catalyst™ 13.11 Beta9.2). I preceded then to uninstall the old drivers, let the computer restart, and installed the new drivers. After that I had no problems in the game or chrome that night.

This morning after being on the computer for about three hours only browsing through chrome, I got the blue screen again. The Windows solution error box reads:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 19
BCP1: 0000000000000003
BCP2: FFFFFA8006977A10
BCP3: FF2DFA8006977A10
BCP4: FF8DFA8006977A10
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111413-23259-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-63383-0.sysdata.xml

I am unsure what the problems is now. This is a new computer build that is a week old. I guess there are some growing pains.

Arc · 14 Nov 2013

Hi Kwall.

Todays BSOD is stop 0x19, and that is caused by AVAST.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa8006977a10, ff2dfa8006977a10, ff8dfa8006977a10}

*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )

Followup: Pool_corruption
---------

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one; for a safety reason.

Next, the BSOD of the other day ....

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880048ae8a9, fffff88005d81fb8, fffff88005d81810}

Probably caused by : atikmdag.sys ( atikmdag+a78a9 )

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

Due to the bugcheck code, it is difficult to discriminate the GPU hardware and the GPU driver as the probable cause. Better to be cautious for the both.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

About the driver, it was a BETA installed there.

Code:

fffff880`04807000 fffff880`053a4000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Jun 05 04:33:11 2013 (51AE722F)
    CheckSum:         00B4F8F0
    ImageSize:        00B9D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Using a BETA driver, you cannot expect stability; as it is still under development. It is for testing, not for daily use. And, you updated to another BETA. Not a good move.

Uninstall the BETA display driver that you have installed. Then clean up the leftover following Drivers - Clean Left over Files after Uninstalling.

Then Update your ATI/AMD display driver to the latest WHQL only (13.9).
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Then let us know how it is running, as it is known that the game itself is problematic.

kwall · 14 Nov 2013

Should I use "ATI Display Driver 13.101WHQL for Win7 32/64" off the asus site instead or 13.9 as suggested? This was the driver being used when I crashed last night not the beta ones.

Arc · 14 Nov 2013

kwall said:

Should I use "ATI Display Driver 13.101WHQL for Win7 32/64" off the asus site instead or 13.9 as suggested? This was the driver being used when I crashed last night not the beta ones.

The timestamp of 13.9 WHQL is not of June.

kwall · 14 Nov 2013

Something during the anti-virus full system scan must be causing the problem. I BSOD using Microsoft Security Essentials.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 24
BCP1: 00000000000C08A5
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111413-32151-01.dmp
C:\Users\Richard\AppData\Local\Temp\WER-74615-0.sysdata.xml

kwall · 14 Nov 2013

Its been nine hour since my last BSOD. I was able to successfully run a full scan with Microsoft Security Essentials at about 6:00 pm EST. Although windows stopped working at 6:43.

The error was:The computer has rebooted from a bugcheck. The bugcheck was: 0x00000051 (0x0000000000000001, 0xfffff8a0110a4010, 0x0000000003e74000, 0x0000000000000465)

After windows restarted I was able to play games for a few hours without crashing. I am still using the latest beta drivers from AMD without any problems so far.

I am still stumped from my last BSOD while running MSE full scan earlier this afternoon. I uploaded SFD zip if it helps with my error around 6:43 pm and if it has any connection to my BSOD problems.

Arc · 15 Nov 2013

Something is going really bad. The last two BSODs .....

REGISTRY_ERROR: BugCheck 51
NTFS_FILE_SYSTEM: BugCheck 24

Plus you are having BSOD during bootable virus scan. Enough evidence of an infected system. Of the HDD is failing.

Have you performed the TDSSKiller scan already? If not, do it. Let us know the result. Then go for a clean reinstall.

kwall · 15 Nov 2013

I used TDSSKiller as instructed but no problems were found. After used Malwarebytes anit malware full system scan that resulted with no problems. Then I tried to use Microsoft Security Essentials fall scan again but unlike last night it crashed this morning. Arc you mentioned that it could be a HDD failure, which could be the case since I been using this HD for eight years. Guess my next step is a fresh windows install?

Arc · 15 Nov 2013

I am saying about the clean install, as there is evidences of disc corruption, but not a full proof. If the clean install also behaves in the same way, the remaining option will be replacing the HDD.

If you go for a clean install, use the WHQL that is supplied by the AMD, not by ASUS. It is still failing in the latest dump, too.

kwall · 15 Nov 2013

Any recommended link to download 13.9whql? I tried the amd auto detect driver program before and it is not working. Its telling me it cannot find my product or OS. I using the new R9 270x.