Taskbar seems to crash explorer.exe, Start11 causing it?

Start11 crashing explorer?

from Stardock.net Forums

Hi, it seems that explorer.exe sometimes 'suddenly' stops working. In the Windows logs I found this error, posted in XML format:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
  <EventID>1000</EventID>
  <Version>0</Version>
  <Level>2</Level>
  <Task>100</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8000000000000000</Keywords>
  <TimeCreated SystemTime="2024-04-20T18:03:33.1347988Z" />
  <EventRecordID>136725</EventRecordID>
  <Correlation />
  <Execution ProcessID="3724" ThreadID="35664" />
  <Channel>Application</Channel>
  <Computer>LAPTOP-UM0PSS8G</Computer>
  <Security UserID="S-1-5-21-2134702857-1559131089-1620348598-1001" />
  </System>
- <EventData>
  <Data Name="AppName">explorer.exe</Data>
  <Data Name="AppVersion">10.0.22621.3374</Data>
  <Data Name="AppTimeStamp">8e690d6e</Data>
  <Data Name="ModuleName">Taskbar.View.dll</Data>
  <Data Name="ModuleVersion">624.4608.60.0</Data>
  <Data Name="ModuleTimeStamp">65e7946e</Data>
  <Data Name="ExceptionCode">c000027b</Data>
  <Data Name="FaultingOffset">000000000048fe52</Data>
  <Data Name="ProcessId">0x45ec</Data>
  <Data Name="ProcessCreationTime">0x1da90e4486377af</Data>
  <Data Name="AppPath">C:\WINDOWS\explorer.exe</Data>
  <Data Name="ModulePath">C:\WINDOWS\SystemApps\MicrosoftWindows.Client.Core_cw5n1h2txyewy\Taskbar.View.dll</Data>
  <Data Name="IntegratorReportId">2a30563c-de81-4cbe-b09f-caeb2d4ca5bd</Data>
  <Data Name="PackageFullName" />
  <Data Name="PackageRelativeAppId" />
  </EventData>
  </Event>
 
Anybody an idea? Could the cause be Start11?
I use Windows 11 Pro, 23H2, build 22631.3447
It is not the memory, I replaced that last week with brand new DIMM's. (32 Gb memory, seems enough... 😉
I have this problem now for over a year, only on this machine. But it is the only one with Start11, and Fences too btw.
 
Thanks,
Jaap
 
start11 explorer.exe crash windows 11 personal computing
89,336 views 5 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

I was asked if you can review this thread https://support.stardock.com/space/SHC/1387200573/Contacting+Stardock+About+ObjectDock+Issues and create a dump file using WinDBG, as mentioned in that link under "Crash Dumps"

Thank you,

Basj,
Stardock Community Assistant

Object Desktop - Get all of our enhancement utilities in one suite
Reply #3 from Stardock Forums Top

Hi Jaap,

You might also try controlling for Start11 and Fences by seeing if this keeps happening without either running on this computer.  If it does keep happening despite this, you could then try using a Windows Sandbox environment to test a fresh install of Windows (to identify if some other program or setting might be causing the problem).  

https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-overview

If it remains a persistent problem on your end with Start11 and/or Fences running, my take here is that your Windows log might be helpful, but probably not as extensive/useful as the WinDBG process outlined here for Crash Collection.  If you don't mind doing so, I would advise following the link basj has just shared above.

Adam McGuinness
Stardock Customer Support Specialist

Reply #4 from Stardock Forums Top

Quoting saadesch, reply 4

Try turning off Start11 for a while and see if the crashes stop. If they do, you’ve found the cause.

I'll only disagree with the word "cause" here. 

In software (or any science based) testing, "correlation without causation" is a thing you might know.  In other words, even if there is a correlation between variables, this does not mean you can confidently say you've identified the cause of a particular issue. 

My suggestion is simply meant to narrow down the variables that may or may not be in conflict, at which point the crash dump collection process identified above might be more appropriate to investigate further. 

Adam McGuinness
Stardock Customer Support Specialist