Explorer crashes whenever I shut down windwos 10TP

Each time I shut down Windows 10 from the Start menu I get an explorer.exe crash with the following message: "The instruction at 0x6a301c8f referenced memory at 0x00000000. The memory cannot be read. Click OK to terminate the program." After I click on OK, Windows 10 shuts down.

This may or may not matter: I'm running Windows 10 inside a VMware Player virtual machine.

Why does explorer.exe crash when I try to shut down Windows 10?

Original Title: Explorer.exe Crashes When Shutting Down

 

Question Info


Last updated May 15, 2019 Views 5,298 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello,

Thank You for posting your query to Microsoft Community.

Did you make any changes on the computer prior to the issue?

One reason you might be getting this error is if your virtual memory settings are very low or due to third party application conflict or system files corruption.

                                                                     

To work with the issue, I would suggest you to follow the steps mentioned:

 

Method 1: Run the System Maintenance Troubleshooter.

 

  1. Press Windows + W, click apps if it is not selected
  2. Type control panel and hit enter
  3. If the icons are not displayed in large size, click on category which is above the list and select large icons
  4. Now click on troubleshooting
  5. Now click system and security and click Run maintenance tasks and proceed further.

                            

Method 2:

I would suggest you to put the computer in Clean Boot state to see if there is any software conflict as clean boot helps in eliminating software conflicts.

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

Note: After performing the troubleshooting steps in clean boot follow the link below and expand “How to return Windows to a normal startup mode

https://support2.microsoft.com/kb/331796?wa=wsignin1.0

Note: The troubleshooting steps in the above link are meant for windows 8, however, you can use the same for windows 10 tech preview as well.

Method 3:

Run the system file checker tool which is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files.

Use the System File Checker tool to repair missing or corrupted system files

http://support.microsoft.com/kb/929833

 

Note: The troubleshooting steps in the above link are meant for windows 8, however, you can use the same for windows 10 tech preview as well.

 

Hope the information is helpful. Please write to us if you still face issues.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Each time I shut down Windows 10 from the Start menu I get an explorer.exe crash with the following message: "The instruction at 0x6a301c8f referenced memory at 0x00000000. The memory cannot be read. Click OK to terminate the program." After I click on OK, Windows 10 shuts down.

This may or may not matter: I'm running Windows 10 inside a VMware Player virtual machine.

Why does explorer.exe crash when I try to shut down Windows 10?

Original Title: Explorer.exe Crashes When Shutting Down

I get the same. I'm using Hyper-V as the Vm software.

Alienwar
Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz
Dual NVIDIA(R) GeForce(R) GTX 860M graphics wit

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Our problem might indeed be caused by the fact that we're running W10TP in a virtual machine. Microsoft should have anticipated that users would run the TP inside a virtual machine. Then again, at this point Windows 10 is still a work in progress, so the problem may resolve itself in later builds.

BTW: I tried to get more info on the error from Event Viewer, but when I try to start Event Viewer in W10TP I see instead a window that says "Ooops, that didn't work!"

In any case, the crash doesn't cause any other problems for W10.

___________________________________________________
Just a regular guy, with no fancy titles or boasts.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Mine does this on a surface pro (not a virtual machine, no non-Microsoft apps installed).  Has since I first installed it.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

It also happens here when I shut down, sometimes when I log off as well.

Clean install on an Acer Aspire One Netbook, No VM

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi,

Thank you for replying to the post.

 

Microsoft recently released an updated build of Windows 10 Technical Preview. Build 9860 introduces new features such as the Notification Center, improvements to navigating Virtual Desktops and smoother window effects to name a few.

 

You can try installing the new build with improved features and let us know if the issue reoccurs. follow the link below:

 

How to install Windows 10 build 9860

http://answers.microsoft.com/en-us/windows/wiki/windows_tp-windows_install/how-to-install-windows-10-build-9860/d8c389ae-31c4-42a2-97df-4815d82dd2b6

 

Hope this is helpful. Feel free to writes to us for further assistance.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi ,

I would suggest you to post your question in the TechNet Forums, where we have support professionals who are well equipped with the knowledge on Virtual Machine issues.  Please visit the link.
 
https://social.technet.microsoft.com/Forums/en-US/home?forum=virtualmachinemgrvmware&filter=alltypes&sort=lastpostdesc

Please reply if you have any questions.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

What programs are you running in Windows 10?

One of those programs is attempting to access a null pointer during shutdown.  That is what causes that error.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I have this problem too, and I'm not running from a VM.

I checked event viewer and I have this system error event there:

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          08/06/2015 20:10:12
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          LOCAL SERVICE
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{D63B10C5-BB46-4990-A94F-E40B9D520160}
 and APPID 
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

...

That AppId is RuntimeBroker (the way I found that out was following the steps described here: https://social.technet.microsoft.com/Forums/systemcenter/en-US/dfc465bc-7bbd-483e-b98b-2ba56fa98313/the-applicationspecific-permission-settings-do-not-grant-local-launch-permission-for-the-com-server?forum=configmgrgeneral):

1. Click Start -> Run -> Type -> dcomcnfg, expand Component Services -> Computers -> My Computer -> DCOM Config.
2. Click View -> Detail -> Now you will get Application Name and Application ID in right side.
3. Scroll down and find the application ID {AD65A69D-3831-40D7-9629-9B0B50A93843} -> Right Click -> Properties and select the Security tab.
3. Click Customize under "Launch & Activation Permission" -> click Edit -> Add in the account NT AUTHORITY\SYSTEM and set local launch and local activation.
4. Restart the application Service linked to this Application ID or restart the server and monitor

However, I can't change any options in dcomcnfg because everything is grayed out. Even if I run it as administrator.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

My build is 10130

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.