Three BSODs within the past few days

Code:

BugCheck A, {0, 2, 1, fffff80001ccc4ff}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+ef )

There seems to be quite a few driver issues, including your graphics card driver again, most of the drivers belong to your motherboard, if the system continues to crash after updating all these drivers, then I believe you either have a PSU problem or a bad motherboard; the nVidia chipset is known to cause a few problems.

Code:

start             end                 module name
fffff880`07d54000 fffff880`07d78000   asmthub3 T (no symbols)           
    Loaded symbol image file: asmthub3.sys
    Image path: asmthub3.sys
    Image name: asmthub3.sys
    Timestamp:        Wed May 02 17:23:54 2012 (4FA15F9A)
    CheckSum:         0002E78B
    ImageSize:        00024000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver belongs to your ASMedia USB 3.0 Hub driver, please update it from here - ASMedia Technology Inc. ????

Code:

start             end                 module name
fffff880`07a27000 fffff880`07d53180   RTKVHD64 T (no symbols)           
    Loaded symbol image file: RTKVHD64.sys
    Image path: RTKVHD64.sys
    Image name: RTKVHD64.sys
    Timestamp:        Tue Feb 26 12:38:48 2013 (512CACD8)
    CheckSum:         00331825
    ImageSize:        0032C180
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver belongs to your Realtek High Definition Audio Function Driver, it is most likely to the latest version, but check for any updates from here - Realtek

Code:

start             end                 module name
fffff880`068cc000 fffff880`068ff000   nvhda64v T (no symbols)           
    Loaded symbol image file: nvhda64v.sys
    Image path: nvhda64v.sys
    Image name: nvhda64v.sys
    Timestamp:        Mon Feb 25 05:27:35 2013 (512AF647)
    CheckSum:         00036E9A
    ImageSize:        00033000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver belongs to your nVidia HDMI Audio Device (nForce chipset driver), it is most likely the latest driver, please check for updates from here - Drivers - Download NVIDIA Drivers

Code:

start             end                 module name
fffff880`05f67000 fffff880`05fcc000   asmtxhci T (no symbols)           
    Loaded symbol image file: asmtxhci.sys
    Image path: asmtxhci.sys
    Image name: asmtxhci.sys
    Timestamp:        Wed May 02 17:23:42 2012 (4FA15F8E)
    CheckSum:         0006360D
    ImageSize:        00065000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver belongs to your Asmedia USB 3.0 driver.

Code:

start             end                 module name
fffff880`02838000 fffff880`02879000   truecrypt T (no symbols)           
    Loaded symbol image file: truecrypt.sys
    Image path: truecrypt.sys
    Image name: truecrypt.sys
    Timestamp:        Tue Feb 07 09:09:36 2012 (4F30EA50)
    CheckSum:         00042EF4
    ImageSize:        00041000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

This driver belongs to your TrueCrypt program, please update from here - TrueCrypt - Downloads

If you followed the steps to get a perfect baseline Clean Reinstall then you have not changed out any drivers other than those given when you ran all rounds of Important and Optional Windows Updates, after enabling Automatically deliver drivers via Windows Update (Step 3).

Now however Harry has identified drivers that are not working correctly, so it is okay to import the latest driver from the Support Downloads webpage for each device he identified.

If you didn't follow the Best Practices for reinstall and already changed out those drivers from the ones Win7 wants, then I would do the reinstall over correctly this time.

It was the same Stop 0xA BSOD as before, but with only the nVidia graphics card driver being blamed this time.

Thanks for the recap, you've tested everything and performed hardware swaps, therefore I feel it's most likely a bad motherboard.

Alright, I'll prepare it to be shipped to MSI for RMA on Monday. I'll report back with my results in a month (or whenever they get the board back to me).

Thank you so much, all of your help means SO MUCH to me!

Very welcome, glad to help and hopefully you will say everything has been solved

Got the mobo back yesterday, and the second time it rebooted it crashed again. It's now crashed more times in the last 24 hours than it had before I sent it in. 7 dumps are in the attached zip file.

I've also attached the chkdsk /r report from the run I just did overnight on my HDD. Haven't run one on my SSD.

I also found this line in my event viewer logs; it's the only error related to the time since I got the mobo back.

Code:

The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.

Also, several of the times they occurred the screen said the problem was Ntfs.sys, but the dumps don't reflect that.

I've seen that Event Log error before, it can either refer to the firmware for your SSD or the BIOS.

Check for any BIOS updates:

Code:

3: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=2237]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = V1.11
BiosReleaseDate = 10/31/2012
SystemManufacturer = MSI
SystemProductName = MS-7693
SystemFamily = To be filled by O.E.M.
SystemVersion = 2.0
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = MSI
BaseBoardProduct = 970A-G46 (MS-7693)
BaseBoardVersion = 2.0

Since you have a SSD:

writhziden said:

If you have an SSD, make sure the following are up to date:

• SSD firmware
• BIOS Version
• Chipset Drivers
• Hard disk controller drivers/SATA drivers
• If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

