mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-14 14:27:22 +00:00
still trying to fix numbering
This commit is contained in:
parent
6492f795a6
commit
8f27e617bb
@ -96,9 +96,9 @@ If you know that devices are experiencing stop error crashes that do not seem to
|
||||
4. Verify that WER can reach all diagnostic endpoints specified in [Enrolling devices in Windows Analytics](windows-analytics-get-started.md)--if WER can only reach some of the endpoints, it could be included in the device count while not reporting crashes.
|
||||
5. Check that crash reports successfully complete the round trip with Event 1001 and that BucketID is not blank. A typical such event looks like this:
|
||||
|
||||
[](images/event_1001.png)
|
||||
[](images/event_1001.png)
|
||||
|
||||
You can use the following Windows PowerShell snippet to summarize recent occurences of Event 1001. Most events should have a value for BucketID (a few intermittent blank values are OK, however).[](images/app-reliability.png)
|
||||
You can use the following Windows PowerShell snippet to summarize recent occurences of Event 1001. Most events should have a value for BucketID (a few intermittent blank values are OK, however).[](images/app-reliability.png)
|
||||
|
||||
```powershell
|
||||
|
||||
@ -117,8 +117,8 @@ Get-WinEvent -FilterHashTable @{ProviderName="Windows Error Reporting"; ID=1001}
|
||||
|
||||
|
||||
```
|
||||
The output should look something like this:
|
||||
[](images/device-reliablity-event1001-PSoutput.png)
|
||||
The output should look something like this:
|
||||
[](images/device-reliablity-event1001-PSoutput.png)
|
||||
|
||||
6. Check that some other installed device, app, or crash monitoring solution is not intercepting crash events.
|
||||
7. Wait 48 hours for activity to appear in the reports.
|
||||
|
Loading…
x
Reference in New Issue
Block a user