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.

"0x000000D1" and "0x000000C9" Stop errors when Message Queuing moves unsent messages to a dead-letter queue in Windows 7 or in Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenarios.�

Scenario 1
  • You install Microsoft Message Queuing (also known as MSMQ) on a computer that is running Windows 7 or Windows Server 2008 R2.
  • Messages are held in a queue. For example, messages are held in the queue when the applications that receive the messages are unavailable.
  • Dead-letter functionality is enabled on the queue so that Message Queuing can move unsent messages to a private dead-letter queue.
  • A message is not received by an application, and a time-out occurs when the message is sent again.
  • Message Queuing moves the message to the dead-letter queue in a transaction.

In this scenario, the computer crashes. Additionally, you receive a Stop error message that resembles the following:
STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
Notes
  • This Stop error describes a DRIVER_IRQL_NOT_LESS_OR_EQUAL issue.
  • The parameters in the Stop error message vary, depending on the configuration of the computer.
  • Not all "0x000000D1" Stop errors are caused by this issue.

Scenario 2
  • You install Microsoft Message Queuing on a computer that is running Windows 7 or Windows Server 2008 R2.
  • Messages are held in a queue. For example, messages are held in a queue when the applications that receive the messages are unavailable.
  • Dead-letter functionality is enabled on the queue so that Message Queuing can move unsent messages to a private dead-letter queue.
  • You enable the Driver Verifier on the computer.
  • A message is not received by an application, and a time-out occurs when the message is sent again.
  • Message Queuing moves the message to the dead-letter queue in a transaction.

In this scenario, you receive a Stop error message that resembles the following:
STOP: 0x000000C9 (parameter1, parameter2, parameter3, parameter4)
Notes
  • This Stop error describes a DRIVER_VERIFIER_IOMANAGER_VIOLATIONL issue.
  • The parameters in the Stop error message vary, depending on the configuration of the computer.
  • Not all "0x000000C9" Stop errors are caused by this issue.

↑ Back to the top


Cause

This issue is caused by a read access violation that occurs when the messages are sent from outgoing queues to dead-letter queues.

↑ 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 website: 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 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. Additionally, you must have Message Queuing installed.

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 apply this hotfix, 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 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 files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductSR_LevelService branch
    6.1.760 1.21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • 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 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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 sizeDateTime
Mqac.sys6.1.7601.21958142,33605-Apr-201203:19
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTime
Mqac.sys6.1.7601.21958189,44005-Apr-201203:57
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTime
Mqac.sys6.1.7601.21958472,57605-Apr-201203:16


↑ 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 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_ad6305e33e90682416dd1abf36dcc280_31bf3856ad364e35_6.1.7601.21958_none_c60467376f706177.manifest
File versionNot applicable
File size714
Date (UTC)05-Apr-2012
Time (UTC)10:28
File nameX86_microsoft-windows-m..cess-control-driver_31bf3856ad364e35_6.1.7601.21958_none_c96964aba28da580.manifest
File versionNot applicable
File size3,650
Date (UTC)05-Apr-2012
Time (UTC)07:42
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_ce648341f19f347638ca2449c2820cdb_31bf3856ad364e35_6.1.7601.21958_none_c9d69d2f4081958f.manifest
File versionNot applicable
File size718
Date (UTC)05-Apr-2012
Time (UTC)10:28
File nameAmd64_microsoft-windows-m..cess-control-driver_31bf3856ad364e35_6.1.7601.21958_none_2588002f5aeb16b6.manifest
File versionNot applicable
File size3,654
Date (UTC)05-Apr-2012
Time (UTC)08:29
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_0aeb63db23ec71e6a523c679fe25437f_31bf3856ad364e35_6.1.7601.21958_none_748bd9da0c28fea6.manifest
File versionNot applicable
File size716
Date (UTC)05-Apr-2012
Time (UTC)10:27
File nameIa64_microsoft-windows-m..cess-control-driver_31bf3856ad364e35_6.1.7601.21958_none_c96b08a1a28bae7c.manifest
File versionNot applicable
File size3,652
Date (UTC)05-Apr-2012
Time (UTC)08:29

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced, KB2688203

↑ Back to the top

Article Info
Article ID : 2688203
Revision : 2
Created on : 5/25/2012
Published on : 5/25/2012
Exists online : False
Views : 384