Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 27/02/2017 14:04:15 your computer crashed
crash dump file: C:\WINDOWS\Minidump\022717-23515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0) 
Bugcheck code: 0x50 (0xFFFFF8031481EC80, 0x10, 0xFFFFF8031481EC80, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 20/02/2017 20:23:42 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFEDC300F6FF78) 
Bugcheck code: 0x1A (0x3451, 0xFFFFEDC300F6FF78, 0xFFFFAE81FAD3C080, 0x0)
Error: MEMORY_MANAGEMENT
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). 
A third party driver was identified as the probable root cause of this system error. 
Google query: MEMORY_MANAGEMENT



On Tue 31/01/2017 17:01:19 your computer crashed
crash dump file: C:\WINDOWS\Minidump\013117-41703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0) 
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFCE0095843180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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.