System Information (local)
Computer name: DESKTOP-JRKSH9I
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: Intel Corporation, DH77EB
CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4256403456 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Fri 5/12/2017 11:52:06 AM your computer crashed
crash dump file: C:\Windows\Minidump\051217-70093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDAC33)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801A5952C33, 0xFFFFD0806509F498, 0xFFFFD0806509ECC0)
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 Fri 5/12/2017 10:30:36 AM your computer crashed
crash dump file: C:\Windows\Minidump\051217-71453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDAC33)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801C1CEEC33, 0xFFFFD7817A196498, 0xFFFFD7817A195CC0)
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 Fri 5/12/2017 8:47:46 AM your computer crashed
crash dump file: C:\Windows\Minidump\051217-68187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)
Bugcheck code: 0x139 (0x3, 0xFFFFE081F7F49700, 0xFFFFE081F7F49658, 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.
On Thu 5/11/2017 12:09:08 PM your computer crashed
crash dump file: C:\Windows\Minidump\051117-25796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802A3AE8894, 0xFFFFDC011E38BE20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 5/11/2017 10:44:50 AM your computer crashed
crash dump file: C:\Windows\Minidump\051117-29968-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDAC33)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803900E3C33, 0xFFFFA7811D157498, 0xFFFFA7811D156CC0)
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.
Conclusion
10 crash dumps have been found and analyzed. Only 5 are included in this report. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Facebook
Twitter
Instagram