Solved BSOD playing FFXIV and browsing on chrome.

[kwall]

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]

Hi Kwall.

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

*******************************************************************************
*                                                                             *
*                        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 ....

[COLOR=Red]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff880048ae8a9, fffff88005d81fb8, fffff88005d81810}
[COLOR=Red]
Probably caused by : atikmdag.sys[/COLOR] ( 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.

fffff880`04807000 fffff880`053a4000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
[COLOR=Red]    Image name: atikmdag.sys
    Timestamp:        Wed Jun 05 04:33:11 2013[/COLOR] (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 http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html.

Then Update your ATI/AMD display driver to the latest WHQL only (13.9).
You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, 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]

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]

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]

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]

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]

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]

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]

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]

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.

 

[Arc]

Here :ar: Desktop

 

[kwall]

Still having problems even after a fresh windows installation. This time the computer blue screened while windows was installing updates. Could there be a problem with one of the updates or is it just that this hard drive seen its last days?

 

[Arc]

No crash dump. The Bugcheck code was 0x1A, but it failed to record the crash dump.

Follow it: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Also 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.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

As there are lots of windows update failure, I will request NoelDP to have a look.

 

[NoelDP]

Hmm - the 'regulated' errors in the windowsupdate.log file simply mean that the server is overloaded, so we can ignore them for the moment.

There are a couple of errors there that may indicate registry problems


Please follow the Windows Update Posting Instructions and post the requested data

 

[kwall]

Update:
Since having the crashes this morning during windows update, there have been no problems so far. Following NoelDP link to the Windows Update Posting Instructions part of the forums, I downloaded System Update Readiness Tool. I ran the tool which then restarted the computer with Windows Updates working again. This time though all the updates worked fine with no bsod. After I ran a full scan of MSE to see if that would cause a bsod like yesterday. This time there were no crashes nor anything found. That led me to try Malwarebyte full scan which had similar results.

With that working well at the moment, should I test my memory with Memtest86+? I have no problems so far browsing chrome with multiple tabs open and watching videos. I will try to game later to see it any problems surface.

 

[kwall]

Well it crashed again . This time I was trying to re-install FFXIV but I was catching a snag on the download. I was uninstalling the files that could download than crash.

The error was:
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA8002005470
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\111613-23540-01.dmp
C:\Users\PotatoV4\AppData\Local\Temp\WER-58703-0.sysdata.xml

I would also like to note that I having problems with getting the 13.9 whql the. Since the AMD auto detect tool does not recognize OS or Card, I used the link you provided Arc. I also ran in to a problem their. I followed the instructions and click custom install to select the driver only. The problems was there was no 13.9 driver option only the hdmi audio driver. I am not sure if its a Asus thing or cannot get it since its the new R9 270x.

 

[NoelDP]

Please post the CBS and CheckSUR data I requested.

 

[kwall]

Here is the cbs for you NoelDP. Had to split what was inside to 2 different zips because I was having trouble uploading it as one. Would the CheckSUR produce a log after its done?

Edit: I ran sfc /scannow and it came up with an error.

 

[NoelDP]

Did you actually read the instruction or not?

From the SFC results

2013-11-17 08:57:30, Info                  CSI    000002fd [SR] Repairing 1 components
2013-11-17 08:57:30, Info                  CSI    000002fe [SR] Beginning Verify and Repair transaction
2013-11-17 08:57:30, Info                  CSI    00000300 [SR] Cannot repair member file [l:30{15}]"NlsData0011.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

From the background CBS data...

2013-11-17 08:28:22, Info                  CSI    [EMAIL="000002ed@2013/11/17:13:28:22.058"]000002ed@2013/11/17:13:28:22.058[/EMAIL] CSI Transaction @0x7f53250 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [65]"TI2.0_0:0/Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0"
 2013-11-17 08:28:22, Info                  CBS    Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-1_neutral_LDR
2013-11-17 08:28:22, Info                  CBS    Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-1_neutral_LDR, PinDeployment: amd64_625642d59cbd9b78ffba236f626be496_31bf3856ad364e35_7.1.7601.22313_none_43c43e854bf640c0
2013-11-17 08:28:22, Info                  CBS    Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-2_neutral_GDR
2013-11-17 08:28:22, Info                  CBS    Exec: Staging Package: Package_1_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0, Update: 2834140-2_neutral_GDR, PinDeployment: amd64_dd5c53d2d61e65bdc0f21e7393b667dc_31bf3856ad364e35_7.1.7601.18142_none_b02a69e93371bf1f
2013-11-17 08:28:22, Info                  CBS    Exec: This is a PSF Package.  Job has been saved and we are returning to client.
2013-11-17 08:28:22, Info                  CSI    [EMAIL="000002ee@2013/11/17:13:28:22.105"]000002ee@2013/11/17:13:28:22.105[/EMAIL] CSI Transaction @0x7f53250 destroyed
2013-11-17 08:28:22, Info                  CBS    Exec: DPX job state saved for one or more packages, aborting the staging and install of execution.
2013-11-17 08:28:22, Info                  CBS    Perf: Stage chain complete.
2013-11-17 08:28:22, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED]
[B]2013-11-17 08:28:22, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f0816 - CBS_E_DPX_JOB_STATE_SAVED][/B]

I'll post a fix for the file error later - please post the CheckSUR data.

 

[kwall]

I am uploading a batch images from my updates history since no errors are shown on the windows update screen. A common occurrence I notice that the batch of failed updates I revived from November 15, 2013 had an error detail of Code80073712 and from November 16, 2013 a batch had an error detail of 80070002. The November 16 batch code switched to code80070003 at "Security Updates for Windows 7 64x based systems (KB2631813).