This nightmare, has been around since a couple of years ago, when I set up a new computer with Win 11 on it.
But I think I might have discovered the reason for it (will be tested after I restart the system).
Symptoms:
You open up a bunch (around 20 or so) of Explorer folders. At some point, the screen refresh starts dragging its feet, and then Explorer crashes.
I had a dump from it two days ago and one today. They both point to the same spot:
Faulting Thread
| Arg 1 | Arg 2 | Arg 3 | Arg 4 | Source |
|---|
| KERNELBASE!RaiseFailFastException+188 | 0007ff6`ecc3be90 | 0007ffc`15780090 | 0000000`00000000 | 0000000`00000000 | |
| explorer!wil::details::WilDynamicLoadRaiseFailFastException+54 | 0000000`04a7dd30 | 0000000`000009a3 | 0000000`00000000 | 0007ff6`ecac45b6 | |
| explorer!wil::details::WilRaiseFailFastException+17 | 0000000`04a7dd30 | 0000000`04a7e1d0 | 0000000`00000000 | 0007ff6`eca585c0 | |
| explorer!wil::details::WilFailFast+a6 | 0007ff6`eca5cee8 | 0000000`000009a3 | 0007ff6`ecc3be90 | 0007ff6`ecaa83be | |
| explorer!wil::details::ReportFailure_NoReturn<3>+ab | 0000000`00000000 | 0000000`00000001 | 0000000`0001014c | 0007ff6`ecc98188 | |
| explorer!wil::details::ReportFailure_Base<3,0>+30 | 0000000`04790ee8 | 0000000`04a7f2b0 | 0007ff6`ecc98150 | 0000000`00000000 | |
| explorer!wil::details::ReportFailure_Hr<3>+4b | 0000000`01349dd0 | 0007ff6`ecc98150 | 0007ff6`ecc98150 | 0000000`00000018 | |
| explorer!wil::details::in1diag3::FailFast_Unexpected+1b | 0000000`00000113 | 0007ff6`ecc98188 | 0000000`0001014c | 0007ff6`eca4bb4b | |
| explorer!CTray::CheckGDIHandleLimit+de | 0000000`04759cc0 | 0000000`00000000 | 0000000`00000000 | 0007452`15f1b450 | |
| explorer!CTray::v_WndProc+918 | 0000000`00000000 | 0000000`0001014c | 0000000`00000113 | 0000000`00000000 | |
| explorer!CImpWndProc::s_WndProc+86 | 0000000`00000000 | 0000000`04a7fa50 | 0000000`00000001 | 0000000`00000113 | |
| user32!UserCallWinProcCheckWow+356 | 0000000`04a7f988 | 0007ff6`eca5c430 | 0000000`0001014c | 0000000`00000000 | |
| user32!DispatchMessageWorker+1dd | 0000000`04a7f988 | 0007ff6`ecc98150 | 0000000`80004005 | 0000000`80004005 | |
| explorer!CTray::_MessageLoop+27c | 0007ff6`ecc98150 | 0000000`80004005 | 0000000`0404f940 | 0007ff6`ecc98150 | |
| explorer!CTray::MainThreadProc+7b | 0000000`00000000 | 0000000`00000000 | 0000000`80004005 | 0000000`00000000 | |
| SHCore!_WrapperThreadProc+15a | 0000000`00000001 | 0000000`00000000 | 0000000`00000000 | 0000000`00000000 | |
| kernel32!BaseThreadInitThunk+17 | 0000000`00000000 | 0000000`00000000 | 00004f0`fffffb30 | 00004d0`fffffb30 | |
| ntdll!RtlUserThreadStart+2c | 0000000`00000000 | 0000000`00000000 | 0000000`00000000 | 0000000`00000000 | |
Exception Information
In explorer.exe.14540.dmp the assembly instruction at explorer!CTray::CheckGDIHandleLimit+de in C:\Windows\explorer.exe from Microsoft Corporation has caused an unknown exception (0xc0000409) on thread 1
Module Information
Image Name: C:\Windows\explorer.exe Symbol Type: PDB
Base address: 0x00000003`00905a4d Time Stamp: Wed Feb 11 06:25:55 2099
Checksum: 0x00000000`00000000 Comments:
Searching \Windows and any folders with Explorer addons I was using, I never found the function CheckGDIHandleLimit in any file in those folders,
No idea where that comes from but the reason is obvious.
Another few minutes of googling, I got lucky, and I found a plausible solution. We'll see what happens...
The info for this is here:
Welcome to LWC Communities!
I doubled the default number and the future will tell :)
Keep an eye on it, in case it's reset to defaults by an update or some other program.