SrvFindMfcb Fails to Obtain Lock If the File Name Is NULL

ID: Q191361

The information in this article applies to:

Microsoft Windows NT Server version 4.0

SYMPTOMS

You may receive a STOP 0x0000000A error message that is caused by MFCBLOCK with a random value of a null pointer.

CAUSE

This occurs because a lock is being released when the lock pointer is not initialized. While searching the Master File List to determine whether the named file is already open, SrvFindMfcb returns a NULL value if the file name string is zero length. At this time, the Lock pointer has not been initialized. On returning to the calling function, Windows NT attempts to release this lock, which causes the system to stop responding with the above error message.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. 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://www.microsoft.com/support/supportnet/overview/overview.asp

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


   Date     Time                  Size    File Name    Platform
   ------------------------------------------------------------
   7/15/98  02:32p                466,768 Srv.sys      (Alpha)

Additional query words: DEC Alpha 4000 stop 0xa

Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0
Platform : winnt
Issue type : kbbug