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:

• Lowered RAM frequency multiple times
• Passed memtest86+ with 10 passes
• Ran Driver Verifier with no issues
• Clean installed Windows
• Removed AMD/ATI Graphic Drivers via DDU and partial reinstall without Catalyst Control Centre

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

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.

Rule 4
No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc) - it is forum policy that no help shall be given to people who knowingly steal software or services.


One of the main reasons for this is that the act of pirating the software will inevitably change the working of the software and make investigation and repair impossible. Please install a legitimate copy of the software and if you are still experiencing the issue we will be pleased to assist - No further assistance will be provided until we are satisfied that the software is genuine.




Open administrative command prompt and type or copy and pste: slmgr /dlv

Post an image into the thread.

If you uninstall all pirated software including Microsoft Office you would be able to comply with rule #4.

First off, huge apologies! I've tried jumping through some hoops to revert it back to its unlicensed state and have attached the slmgr.vbs /dlv output. Also, with regards to other product such as office, I have not pirated any of them and have provided a picture showing its "Expiration" notification - not been activated.

Genuine_Office.txt:

1. Open an elevated command prompt (cmd).
2. In the elevated command prompt, copy & paste the command below, and press Enter:

Code:

for /f "delims=|" %a in ('dir /B /S C:\*ospp.vbs') do cscript "%a" /dstatus > "%userprofile%\Desktop\Genuine_Office.txt"

zip Genuine_Office.txt (you find it on Desktop) and upload please.

Attached!

Hi,
this is from the Genuine_Office.txt:

Code:

PRODUCT ID: 00202-50481-78829-AA161
SKU ID: 149dbce7-a48e-44db-8364-a53386cd4580
LICENSE NAME: Office 16, Office16O365ProPlusR_Subscription1 edition
LICENSE DESCRIPTION: Office 16, TIMEBASED_SUB channel
BETA EXPIRATION: 01/01/1601
LICENSE STATUS:  ---OOB_GRACE--- 
ERROR CODE: 0x4004F00C
ERROR DESCRIPTION: The Software Licensing Service reported that the application is running within the valid grace period.
REMAINING GRACE: 9 days  (13280 minute(s) before expiring)
Last 5 characters of installed product key:

I dont know much aber Office 365 licensing but for me it looks okay.

But anyway

Theres a tool which is used to bypass the activation of microsoft products. If you are sure you did not use a tool like this, maybe a friend or store tech did it without your knowledge.

I should have stated this earlier, but I had a school account linked with Office 365 and used the installation through that. Though it's been a while since I had installed it and due to summer break the product had reached its expiry. Hope that makes sense!

Hello, I did try and remove and revert as much as I could (and then post the /dlv output to ensure what I provided was complying with rule 4) but I fear traces are left behind. I tried reinstalling the OS though not much changed - if it comes to it I'm not sure what my other options are!