Event Not Reset in ScsiClassGetInquiryData in SCSI Class Driver

Article translations Article translations
Article ID: 236330 - View products that this article applies to.
This article was previously published under Q236330
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

Symptoms

When you are using some third-party SCSI filter drivers, you may receive error messages that refer to either the SCSI class drivers or the third-party filter driver. The exact stop code will vary, with "STOP 0xA" and "STOP 0x1E" being the most common.

Cause

The Windows NT SCSI Class driver does not properly handle a notification event when sending SCSI_IOCTL_GET_INQUIRY_DATA, so an underlying filter driver that handles the request asynchronously may cause an error message on a blue screen (STOP screen).

This happens because the event being used to signal that the asynchronous request has been fulfilled is not reset properly on a retry of the request, causing the next I/O packet to be set before the request is finished.

Resolution

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
  • Windows Service Pack Center -or-

  • 152734how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Status

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Properties

Article ID: 236330 - Last Review: November 2, 2013 - Revision: 3.0
Applies to
  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT Workstation 4.0 Developer Edition
Keywords: 
kbnosurvey kbarchive kbbug kbfix kbqfe KB236330

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com