mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 05:13:40 +00:00
Merge branch 'master' into nimishasatapathy-4939910
This commit is contained in:
Asha Iyengar
GitHub
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 03/23/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 03/23/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 03/27/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 04/17/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
@ -19,37 +19,37 @@ Here's a step-by-step guide to adding an Azure Active Directory tenant, adding a
|
||||
> **Note** If you have paid subscriptions to Office 365, Microsoft Dynamics CRM Online, Enterprise Mobility Suite, or other Microsoft services, you have a free subscription to Azure AD. For step-by-step guide to register this free subscription, see [Register your free Azure Active Directory subscription.](#register-your-free-azure-active-directory-subscription)
|
||||
|
||||
|
||||
1. Sign-up for Azure AD tenant from [this website](https://account.windowsazure.com/organization) by creating an administrator account for your organization.
|
||||
1. Sign up for Azure AD tenant from [this website](https://account.windowsazure.com/organization) by creating an administrator account for your organization.
|
||||
|
||||
|
||||
|
||||
2. Enter the information for your organization. Click **check availability** to verify that domain name that you selected is available.
|
||||
2. Enter the information for your organization. Select **check availability** to verify that domain name that you selected is available.
|
||||
|
||||
|
||||
|
||||
3. Complete the login and country information. You must provide a valid phone number, then click **Send text message** or **Call me**.
|
||||
3. Complete the login and country information. Enter a valid phone number, then select **Send text message** or **Call me**.
|
||||
|
||||
|
||||
|
||||
4. Enter the code that you receive and then click **Verify code**. After the code is verified and the continue button turns green, click **continue**.
|
||||
4. Enter the code that you receive and then select **Verify code**. After the code is verified and the continue button turns green, select **continue**.
|
||||
|
||||
|
||||
|
||||
5. After you finish creating your Azure account, you are ready to add an Azure AD subscription.
|
||||
5. After you finish creating your Azure account, you can add an Azure AD subscription.
|
||||
|
||||
If you don't have a paid subscription to any Microsoft service, you can purchase an Azure AD premium subscription. Go to Office 356 portal, <https://portal.office.com/> and then sign in using the admin account that you just created in Step 4 (for example, user1@contosoltd.onmicrosoftcom).
|
||||
If you don't have a paid subscription to any Microsoft service, you can purchase an Azure AD premium subscription. Go to the Office 356 portal at https://portal.office.com/, and then sign in using the admin account that you created in Step 4 (for example, user1@contosoltd.onmicrosoftcom).
|
||||
|
||||
|
||||
|
||||
6. Click **Install software**.
|
||||
6. Select **Install software**.
|
||||
|
||||
|
||||
|
||||
7. In the Microsoft 365 admin center, select **Purchase Services** from the left nagivation.
|
||||
7. In the Microsoft 365 admin center, select **Purchase Services** from the left navigation.
|
||||
|
||||
|
||||
|
||||
8. On the **Purchase services** page, scroll down until you see **Azure Active Directory Premium**, then click to purchase.
|
||||
8. On the **Purchase services** page, scroll down until you see **Azure Active Directory Premium**, then select to purchase.
|
||||
|
||||
|
||||
|
||||
@ -57,7 +57,7 @@ Here's a step-by-step guide to adding an Azure Active Directory tenant, adding a
|
||||
|
||||
|
||||
|
||||
10. After the purchase is completed, you can login to your Office 365 Admin Portal and you will see the **Azure AD** option from the Admin drop-down menu along with other services (SharePoint, Exchange, etc...).
|
||||
10. After the purchase is completed, you can log in to your Office 365 Admin Portal and you will see the **Azure AD** option from the Admin drop-down menu along with other services (SharePoint, Exchange, etc....).
|
||||
|
||||
|
||||
|
||||
@ -71,7 +71,7 @@ If you have paid subscriptions to Office 365, Microsoft Dynamics CRM Online, Ent
|
||||
|
||||
|
||||
|
||||
2. On the **Home** page, click on the Admin tools icon.
|
||||
2. On the **Home** page, select on the Admin tools icon.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 11/19/2019
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 09/18/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 09/18/2018
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 02/22/2018
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
---
|
||||
|
||||
# Azure Active Directory integration with MDM
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 12/18/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 04/16/2020
|
||||
ms.reviewer:
|
||||
|
||||
@ -5,7 +5,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.localizationpriority: medium
|
||||
ms.date: 09/30/2019
|
||||
ms.reviewer:
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 09/18/2017
|
||||
---
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
@ -21,7 +21,7 @@ The CellularSettings configuration service provider is used to configure cellula
|
||||
|
||||
The following image shows the CellularSettings CSP in tree format as used by Open Mobile Alliance Client Provisioning (OMA CP). The OMA DM protocol is not supported with this configuration service provider.
|
||||
|
||||
|
||||
|
||||
|
||||
<a href="" id="dataroam"></a>**DataRoam**
|
||||
<p style="margin-left: 20px"> Optional. Integer. Specifies the default roaming value. Valid values are:</p>
|
||||
@ -53,19 +53,6 @@ The following image shows the CellularSettings CSP in tree format as used by Ope
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
## Related topics
|
||||
|
||||
[Configuration service provider reference](configuration-service-provider-reference.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -11,7 +11,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 06/26/2017
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 02/28/2020
|
||||
---
|
||||
|
||||
|
||||
@ -8,7 +8,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: lomayor
|
||||
author: dansimp
|
||||
ms.date: 12/05/2017
|
||||
---
|
||||
|
||||
|
||||
@ -14,7 +14,7 @@ ms.date: 06/25/2018
|
||||
|
||||
# Diagnose MDM failures in Windows 10
|
||||
|
||||
To help diagnose enrollment or device management issues in Windows 10 devices managed by an MDM server, you can examine the MDM logs collected from the desktop or mobile device. The following sections describe the procedures for collecting MDM logs.
|
||||
To help diagnose enrollment or device management issues in Windows 10 devices managed by an MDM server, you can examine the MDM logs collected from the desktop. The following sections describe the procedures for collecting MDM logs.
|
||||
|
||||
## Download the MDM Diagnostic Information log from Windows 10 PCs
|
||||
|
||||
@ -30,6 +30,27 @@ To help diagnose enrollment or device management issues in Windows 10 devices m
|
||||
|
||||
1. In File Explorer, navigate to c:\Users\Public\Documents\MDMDiagnostics to see the report.
|
||||
|
||||
## Use command to collect logs directly from Windows 10 PCs
|
||||
|
||||
You can also collect the MDM Diagnostic Information logs using the following command:
|
||||
|
||||
```xml
|
||||
mdmdiagnosticstool.exe -area DeviceEnrollment;DeviceProvisioning;Autopilot -cab c:\users\public\documents\MDMDiagReport.cab
|
||||
```
|
||||
- In File Explorer, navigate to c:\Users\Public\Documents\MDMDiagnostics to see the report.
|
||||
|
||||
### Understanding cab structure
|
||||
The cab file will have logs according to the areas that were used in the command. This explanation is based on DeviceEnrollment,DeviceProvisioning and Autopilot areas. It applies to the cab files collected via command line or Feedback Hub
|
||||
|
||||
- DiagnosticLogCSP_Collector_Autopilot_*: Autopilot etls
|
||||
- DiagnosticLogCSP_Collector_DeviceProvisioning_*: Provisioning etls (Microsoft-Windows-Provisioning-Diagnostics-Provider)
|
||||
- MDMDiagHtmlReport.html: Summary snapshot of MDM space configurations and policies. Includes, management url, MDM server device id, certificates, policies.
|
||||
- MdmDiagLogMetadata,json: mdmdiagnosticstool metadata file, contains command line arguments used to run the tool
|
||||
- MDMDiagReport.xml: contains a more detail view into the MDM space configurations, e.g enrollment variables
|
||||
- MdmDiagReport_RegistryDump.reg: contains dumps from common MDM registry locations
|
||||
- MdmLogCollectorFootPrint.txt: mdmdiagnosticslog tool logs from running the command
|
||||
- *.evtx: Common event viewer logs microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin.evtx main one that contains MDM events.
|
||||
|
||||
## Collect logs directly from Windows 10 PCs
|
||||
|
||||
Starting with the Windows 10, version 1511, MDM logs are captured in the Event Viewer in the following location:
|
||||
|
||||
@ -36,31 +36,6 @@ EnrollmentStatusTracking
|
||||
--------HasProvisioningCompleted
|
||||
|
||||
|
||||
./Device/Vendor/MSFT
|
||||
EnrollmentStatusTracking
|
||||
----DevicePreparation
|
||||
--------PolicyProviders
|
||||
------------ProviderName
|
||||
----------------InstallationState
|
||||
----------------LastError
|
||||
----------------Timeout
|
||||
----------------TrackedResourceTypes
|
||||
--------------------Apps
|
||||
----Setup
|
||||
--------Apps
|
||||
------------PolicyProviders
|
||||
----------------ProviderName
|
||||
--------------------TrackingPoliciesCreated
|
||||
------------Tracking
|
||||
----------------ProviderName
|
||||
--------------------AppName
|
||||
------------------------TrackingUri
|
||||
------------------------InstallationState
|
||||
------------------------RebootRequired
|
||||
--------HasProvisioningCompleted
|
||||
|
||||
|
||||
./User/Vendor/MSFT
|
||||
./Device/Vendor/MSFT
|
||||
EnrollmentStatusTracking
|
||||
----DevicePreparation
|
||||
|
||||
@ -11,8 +11,7 @@ ms.author: dansimp
|
||||
ms.topic: article
|
||||
ms.prod: w10
|
||||
ms.technology: windows
|
||||
author: manikadhiman
|
||||
ms.date: 11/19/2020
|
||||
author: dansimp
|
||||
---
|
||||
|
||||
# MDM enrollment of Windows 10-based devices
|
||||
@ -169,10 +168,10 @@ There are a few instances where your device cannot be connected to an Azure AD d
|
||||
|
||||
|
||||
|
||||
## Connect personally-owned devices
|
||||
## Connect personally owned devices
|
||||
|
||||
|
||||
Personally-owned devices, also known as bring your own device (BYOD), can be connected to a work or school account, or to MDM. Windows 10 does not require a personal Microsoft account on devices to connect to work or school.
|
||||
Personally owned devices, also known as bring your own device (BYOD), can be connected to a work or school account, or to MDM. Windows 10 does not require a personal Microsoft account on devices to connect to work or school.
|
||||
|
||||
### Connect to a work or school account
|
||||
|
||||
@ -248,7 +247,7 @@ To create a local account and connect the device:
|
||||
|
||||
After you complete the flow, your device will be connected to your organization’s MDM.
|
||||
|
||||
### Help with connecting personally-owned devices
|
||||
### Help with connecting personally owned devices
|
||||
|
||||
There are a few instances where your device may not be able to connect to work.
|
||||
|
||||
@ -280,7 +279,7 @@ The deep link used for connecting your device to work will always use the follow
|
||||
| accesstoken | Custom parameter for MDM servers to use as they see fit. Typically, this can be used as a token to validate the enrollment request. Added in Windows 10, version 1703. | string |
|
||||
| deviceidentifier | Custom parameter for MDM servers to use as they see fit. Typically, this can be used to pass in a unique device identifier. Added in Windows 10, version 1703. | GUID |
|
||||
| tenantidentifier | Custom parameter for MDM servers to use as they see fit. Typically, this can be used to identify which tenant the device or user belongs to. Added in Windows 10, version 1703. | GUID or string |
|
||||
| ownership | Custom parameter for MDM servers to use as they see fit. Typically, this can be used to determine whether the device is BYOD or Corp Owned. Added in Windows 10, version 1703. | 1, 2, or 3 |
|
||||
| ownership | Custom parameter for MDM servers to use as they see fit. Typically, this can be used to determine whether the device is BYOD or Corp Owned. Added in Windows 10, version 1703. | 1, 2, or 3. Where "1" means ownership is unknown, "2" means the device is personally owned, and "3" means the device is corporate-owned |
|
||||
|
||||
> [!NOTE]
|
||||
> AWA and AADJ values for mode are only supported on Windows 10, version 1709 and later.
|
||||
|
||||
@ -35,29 +35,34 @@ Our analysis of the root causes of crashes indicates the following:
|
||||
- 5 percent are caused by Microsoft code
|
||||
- 15 percent have unknown causes (because the memory is too corrupted to analyze)
|
||||
|
||||
> [!NOTE]
|
||||
> The root cause of Stop errors is never a user-mode process. While a user-mode process (such as Notepad or Slack) may trigger a Stop error, it is merely exposing the underlying bug which is always in a driver, hardware, or the OS.
|
||||
|
||||
## General troubleshooting steps
|
||||
|
||||
To troubleshoot Stop error messages, follow these general steps:
|
||||
|
||||
1. Review the Stop error code that you find in the event logs. Search online for the specific Stop error codes to see whether there are any known issues, resolutions, or workarounds for the problem.
|
||||
|
||||
2. As a best practice, we recommend that you do the following:
|
||||
|
||||
a. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:
|
||||
- [Windows 10, version 2004](https://support.microsoft.com/help/4555932)
|
||||
- [Windows 10, version 1909](https://support.microsoft.com/help/4529964)
|
||||
- [Windows 10, version 1903](https://support.microsoft.com/help/4498140)
|
||||
- [Windows 10, version 1809](https://support.microsoft.com/help/4464619)
|
||||
- [Windows 10, version 1803](https://support.microsoft.com/help/4099479)
|
||||
- [Windows 10, version 1709](https://support.microsoft.com/help/4043454)
|
||||
- [Windows 10, version 1703](https://support.microsoft.com/help/4018124)
|
||||
- [Windows Server 2016 and Windows 10, version 1607](https://support.microsoft.com/help/4000825)
|
||||
- [Windows 10, version 1511](https://support.microsoft.com/help/4000824)
|
||||
- [Windows Server 2012 R2 and Windows 8.1](https://support.microsoft.com/help/4009470)
|
||||
- [Windows Server 2008 R2 and Windows 7 SP1](https://support.microsoft.com/help/4009469)
|
||||
1. Make sure that you install the latest Windows updates, cumulative updates, and rollup updates. To verify the update status, refer to the appropriate update history for your system:
|
||||
|
||||
b. Make sure that the BIOS and firmware are up-to-date.
|
||||
- [Windows 10, version 2004](https://support.microsoft.com/help/4555932)
|
||||
- [Windows 10, version 1909](https://support.microsoft.com/help/4529964)
|
||||
- [Windows 10, version 1903](https://support.microsoft.com/help/4498140)
|
||||
- [Windows 10, version 1809](https://support.microsoft.com/help/4464619)
|
||||
- [Windows 10, version 1803](https://support.microsoft.com/help/4099479)
|
||||
- [Windows 10, version 1709](https://support.microsoft.com/help/4043454)
|
||||
- [Windows 10, version 1703](https://support.microsoft.com/help/4018124)
|
||||
- [Windows Server 2016 and Windows 10, version 1607](https://support.microsoft.com/help/4000825)
|
||||
- [Windows 10, version 1511](https://support.microsoft.com/help/4000824)
|
||||
- [Windows Server 2012 R2 and Windows 8.1](https://support.microsoft.com/help/4009470)
|
||||
- [Windows Server 2008 R2 and Windows 7 SP1](https://support.microsoft.com/help/4009469)
|
||||
|
||||
c. Run any relevant hardware and memory tests.
|
||||
1. Make sure that the BIOS and firmware are up-to-date.
|
||||
|
||||
1. Run any relevant hardware and memory tests.
|
||||
|
||||
3. Run the [Machine Memory Dump Collector](https://home.diagnostics.support.microsoft.com/selfhelp?knowledgebasearticlefilter=2027760&wa=wsignin1.0) Windows diagnostic package. This diagnostic tool is used to collect machine memory dump files and check for known solutions.
|
||||
|
||||
@ -74,7 +79,7 @@ To troubleshoot Stop error messages, follow these general steps:
|
||||
>[!NOTE]
|
||||
>If there are no updates available from a specific manufacturer, it is recommended that you disable the related service.
|
||||
>
|
||||
>To do this, see [How to perform a clean boot in Windows](https://support.microsoft.com/help/929135)
|
||||
>To do this, see [How to perform a clean boot in Windows](https://support.microsoft.com/help/929135).
|
||||
>
|
||||
>You can disable a driver by following the steps in [How to temporarily deactivate the kernel mode filter driver in Windows](https://support.microsoft.com/help/816071).
|
||||
>
|
||||
@ -85,12 +90,18 @@ To troubleshoot Stop error messages, follow these general steps:
|
||||
To configure the system for memory dump files, follow these steps:
|
||||
|
||||
1. [Download DumpConfigurator tool](https://codeplexarchive.blob.core.windows.net/archive/projects/WinPlatTools/WinPlatTools.zip).
|
||||
|
||||
2. Extract the .zip file and navigate to **Source Code** folder.
|
||||
|
||||
3. Run the tool DumpConfigurator.hta, and then select **Elevate this HTA**.
|
||||
3. Select **Auto Config Kernel**.
|
||||
4. Restart the computer for the setting to take effect.
|
||||
5. Stop and disable Automatic System Restart Services (ASR) to prevent dump files from being written.
|
||||
6. If the server is virtualized, disable auto reboot after the memory dump file is created. This lets you take a snapshot of the server in-state and also if the problem recurs.
|
||||
|
||||
4. Select **Auto Config Kernel**.
|
||||
|
||||
5. Restart the computer for the setting to take effect.
|
||||
|
||||
6. Stop and disable Automatic System Restart Services (ASR) to prevent dump files from being written.
|
||||
|
||||
7. If the server is virtualized, disable auto reboot after the memory dump file is created. This lets you take a snapshot of the server in-state and also if the problem recurs.
|
||||
|
||||
The memory dump file is saved at the following locations:
|
||||
|
||||
@ -103,7 +114,7 @@ The memory dump file is saved at the following locations:
|
||||
| Automatic memory dump file | %SystemRoot%\MEMORY.DMP |
|
||||
| Active memory dump file | %SystemRoot%\MEMORY.DMP |
|
||||
|
||||
You can use the Microsoft DumpChk (Crash Dump File Checker) tool to verify that the memory dump files are not corrupted or invalid. For more information, see the following video:
|
||||
You can use the Microsoft DumpChk (Crash Dump File Checker) tool to verify that the memory dump files are not corrupted or invalid. For more information, see the following video:<br/><br/>
|
||||
|
||||
>[!video https://www.youtube.com/embed/xN7tOfgNKag]
|
||||
|
||||
@ -133,31 +144,44 @@ You can use the tools such as Windows Software Development KIT (SDK) and Symbols
|
||||
|
||||
### Advanced debugging references
|
||||
|
||||
[Advanced Windows Debugging](https://www.amazon.com/Advanced-Windows-Debugging-Mario-Hewardt/dp/0321374460)<br>
|
||||
[Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)](/windows-hardware/drivers/debugger/index)
|
||||
- [Advanced Windows Debugging](https://www.amazon.com/Advanced-Windows-Debugging-Mario-Hewardt/dp/0321374460)
|
||||
- [Debugging Tools for Windows (WinDbg, KD, CDB, NTSD)](/windows-hardware/drivers/debugger/index)
|
||||
|
||||
### Debugging steps
|
||||
|
||||
1. Verify that the computer is set up to generate a complete memory dump file when a crash occurs. See the steps [here](troubleshoot-windows-freeze.md#method-1-memory-dump) for more information.
|
||||
|
||||
2. Locate the memory.dmp file in your Windows directory on the computer that is crashing, and copy that file to another computer.
|
||||
|
||||
3. On the other computer, download the [Windows 10 SDK](https://developer.microsoft.com/windows/downloads/windows-10-sdk).
|
||||
|
||||
4. Start the install and choose **Debugging Tools for Windows**. This installs the WinDbg tool.
|
||||
5. Open the WinDbg tool and set the symbol path by clicking **File** and then clicking **Symbol File Path**.<br>
|
||||
a. If the computer is connected to the Internet, enter the [Microsoft public symbol server](/windows-hardware/drivers/debugger/microsoft-public-symbols) (https://msdl.microsoft.com/download/symbols) and click **OK**. This is the recommended method.<br>
|
||||
b. If the computer is not connected to the Internet, you must specify a local [symbol path](/windows-hardware/drivers/debugger/symbol-path).
|
||||
|
||||
5. Open the WinDbg tool and set the symbol path by clicking **File** and then clicking **Symbol File Path**.
|
||||
|
||||
1. If the computer is connected to the Internet, enter the [Microsoft public symbol server](/windows-hardware/drivers/debugger/microsoft-public-symbols) (https://msdl.microsoft.com/download/symbols) and click **OK**. This is the recommended method.
|
||||
|
||||
1. If the computer is not connected to the Internet, you must specify a local [symbol path](/windows-hardware/drivers/debugger/symbol-path).
|
||||
|
||||
6. Click on **Open Crash Dump**, and then open the memory.dmp file that you copied. See the example below.
|
||||
|
||||
|
||||
|
||||
7. There should be a link that says **!analyze -v** under **Bugcheck Analysis**. Click that link. This will enter the command !analyze -v in the prompt at the bottom of the page.
|
||||
|
||||
8. A detailed bugcheck analysis will appear. See the example below.
|
||||
|
||||
|
||||
|
||||
9. Scroll down to the section where it says **STACK_TEXT**. There will be rows of numbers with each row followed by a colon and some text. That text should tell you what DLL is causing the crash and if applicable what service is crashing the DLL.
|
||||
|
||||
10. See [Using the !analyze Extension](/windows-hardware/drivers/debugger/using-the--analyze-extension) for details about how to interpret the STACK_TEXT output.
|
||||
|
||||
There are many possible causes of a bugcheck and each case is unique. In the example provided above, the important lines that can be identified from the STACK_TEXT are 20, 21, and 22:
|
||||
|
||||
(HEX data is removed here and lines are numbered for clarity)
|
||||
|
||||
```
|
||||
```console
|
||||
1 : nt!KeBugCheckEx
|
||||
2 : nt!PspCatchCriticalBreak+0xff
|
||||
3 : nt!PspTerminateAllThreads+0x1134cf
|
||||
@ -214,8 +238,11 @@ We estimate that about 75 percent of all Stop errors are caused by faulty driver
|
||||
Use the following guidelines when you use Driver Verifier:
|
||||
|
||||
- Test any “suspicious” drivers (drivers that were recently updated or that are known to be problematic).
|
||||
|
||||
- If you continue to experience non-analyzable crashes, try enabling verification on all third-party and unsigned drivers.
|
||||
|
||||
- Enable concurrent verification on groups of 10–20 drivers.
|
||||
|
||||
- Additionally, if the computer cannot boot into the desktop because of Driver Verifier, you can disable the tool by starting in Safe mode. This is because the tool cannot run in Safe mode.
|
||||
|
||||
For more information, see [Driver Verifier](/windows-hardware/drivers/devtest/driver-verifier).
|
||||
@ -243,7 +270,7 @@ USER_MODE_HEALTH_MONITOR <br>Stop error code 0x0000009E | This Stop error indic
|
||||
|
||||
This bugcheck is caused by a driver hang during upgrade, resulting in a bugcheck D1 in NDIS.sys (a Microsoft driver). The **IMAGE_NAME** tells you the faulting driver, but since this is Microsoft driver it cannot be replaced or removed. The resolution method is to disable the network device in device manager and try the upgrade again.
|
||||
|
||||
```
|
||||
```console
|
||||
2: kd> !analyze -v
|
||||
*******************************************************************************
|
||||
* *
|
||||
@ -397,12 +424,12 @@ FAILURE_ID_REPORT_LINK: https://go.microsoft.com/fwlink/?LinkID=397724&FailureHa
|
||||
Followup: ndiscore
|
||||
---------
|
||||
```
|
||||
|
||||
### Example 2
|
||||
|
||||
In this example, a non-Microsoft driver caused page fault, so we don’t have symbols for this driver. However, looking at **IMAGE_NAME** and or **MODULE_NAME** indicates it’s **WwanUsbMP.sys** that caused the issue. Disconnecting the device and retrying the upgrade is a possible solution.
|
||||
|
||||
```
|
||||
|
||||
```console
|
||||
1: kd> !analyze -v
|
||||
*******************************************************************************
|
||||
* *
|
||||
|
||||
Reference in New Issue
Block a user