Hi and thanks for reaching out. My name is William. I'm a Windows technical expert. I'll be happy to help you out today.
This is not going to be resolved by any system utilities like sfc or dism as the issue does not lie with the operating system but likely with hardware.
The general stop code is MEMORY_MANAGEMENT (1a). However, I dont think this has anything to do with RAM specifically (as some may often point out). The first parameter of the stop code is 0x0000000000041201 (or 0x41201). This is telling because this parameter often indicates there was an issue with querying a virtual memory address. Basically, virtual memory is where Windows allocates memory in RAM to the disk, otherwise known as the pagefile and there was issue recovering that memory.
I would start by re-seating your hard drive cables. If you made any changes to the virtual memory settings (such as disabling page file) I would set those back to system managed.
Also check your storage device for bad blocks. You can find errors related to this in the Windows Event Viewer > Windows Logs > System. If the page files resides in any number of bad blocks, the virtual address and data cannot be retrieved and will halt the system. You should also run a chkdsk /r on the system drive. This will mark the bad blocks as unusable and not store data on them.
Finally, you may want to throw up a few more minidumps so I can check to see if they are consistently showing the same stop codes or similar.
2 people found this reply helpful
·
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.