Alright, thanks for the answers so far, my motherboard is indeed GIGABYTE, a AMD GA-F2A88XM-D3H FM2+ rev 3.0 Micro ATX , I have 4gb ram (used to have 8 but one stopped working some time ago, but a replacement is on the way) and power is a Corsair CX-430W. So far I have not had any more crashes, and I disabled some start up programs and maybe that helped, but I enabled the mini-dumps and checked for logs with the program listed and will copy it here.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 02/07/2017 17:57:50 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070217-6578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x5100, 0xFFFF8B52868B5A68, 0x1, 0x1D400000800)
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 Sun 02/07/2017 15:17:37 your computer crashed
crash dump file: C:\WINDOWS\Minidump\070217-74718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x1A (0x5100, 0xFFFFCD52C10102A8, 0x40, 0x800)
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 Sun 02/07/2017 13:21:05 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF80125A64E70)
Bugcheck code: 0x7F (0x8, 0xFFFFF80125A64E70, 0xFFFF800145111000, 0xFFFFF80123CC2A9F)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
A third party driver was identified as the probable root cause of this system error.
Google query: UNEXPECTED_KERNEL_MODE_TRAP
On Fri 30/06/2017 00:56:02 your computer crashed
crash dump file: C:\WINDOWS\Minidump\063017-9015-01.dmp
This was probably caused by the following module: hal.dll (0xFFFFF802F2A20085)
Bugcheck code: 0xA (0xFFFFF7824008A200, 0xFF, 0x0, 0xFFFFF802F2A20085)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 29/06/2017 23:44:01 your computer crashed
crash dump file: C:\WINDOWS\Minidump\062917-9609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xA (0x808, 0x2, 0x1, 0xFFFFF801996422EC)
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.