Windows 10: Windows crashing, BSOD caused by ntkrnlmp.exe, IRQL_NOT_LESS_OR_EQUAL

Hi y'all looking for some help, Ive seen several other posts like this so it looks like the place to get this figured out. I have been having a issue recently with windows crashing to bluescreen with IRQL_NOT_LESS_OR_EQUAL and when i look at the mini-dump files it points to ntkrnlmp.exe which from what i understand means it is something else. An interesting thing is that after it crashes in this way i can only get the computer to fully boot again by resetting the CMOS unplugging the battery for 30 seconds and letting the charge go. From some research this appeared to be the ram but changing

:)

 

IRQL_NOT_LESS_OR_EQUAL caused by ntoskrnl.exe BSOD recurring

Hi, thank you for patiently waiting, upon analyzing and checking the DMP files, the error you have is ntkrnlmp.exe, this is usually caused by Damaged power cords and adapters and drivers, to fix this issue kindly refer to the steps provided on this link:

https://www.lifewire.com/fix-the-ntkrnlmp-exe-e...

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.

Additional note: If the issue persists, I suggest contacting a local technician to physically check the device for any hardware-related issues.

 

Windows crashing, BSOD caused by ntkrnlmp.exe, IRQL_NOT_LESS_OR_EQUAL

If the BSOD's continue to list different drivers, it may be time to consider backing up your files and clean install Windows from a bootable USB to rule out system corruption as a cause of the system crashes.

 

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: