BSOD Playing Civ V, Ran sfc /SCANNOW cannot repair some CBS.log Files

Looks like Avast! is causing the problem at the moment.

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\PUDDLEJUMPER-Mon_12_29_2014_145337_27\122914-6864-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.22736.amd64fre.win7sp1_ldr.140706-1507
Machine Name:
Kernel base = 0xfffff800`02a4f000 PsLoadedModuleList = 0xfffff800`02c92890
Debug session time: Mon Dec 29 20:15:55.688 2014 (UTC + 6:00)
System Uptime: 4 days 19:28:23.859
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa800c6d5960, 6d00630066006d, 2a7393139373326}

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa800c6d5960, the pool entry being checked.
Arg3: 006d00630066006d, the read back flink freelist value (should be the same as 2).
Arg4: 02a7393139373326, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  NvNetworkServi

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002bf74b3 to fffff80002ac2bc0

STACK_TEXT:  
fffff880`02cfca68 fffff800`02bf74b3 : 00000000`00000019 00000000`00000003 fffffa80`0c6d5960 006d0063`0066006d : nt!KeBugCheckEx
fffff880`02cfca70 fffff880`013a7819 : fffffa80`00000004 fffffa80`5feda010 fffffa80`5f4fba00 fffffa80`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`02cfcb60 fffff880`013b7692 : fffffa80`0cba1cf0 00000000`00000002 fffffa80`0cba1cf0 fffff880`02cfcd80 : fltmgr!FltpReallocNameControl+0x39
fffff880`02cfcb90 fffff880`013a575b : 00000000`00000000 fffffa80`0cba1cf0 00000000`00000000 fffffa80`103158f8 : fltmgr!FltpGetFileNameFromFileObject+0x1f2
fffff880`02cfcc20 fffff880`0139ffe0 : fffff880`01b65418 fffff880`01a8cf07 fffff880`02cfcd80 fffffa80`5b9c44c0 : fltmgr! ?? ::NNGAKEGL::`string'+0x171b
fffff880`02cfcc50 fffff880`0139fead : fffffa80`21c4b600 fffffa80`11ca66d0 fffffa80`5f4fb9b8 fffffa80`5b849b08 : fltmgr!FltpCallOpenedFileNameHandler+0x20
fffff880`02cfcc90 fffff880`0138bb9d : c00000bb`00000000 00000000`00000000 00000000`00000000 fffffa80`103158f8 : fltmgr!FltpCreateFileNameInformation+0x17d
fffff880`02cfccf0 fffff880`01385bf6 : fffffa80`0ca38080 00000000`00000000 fffffa80`103158f8 00000000`00000000 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`02cfcd30 fffff880`0138cb44 : fffffa80`0f521700 00000000`00000000 00000000`00000000 00000000`00000102 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`02cfcdb0 fffff880`06c11bb5 : fffffa80`0cba1cf0 fffffa80`5b84b6a0 00000000`00000000 fffffa80`103158f8 : fltmgr!FltGetFileNameInformation+0x184
fffff880`02cfce40 fffff880`013a0035 : fffffa80`5b84b6a0 00000000`00002706 00000000`00000000 00000000`000008fe : luafv!LuafvGenerateFileName+0x6d
fffff880`02cfce70 fffff880`0139fead : fffffa80`0f219000 fffffa80`103158f8 fffffa80`5b84b6a0 00000000`00000001 : fltmgr!FltpCallOpenedFileNameHandler+0x75
fffff880`02cfceb0 fffff880`0138bb9d : c00000bb`08fe0000 00000000`00000000 fffffa80`119ecfb0 fffffa80`119ec4d0 : fltmgr!FltpCreateFileNameInformation+0x17d
fffff880`02cfcf10 fffff880`01385bf6 : fffffa80`0ca38080 fffffa80`119ec4c0 fffffa80`103158f8 00000000`00000000 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`02cfcf50 fffff880`0138cb44 : fffffa80`0f521700 00000000`00000000 fffffa80`119ec4c0 00000000`00000102 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`02cfcfd0 fffff880`046e1775 : fffffa80`5b84b6a0 fffffa80`5ff9fc20 00000000`00000000 00000000`00000000 : fltmgr!FltGetFileNameInformation+0x184
fffff880`02cfd060 fffffa80`5b84b6a0 : fffffa80`5ff9fc20 00000000`00000000 00000000`00000000 fffffa80`0f097f40 : aswSnx+0x3775
fffff880`02cfd068 fffffa80`5ff9fc20 : 00000000`00000000 00000000`00000000 fffffa80`0f097f40 00000000`00000000 : 0xfffffa80`5b84b6a0
fffff880`02cfd070 00000000`00000000 : 00000000`00000000 fffffa80`0f097f40 00000000`00000000 00000000`00000000 : 0xfffffa80`5ff9fc20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+a53
fffff800`02bf74b3 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+a53

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53

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

Please uninstall it and replace with MSE.

Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other internet security software. Malwarebytes is a great combo to MSE. They are free and lightweight.

Also uninstall your existing Antivirus software before you install MSE.

Good and Free system security combination.

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

 Clean boot

• Troubleshoot Application Conflicts by Performing a Clean Startup

Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:

• How to Change, Add, or Remove Startup Programs in Windows 7

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow

Full tutorial here:

• SFC /SCANNOW Command - System File Checker

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

 Hard Drive Diagnostics

• Double click and open my computer.
• Right click on desired drive and hit properties.
• Click on tools tab and Check now.

Read complete instructions on the tutorial: Disk Check

Other Tests:

 

• Upload a screenshot of your hard disk using Crystal Disk Info.
• Make a hard drive test from the hard drive manufacturers website.
• Test your Hard Drive with SeaTools.

Temp Monitoring

Check for heating issues using Speccy or HWMonitor.

• Speccy - System Information - Free Download
• HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Upload a screen shot with either of the tools: Screenshots and Files - Upload and Post in Seven Forums

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.