Article ID: 323708 - View products that this article applies to.
This article was previously published under Q323708
If you connect a new device while an infrared device is in communication range or is communicating, the computer may stop responding (hang) or may display an "exception" error message on a blue screen. This problem occurs only with computers that use the National Semiconductor fast infrared (or compatible) hardware driver (Nscirda.sys).
The process that determines which resources to assign to the new device does not give the infrared device driver any time to process accepted incoming data. The device driver eventually runs out of buffers This causes an exception because the driver does not verify that it has run out of buffers.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English 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 ----------------------------------------------------- 29-My-2002 12:10 4.10.1999 23,536 Nscirda.sys
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
To identify which fast infrared port driver you are using: