Article ID: 320949 - Last Review: February 12, 2007 - Revision: 2.3

PRB: 1394 Devices Stop Responding During Isochronous Transfer Operations

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

This article was previously published under Q320949

Expand all | Collapse all

SYMPTOMS

When a 1394 device performs an isochronous transfer, this operation may be unsuccessful if certain non-page aligned data buffers are used.

Back to the top

If a 1394 device driver passes non-page aligned data buffers at REQUEST_ISOCH_ATTACH_BUFFERS time and uses the DESCRIPTOR_SYNCH_ON_SY flag in the attached isoch descriptors, you may receive an error message on a blue screen. Note that not all non-page aligned buffers cause this behavior. This behavior occurs if Ohci1394.sys does not correctly map the ScatterGather DMA array.

Back to the top

RESOLUTION

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

260910 (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack

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

322389 (http://support.microsoft.com/kb/322389/EN-US/ ) How to Obtain the Latest Windows XP Service Pack

The English-language version of this fix should have the following file attributes or later:

Date         Time   Version        Size    File name     Operating system
-------------------------------------------------------------------------
07-Mar-2002  10:51  5.0.2195.5040  37,712  OHCI1394.SYS  Windows 2000
11-Mar-2002  12:18  5.1.2600.34    55,552  OHCI1394.SYS  Windows XP

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 3 (SP3) and Microsoft Windows XP Service Pack 1 (SP1).

Back to the top