Windows 10 BSOD IRQL Not Less or Equal

[nine_seven]

Hi, Over the past 3 days, computer has bluescreened 12 times. At the start the reasons have differed but it is consistently giving the same error message 'IRQL Not Less or Equal' kernal power error 41.
This is happening while doing pretty much anything (gaming, browsing, etc). I've tried reinstalling drivers for my graphics card and network adapters, clean windows 10 install, reseating GPU and RAM (which then caused an hour of fiddling around because it wouldnt display anything).
I'm running out of things to try and need some assistance. Any Ideas.

Thanks!

 

[Ralston18]

"Power Error 41".

What wattage and how old is your PSU? Make and model?

Power supply problems can manifest in any number of ways.

Event Viewer may provide more information if you look for errors or warning that occur just before or at the time of the BSODs.

Even if the PSU is new that does not necessarily mean that it is fully functional and cannot have problems.

 

[nine_seven]

"Power Error 41".

What wattage and how old is your PSU? Make and model?

Power supply problems can manifest in any number of ways.

Event Viewer may provide more information if you look for errors or warning that occur just before or at the time of the BSODs.

Even if the PSU is new that does not necessarily mean that it is fully functional and cannot have problems.

I have an EVGA Supernova 850 G2 which is about 9 to 12 months old.
I have looked through event viewer and it seems that about 2 to 3 seconds before each 'Power Error 41' there is the same Error event, Source: Application Popup, event ID: 56, [Qualifiers]: 49156

 

[Ralston18]

Very good.

Google " Application Popup, event ID: 56, [Qualifiers]: 49156"

You do not need to immediately do anything.

Just take a look at the implications of the error message and then narrow them down as applicable to your system, setup/configuration.

Modify the search criteria and look for links that have a common pattern with respect to your problem.

The overall objective being to find a problem matching your problem with a corresponding cause and, hopefully, a fix.

 

[nine_seven]

Very good.

Google " Application Popup, event ID: 56, [Qualifiers]: 49156"

You do not need to immediately do anything.

Just take a look at the implications of the error message and then narrow them down as applicable to your system, setup/configuration.

Modify the search criteria and look for links that have a common pattern with respect to your problem.

The overall objective being to find a problem matching your problem with a corresponding cause and, hopefully, a fix.

Done some googling and multiple people advised to update the BIOS. Have just done so, also realised that it was 2 1/2 years out of date...whoops. I'm going to bed now as its 2am here, will see how it fairs tomorrow with the new BIOS update and will let you know if it's still an issue, fingers crossed. Thank you for your assistance so far!

 

[Ralston18]

You are welcome.

Please remember to update your posts with whatever happens. May well be that someone else may spot some error or omission or commission on my part.

 

[nine_seven]

No luck.
My computer blue screened again at around 11am this morning.
After speaking to some friends, one of them recommended rolling my GPU drivers back further than I already had done, so I did. I am now on version 382.53. This was running fine for about 9 hours with no blue screens. Then about 5 minutes ago, the BSOD appeared, with the error PFN_LIST_CORRUPT, but with the same Kernal Power Event 41 in event viewer.

 

[Ralston18]

Check the following postings from within this Forum:

http://www.tomsguide.com/answers/id-3374187/kernel-power-determine-crashes.html

 

[nine_seven]

Sorry for the delay in replying!
After performing a second clean install of Windows 10 64 bits, the BSOD returned, but this time it successfully created the memory dump.
After looking through them in BlueScreenView, the reason my pc has been blue screening is due to a driver named ntoskrnl.exe. I googled this and it says this is due to a memory leak however I'm not sure how to fix this.
Any ideas?