Colif :
Exception code c0000005 is the code for an access violation. That means that your program is accessing (either reading or writing) a memory address to which it does not have rights -
https://stackoverflow.com/questions/17168982/exception-error-c0000005-in-vc
Do you always get a BSOD?
Can you follow option one on the following link -
here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD
that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and
someone with right software to read them will help you fix it 
This is the dmp file I have on what's going on... Also I apologize it took so long to reply.. but since I posted this I have tried a new set of ram and a new mobo and hard drive.. also a amd graphics card and not a nvidia.. .... and fresh installs of windows 10 3 times.. always the same result.. can the CPU itself be doing this?.. i've built for years and never ran into a faulty cpu..however its literally the only thing i can't been able to swap
Dump File : 062118-4250-01.dmp
Crash Time : 6/21/2018 3:54:44 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 00000000`00000008
Parameter 2 : ffff9981`c48b0050
Parameter 3 : 0000007f`775fd658
Parameter 4 : 0000274e`523ac045
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062118-4250-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 17134
Dump File Size : 393,234
Dump File Time : 6/21/2018 3:55:16 PM
==================================================
==================================================
Dump File : 062118-4156-01.dmp
Crash Time : 6/21/2018 3:57:41 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x1000007f
Parameter 1 : 00000000`00000008
Parameter 2 : ffffaf00`8f8ee050
Parameter 3 : 0000002a`973fd4b8
Parameter 4 : 00006020`820f0d31
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\062118-4156-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 17134
Dump File Size : 383,466
Dump File Time : 6/21/2018 3:59:29 PM
==================================================
========THIS IS WINDBG INFO========
Microsoft (R) Windows Debugger Version 10.0.17674.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\062118-4250-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`868a8000 PsLoadedModuleList = 0xfffff803`86c621f0
Debug session time: Thu Jun 21 15:54:44.374 2018 (UTC - 4:00)
System Uptime: 0 days 0:03:26.243
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, ffff9981c48b0050, 7f775fd658, 274e523ac045}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0000274e`523ac045 d9f8 fprem
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffff9981c48b0050
Arg3: 0000007f775fd658
Arg4: 0000274e523ac045
Debugging Details:
------------------
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.17134.112 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.
SYSTEM_PRODUCT_NAME: H270-Gaming 3
SYSTEM_SKU: Default string
SYSTEM_VERSION: Default string
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: F8
BIOS_DATE: 11/08/2017
BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.
BASEBOARD_PRODUCT: H270-Gaming 3
BASEBOARD_VERSION: x.x
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
DUMP_TYPE: 2
BUGCHECK_P1: 8
BUGCHECK_P2: ffff9981c48b0050
BUGCHECK_P3: 7f775fd658
BUGCHECK_P4: 274e523ac045
BUGCHECK_STR: 0x7f_8
CPU_COUNT: 8
CPU_MHZ: 1068
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 70'00000000 (cache) 70'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-LHTG8H3
ANALYSIS_SESSION_TIME: 06-21-2018 23:45:40.0762
ANALYSIS_VERSION: 10.0.17674.1000 amd64fre
LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000274e523ac045
STACK_TEXT:
0000007f`775fd658 00000000`00000000 : 000001da`4ad5d010 0000007f`775fd7d8 0000007f`775fd680 00000002`00000000 : 0x0000274e`523ac045
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID: INVALID_KERNEL_CONTEXT_0x7f_8
DEFAULT_BUCKET_ID: INVALID_KERNEL_CONTEXT_0x7f_8
PRIMARY_PROBLEM_CLASS: INVALID_KERNEL_CONTEXT_0x7f_8
FAILURE_BUCKET_ID: INVALID_KERNEL_CONTEXT_0x7f_8
TARGET_TIME: 2018-06-21T19:54:44.000Z
OSBUILD: 17134
OSSERVICEPACK: 112
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-06-08 05:00:00
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.17134.112
ANALYSIS_SESSION_ELAPSED_TIME: 37d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:invalid_kernel_context_0x7f_8
FAILURE_ID_HASH: {7dec4a1f-e7bf-6cb5-680a-3c5c14a52b06}
Followup: MachineOwner
---------
Facebook
Twitter
Instagram