"0xD1" Stop error when computer is restarted by the Sysprep.exe process in Windows 8.1 or Windows Server 2012 R2

Consider the following scenario:

• You have a computer that is running Windows 8 or Windows Server 2012.
• You upgrade the computer to Windows 8.1 or Windows Server 2012 R2.
• As part of the upgrade process, the Sysprep.exe process is run to generalize the system.
• The system restarts after the process.

In this scenario, the upgrade process stops unexpectedly, and you receive a Stop error message that resembles the following:Notes

• The Stop error 0x0000009F describes a DRIVER_IRQL_NOT_LESS_OR_EQUAL issue.
• The parameters in this Stop error message vary, depending on the configuration of the computer.
• Not all "0x000000D1" Stop errors are caused by this issue.

This issue occurs because of an access violation on the athwnx.sys file.

How to obtain this update

This update is automatically applied during the upgrade using Dynamic Update. Therefore, you must connect your computer to the Internet during the installation.�

Prerequisites

To apply this update, you must be running Windows 8.1 or Windows Server 2012 R2.

Registry information

To apply this update, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

The global version of this update installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

For all supported x86-based versions of Windows 8.1

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: