Windows 10: WHEA_UNCORRECTABLE_ERROR and IRQL_NOT_LESS_OR_EQUAL bluescreens

Minidump files are here: https://drive.google.com/drive/folders/1epKtZ-L1wsb-3yOPqeQWtx6ekhM1U-K5

:)

 

IRQL_NOT_LESS_OR_EQUAL bluescreen

Hi DaveM121,

Sorry to bother you again, but today I had "IRQL_NOT_LESS_OR_EQUAL" bluescreen again, I checked the EventViewer to see the possible cause and it again saved the dump at "C:\Windows\MEMORY.DMP.". I have uploaded it to OneDrive once again.

Is this still related to Motherboard Chipset drivers? Because I have already downloaded and installed latest chipset driver for my motherboard after your suggestion to do so. Not sure what is the cause of this IRQL_NOT_LESS_OR_EQUAL system error this time.

Sorry to bother you and thank you for your time!!!

 

Bluescreens, on top of bluescreens.

When I built my PC back in 2016, I began to blue screen not short afterwards. I thought it would solve itself, but no. It crashes at random times of the day, and has no correlation with what I am doing. I could be staring at my desktop and my PC would bluescreen.
My temperatures are fine when gaming, and overclocking had nothing to do with it considering that it bluescreened before I overclocked. I'm stuck and really have no clue as to what I should do next, considering I've looked at registry errors, driver issues,
updates, etc.

If I need to post anything like specs or windows logs, let me know. From memory I know a few bluescreens I got were:

KMODE_EXCEPTION_NOT_HANDLED

IRQL_NOT_LESS_OR_EQUAL

WHEA_UNCORRECTABLE_ERROR

MEMORY_MANAGEMENT

From memory I believe a few filetypes that the bluescreen listed were:

tcpip.sys

usbaudio.sys

fltmgr.sys

If anyone has any insight to this, it would be much appreciated.

 

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.