Memory Management BSOD

[gabby131]

Greetings!

 

One of the PCs in my home is having the BSOD where the stop code is 0x0000001a (memory management).

I reset the memory speed to stock settings (2133mhz) and did memtest/windows memory test with no errors. (nothing else overclocked).

 

3 things, a good and 2 bad....no, all bad things:

 

The bad:  there was a dump file, but I am stupid....can't read it.

the other bad:  I lost the dump files

the worst:  I only have this below:

 

 

Can you assist me on this one?  it says on MS docs that the Parameter x1a 61941 is "The paging hierarchy is corrupt. Parameter 2 is a pointer to the virtual address which caused the fault."

but the Parameter 2 is:

 

 

As I stated above, I lost the dump file, nothing in C\WINDOWS.  So this means i'm screwed?

 

Specs:  5930K, GTX 1080, Corsair Vengeance 2400mhz 4gb x4 RAM

 

Thank you and regards,

 

[Boomwebsearch]

6 minutes ago, gabby131 said:

BSOD where the stop code is 0x0000001a (memory management).

Sometimes simply reseating the RAM in your computer gets the problem fixed although sometimes that does not happen and that could be an indicator or possible hardware damage or something which has gone corrupt and not able to be read properly by your computer system. I would first try reseating the RAM then going on the computer and seeing if the BSOD pops up again. If it does then try replacing the memory with not mixed and matched memory to try and see if the issue is solved. If that is not the case then there are many things that could have gone corrupt and I would replace the related files and drivers.

[gabby131]

1 minute ago, Boomwebsearch said:

Sometimes simply reseating the RAM in your computer gets the problem fixed although sometimes that does not happen and that could be an indicator or possible hardware damage or something which has gone corrupt and not able to be read properly by your computer system. I would first try reseating the RAM then going on the computer and seeing if the BSOD pops up again. If it does then try replacing the memory with not mixed and matched memory to try and see if the issue is solved. If that is not the case then there are many things that could have gone corrupt and I would replace the related files and drivers.

Dayum, those are the things I already did initially (except replacing RAM, just tried one stick on all slots at a time) and still got the error.

Maybe i'll just re-install windows if this is a driver 'search and destroy' type of troubleshooting.

 

Thaank you! @Boomwebsearch ^____________________^

[gabby131]

Just now, Inx said:

If you can capture a new dump file, I can analyse them and tell you what likely caused it.

 

I have an issue where I was getting the same stop code on my machine in my sig, and it's overclocked as well.  When returning to stock the BSOD was still happening, and it turned out it was hwinfo64 causing it.

Yay! \Ü/

 

I will try to replicate....might take a while.  To make sure i'll do what Boomwebsearch suggested again and then do my normal stuff.

I recall the last time it happened, I had HWmonitor, discord, steam, corsair iCUE (that keeps on crashing), MSI afterburner open besides of those non windows/MS programs.

 

Will update.....

[gabby131]

4 minutes ago, Inx said:

If you have two different programs open that monitor sensor data, you might cause a conflict.  I didn't believe it at first but I think that may be what was happening with hwinfo64 on my system, too many things were attempting to read sensor data (at the time I was trying to figure out why core temps on my cpu were reading differently among different programs, and apparently some apps assume my xeon's tjmax is 100c, when it's actually 85c).

ooohhhhh shiiiiiiii.............. both HWmonitor and iCUE can read/monitor hardware/sensor data....alright I will make sure all of those programs are active when I do my journey of replicating the issue.

 

Thanks again! ^___^

 

EDIT:  and MSI afterburner is also a monitoring software.

EDIT2:  the mobo is an ASUS X99 Sabertooth.  Noticed the dust-defenders (those plastic things you can place on empty PCI-E and RAM slots) are installed.  I removed them to ensure accuracy.   and gave the pc a little dusting.

[gabby131]

crashed again but no event logs.  funny thing is all the crashes happen around 12.30am.  will continue to monitor.

[gabby131]

My issue did not replicate again after a few days, even with the software I suspect to be the culprit still running.

What I did differently is to run folding@home to see if it'll trigger with high loads and a windows 10 update.

 

After those, I decided to perform the task suggested above.

 

I re-seat RAM and GPU, removed the dust-defenders, and only ran MSI after burner as monitoring software (made sure no conflicting software).

the monitoring on iCUE is limited to RAM, the corsair coolers and peripherals, mobo, and power supply temps, which MSI afterburner cannot monitor (or I removed from monitor tab).

 

Marked this as solved, as the issue when it initiated, happens almost every day to twice daily.  Thank you @Inx and @Boomwebsearch for you assistance!