Windows 10: ntkrnlmp.exe based BSOD

Hi all. I've been having random BSOD crashes on my PC for some time now. Most recently, I've re-installed the entire OS from scratch and the issue still remains. This leads me to think that the issue may be hardware related (faulty RAM?). I'm posting the results of my crash dump file analysis below in hopes someone may be able to shed some more light on it.


I uploaded log files on

https://1drv.ms/u/s!AsMes1KfmnEmi3RIl4c7z79Vcm4c



Thanks!

:)

 

Multiple BSODs caused by ntkrnlmp.exe in Windows 10

Also, i not that to geeky to comprehend what was written in the .DMP file, you can also check this:

BSOD - ntoskrnl.exe & ntkrnlmp.exe Solved - Windows 10 Forums

it says that it regards the BIOS. . . . ?

 

BSOD's have returned! [ntkrnlmp, ntoskrnl] HYPERVISOR error


Hello all, its nice to be back!
I've had a couple threads in the forum which regard my issues with BSODs the last being around 5 months ago from now and the other a bit longer. Though generally the errors have been consistent but has dipped in frequency with the help I received (thanks!) Since my last post, I have had near to no blue screens but am getting the odd few this past month, and judging by WhoCrashed, the modules which seem to cause it have been the same ever since.
In summary, here's what has been done:

I have my doubts on what may have caused the current one and here is what WhoCrashed states:

Code:

Code:

This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)  Bugcheck code: 0x20001 (0x11, 0x210CC1, 0x1003, 0xFFFFE80000231DF0) Error: HYPERVISOR_ERROR file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: The hypervisor has encountered a fatal error. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

Event 10016 error

Hi seahenting, generally BSOD's are caused by a corrupt / incompatible device driver, when ntkrnlmp is listed alone as the cause, it is very had to diagnose the underlying issue . . .