Windows 10: IRQL_NOT_LESS_OR_EQUAL and various other BSOD Messages.

Are there more dumps present in %systemroot%\minidump of the recent crashes except for the most latest dump?

 

I have just reran the dm_log and managed to gather one more BSOD. The other dmps files must have been removed from my system restore sadly.

I have attached the new file with the additional BSOD dmp. Thanks

 

With a little bit of luck the cause of the 0xC5 is the same as the graphics crash, if this is not the case then we need to use driver verifier with a small customization in the settings from what we normally suggest.

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial to do so *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums
Attachment 83694
Code: 1: kd> lmvm nvlddmkm Browse full module list start end module name fffff800`31bf0000 fffff800`326e7000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Browse all global symbols functions data Timestamp: Thu Nov 05 15:35:23 2015 (563B692B) CheckSum: 00ABAB17 ImageSize: 00AF7000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

[/quote] I hope it is the same. Its just weird the black screens happen when only stress testing and not in games.

I have followed your steps and the tutorial you linked. The previous drivers were uninstalled via safe mode and the latest from the Nvidia website are now installed. I will run the same benchmarks again now to see if it occurs again.

Thanks *Smile

 

After uninstalling and re installing the driver I still got the black screens when running the stress testing programs, after closing some applications from my tray including (CAM software NZXT, Samsung magician and MSI afterburner) I do not get the black screens when running the tests.

I didn't have enough time to individually test each application to see which one was causing the issue, but will look into this soon. My thoughts are that it is the CAM software, as this is quite new on the system, and didn't have any issues last time when over clocking without it.

 

You have a lead at least *Smile