Code:

BugCheck D1, {fffffffffffdb610, 2, 8, fffffffffffdb610}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0487f000 fffff880`05373000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jul 26 03:41:39 2013 (51F1E1E3)
    CheckSum:         00ACD06A
    ImageSize:        00AF4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Ensure you have the latest WHQL driver from here - NVIDIA Driver Downloads - Advanced Search

Version: 320.49
Release Date for Desktops and Notebooks : July 1st 2013
In Device Manager: 9.18.13.2049

Code:

0: kd> lmvm Netwsw00
start             end                 module name
fffff880`05631000 fffff880`06183000   Netwsw00 T (no symbols)           
    Loaded symbol image file: Netwsw00.sys
    Image path: \SystemRoot\system32\DRIVERS\Netwsw00.sys
    Image name: Netwsw00.sys
    Timestamp:        Thu Apr 18 15:31:35 2013 (517003C7)
    CheckSum:         00AFF8E7
    ImageSize:        00B52000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your Intel® Wireless WiFi Link Adapter driver seems to be a possible cause, please check for any potential updates from here - Intel Customer Support

Code:

CHKDSK is verifying file data (stage 4 of 5)...
Windows replaced bad clusters in file 37576
of name \$RECYCLE.BIN\S-1-5-~1\$RJ4BGE5\steamapps\common\Portal 2\platform\shaders\fxc\spritecard_ps20b.vcs.
Windows replaced bad clusters in file 37771
of name \$RECYCLE.BIN\S-1-5-~1\$RJ4BGE5\steamapps\common\Portal 2\portal2\media\laser_danger_horiz.bik.
Windows replaced bad clusters in file 58737
of name \$RECYCLE.BIN\S-1-5-18\$R9U1GKG\NVIDIA Corporation\Installer2\Display.3DVision.0\nvst3CHT.chm.
Windows replaced bad clusters in file 58738
of name \$RECYCLE.BIN\S-1-5-18\$R9U1GKG\NVIDIA Corporation\Installer2\Display.3DVision.0\nvst3CSY.chm.
Windows replaced bad clusters in file 58748
of name \$RECYCLE.BIN\S-1-5-18\$R9U1GKG\NVIDIA Corporation\Installer2\Display.3DVision.0\nvst3HUN.chm.
Windows replaced bad clusters in file 58754
of name \$RECYCLE.BIN\S-1-5-18\$R9U1GKG\NVIDIA Corporation\Installer2\Display.3DVision.0\nvst3PLK.chm.
Windows replaced bad clusters in file 112945
of name \$RECYCLE.BIN\S-1-5-~1\$RJ4BGE5\config\overlayhtmlcache\f_000157.
Windows replaced bad clusters in file 116706
of name \DOCUME~1\Public\100OLYMP\PC080050.AVI.

Driver Verifier:

Code:

BugCheck D5, {fffff980226a4fb8, 1, fffff880049fb31b, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+1b231b )

Code:

Usual causes:  Device driver

This bugcheck indicates that the nVidia graphics card driver, has referenced and then written to a memory address which has already been freed.

Code:

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`04849000 fffff880`0532e000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 10:06:16 2013 (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Are you able to boot into Safe Mode? I'll remove the driver completely, and then see if Windows still crashes.

Code:

BugCheck 1E, {ffffffffc0000096, fffff8800c9e6912, 0, 0}

*** WARNING: Unable to verify timestamp for cpudrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpudrv64.sys
Probably caused by : cpudrv64.sys ( cpudrv64+1912 )

Code:

Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS

Code:

0: kd> lmvm cpudrv64
start             end                 module name
fffff880`0c9e5000 fffff880`0c9ed000   cpudrv64 T (no symbols)           
    Loaded symbol image file: cpudrv64.sys
    Image path: \??\C:\Program Files (x86)\SystemRequirementsLab\cpudrv64.sys
    Image name: cpudrv64.sys
    Timestamp:        Tue Aug 11 17:39:13 2009 (4A819EB1)
    CheckSum:         0000D622
    ImageSize:        00008000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

It seems to part of the SystemRequirementsLabs program, which I've seen cause problems before, either check for a later version of the program or remove the program completely.

Code:

BugCheck A, {b4c0, 2, 1, fffff800032e64ff}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+ef )

Code:

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Code:

2: kd> lmvm amd_sata
start             end                 module name
fffff880`00c6c000 fffff880`00c83000   amd_sata T (no symbols)           
    Loaded symbol image file: amd_sata.sys
    Image path: \SystemRoot\system32\DRIVERS\amd_sata.sys
    Image name: amd_sata.sys
    Timestamp:        Fri Apr 15 19:37:14 2011 (4DA8905A)
    CheckSum:         0001BF2D
    ImageSize:        00017000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Have you checked for any driver updates for your AMD SATA ACHI driver? I would firstly check the motherboard support page and then the AMD support page.

Most of your dump files seem to point to driver related issues, for example threads waiting upon the completion of IRPs, which don't get completed or not completed in time.