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.

An isochronous data transfer through an IEEE 1394 device suddenly stops in Windows Vista or in Windows Server 2008


View products that this article applies to.

Symptoms

When you perform an isochronous data transfer to or from an IEEE 1394 device on a computer that is running Windows Vista or Windows Server 2008, the isochronous data transfer suddenly stops.

If you have enabled the Driver Verifier for the driver that the device uses to perform the isochronous data transfer, the operating system crashes. Additionally, you receive the following Stop error message on a blue screen:
STOP 0x000000D1 (parameter1, 00000002, 00000001, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL ohci1394.sys

↑ Back to the top


Cause

This problem occurs because of a race condition in the Microsoft IEEE 1394 bus driver stack. The race condition occurs when the bus driver stack attaches and detaches buffers in an isochronous data transfer.

Buffers are attached and detached during an isochronous transfer process. Under a certain timing condition, the isochronous transfer process is complete before the buffer is attached. In this timing condition, the buffer may be detached and freed before the buffer-attachment operation is completed. When this condition occurs, the final status of the attach operation may be written to the buffer structure (ISOCH_DESCRIPTOR) after the buffer has already been freed. This generates a write operation to an invalid memory address.

↑ 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: 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the computer must be running one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista SP2
  • Windows Server 2008
  • Windows Server 2008 SP2

Restart requirement

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

Hotfix replacement

This hotfix replaces the following hotfixes:
  • Hotfix 952824
  • Hotfix 952140
  • Hotfix 958149

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.

For all supported x86-based versions of Windows Vista and of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
1394bus.sys6.0.6001.2244753,37610-Jun-200909:58Not Applicable
Ohci1394.sys6.0.6001.2244762,20810-Jun-200909:58Not Applicable
1394bus.sys6.0.6002.2215053,37610-Jun-200909:42Not Applicable
Ohci1394.sys6.0.6002.2215062,20810-Jun-200909:42Not Applicable

For all supported x64-based versions of Windows Vista and of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
1394bus.sys6.0.6001.2244765,28010-Jun-200910:26x64
Ohci1394.sys6.0.6001.2244772,44810-Jun-200910:27x64
1394bus.sys6.0.6002.2215065,28010-Jun-200910:07x64
Ohci1394.sys6.0.6002.2215072,44810-Jun-200910:07x64

For all supported Itanium-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
1394bus.sys6.0.6001.22447175,61610-Jun-200910:06Not Applicable
Ohci1394.sys6.0.6001.22447172,03210-Jun-200910:06Not Applicable
1394bus.sys6.0.6002.22150175,61610-Jun-200909:56Not Applicable
Ohci1394.sys6.0.6002.22150172,03210-Jun-200909:57Not Applicable

↑ 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

The sequence by which an IEEE 1394 client device driver handles isochronous data buffers during an isochronous data transfer includes the following three phases:

Phase 1: Set up an isochronous transfer
Collapse this tableExpand this table
ActionDetail/Request
Allocate bandwidthREQUEST_ISOCH_ALLOCATE_BANDWIDTH
Allocate a channelREQUEST_ISOCH_ALLOCATE_CHANNEL
Allocate a resource handleREQUEST_ISOCH_ALLOCATE_RESOURCES
Attach buffers to the resource handleREQUEST_ISOCH_ATTACH_BUFFERS
Begin the data transferREQUEST_ISOCH_LISTEN / REQUEST_ISOCH_TALK

Phase 2: Process the isochronous transfer

Note The following four steps are repeated continuously while the isochronous data transfer is in progress.
Collapse this tableExpand this table
ActionDetail/Request
Isoch callbackMicrosoft IEEE 1394 bus driver stack calls the callback routine that is specified in the ISOCH_DESCRIPTOR as soon as the host controller has completed its direct memory access (DMA) transfer.
Detach buffersREQUEST_ISOCH_DETACH_BUFFERS
Detach buffers completionProcess the data from the buffers (for a Listen) or prepare data to be transmitted (for a Talk)
Reattach buffers to continue transferring data REQUEST_ISOCH_ATTACH_BUFFERS

Phase 3: Complete the isochronous transfer
Collapse this tableExpand this table
ActionDetail/Request
Stop the data transferREQUEST_ISOCH_STOP
Detach buffersREQUEST_ISOCH_DETACH_BUFFERS
Deallocate the resource handleREQUEST_ISOCH_FREE_RESOURCES
Free the channelREQUEST_ISOCH_FREE_CHANNEL
Free bandwidthREQUEST_ISOCH_FREE_BANDWIDTH
For more information, 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

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbpubtypekc, kbqfe, kbhotfixserver, KB970076

↑ Back to the top

Article Info
Article ID : 970076
Revision : 2
Created on : 7/8/2009
Published on : 7/8/2009
Exists online : False
Views : 470