Colif :
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
if it just blames ntoskrnl for everything, 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
WHEA errors are hardware though can sometimes be drivers as well. Updating bios can fix them sometimes.
The rest aren't so clearly defined. the dumps or whocrashed may show us more.
turn off any overclocks, remove overclocking software as well.
So I had used WhoCrashed and it gave me those error messages that I named previously. I'll also upload my minidump files.
Here's the link for the minidumps:
https://1drv.ms/f/s!Arrd5tLtuL1AgotXITsp13xL56lE0w
The whole link won't underline it blue so you need to just highlight it and copy and paste.
Here is the summary of WhoCrashed:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 4/18/2017 5:59:27 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-14250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6B3827)
Bugcheck code: 0x124 (0x0, 0xFFFF818BF11E68F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. 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 Tue 4/18/2017 4:26:56 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-14265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x109 (0xA3A00ED9854D250E, 0xB3B71B5FD7CE1F20, 0x6, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 Tue 4/18/2017 4:26:56 PM 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: 0x109 (0xA3A00ED9854D250E, 0xB3B71B5FD7CE1F20, 0x6, 0x18)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 Tue 4/18/2017 1:18:03 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041817-10687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1F1958)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801E4A7B958, 0xFFFFDF0005DFD128, 0xFFFFDF0005DFC950)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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.
On Mon 4/17/2017 10:54:47 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\041717-14906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0x139 (0x3, 0xFFFF9600D9BF5720, 0xFFFF9600D9BF5678, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Facebook
Twitter
Instagram