Told you it might be a bit premature.
Unfortunately I'm not seeing anything frightening with you latest dump. Looks like the only old driver still hanging around out there is hamachi and of course you already know that.
This one:
Code:
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
[U][B]BugCheck 24, {1904fb, fffff8800713e3e8, fffff8800713dc40, fffff880010b2290}[/B][/U]
[U][B]Probably caused by : Ntfs.sys[/B][/U] ( Ntfs!NtfsExtendedCompleteRequestInternal+114 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[U][B]NTFS_FILE_SYSTEM (24)[/B][/U]
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800713e3e8
Arg3: fffff8800713dc40
Arg4: fffff880010b2290
Debugging Details:
------------------
EXCEPTION_RECORD: fffff8800713e3e8 -- (.exr 0xfffff8800713e3e8)
ExceptionAddress: fffff880010b2290 (fltmgr!FltpPurgeVolumeNameCache+0x0000000000000050)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: ffffffffffffffff
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: fffff8800713dc40 -- (.cxr 0xfffff8800713dc40)
rax=83485708245c8948 rbx=fffff88004bd2160 rcx=fffffa80062e0518
rdx=fffff88004bd2101 rsi=0000000000000000 rdi=fffffa80062e0010
rip=fffff880010b2290 rsp=fffff8800713e620 rbp=83485708245c8918
r8=ffffffffffffffff r9=ffffffffffffffff r10=fffff80002e59000
r11=fffff8a003b6d208 r12=fffffa80062e0580 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
fltmgr!FltpPurgeVolumeNameCache+0x50:
fffff880`010b2290 f083454401 lock add dword ptr [rbp+44h],1 ss:0018:83485708`245c895c=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: NULL_DEREFERENCE
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: ffffffffffffffff
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003108100
0000000000000000
FOLLOWUP_IP:
Ntfs!NtfsExtendedCompleteRequestInternal+114
fffff880`01255e84 488b5c2450 mov rbx,qword ptr [rsp+50h]
FAULTING_IP:
fltmgr!FltpPurgeVolumeNameCache+50
fffff880`010b2290 f083454401 lock add dword ptr [rbp+44h],1
BUGCHECK_STR: 0x24
LAST_CONTROL_TRANSFER: from fffff880010a9a10 to fffff880010b2290
STACK_TEXT:
fffff880`0713e620 fffff880`010a9a10 : fffffa80`05a10740 fffffa80`062e0010 00000000`00000000 fffffa80`078b86c0 : fltmgr!FltpPurgeVolumeNameCache+0x50
fffff880`0713e660 fffff880`010a4b9b : fffffa80`062e0010 00000000`00000000 fffffa80`078b86c0 00000000`00000000 : fltmgr! ?? ::NNGAKEGL::`string'+0x1a04
fffff880`0713e6a0 fffff880`01084eca : fffffa80`07951010 fffffa80`061259e0 00000000`00000000 0070006d`0075004a : fltmgr!FltpReinstateNameCachingAllFrames+0x4b
fffff880`0713e6d0 fffff800`02ed9021 : 00000000`00000000 fffff800`031d1c81 00000000`00000000 fffff880`01084132 : fltmgr!FltpPassThroughCompletion+0x8a
fffff880`0713e710 fffff880`01255e84 : fffffa80`08376560 00000000`00000001 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`0713e800 fffff880`012e220c : fffff8a0`10d2d140 fffffa80`0628a180 00000000`00000000 00000000`00000701 : Ntfs!NtfsExtendedCompleteRequestInternal+0x114
fffff880`0713e840 fffff880`01253574 : fffffa80`08376560 fffffa80`081dd010 fffff880`0713e901 fffff880`0713e900 : Ntfs!NtfsCommonSetInformation+0xef3
fffff880`0713e920 fffff880`01081bcf : fffffa80`081dd3b0 fffffa80`081dd010 fffffa80`08376560 fffff880`0713e948 : Ntfs!NtfsFsdSetInformation+0x11c
fffff880`0713e9a0 fffff880`010806df : fffffa80`061259e0 fffffa80`081dd010 fffffa80`06125900 fffffa80`081dd010 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0713ea30 fffff800`031b5063 : 00000000`000000b4 fffff880`0713eca0 00000000`00000000 fffffa80`0801d230 : fltmgr!FltpDispatch+0xcf
fffff880`0713ea90 fffff800`02ed4ed3 : 00000000`00000c38 fffffa80`0573b900 00000000`0334e5f8 fffff800`000000b4 : nt!NtSetInformationFile+0x91f
fffff880`0713ebb0 00000000`776f158a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0334e5d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776f158a
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: Ntfs!NtfsExtendedCompleteRequestInternal+114
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b
STACK_COMMAND: .cxr 0xfffff8800713dc40 ; kb
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114
BUCKET_ID: X64_0x24_Ntfs!NtfsExtendedCompleteRequestInternal+114
Followup: MachineOwner
Looks more like an issue with your hard disk;
Likely causes: Disk corruption, insufficient physical memory, device driver, disk or drive controller failing or failure.
So we should probably chase down any potential disk issues.
Open an elevated command prompt and type
chkdsk C: /R
hit enter
answer yes "Y" to the prompt
and reboot
Let it finish all five stages and see what that produces in the way of worth while information if any. If you miss the report at the end you can examine the log file in Event Viewer->Windows Logs->Application
Let us know what that produces.
And probably next up you'll likely want to
Download Memtest86+
from this location here. Burn the ISO to a CD and boot the computer from the CD.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Test RAM sticks individually. When you find a good one then test it in all slots. Post back with the results.
See
this Guide to using Memtest 86+
Additionally since that particular game seems to really stess the CPU you may want to look into increasing the associated voltage to help support the added burden (vcore or VccIO) you may need to check your motherboard documentation regarding that particular task or perhaps see if there might be a specific support forum for your individual board or board manufacturer where you might get some information regarding the process and its' associated Pro's and Con's. Typically a bump in Vcore will likely result in a slight increase in temps which should be monitored to guard against overheating and possible damage.
