FIX: Isoch Callback Not Called or Error on Blue Screen Occurs When Starting Isoch Stream

Support for Windows XP has ended

Microsoft ended support for Windows XP on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article was previously published under Q330421
This article has been archived. It is offered "as is" and will no longer be updated.
When you start the isoch stream, you may experience one of the following symptoms:
  • On Windows 2000, the isoch callback is not called.
  • On Windows XP, you receive an error on a blue screen.
The problem occurs because the whole isochronous transfer that is requested uses only one isochronous packet.

Under Windows 2000, you do not receive an error on a blue screen. However, the data that is received during the transfer is incorrect, or the driver stops responding because it never received an isoch callback to notify it that the direct memory access (DMA) transfer has been completed.

Under Windows XP, before the DMA transfer starts, during the construction of the DMA scatter/gather list, you receive an error on a blue screen.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 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: 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.The P1 version of this fix has the file attributes (or later) 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 tool in Control Panel.
   Date        Time    Version        Size    File name     Platform   ---------------------------------------------------------------------   03-Oct-2001 13:56   5.0.2195.4455  22,064  sonydcam.sys  Windows 2000   16-Oct-2002 19:40   5.0.2195.6092  37,680  ohci1394.sys  Windows 2000   17-Oct-2002 10:20   5.1.2600.103   55,424  ohci1394.sys  Windows XP SP1   17-Oct-2002 10:27   5.1.2600.1133  55,680  ohci1394.sys  Windows XP SP2				
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

Article ID: 330421 - Last Review: 02/27/2014 21:15:32 - Revision: 2.6

Microsoft Windows 2000, Microsoft Windows XP Professional

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kboswin2000fix kbwin2ksp4fix kbbug kbfix KB330421