Windows 10: Error at shutdown

I googled your issue (i had/have (on & off) this issue with a particular software (Sticky Password)), see whether this helps any -

Build 10131 Explorer.exe Application error. The instruction at - Microsoft Community

In essence it says -

I understand that you are getting explorer.exe – Application error while (shutting down) the computer.

This usually occurs if the Operating System does not allocate a large enough buffer for the maximum string length that is permitted. When the data is larger than the buffer size, the Winlogon service stops unexpectedly and your computer generates the error message.

To resolve the issue, please try increasing the virtual memory of your computer and check if the issue persists.

Follow the steps below to change the virtual memory:

• Press Windows Key + E
• Right Click on This PC or the name of your computer.
• Select Properties and then select Advanced System Settings.
• Select Advanced Tab, under Performance, click Settings.
• Click on Advanced, Under Virtual memory, click Change.
• In the Drive list, click the drive that contains the paging file you want to change.

If you are still facing the same issue, please perform a clean boot and check if it helps.

Perform Clean Boot

A clean boot allows the Windows operating system to launch without any additional programs or services running when you turn the computer on. This allows you to determine if computer issues are caused by a program or service that starts up when you boot the machine.

Place the computer in clean boot and check if the issue persists. You may follow the article mentioned to perform a clean boot.

Perform a Clean Boot

Refer: http://support.microsoft.com/kb/929135

Note: After performing the troubleshooting steps for clean boot refer to the section“how to reset the computer to start normally after clean boot troubleshooting”.

Good luck!

 

What is the recommended virtual memory amount that I should have?

Currently it's set to automatic.

What doesn't make sense is I'm getting this message when I'm hardly do much on the computer. Like this morning I turned the computer on checked my email and a couple webpages and shut the computer down and got the error message.
I shut my computer down every night so I shouldn't have unexpected build up in virtual memory.

 

I just checked mine, my minimum custom size is the equivalent of the total RAM in my rig (4 GB) - 4000 MB . The maximum size is double my RAM - 8000 MB. I changed to these settings ages ago and haven't had a problem with the sizes chosen, no performance issues, no blue screens regarding, etc.

Regardless, it should be set at least to the 'recommended' setting.

YMMV *Wink

 

I changed my virtual memory manually and it worked for a little bit, however last night when shutting down the computer I got the same exact error message again.

 

https://support.microsoft.com/en-us/kb/2929203

sadly the settings charm has gone so try a different method of shutdown.

http://www.7tutorials.com/7-ways-shu...0-pc-or-device

my money's on WinX

 

Ya I've shutdown with the "power charm" in the start menu and by right clicking and hitting shut down either way doesn't matter I get the message. But thank you for the support article I'm glad it says that it's safe to ignore because I was always worried I was doing some damage to my computer.

 

Just for fun, create a new desktop shortcut and put this in "shutdown.exe /s /t 5" (without quotation marks) see what happens.

 

It doesn't matter which way I shut it down, it has the error message. Even one time my antivirus asked to restart the computer and it did it. It even did it when windows update asked to restart computer.

 

So after 3 years I've finally discovered the problem! Java installed 32 bit software automatically when I went to their website to install/update java years ago. Just recently due to the help of a friend trying to get Minecraft with Mods working it was discovered. Therefore I uninstalled my current Java and downloaded/installed 64-bit Java and haven't had the message since.

I can now mark this thread as solved. Also anyone else with this mysterious problem...here is the solution.