Windows Explorer crash

Question

Explorer is crashing, leaving the following in Event Viewer:

Faulting application name: Explorer.EXE, version: 10.0.19041.2913, time stamp: 0x71fdc1b4

Faulting module name: ntdll.dll, version: 10.0.19041.2788, time stamp: 0x2f715b17

Exception code: 0xc000071f

Fault offset: 0x00000000000bac63

Faulting process id: 0x2cac

Faulting application start time: 0x01d9cc4a2c92526c

Faulting application path: C:\WINDOWS\Explorer.EXE

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

Report Id: c04c2758-7096-41c1-84b9-9ab23400b64f

Faulting package full name: 

Faulting package-relative application ID: 

This is recurring issue with w10 through the years.

Debugger reporting in synopsis:

PROCESS_NAME:  explorer.exe

ERROR_CODE: (NTSTATUS) 0xc000071f - A threadpool worker thread enter a callback, which left with preferred languages set.  This is unexpected, indicating that the callback missed clearing them.

EXCEPTION_CODE_STR:  c000071f

ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute [ThreadPoolContext] from Frame:[0] on thread:[2de4]

STACK_TEXT:  
00000000`0295f860 00007ff8`852c3784     : 00000000`00000001 00000000`00000000 00000000`0295fc18 00000000`009979c0 : ntdll!TppCallbackCheckThreadAfterCallback+0x671b7
00000000`0295f980 00007ff8`852c2fd1     : 00000000`00000000 00000000`00000000 00000000`00980b50 00000000`00980b68 : ntdll!TppCallbackEpilog+0x34
00000000`0295faa0 00007ff8`83d87614     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x4a1
00000000`0295fda0 00007ff8`852c26b1     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000000`0295fdd0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

SYMBOL_NAME:  ntdll!TppCallbackCheckThreadAfterCallback+671b7

MODULE_NAME: ntdll

IMAGE_NAME:  ntdll.dll

STACK_COMMAND:  .ecxr ; ~~[0x2de4]s ; .frame 0 ; ~2s; .ecxr ; kb

FAILURE_BUCKET_ID:  APPLICATION_FAULT_HEAP_DUMP_NEEDED_c000071f_ntdll.dll!TppCallbackCheckThreadAfterCallback

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  10.0.19041.3155

FAILURE_ID_HASH:  {7dd08ebc-57e0-3ec5-7896-821d7dbd5cae}

Followup:     MachineOwner

Is there any identified cause after all these years?

Answer 1

Yes, in some cases updates really bring problems for a portion of users, as Windows runs on a huge amount of different hardware configurations this is even imaginable that will happen. A good practice is to create a restore point on a weekly basis so that, in case an update causes a problem, you have the option of going back to a previous stable point of the system.

Usually, when these update issues are identified Microsoft will try to fix them in future updates.

I'm glad that in place upgrade has helped you in this case.

Answer 2

multiple times, with no results whatsoever.

DISM commands and SFC gives a solution to similar problems extremely rarely.

Most commonly come from botched windows updates,,,but nobody can identify exactly what.

Anyhow after 2 in-place upgrades and reinstalls of subsequent windows updates, things seem to be back to normal (sofar).

But all this (and for so many years) is just a testimony that windows updates are out of the full control of Microsoft.

Answer 3

Thanks for the feedback abax2000abax2000. We are a community of Microsoft users just like you, we are not affiliated with Microsoft. Procedures are usually suggested in order of complexity and in most cases the simplest procedures usually solve certain problems. Have you already tried the suggested procedures?

Answer 4

I was not looking exactly for automated replies $5 per piece :-)

I guess that Microsoft can do better

Answer 5

Hi, my name is Anderson Souza, I hope I can help you with your issue.

First, it is important to ensure that all available updates for Windows are installed. To do this go to Start > Settings > Update and Security > Check for updates.

Apply all available updates.

On that same screen, you will see "Show optional updates", in this option you can mark optional driver updates, as the system is showing this instability, updating these drivers can help too.

Also, ensure your apps are up to date. Check the proper procedures at the link below:

https://support.microsoft.com/account-billing/s...

Check if the problem persists. If so, you can try checking the integrity of your system files. Windows has two tools commonly used for this purpose: SFC and DISM.

The System File Checker (SFC) tool built into Windows will scan your Windows system files for corruption or any other changes. If a file has been modified, it will automatically replace that file with the correct version. If the SFC command doesn’t work, you can also try the Deployment Image Servicing and Management (DISM) command to repair the underlying Windows system image.

[ Using System File Checker in Windows ]

System File Checker is a utility in Windows that checks for problems with files on your computer. To run it, follow these steps:

Make sure you've installed the latest updates for Windows, and then restart your machine. To find out more, read Update Windows.

In the search box on the taskbar, type Command Prompt, and right-click or press and hold Command Prompt (Desktop app) from the list of results. Select Run as administrator, and then select Yes.

Type

DISM.exe /Online /Cleanup-image /Restorehealth

(note the space before each "/"), and then press Enter. (Note: This step may take a few minutes to start and up to 30 minutes to complete.)

After you see a message that says "The operation completed successfully," type

sfc /scannow

(note the space between "sfc" and "/") and press Enter.

After you see a message that says, "Verification 100% complete," type exit.