Lemonde
  • Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
6 years ago
We are seeing the following on Windows 10 joined to a domain, but do not see Explorer or the Windows Shell visibly crashing or freezing.

Log Name: Application
Source: Application Error
Date: 9/4/2018 6:37:46 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: %COMPUTERNAME%.domain.suffix
Description:
Faulting application name: ShellExperienceHost.exe, version: 10.0.17134.1, time stamp: 0x5ace103a
Faulting module name: twinapi.appcore.dll, version: 10.0.17134.137, time stamp: 0xb5d50228
Exception code: 0xc000027b
Fault offset: 0x000000000009cad5
Faulting process id: 0x2064
Faulting application start time: 0x01d43e9208fd2c54
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\System32\twinapi.appcore.dll
Report Id: 287b52d9-9f47-4a29-81f0-e341effef46d
Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.17134.112_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App
Event Xml:



1000
2
100
0x80000000000000

8115
Application
%COMPUTERNAME%.domain.suffix



ShellExperienceHost.exe
10.0.17134.1
5ace103a
twinapi.appcore.dll
10.0.17134.137
b5d50228
c000027b
000000000009cad5
2064
01d43e9208fd2c54
C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
C:\Windows\System32\twinapi.appcore.dll
287b52d9-9f47-4a29-81f0-e341effef46d
Microsoft.Windows.ShellExperienceHost_10.0.17134.112_neutral_neutral_cw5n1h2txyewy
App


Sponsor

Want to thank us? Use: Patreon or PayPal or Bitcoins: bc1q4whppe29dw77rm4kv4pln0gqae4yjnxly0dny0hky6yhnafukzjsyrsqhk

All opinions expressed within these pages are sent in by members of the public or by our staff in their spare time, and as such do not represent any opinion held by sircles.net Ltd or their partners.


Lemonde
  • Lemonde
  • 100% (Exalted)
  • Advanced Member Topic Starter
6 years ago
Has no one got any ideas about this one?

Does it matter if explorer is not really crashing?

Is it actually just reopening so fast I don’t see It?

Either way should I just ignore it?