Windows 10: Explorer.exe memory read error when updating Windows

  1.    10 Jan 2017 #1

    Explorer.exe memory read error when updating Windows


    So yeah this hasn't happened to me before but I just had a memory read error come up on explorer.exe when I clicked on Restart Now to install the latest CU update. I www just wondering if this happens sometimes? I have restarted and shut down completely a few times and even installed a Windows defender update without any issue. My memory is showing the full amount so I can't see anything wrong. Has anyone else had this?
      My ComputerSystem Spec

  2.    10 Jan 2017 #2

    Haven't seen this before, but would encourage you to make sure that your OS files are OK. Please run DISM /online /cleanup-image /checkhealth in an administrative command prompt windows. Your output should look like this:
    Click image for larger version. 

Name:	goodcheck.jpg 
Views:	1 
Size:	67.3 KB 
ID:	116580
    If you see something different, post a screen cap here and we'll do further diagnosis.
    Thanks, and best wishes,
    --Ed--
      My ComputersSystem Spec

  3.    10 Jan 2017 #3

    Cheers Ed. I've done that and got exactly the same result "No corruption". It's very strange as I noticed last time I had to install an update the usage for explorer when uptown 100% which was a known issue I believe and now it brought up that memory read error. I've restarted and shut down a few times, even browsed a bit etc and everything runs smoothly. I'm wondering now if it's how explorer interacts with windows update as you click Restart Now or Install Now
      My ComputerSystem Spec

  4.    10 Jan 2017 #4

    Gosh, that's something I don't know anything about. Hopefully, one of the forum's heavier hitters will weigh in on this. But at least with DISM ... /checkhealth providing a clean bill of health, you can be reasonably sure that the update didn't damage any of your system files.
    HTH,
    --Ed--
      My ComputersSystem Spec

  5.    10 Jan 2017 #5

    Given that it's a memory error, you might want to run the Windows Memory Diagnostic, mdsched.exe, to see if it finds anything. This is best launched overnight, just before you go to bed, and left running all night long.
    HTH,
    --Ed--
      My ComputersSystem Spec

  6.    10 Jan 2017 #6

    Thanks Ed. Running an extended test on it now. I have 16GB ram so I imagine it may take a while.
      My ComputerSystem Spec


 

Related Threads
Hello, thank you for checking out my post. About a month ago a friend convinced me to make the jump from windows 7 to 10. It's been great since I've customized it to my liking, however...this morning, before work, i experienced something I've...
Read through all the info about it with a search. Nobody really knows how to fix it. I think the last time, I did a clean install. Microsoft is the pits !
Solved Write to read only memory in BSOD Crashes and Debugging
I have had two BSODs this morning, the first was PFN list corrupt closely followed by Write to read only memory. This is a clean install of Windows 10, I thought it might cure the BSODs but no such luck. So glad to find this forum. 82075
Hi, I'm getting huge memory use while running very little and I'm unsure why. It only started when I installed Windows 10. Currently this is what my resource monitor looks like 26925 I have 8 gig of ram, DDR3 / 1867mhz / none overclocked or...
Hi everyone! Im new on this forum. Ive been using windows 10 since this january and everything was fine until build 10130 came up. Everytime I shut down my computer I receive the following error: This is a bit annoying because I dont know...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:12.
Find Us