"Stop 0x00000050" in Ntfs.sys Under Stress Accessing Freed FCB

View products that this article applies to.

This article was previously published under Q252192

Expand all | Collapse all

SYMPTOMS

A Windows 2000-based computer that is under stress in Ntfs.sys may display the following error message on a blue screen:

STOP: 0x00000050 (0xe235ed29, 0x00000000, 0xbfef1b96, 0x00000001)
PAGE_FAULT_IN_NONPAGED_AREA

Back to the top

CAUSE

The NTFS driver accessed a File Control Block (FCB) after it was already freed.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 (http://support.microsoft.com/kb/260910/EN-US/ ) How to Obtain the Latest Windows 2000 Service Pack

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 1.

Back to the top

The following sample text is an example of the information you may receive if you use the Kernel Debugger tool to view a memory dump. Note that some of the numeric information may differ based on your computer configuration, but the symbolic information will be similar if not exactly the same.

1: kd> !trap f63dd180
eax=00000103 ebx=e235eca8 ecx=00000000 edx=00000000 esi=00000001
edi=f63dd594 eip=bfef1b96 esp=f63dd1f4 ebp=f63dd200
iopl=0 nv up ei pl zr na po nc
vip=0 vif=0
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
ErrCode = 00000000
bfef1b96 f6838100000004 test byte ptr [ebx+0x81],0x4
1: kd> !k
ChildEBP RetAddr Args to Child
f63dd200 bfef24f9 Ntfs!NtfsOpenExistingAttr+0xb0
f63dd310 bfef4c35 Ntfs!NtfsOpenAttributeInExistingFile+0x3bd
f63dd41c bfeef910 Ntfs!NtfsOpenExistingPrefixFcb+0x339
f63dd754 bfef09fd Ntfs!NtfsCommonCreate+0xf31
f63dd7f4 8041d637 Ntfs!NtfsFsdCreate+0x157
f63dd808 804bde28 ntkrnlmp!IopfCallDriver+0x35
f63dd988 804be35a ntkrnlmp!IopParseDevice+0x9fc
f63dd9c0 8044e03d ntkrnlmp!IopParseFile+0x44
f63dda2c 804d3a21 ntkrnlmp!ObpLookupObjectName+0xe3
f63ddb3c 8049e5f6 ntkrnlmp!ObOpenObjectByName+0xc5
f63ddc10 f66a4c7b ntkrnlmp!IoCreateFile+0x3ec
f63ddc80 f66a6fa4 srv!SrvIoCreateFile+0x322
f63ddd10 f66a73b3 srv!DoDelete+0x1c8
f63ddd84 f66a8f5d srv!BlockingDelete+0xde
f63ddda8 80452614 srv!WorkerThread+0x115

Back to the top