Microsoft KB Archive/236330

= Event Not Reset in ScsiClassGetInquiryData in SCSI Class Driver =

Article ID: 236330

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q236330



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.



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:


 * http://www.microsoft.com/windows/servicepacks/ -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/directory/overview.asp

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.

Keywords: kbbug kbfix kbqfe KB236330

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.