Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 01/07/17 12:40:10 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\010717-22187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x124 (0x0, 0xFFFF850CB919C028, 0xF2000000, 0x10014)
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 Fri 01/06/17 11:42:55 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\010617-25171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0x500000008, 0x2, 0x0, 0xFFFFF8026CCAE9A1)
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.
On Fri 01/06/17 11:36:43 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\010617-18562-01.dmp
This was probably caused by the following module: hal.dll (hal+0x36811)
Bugcheck code: 0x9C (0x0, 0xFFFFCE009F046760, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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 Fri 01/06/17 7:44:10 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\010617-22531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xD1 (0xFFFFFFFFFFD01150, 0xFF, 0x0, 0xFFFFFFFFFFD01150)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 01/06/17 12:07:47 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\010617-21828-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x7C6F6)
Bugcheck code: 0x10D (0x5, 0x2EFB4BFE8FD8, 0x1001, 0xFFFFD104B36CE010)
Error: WDF_VIOLATION
file path: C:\WINDOWS\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
Bug check description: This indicates that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 5 are included in this report.
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.
Colif :
I can't read dumps but this program can. Can you download and run whocrashed:
http://www.resplendence.com/whocrashed
it will create a summary of the errors and may show the cause - we can look at that while you wait for people who can read dumps
Copy/paste results here and I see what I can do
Facebook
Twitter
Instagram