Windows 10: Constant BSOD - IRQL_NOT_LESS_OR_EQUAL

Hello! I keep getting a constant BSOD as stated above every 1 to 2 hours of using my PC. I have tried to do just about all the things i can find online, i have updated drivers, i have turned XMP off and have even reinstalled windows reinstalling made so that i did not have a blue screen all day after doing things on my PC for about 9 hours but then it returned eventually. I have run windows memory diagnostic but this hasnt shown any errors.I have had a technician from MS log in via remote and adjust a few things, but this did not solve my problem. For context, this is a custom built PC which

:)

 

KernelBase.dll is broken constant BSOD's constant game crashing.

Hi Darry,

User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

To create a user profile, follow these steps:

• Go to Settings. Click Accounts.
• Select Family & other people.
• Select the Add someone else to this PC tab.
• Name the user as Test.
• Leave the password field blank.
• Hit Next.
• Sign in as Test user.

You may also check this link
to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.

 

BSOD - IRQL_NOT_LESS_OR_EQUAL

Hi,

I have been experiencing BSODs in the last 4 days.

The last BSOD showed me "IRQL_NOT_LESS_OR_EQUAL" and I don't know what happened.

(I forgot what the previous BSODs error, I believe it was not "IRQL_NOT_LESS_OR_EQUAL").

Here is the link for my last 3 minidumps file and MSinfo32.

https://drive.google.com/open?id=0B1MN1Ypl7R3rbmt2VEh0MWxCNzA

Please, I need your help.

Thanks.

 

IRQL_Not_Less_Or_Equal

sigh
If your computer auto restarts on BSOD find the setting in windows to make it stop.
Second step is to look for the error code of the BSOD.
Perhaps easier would be to use an online application such as bluescreen viewer.
Once you know which driver is causing the problem you can look further into fixing it.