The following table describes some log files and how to use them for troubleshooting purposes:
@@ -149,47 +149,72 @@ Setupmem.dmp: If OS bugchecks during upgrade, setup will attempt to extract a mi
Setupapi: Device install issues – 0x30018
Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.
-
-
-
-
-## Common error codes and resolution procedures
-A common result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, except for the SafeOS phase. Therefore, it can be associated with several different extend codes. A result code of 0xC1900101 usually indicates that an incompatible driver is present, which can cause blue screens, system hangs, and unexpected reboots. Analysis of all available supplemental log files is typically helpful in indentifying the incompatible driver. You can also attempt to run setup in the absence of drivers by performing a [clean boot](https://support.microsoft.com/en-us/kb/929135) before initiating the upgrade process.
-
-
-| Error code
- | Cause
- | Mitigation
- |
-
-| 0xC1900101 - 0x20017 |
-A driver has caused an illegal operation and Windows was not able to migrate the driver, resulting in a rollback of the operating system. |
-To resolve this issue:
+## Common errors
+A common result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the SafeOS phase. 0xC1900101 usually indicates that an incompatible driver is present, which can cause blue screens, system hangs, and unexpected reboots.
+
+Analysis of all available supplemental log files is typically helpful in indentifying the incompatible driver. You can also attempt to run setup in the absence of drivers by performing a [clean boot](https://support.microsoft.com/en-us/kb/929135) before initiating the upgrade process. The following general procedures can be used to diagnose a result code of 0xC1900101 during different phases of Windows Setup:
+
+
+| 0xC1900101 - 0x20017 |
+
+
+| Cause
+ | A driver has caused an illegal operation.
+
Windows was not able to migrate the driver, resulting in a rollback of the operating system.
+ |
+ |
+
+
+| Mitigation
+ |
1. Make sure all that drivers are updated.
-2. Open the Setuperr.log and Setupact.log files under the %windir%\Panther directory, and then locate the problem drivers. Refer: [Understanding Failures and Log Files](https://technet.microsoft.com/en-us/library/ee851579.aspx)
+2. Open the Setuperr.log and Setupact.log files under the %windir%\Panther directory, and then locate the problem drivers.
+
For more information, see [Understanding Failures and Log Files](https://technet.microsoft.com/en-us/library/ee851579.aspx).
3. Update or uninstall the problem drivers.
- |
-
+
+ |
+
+
- |
-| 0xC1900101 - 0x30018 |
-A device driver has stopped responding to setup.exe during the upgrade process. |
-Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display. Contact your hardware vendor to obtain updated device drivers.
- Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
- |
-
+
+| 0xC1900101 - 0x30018 |
+
+
+| Cause
+ | | A device driver has stopped responding to setup.exe during the upgrade process.
+ |
+ |
+
+
+| Mitigation
+ |
+Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
+
Contact your hardware vendor to obtain updated device drivers.
+
Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
+ |
+ |
+
+
-
-| 0xC1900101 - 0x4000D |
-A driver configuration issue occurred during the Windows setup process and a rollback occurred. |
-Review the rollback log and determine the stop code. The rollback log is located in the **C:\$Windows.~BT\Sources\Panther** folder. Look for text similar to the following:
-
-
Info SP Crash 0x0000007E detected
+
+| 0xC1900101 - 0x4000D |
+
+
+| Cause
+ | | A rollback occurred due to a driver configuration issue.
+ |
+ |
+
+
+| Mitigation
+ | Review the rollback log and determine the stop code.
+
The rollback log is located in the **C:\$Windows.~BT\Sources\Panther** folder. Look for text similar to the following:
+ Info SP Crash 0x0000007E detected
Info SP Module name :
Info SP Bugcheck parameter 1 : 0xFFFFFFFFC0000005
Info SP Bugcheck parameter 2 : 0xFFFFF8015BC0036A
@@ -202,31 +227,39 @@ A common result code is 0xC1900101. This result code can be thrown at any stage
Typically there is a a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:
1. Make sure you have enough disk space.
-2. If a driver is identified in the bug check message, disable the driver, or check with the manufacturer for driver updates.
+2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
3. Try changing video adapters.
4. Check with your hardware vendor for any BIOS updates.
5. Disable BIOS memory options such as caching or shadowing.
- |
-
-
-| 0xC1900101 - 0x40017 |
-Windows 10 upgrade fails after the second reboot, which is most like to be caused by a faulty driver, for example antivirus filter drivers or encryption drivers. |
-Clean boot into Windows, and then attempt the upgrade to Windows 10.
+
+ |
+ |
+
+
+
+
+| 0xC1900101 - 0x40017 |
+
+
+| Cause
+ | Windows 10 upgrade failed after the second reboot.
+
This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers.
+ |
+ |
+
+
+| Mitigation
+ | Clean boot into Windows, and then attempt the upgrade to Windows 10.
For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135).
Ensure you select the option to "Download and install updates (recommended)."
- |
-
-
-
-| 0x8007002C - 0x4000D |
-The user cancelled an interactive dialog. |
-Start the upgrade process again again. |
-
-
-
+ |
+
+
+
+
## Common errors I've edited but don't know how to classify
|