"STOP: 0x00000001" error occurs in Windows Server 2008 R2 or in Windows 7

Article translations Article translations
Article ID: 2203330 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 R2 or Windows 7.
  • You install a third-party application for the multiple transport Media Transfer Protocol (MTP) device or for the Windows Portable Device (WPD) .
  • You connect a MTP or WPD device to the computer for the first time.
In this scenario, you receive the following stop error message:
STOP: 0x00000001 (parameter1, parameter2, parameter3, parameter4)
APC_INDEX_MISMATCH
Note 
  • The parameters in this Stop error message vary, depending on the configuration of the computer.  
  • Not all Stop 0x00000001 error messages are caused by this issue.

CAUSE

This issue occurs because of a race condition in the Compositebus.sys driver.

When a MTP or WPD device connects to the computer for the first time, the composite bus enumerator detects the device and tries to install the WPD composite driver. During the installation process, the third-party application may run a USB device reset command. If the reset command occurs in a certain period, the race condition occurs. This certain period is after the MTP and USB driver or the MTP and IP driver is installed and before the MTP composite multiple transport driver is installed. 

When the race condition occurs, the Compositebus.sys driver incorrectly releases a Windows Driver Foundation (WDF) lock when the Compositebus.sys drive does not have the lock. The APC_INDEX_MISMATCH Stop error occurs when the release function makes the asynchronous procedure call (APC) state of the current thread inconsistent.

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 Server 2008 R2 or Windows 7.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) 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 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • 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 Server 2008 R2 and 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeHashesPlatform
Compositebus.sys6.1.7600.2073531,23216-Jun-201004:05MD5: 44C8853FECD1147C86BBAAE7EE0BE4CF
SHA1: E061D71BC174CE9E1C4FFEA58BCA76F2EED74F9A
x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeHashesPlatform
Compositebus.sys6.1.7600.2073538,91216-Jun-201004:13MD5: 624252B323794238565356BADB094295
SHA1: A30F87883042F4B56868D8859DDCEC4A444AFAEA
x64
For all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeHashesPlatform
Compositebus.sys6.1.7600.2073586,52816-Jun-201003:49MD5: 4F49ACAAD6BE0F0A63EF993A596662C6
SHA1: 444ACA14FFF89085ADA7067F03501B0BAA9D83EF
IA-64

STATUS

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

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
For more information, visit the following Microsoft websites:
General information about the "0x00000001" Stop error
General information about Windows Portable Devices (WPD)
General information about multiple transport devices in Windows 7

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File namePackage_1_for_kb2203330~31bf3856ad364e35~x86~~6.1.1.0.mum
File versionNot applicable
File size1,856
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable
File namePackage_2_for_kb2203330~31bf3856ad364e35~x86~~6.1.1.0.mum
File versionNot applicable
File size1,839
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable
File namePackage_for_kb2203330_rtm~31bf3856ad364e35~x86~~6.1.1.0.mum
File versionNot applicable
File size1,907
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_compositebus.inf_31bf3856ad364e35_6.1.7600.20735_none_b9eedc086911a9ab.manifest
File versionNot applicable
File size2,117
Date (UTC)16-Jun-2010
Time (UTC)06:37
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_compositebus.inf_31bf3856ad364e35_6.1.7600.20735_none_160d778c216f1ae1.manifest
File versionNot applicable
File size2,121
Date (UTC)16-Jun-2010
Time (UTC)07:23
SHA-1 hashNot applicable
MD5 hashNot applicable
File namePackage_1_for_kb2203330~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size2,070
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable
File namePackage_2_for_kb2203330~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size1,849
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable
File namePackage_for_kb2203330_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size2,123
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_compositebus.inf_31bf3856ad364e35_6.1.7600.20735_none_b9f07ffe690fb2a7.manifest
File versionNot applicable
File size2,119
Date (UTC)16-Jun-2010
Time (UTC)07:13
SHA-1 hashNot applicable
MD5 hashNot applicable
File namePackage_1_for_kb2203330~31bf3856ad364e35~ia64~~6.1.1.0.mum
File versionNot applicable
File size1,861
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable
File namePackage_for_kb2203330_rtm~31bf3856ad364e35~ia64~~6.1.1.0.mum
File versionNot applicable
File size1,450
Date (UTC)16-Jun-2010
Time (UTC)22:20
SHA-1 hashNot applicable
MD5 hashNot applicable

Properties

Article ID: 2203330 - Last Review: August 12, 2010 - Revision: 1.0
APPLIES TO
  • Windows 7 Enterprise
  • Windows 7 Home Basic
  • Windows 7 Home Premium
  • Windows 7 Professional
  • Windows 7 Starter
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2203330

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com