Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Windows 7 stops responding when it tries to enter hibernation (S4) if the BIOS does not support RTC alarms

Windows 7 stops responding when it tries to enter hibernation (S4) if the BIOS does not support RTC alarms

View products that this article applies to.

Symptoms

Consider the following scenario:
  • The BIOS on a computer that is running Windows 7 does not support real time clock (RTC) alarms.
  • You try to perform a test on the computer by using the Windows Logo Kit (WLK).
  • The computer tries to enter hibernation (S4).
In this scenario, the computer stops responding.

↑ Back to the top

Cause

This issue occurs because a call to the video card stops responding when the Hardware Abstraction Layer (HAL) tries to reset the video card back to VGA mode.

The WLK test enables a flag in the registry if the BIOS does not support RTC alarms. This flag informs the kernel to restart the computer after the computer enters hibernation (S4), instead of powering the computer off. This behavior is required because the computer cannot wake up automatically after it is powered off. Before the kernel restarts the computer, the HAL calls the video card to reset the video card back to VGA mode. This call stops responding because the video card is powered off.

↑ Back to the top

Resolution

Hotfix information

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

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 or Windows 7 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix 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.
Windows 7 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.21xxx    		Windows 7RTMLDR
    6.1.760
    1.21xxx    		Windows 7SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Hal.dll6.1.7600.21085194,41605-Nov-201104:44x86
Halacpi.dll6.1.7600.21085137,07205-Nov-201104:44x86
Halmacpi.dll6.1.7600.21085194,41605-Nov-201104:44x86
Hal.dll6.1.7601.21855194,41605-Nov-201104:35x86
Halacpi.dll6.1.7601.21855137,07205-Nov-201104:35x86
Halmacpi.dll6.1.7601.21855194,41605-Nov-201104:35x86
For all supported x64-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Hal.dll6.1.7600.21085263,02405-Nov-201105:36x64
Hal.dll6.1.7601.21855263,02405-Nov-201105:42x64

↑ Back to the top

Status

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

↑ Back to the top

More Information

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7

Additional files for all supported x86-based versions of Windows 7
File nameX86_16da04f743b53520b99ceb3aaef9bf18_31bf3856ad364e35_6.1.7601.21855_none_f794eaa72f4dbc70.manifest
File versionNot Applicable
File size691
Date (UTC)05-Nov-2011
Time (UTC)15:17
File nameX86_d70648bcf5a2686efe65d6f6dc3eed6b_31bf3856ad364e35_6.1.7600.21085_none_d2301fbe33758f9e.manifest
File versionNot Applicable
File size691
Date (UTC)05-Nov-2011
Time (UTC)15:17
File nameX86_microsoft-windows-hal_31bf3856ad364e35_6.1.7600.21085_none_ab88c732d41b9195.manifest
File versionNot Applicable
File size9,274
Date (UTC)05-Nov-2011
Time (UTC)05:01
File nameX86_microsoft-windows-hal_31bf3856ad364e35_6.1.7601.21855_none_ad8fbdc0d1297393.manifest
File versionNot Applicable
File size9,274
Date (UTC)05-Nov-2011
Time (UTC)05:00
Additional files for all supported x64-based versions of Windows 7
File nameAmd64_480e0fbc56f6b38e6e2d051fd6835b0b_31bf3856ad364e35_6.1.7601.21855_none_45e51fa1a890cafd.manifest
File versionNot Applicable
File size695
Date (UTC)05-Nov-2011
Time (UTC)15:17
File nameAmd64_d16e2d5fd3a56690877802a6fc34e55b_31bf3856ad364e35_6.1.7600.21085_none_816de335c9e00692.manifest
File versionNot Applicable
File size695
Date (UTC)05-Nov-2011
Time (UTC)15:17
File nameAmd64_microsoft-windows-hal_31bf3856ad364e35_6.1.7600.21085_none_07a762b68c7902cb.manifest
File versionNot Applicable
File size7,549
Date (UTC)05-Nov-2011
Time (UTC)05:57
File nameAmd64_microsoft-windows-hal_31bf3856ad364e35_6.1.7601.21855_none_09ae59448986e4c9.manifest
File versionNot Applicable
File size7,549
Date (UTC)05-Nov-2011
Time (UTC)06:10

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2641634
Revision : 1
Created on : 1/7/2017
Published on : 12/14/2011
Exists online : False
Views : 183