Colif :
So as to not waste anymore time tomorrow (not that I am saying memtest is a waste, but so you don't have to wait too much longer). 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 else with right software to read them will help you fix it
The above assumes you on win 10? otherwise you can find similar steps here:
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
the dump files will reveal a lot more than who crashed but I can't read dumps and who crashed allows those of us who can't to at least help;
Crash Dump Analysis
memtest ran for 8 consecutive passes, so I was able to run whocrashed. Here's the summary
Also, I ran MSI live update again and it said that the only motherboard driver I don't have installed/updated is Realtek HD Audio Drivers. So I will install that but I don't think that is the cause of my problems.
https://drive.google.com/open?id=0B1ID422_ty5hT05jaDhuNm9INUU <- 1st one in the minidump folder
https://drive.google.com/open?id=0B1ID422_ty5hYU5IWE5jNzVZMGc <- 2nd one in the minidump folder
https://drive.google.com/open?id=0B1ID422_ty5hNXpaOUcwWXd5NVE <- 3rd one in the minidump folder
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 25/01/2017 7:33:31 AM your computer crashed
crash dump file: C:\Windows\Minidump\012517-8796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x18 (0x0, 0xFFFFE38823F677D0, 0x2, 0xFFFFFFFF00002DDC)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
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 25/01/2017 7:33:31 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x18 (0x0, 0xFFFFE38823F677D0, 0x2, 0xFFFFFFFF00002DDC)
Error: REFERENCE_BY_POINTER
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sun 22/01/2017 12:55:26 PM your computer crashed
crash dump file: C:\Windows\Minidump\012217-6718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x4E (0x9A, 0x44F797, 0x2, 0x0)
Error: PFN_LIST_CORRUPT
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 the page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 20/01/2017 1:43:29 PM your computer crashed
crash dump file: C:\Windows\Minidump\012017-8671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xFFFFF803BCC37D90, 0x2, 0x0, 0xFFFFF803BC151AEA)
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.