Windows 10: BSOD - MEMORY_MANAGEMENT in ntoskrnl.exe

I have had my computer for about three years, I think.

A few days ago I started getting bluescreens, the first couple with random codes (IRQL_NOT_LESS_OR_EQUAL and another one that I don't remember). Then I got the same MEMORY_MANAGEMENT in ntoskrnl.exe three times in a row. Unfortunately, the first minidumps disappeared. A couple of updates were installed on 03/14, just before the blue screens started (I think. Not sure at 100%). One is KB4088776 and the other one is a flash update, KB4088785.

I have updated the GPU drivers and successfully passed the Windows memory diagnostics.

Thank you very much for your help.

:)

 

Lots of BSOD's

PS: after my previous/last replie i had 3 more BSOD's:

seems like there are a lot of random once...

MEMORY_MANAGEMENT win32kbase.sys

MEMORY_MANAGEMENT ntoskrnl.exe

ntoskrnl.exe

 

Help analyze frequent BSOD, please

Experiencing frequent BSODs (Memory_Management mostly). Fixed one culprit (Intel SmartConnect driver) but can't find what else is causing NTOSKRNL.EXE to crash.

Per your instructs, an archive of the Minidump, sys specs, etc follows.

BSOD.zip

Thanks!

(desperate)

 

Try running a more detailed memory test - the windows memory diagnostic test is not able to check for all errors.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.

 

Thank you very much. I don't really think the memory is the problem here. The issue arising just after a windows update seems pretty suspicious to me.

I've made a couple passes of memtest anyway, and I will let it overnight just in case.

Meanwhile, I would appreciate any other advice.

 

The passes are taking more time than I expected. I have had to log into windowsa few times. The first time it made nearly two passes (only one complete), the second time it made two passes, and this last time it has been three passes in about 11 hours (pic attached). Please, take my word for this. I will make a few more passes through the weekend, but I don't think I will be able to make eight passes in a row.

 

We do not think the results are valid unless a full 8 passes are completed in one go. What I would suggest is to work with just one stick at a time overnight.

I will have another look at the crash dumps in case I can spot anything else. I suggest you try the beta log collector which is provided at the end of the BSOD posting instructions and post some new files. It might provide a bit more data for us to work on.

 

Thank you very much for taking your time.

Would you be so kind to explain why the results would be invalid if I perform 8 passes in multiple batches?

Thank you! But wait, I have detected that I had some drivers that needed updating.

I think I will update them and test the system for a few days. If I got another BSOD I will use the beta collector with the updated drivers and post here the info. In the meanwhile, I will try to find a moment to make that 8-pass in a go.
Is that OK?

 

All sounds a good approach. We insist on the 8 passes which have to be completed as a continuous process so that the RAM is given a thorough test under extended operating conditions. In some cases we have seen errors turn up only after 9 or more passes but that is a rare case.

 

Thank you again.
I have had another BSOD six hours after booting the computer.

Here is the file generated by the beta logger. I will try to get to the 8 passes in a row this weekend
DESKTOP-RNKHQ4L (2018-03-22 22 21).zip

 

Ok, I stand corrected.





It failed in the first 8 passes combined. I can't see how performing the eight passes in one go can help in the general case (in some special cases sure it can).

Anyway, I think this thread is solved.

Thank you a lot.