BSOD IRQL_NOT_LESS_OR_EQUAL after sitting idle for around five minutes

So this problem cropped up yesterday, and I'm no stranger to it. This Win10 install is relatively fresh, just a few weeks old with not too much being installed on it. Less than 24 hours ago, I began getting these BSODs out of the blue whenever my computer sits idle.

First and foremost, the system is indeed overclocked but has passed 6 hours stable with Prime95, OCCT and even Linpack, and I've ran several instances of Memtest86+ all to verify there isn't anything wrong hardware wise. But for the sake of troubleshooting, I completely went to stock clocks and still get it after sitting idle.

From what I'm gathering after a bit of reading around, this is indeed something driver level for the most part. Before all this started yesterday, the computer had been on overnight. I checked to see if anything had updated without me knowing, but there were no updates. As far as I know, no software had been installed or updated.

This has been no stranger to me, as this isn't the first time this obscure BSOD popped up out of the blue. Always after a few weeks of running this machine, it'll have fits like this once a week where it just constantly crashes when left idle. Then be okay. Then another week passes and it has another day where it just won't cooperate until another fresh install.


-Edit-
Edited to include requested DM info.

So I've done a bit of fiddling around, ended up disabling ULPS since I was kinda leaning towards GPU driver issues. Two crashes since then, both now ATTEMPTED WRITE TO READ ONLY MEMORY.

Including those two new dumps with this post.

Much appreciated on you looking into it for me. Honestly, I've only let it go for maybe three or four passes before I call it good. I had some time today to really start looking at things with a fine tooth comb when it came to some of my motherboard settings, and come to find out... My board isn't properly setting the correct timings for the rated speed it's selecting. It's probably been this way for a good year, no less. I had to replace my motherboard and CPU last year (VRM Failure smoked both) but the ram sticks were tested on that setup up to 2500, and the previous board automatically set the timings appropriately.

If anything, this totally verifies that it's indeed something with my ram which I've had suspicions on for a while. I was not aware that 8 passes was the recommended time for testing, so tonight or tomorrow (time permitting) I'll set the timings proper and let it make the full 8 passes and get back with you.