Chrome was what crashed on your computer but it was driven into it by a problem with NTFS, sys, this could be a driver issue but it could also be a problem with a full or failing HDD, see info below that I have highlighted in red;
Debug session time: Mon Aug 14 13:33:49.589 2017 (UTC - 4:00)
System Uptime: 0 days 3:28:42.115
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NTFS_FILE_SYSTEM (24)
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: 00000000000c08a5
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x24
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88001215c25 to fffff80002e80980
STACK_TEXT:
fffff880`0baea578 fffff880`01215c25 : 00000000`00000024 00000000`000c08a5 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0baea580 fffff880`0123a2b5 : 00000001`00000000 00000000`00000000 00000000`00000000 000005b0`00000000 : Ntfs!NtfsPagingFileIo+0x155
fffff880`0baea680 fffff880`0116ebcf : fffffa80`0c7e0da8 fffffa80`0c7e0a50 fffffa80`08e1b010 00000000`00000000 : Ntfs! ?? ::FNODOBFM::`string'+0x64c9
fffff880`0baea730 fffff880`0116d6df : fffffa80`08b938f0 fffffa80`08b938f0 fffffa80`08b93800 fffffa80`0c7e0a50 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`0baea7c0 fffff800`02ea8f19 : fffffa80`0c7e0a50 fffffa80`06acbdc0 fffff880`0baea901 fffff800`02fffe80 : fltmgr!FltpDispatch+0xcf
fffff880`0baea820 fffff800`02ea89a1 : 00000000`00000001 00000000`00000001 fffffa80`06acbdc0 fffffa80`06acbd70 : nt!IoPageRead+0x2a9
fffff880`0baea8b0 fffff800`02e8ed1a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000231`55f80005 : nt!MiIssueHardFault+0x255
fffff880`0baea980 fffff800`02e7eaae : 00000000`00000001 00000231`55f80018 00000000`0030d901 00000000`011694e0 : nt!MmAccessFault+0x146a
fffff880`0baeaae0 000007fe`d3ec9e5c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0030da10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`d3ec9e5c
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsPagingFileIo+155
fffff880`01215c25 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Ntfs!NtfsPagingFileIo+155
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 593ab68d
FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155
BUCKET_ID: X64_0x24_Ntfs!NtfsPagingFileIo+155
Followup: MachineOwner
Download then run Speccy (free) and post the resultant url for us, details
here, this will provide us with information about your computer hardware + any software that you have installed that may explain the present issue/s.