Windows 10: Memory Management Crash
Memory Management Crash
Can someone please analyze this minidump? What happened basically is that the PC very often doesn't go into sleep mode (just turns off the screen and doesn't let me do anything) so I am forced to do a hard reset. At that point, a BSOD usually pops up that the PC ran into an error and something about memory management.
If I were to restart and put it in sleep mode right away, it would do it just fine so I assume after prolonged usage, something happens which prevents it from going to sleep.
Still, a hard reset shouldn't BSOD regardless.
Any input is appreciated.
The data in the pagefile is corrupted when it happens, this may be due to failure of hardware.
Run below scans on the TOSHIBA DT01ACA200 hard drive or the C: partition.
ADDITIONAL_DEBUG_TEXT: Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests
- Short Drive Self Test
- Short generic
- Long generic
If the short generic fails, no need for the long generic.
Do not run SeaTools on an SSD as the results will be invalid.
Disk Check - Windows 7 Help Forums
Run HDTune to
- scan for errors, no quick scan but full scan
- check the health,
It may take some time, but please take the time you need to perform it properly.
Let me know what the results are
- of the error scan,
- make a screenshot of the health of every hard drive and post the screenshots,
- post screenshots with the benchmark of the
- transfer rate,
- access time,
- burst rate,
- cpu usage.
I did as you asked.
I compressed all of the results in a rar file. The checks were all ran on the Toshiba hd you pointed out and I didn't do the "write" portion of the benchmark since it didn't let me do it without erasing the partitions (the read portion was benchmarked though just fine).
Regarding the other hd health (which is the only thing you asked me to screenshot), as you can see, 2 of them have a problem (SSD is a red one and Seagate is a yellow one) although I am not sure how much of an effect that has on anything.
However, I did read that there are too many criteria that different software report, and I stumbled upon the following response:
"If both Samsung Magician and Crystal Disk do not report a problem, believe what they tell you and ignore HD Tune. In fact, I would get rid of HD Tune altogether. Too many diagnostic softwares just cause doubt and confusion."
And so I ended up using both of those tools (Crystal Disk and Samsung Magician and both reported no problems on the SSD (Seagate is fine as well although I didn't screenshot it). I am attaching a picture too from those applications.
Is the firmware of the SSD updated?
HDTune is usually correct, but that is because other attributes are more often failing which are more generic attributes.
The attribute that failed is an attribute that is used in Samsung devices, HDTune can't be 100% correct about such attributes so if it were me I would ignore it
The Calibration Retry Count is something you have to keep an eye on, if it increases it means the hard drive is failing/faulty.
Not sure. I checked on the Dell website and the date is 2015 April. I could update it perhaps, but the changes don't seem to be worth it:
Samsung SSD PM851 Firmware Update Driver Details | Dell Middle East
Is there anything else you need me to do? What is the cause of the BSOD?
Generally speaking, which is also this time the case, the 0x1A crash doesn't show a specific cause.
- hard drive
The dump doesn't point directly to anything, but based on the causes I've mentioned and a few things in the dump there is a chance the drives are involved in it.
So should I update the topic when I get another crash? I am sure I can replicate it soon enough but it seems that the dump would be pretty much the same so I don't know what else could shed light on this.
I initially assumed the "memory management" part would refer to the ram but the diagnostics I did yielded no errors either. Then, based on the error you investigated, it seemed as if it was some sort of perhaps corrupt pagefile? Judging from my past experience with using older versions of windows, sometimes the pagefile got corrupted after hard resets and windows automatically repaired it. It seems that in this case it simply opted to generate the BSOD, restart, and boot back up as if nothing had happened.
Is there a way to prevent the necessity to hard reset? Basically, as I outlined in the beginning, the PC simply doesn't enter sleep mode but the monitor turns off (so using the mouse or keyboard doesn't do anything) so I press the power button because I see no other choice.
I've also been experiencing PC sluggishness over the past couple of weeks. It just seems that the UI is unresponsive more often than responsive and things take longer to open-up/close than I am typically used to.
I don't know if both of these things are related, but thought it was worth pointing out. I am really not sure what it could be as all my drivers from Dell are the latest one (unless they themselves don't update their page or something):
Product Support | Dell US
If you mean the built-in diagnostics, the built-in diagnostics test isn't really reliable. It doesn't find errors when others do.
the diagnostics I did yielded no errors either.
Regarding corruption in the page file, that isn't 'fixable', because the page file is an additional way of storing more data in memory, temporarily. It allows for a large working set to reside in memory, while other data is paged to disk for use another time.
The data that is corrupted in the page file is caused by either not proper storing, or a part of the disk is damaged.
Resetting the page file deletes all the data in the page file removing the corruption, when you reconfigure the page file the data that was improper stored usually is stored again but proper although the data might be slightly different at least, when it comes to the disk the data either doesn't reach the same amount of data stored to reach that place causing the corruption on the disk or it is already been used.
So it happened again today. What else can I do? I know it's probably all the same, but I'll post it again after the crash.
Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums
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.
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.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.
This randomly happend after rebooting my laptop,
was not tampering with any drivers or anything.
Hopefully someone can figure out whats wrong in total i get 3 different messages across those files.
Memory Management being the first and most...
Hello. Beginning from Saturday while playing with crashes and freezes I might have fixed my driver problems, but upon booting up my PC the next day, I was receiving constant Memory_Management BSOD errors every 20 minutes to 1 hour when trying to...
Alright.. going to give this forum a shot, I've tried tomshardware for over a month to no avail... I keep getting a BSOD over Memory management System service exception iqrl less than or equal to etc.. I've gotten minidump files for them and ran...
I installed Windows 10 64 bit on Nov. 7. It was good for a day or two. Not the system crashes after being started for 8 to 81/2 hours. This happens every day. I get an error say:
Your PC has encountered an error and needs to restart.
I built a new PC and now I have some troubles getting it to work.
I get so many bluescreens, most of them appear when I am on the desktop a few minutes after the PC starts (sometimes I can start playing games, but after a few minutes...