Constant IRQL_NOT_LESS_OR_EQUAL BSOD

Currently getting constant IRQL_NOT_LESS_OR_EQUAL BSOD within 5 minutes of booting up my computer (Windows 10) regardless of what I am doing. A couple months ago, had a lot of random BSOD issues that went away when turning XAMP off in the BIOS. The computer works fine in safe mode. Have updated to latest graphics driver with no change. Log file dump here.

Specs:
i7 11700
3070Ti
Gigabyte Z590 Aorus Ultra
750W Corsair gold PSU

Hello and welcome to the forum. There are special instructions at the top of this forum section for posting BSOD threads. Provide the required logs referred to in that thread so someone can help you.

"Before posting a BSOD thread, please read the instructions here: Blue/Black Screen of Death (BSOD) Posting Instructions
If you need to add new information, please make a new post in your initial BSOD thread."

The log dumps are linked in the original post, they were too big to attach. Are they not accessible?

Sorry, my bad. My old eyes overlooked it. Yes they are accessible through you link. @zbook or one of the other folks here who are proficient in analyzing logs will be with you soon. We are all in different time zones so it sometimes takes a while.

This specific bug is usually caused by a bad memory module (or bad slot), conflicting/corrupted system service, drivers or Bios. The latest Crash Dumps you posted (from yesterday) - happened when Windows Defender tried to update its definitions - by accessing the physical or virtual memory (paging file) - incorrectly or the path was invalid (if the physical memory or storage has issues). And since it crashed and couldn't finish the update - on next restart it tried again (or maybe was simply triggered by the daily scheduled) - end-ing up with same result (BSOD). Yet, that's not to say that Windows Defender is the issue (unless it's corrupted) - since you have multiple errors - caused even during Windows Updates. I see you have Windows 10 - but not the latest build (22H2) - so that would be my first recommendation. But for start open CMD as Administrator (Win Key + X) - and type the following commands:

sfc /scannow

To check the health： Dism /Online /Cleanup-Image /CheckHealth

To scan the health： Dism /Online /Cleanup-Image /ScanHealth

To restore the health： Dism /Online /Cleanup-Image /RestoreHealth

...see if this helps with possible OS corruptions (it's not always successful tho - sometimes only a Windows Reset can help - if you don't have a back-up from a time when it was fully stable). You could follow the next steps for testing the ram: How to Test RAM: Making Sure Bad Memory Isn't Crashing Your PC

The logs displayed an unlicensed version of Windows 10.

Please activate Windows 10 making sure that it is properly licensed.

Then open a thread in our sister forum: Ten Forums