Been having trouble with the IRQL_NOT_LESS_OR_EQUAL BSOD for many months now

Hello @xilolee, long time no talk. I finally encountered a BSOD since the last time we spoke.
Earlier yesterday, I was hit with a BSOD I have never seen in my life, called "MEMORY_MANAGEMENT"

Figuring it was just a rare outlier, I decided to ignore it. However, it happened again just now, so there might be something wrong.
My system has remained unchanged for the most part after upgrading to Build 2004. This may be the first BSOD I experienced since then, actually.
I have attached the minidumps for your kind analysis.

If you could see whether there is anything you can diagnose from the minidumps, that would be helpful. Thank you very much!
 

Attachments

I'll add my observation here and I hope @xilolee will also add his recommendations too. The dumps show a memory problem and suggests there has been memory corruption. There are various reasons for this but for now I would like to see you running your memory at the recommended clock speed for the processor. The Intel(R) Core(TM) i7-8086K CPU @ 4.00GHz is designed for DDR4 memory running at 2666MHz. Your memory is actually set up at 3000MHz. Often this does not cause any problems but in some cases it can contribute to BSODs and in recent builds of Windows 10 I have seen this situation more often.

See if your system runs better at the lower memory clock speed which you can adjust in the BIOS.
 
Hi, thank you for your response @philc43! I actually did a bit more searching on the web in regards to the MEMORY_MANAGEMENT BSOD, and some places suggested for the RAM to be reseated.
I did that, disconnecting the power cord and taking out the RAM and swapping them around different slots, and the BSOD stopped occurring after the third instance. Perhaps you could take note of that in case somebody else experiences that BSOD as well.

On a side note, I experienced PAGE_FAULT_IN_NONPAGED_AREA as well as INTERRUPT_EXCEPTION_NOT_HANDLED afterwards, but based on what WhoCrashed described, they seemed to be outliers not worth concerning myself about. The former seemed to point to a storage drive issue (which I have encountered BSODs before so no surprise here; might have a bad drive), and the latter is apparently "very infrequent" according to Microsoft, so I'll just ignore it.
 
Hi @xilolee, sorry for not getting back to you. I've been busy lately, and haven't really had the time to check in. The C-states have always been off.

Now then, over the course of the month, I've been experiencing a lot of BSODs.
Half of them were irregular (different error codes each time; you name it and I've probably experienced it), and the other half were consistently KMODE_EXCEPTION_NOT_HANDLED.
Every time I got the KMODE error, WhoCrashed would quote that something was wrong with the Processor Device Driver (intelppm.sys).

Before August, I've never had BSODs happen this frequently. Now it's happening pretty much once every other day or more.
I haven't changed anything in the system, apart from whatever Windows Update provides me. I genuinely feel that my system has gotten a lot more unstable after upgrading to Build 2004.
Before, I almost never get a BSOD outside of gaming, and I always attributed it to the possibility that gaming might've heated up my CPU and caused it to throw an error.
But now, I don't even have to be gaming for it to suddenly happen out of the blue.

One "pattern" that I have noticed is that the the BSODs tend to occur once my committed memory starts to build up. That is, when it starts to reach over high amounts like 25-30 GB.
That typically happens after about 1-2 days of cumulative uptime, since I always sleep my PC in order to maintain my workspace. (It's inconvenient to keep setting it up after a restart.)

Some rudimentary research on Google gave me an interesting finding to consider: There is a possibility that my CPU or RAM might be "bad." See here.
I already put my RAM under rigorous tests with Memtest86+ and the Windows Memory Diagnostic, but they didn't return any negative results. This was the same when I checked it several times in the past.
I can also put my PC under various stress tests for several hours (including Prime95), and they would always pass without any issue.

My PC has thrown a BSOD every so often (once a month at least) ever since I bought and installed the CPU, but I've always shrugged it off as being too infrequent to matter.
But after reading that post that I linked, I am now under the impression that I might have a faulty CPU that may have degraded or something.

I'm truly at a loss and I'm not sure what's going on. I don't know if my CPU/RAM is faulty or if it is genuinely a Windows 10 problem (Build 2004) that I should patiently wait to get fixed.
What do you suggest I should do? Should I replace my CPU/RAM? In the meanwhile, I'll try reseating my RAM again in hopes that it stabilizes the PC. Thank you, again
 

Attachments

Attachments

There were 5 BSOD dump files collected.

These occurred between 8/23 and 8/29.

Bugchecks were:
50
1E
BE
A
133



For all steps / tests please make sure images are posted into the thread.
If there are any problems posting images please use share links.




Please perform the following steps:

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan

7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


8) The BIOS: Version/Date American Megatrends Inc. 1502, 2/21/2020
Upgrade the BIOS: 1502 > 1602
"- Improve system stability
- Update Microcode and ME firmware for Intel security issue"
PRIME Z390-A Driver & Tools | Motherboards | ASUS USA



9) This drive was reported with drive file corruption on 6/26 and was no longer displayed in the logs: Drive G:
Indicate the status of this drive.



10) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
11) re-install the Nvidia GPU driver from the Nvidia website
12) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.2.7 (or newer version if available)
Wagnardsoft

Display Driver Uninstaller: How to use - Windows 7 Help Forums
Display Driver Uninstaller: How to use - Windows 7 Help Forums

Download Drivers | NVIDIA
Download Drivers | NVIDIA



13) Uninstall and reinstall: e1d68x64.sys
Intel(R) Ethernet
Updating a driver.


14) Run the Intel driver and support assistant to make sure drivers are up to date:
Download Intel® Driver & Support Assistant



15) Run Memtest86 version 8.4 (or newer version if available) for four passes.
Repeat the test so that eight passes are performed.

MemTest86 - Official Site of the x86 Memory Testing Tool

Use a camera or smart phone camera to take pictures and post images into the thread.
In case there are any problems uploading images use share links (one drive, drop box, or google drive)

Memtest86 has a feature to produce a text report.
Please post this in addition to the images.



16) The RAM modules were not seen on the motherboard manufacturer's Qualified Venor List (QVL)
F4-3000C15-16GTZ
Please indicate whether you were able or not able to find the modules on the QVL.
PRIME Z390-A Memory / Device Support | Motherboards | ASUS USA











Code: 
e1dexpress    Intel(R) PRO/1000 PCI Express Network Connection Driver D    c:\windows\system32\driverstore\filerepository\e1d68x64.inf_amd64_61aa07b8041d598f\e1d68x64.sys    Kernel Driver    Yes    Manual    Running    OK    Normal    No    Yes


Code: 
Name    [00000002] Intel(R) Ethernet Connection (7) I219-V
Adapter Type    Ethernet 802.3
Product Type    Intel(R) Ethernet Connection (7) I219-V
Installed    Yes
PNP Device ID    PCI\VEN_8086&DEV_15BC&SUBSYS_86721043&REV_10\3&11583659&0&FE
Last Reset    8/30/2020 12:25 AM
Index    2
Service Name    e1dexpress
Memory Address    0xA4300000-0xA431FFFF
IRQ Channel    IRQ 4294967280
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\E1D68X64.INF_AMD64_61AA07B8041D598F\E1D68X64.SYS (12.18.9.10, 584.06 KB (598,080 bytes), 1/31/2020 3:29 PM)


Code: 
nvlddmkm.sys Wed Aug 12 15:15:17 2020 (5F3469F5)

Code: 
e1d68x64.sys Thu Jun 27 00:58:38 2019 (5D14772E)
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top