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. You receive a Stop error message on a Windows Vista-based computer: "Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000)"

You receive a Stop error message on a Windows Vista-based computer: "Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000)"

Symptoms

Consider the following scenario:
  • You are using a Windows Vista-based computer.
  • The color scheme is set to Windows Aero.
  • You enter your credentials to unlock the computer. When you unlock the computer, you switch from a secure desktop to the default desktop.
  • An event hook is running in the secure desktop. The event hook is registered by using the SetWinEventHook application programming interface (API).
Note A secure desktop appears when the computer is locked. When a secure desktop appears, you can enter your credentials to unlock the computer.

In this scenario, you receive a Stop error message that resembles the following:
Stop 0x00000001 (0x00000000, 0x7FFDC000, 0X0000FFFF, 0X00000000)
Note The Stop error message always has a Stop error code of 0x00000001. Also, the third parameter of the Stop error message is always 0x0000FFFF.

This problem may also occur after you repeatedly put the computer to sleep.

↑ Back to the top

Cause

This problem occurs because of an error in the Win32k.sys file.

↑ Back to the top

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack

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 this specific problem. 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

There are no prerequisites for installing this hotfix.

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 English version of this hotfix 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.
Windows Vista, 32-bit versions
File nameFile versionFile sizeDateTimePlatform
Update.mumNot applicable1,99302-May-200720:09Not applicable
X86_dc9916adfe51d55bbaa692d6cf65991a_31bf3856ad364e35_6.0.6000.20590_none_749f95112e9165d0.manifestNot applicable69402-May-200720:09Not applicable
X86_microsoft-windows-win32k_31bf3856ad364e35_6.0.6000.20590_none_b73584c7b6c6d9c4.manifestNot applicable6,92802-May-200720:17Not applicable
Win32k.sys6.0.6000.205902,027,52002-May-200710:29x86
Windows Vista, 64-bit versions
File nameFile versionFile sizeDateTimePlatform
Amd64_c708689091d397a70cf7dd41a54048fb_31bf3856ad364e35_6.0.6000.20590_none_ccc06f608e910ab8.manifestNot applicable69802-May-200720:10Not applicable
Amd64_microsoft-windows-win32k_31bf3856ad364e35_6.0.6000.20590_none_1354204b6f244afa.manifestNot applicable6,94402-May-200720:21Not applicable
Update.mumNot applicable2,00502-May-200720:10Not applicable
Win32k.sys6.0.6000.205902,749,95202-May-200710:44x64

↑ 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. This problem was first corrected in Windows Vista Service Pack 1.

↑ Back to the top

More Information

For more information about the SetWinEventHook function, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms696160.aspx

↑ Back to the top

Keywords: kb, kbqfe, kbexpertiseinter, kbhotfixserver, kbvistasp1fix, kbautohotfix

↑ Back to the top

Article Info
Article ID : 935936
Revision : 5
Created on : 8/20/2020
Published on : 8/20/2020
Exists online : False
Views : 69