Consider the following scenarios in a Windows 8 installation that is Unified Extensible Firmware Interface (UEFI)-compliant and that has a UEFI/GPT configuration.

Scenario 1

• The Turn on fast startup power option is enabled.
• You shut down Windows 8 and restart the computer normally.
• When the computer restarts, Windows 8 is forcibly turned off or reset.

Scenario 2

• The Turn on fast startup power option is either disabled or enabled.
• You perform a normal hibernatation operation.
• When the computer restarts, Windows 8 is forcibly turned off or reset.

In either scenario, if you try to restart Windows 8 again, the system freezes before the desktop is generated. At that point, the screen is either blank or displays only a blinking cursor.

Cause:

If you restart the computer after it is forcibly turned off, Windows 8 tries to use the fast startup method. When this occurs, the system determines that the previous restart attempt was unsuccessful, and then it tries to restart by using the full startup method. However, this full startup attempt fails because of an access violation that is caused by memory corruption.

Resolution:

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next P1 that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The P1 version of this P2 has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Workaround:

To recover a computer that cannot start, use one of the following workarounds.

Important These workarounds may not recover your system or restore your computer to a functional state.

• Workaround 1
  1. Start the UEFI user interface. The method to start this interface varies among computers. For more information, refer to the documentation for your environment.
  2. Select the Compatibility Support Module option.
     
     Note: This is a hybrid legacy mode.
  If the Compatibility Support Module option is not available in step 2, try Workaround 2.
• Workaround 2
  Note: This workaround is intended to be used only in a system that has the Intel Smart Response Technology (SRT) feature enabled on a computer that uses Intel Rapid Storage Technology (RST).
  1. Start the UEFI user interface.
     
     Note: The method to start this interface varies among computers. For more information, refer to the UEFI documentation.
  2. Click System Setup on the Startup Option menu.
  3. In the System Setup screen, click the Advancedtab.
  4. CLick Intel Rapid Storage Technology (RST).
  5. Select the RST driver. The version number starts with 11.5.x.xxxx or 11.6.x.xxxx.
  6. Browse to the disk ID that has a number.
     
     Note: This ID represents the boot disk.
  7. Select the disk from step 6, and then select the option to synchronize data. When the synchronization is finished, select the option to remove acceleration.
  8. Accept the warning about data loss.
  9. Restart the computer.
     
     Note: You do not have to back out of the menus in order to save the changes.

Status:

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

 

Related Topics :