Colif :
1. Can you follow option one here:
http://www.tenforums.com/tutorials/5560-bsod-minidump-configure-create-windows-10-a.html
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
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 
2. while we wait on someone to read those, can you download and run
who crashed - it will give us a glimpse of the errors you getting and might help us solve them
Copy/paste summary in here and I see what I can do
3. try running the free version of http://www.memtest86.com/ on your memory sticks, one at a time. Any errors are too many. it makes a bootable USB so don't need to run it in windows
memory management BSOD can be ram, hdd or drivers.
Sorry this has taken so long to reply school has gone very busy. Whocrashed gave me this:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 4/26/2017 7:35:46 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\042617-30062-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x411, 0xFFFF94811C976458, 0xB4E00003CE788884, 0xFFFF94801C976458)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 4/26/2017 7:35:46 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0x44A9F)
Bugcheck code: 0x1A (0x411, 0xFFFF94811C976458, 0xB4E00003CE788884, 0xFFFF94801C976458)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 4/13/2017 6:56:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041317-38046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x1A (0x31, 0xFFFF8A848A934260, 0xFFFFB200AF01C000, 0xFFFFC88C57019D47)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 3/15/2017 1:56:12 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\031517-27234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x48, 0x2, 0x1, 0xFFFFF802BF0690CE)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
So it looks like its windows drivers messing stuff up. I would love for it to not be a hardware issue. What website should I put the mem dumps?
Facebook
Twitter
Instagram