Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 24.12.2017 05:33:27 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122417-34078-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x139 (0x3, 0xFFFFFA883887D6E0, 0xFFFFFA883887D638, 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 Sat 23.12.2017 17:38:05 your computer crashed
crash dump file: C:\WINDOWS\Minidump\122317-33046-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x1640E0)
Bugcheck code: 0x4E (0x99, 0x11D14F, 0x2, 0xA00001000019B50)
Error:
PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.
Conclusion
2 crash dumps have been found and analyzed. 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.