Event Viewer ?

[saren]

Hello everyone i just win 10 on a new laptop HP i checked EVENT VIEWER and found an error under Applications occuring every few minutes but I don't notice it

What does this mean

Log Name: Application
Source: Application Error
Date: 9/8/2017 11:17:41 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-DVUHDKL
Description:
Faulting application name: ShellExperienceHost.exe, version: 10.0.10240.16401, time stamp: 0x55b1a820
Faulting module name: twinapi.appcore.dll, version: 10.0.10240.16397, time stamp: 0x55af1390
Exception code: 0xc000027b
Fault offset: 0x000000000006687f
Faulting process id: 0x9d0
Faulting application start time: 0x01d328b9cdccce89
Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
Faulting module path: C:\Windows\System32\twinapi.appcore.dll
Report Id: 3f09a50a-d755-45f8-9096-9510c3180a19
Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.10240.16384_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-09-08T15:47:41.000000000Z" />
<EventRecordID>2745</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-DVUHDKL</Computer>
<Security />
</System>
<EventData>
<Data>ShellExperienceHost.exe</Data>
<Data>10.0.10240.16401</Data>
<Data>55b1a820</Data>
<Data>twinapi.appcore.dll</Data>
<Data>10.0.10240.16397</Data>
<Data>55af1390</Data>
<Data>c000027b</Data>
<Data>000000000006687f</Data>
<Data>9d0</Data>
<Data>01d328b9cdccce89</Data>
<Data>C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe</Data>
<Data>C:\Windows\System32\twinapi.appcore.dll</Data>
<Data>3f09a50a-d755-45f8-9096-9510c3180a19</Data>
<Data>Microsoft.Windows.ShellExperienceHost_10.0.10240.16384_neutral_neutral_cw5n1h2txyewy</Data>
<Data>App</Data>
</EventData>
</Event>

 

[Regedit32]

Hi Saren,

Welcome to the Forum.


Most well coded applications today include exception handlers to handle expected / unexpected errors while an application is running.

For example, if you were running a PowerShell Script to fill out a Form, and it used a input dialog to request from a User their Gender, M or F, but the user accidentally taps some other key without noticing, and thus submits erroneous data, the exception handler would kick in to prevent the Script crashing - most likely it would notify you you typed an incorrect letter, and prompt you to enter M or F again.

All kinds of things can cause an application exception of course, including a faulty assembly file (DLL), and incorrect file path to an application, a non matching File Hash (.e.g. using Windows 7 DLL file when an updated version is available for Windows 10), and so forth.

When an application cannot handle the exception a log will be created [ if your Registry is correctly set up ] which Windows uses to monitor dump files after an application has crashed because of an unhandled exception. The one you may well be familiar with if you've used Windows over the years is the pop up dialog that connects to Microsoft to scan for a possible solution or fix to a logged error. In layman's terms this is called a 'Second Chance Exception Handler'. When that 'Second Chance' fails to address the cause of the error Event 1000 is recorded into your Event Viewer.

Taking a look at your particular Event details the faulting application is ShellExperienceHost.exe for Windows 10 Build 10240 and the cause of the exception was its support Assembly: twinapi.appcore.dll located at C:\Windows\System32\ or %systemroot%

Judging by the remaining information the Error was ultimately handled during the Second Exception Handler process - hence it being logged, so in all likelihood you have no further action to take for now. You would need to address it though should you start noticing any Windows Universal apps start failing to run, as some of these require the ShellExperienceHost to be running.

If you open an Administrator: Command Prompt you could run the System File Check to scan for issues and allow Windows to attempt to repair it for you. E.G. SFC /scannow

You could also use the more advanced health scanning and system repair tools like Deployment Image Servicing & Management (DISM). This would require you have a Windows Image file matching your current installed OS, to pull fresh files from to replace any faulty ones.

For more on how to use this tool read: https://technet.microsoft.com/en-us/library/hh824869.aspx


Regards,

Regedit32

 

[saren]

Thank you