Windows 10: IRQL_NOT_LESS_OR_EQUAL & MEMORY_MANAGEMENT BSOD's

Please don't enable driver verifier again after it found drivers, but first test your system for stability.

 

Well I received a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M BSOD, (I didn't enable verifier after it found the one driver) while doing absolutely nothing. I had steam open, and a full screen video that was paused because I was waiting for it to buffer. I wound up taking a quick nap and was rudely awoken to the Windows log on sound.

 

BSOD Posting Instructions

 

There are 2 crashes, either of them is caused by driver verifier and looks to be from something that you attached via USB.
This driver does not come back in the logs as present on your system.
Code: 1: kd> lmvm usbpcap Browse full module list start end module name fffff801`cdb70000 fffff801`cdb7e000 USBPcap T (no symbols) Loaded symbol image file: USBPcap.sys Image path: \SystemRoot\system32\DRIVERS\USBPcap.sys Image name: USBPcap.sys Browse all global symbols functions data Timestamp: Fri Oct 02 11:09:46 2015 (560E49DA) CheckSum: 000102F9 ImageSize: 0000E000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Yes because USBPcap was a component of wireshark that I have since uninstalled, as of a few days ago. I will try playing overwatch today and see if I get a bluescreen. As I mentioned, I only really seem to get them while playing Overwatch for the most part.

 

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY, and PAGE_FAULT_IN_NONPAGED_AREA BSOD's tonight.

I re-seated the RAM as such that each of the four modules are in a different slot. Figured it really couldn't hurt. I have attached a zip file. I was playing Silther.io and watching a full-screen video on the other monitor when the most recent one took place.

I'd also like to add that sfc /scannow yielded a result: "Windows Resource protection found corrupt files but was unable to fix some of them"

how do I go about fixing that?

 

Upload the cbs.log file located at %systemroot%\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.

Please remove 2-3 memory sticks, ensure the left-over memory is seated properly and try to run that way. You'll want to prevent stuff that takes a lot of memory.
Even though we have done a memory test it looks like a memory issue, MemTest86+ is not always 100% correct so errors can be missed.
What you need to do when a crash occurs:
Stick 1 in slot 1 - crash? Move to the next
Stick 1 in slot 2 - crash? Move to the next
Stick 1 in slot 3 - crash? Move to the next
Stick 1 in slot 4 - crash? Move to the next
Stick 2 in slot 1 - crash? Move to the next
Stick 2 in slot 2 - crash? Move to the next
Stick 2 in slot 3 - crash? Move to the next
Stick 2 in slot 4 - crash? Move to the next
Stick 3 in slot 1 - crash? Move to the next
Stick 3 in slot 2 - crash? Move to the next
Stick 3 in slot 3 - crash? Move to the next
Stick 3 in slot 4 - crash? Move to the next
Stick 4 in slot 1 - crash? Move to the next
Stick 4 in slot 2 - crash? Move to the next
Stick 4 in slot 3 - crash? Move to the next
Stick 4 in slot 4 - crash?

Note it if a crash occurs and if a crash does not occurs, post the results please.

I am aware that this could take up a lot of time, but swapping is the best way to identify what is causing the crashes.

If somehow the results are improper I would suggest to go for a clean install after backing up everything you do not want to loose.

Please do NOT rush with installing everything again, but take it slow. Install all Windows Updates, install the drivers ASUS provides but do NOT install any software. We need your system to have as less as possible installed to prevent a BSOD from occuring again after a few hours of a clean installation because of a rush for installing software, this could cause us to start all over again.

 

​CBS.log - Google Drive

That's the CBS Log

I won't be around much for the next week and a half, but as soon as I am able to test the RAM sticks I will come back to this thread and let you know. Worst case scenario I will start a new thread.

I am honestly considering just making a new build, new mobo, new cpu, wipe HDD and start over. I feel as if the issue lies within the drivers, and seeing as how my hardware is ~4 years old, perhaps it's just time. Thanks again for troubleshooting with me, I will update whenever I can.

Is it possible the paged memory BSOD's have to do with the Hard Drive's page filing system?

 

Real quick I cannot find problems in CBS log, but I am no analyst for that part.

You know what paged memory is?

 

It was my understanding that it lowers the amount of RAM used for frequent tasks by storing a page file on the drive, am I wrong? I'm just spitting out ideas. when I see PAGE_FAULT_IN_NONPAGED_AREA I think of paged memory, especially since I've gotten other memory related BSODs.

 

What happens when there is not enough RAM is that some data is paged to the pagefile to make room for other tasks, the pagefile is the virtual memory on the hard drive.

In a simple explanation, with an IRQL of level 2 or higher a driver has access to certain areas of the kernel, however when the driver wants to reference an invalid memory address or a wrong memory address a pagefault occurs. With IRQL of level 2 or higher we move from paged memory to nonpaged memory, in nonpaged memory a pagefault does not occur under proper circumstances so when a pagefault occurs it is a violation of the rules and thus a BSOD occurs.

 

Thank you for your detailed explanation, as these are terms I understand. This helps me get a better idea of what's going on with my own computer a little more. Would it be possible to explain briefly why a fault would not correct itself, and why it would cause windows to seize up and force a restart (IE: BSOD)?

 

Windows cannot correct errors on drivers & hardware, what it can do is modify a few things of its own system but nothing more.

If you know the function of the BSOD then you know the answer to your second question.

 

Okay so I used WhoCrashed to analyze some crash dumps (a few from today) and the Intel Gigabit Adapter driver was the cause for a couple of them. Checked device manager and the driver is from may of 2015 even though I thought I had updated it after your prior post about which drivers were outdated. I am updating the driver as we speak and will see if it helps my issue with a couple less blue screens hopefully.

 

Programs as WhoCrashed are a joke, they cannot analyze dumps properly.