Windows 10: Random BSOD daily/every other day.(ntkrnlmp.exe , ntoskrnl.exe)

Windows version 1909 (OS Build 18363.535)

Hey there. I've been getting random BSODs since I bought this PC from someone. It was originally reset using the windows 'reset this pc' function. I've since done a fresh install of windows 10 to try and remedy the issue but after just one day I got this error again. It's seemingly random. Earlier it crashed while i was playing World of Warcraft. It has crashed before when I was simply browsing in the internet.

The BSOD always shows this "Error: CRITICAL_STRUCTURE_CORRUPTION"

I've attached a file I got from V2 log creator.

:)

 

BSOD ntoskrnl..exe+1b35e0

Hi, KirbyBakken

My name is Maritza and I am an Independent Advisor. I would be happy to help you today.

Check this link, I hope it helps

https://www.thewindowsclub.com/ntoskrnl-exe-hig...

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised
on the site before you decide to download and install it.

Let us know if these steps help you to resolve the issue.

 

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 - Windows 10 Help 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.