About 1 in 50 times I get a BSOD in Fastfat!FatOpenExistingFcb+a1 after
formating DVD-RAM media on Windows XP with my filesystem and attempting to
remount (fastfat will attempt to claim this type of media; as will my
filesystem). If I’m seeing the dump correctly, the BSOD was actually on a
“je” command. Is that possible? (The target memory to the je was not
paged out.)
Here’s the dump…
Microsoft (R) Windows Debugger Version 6.1.0017.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Windows XP Kernel Version 2600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpclient.010817-1148
Kernel base = 0x804d2000 PsLoadedModuleList = 0x80547b28
Debug session time: Thu Jan 23 00:18:38 2003
System Uptime: 0 days 3:33:58.312
Loading Kernel Symbols
…
Loading unloaded module list
…
Loading User Symbols
PEB is paged out (Peb = 7ffdf00c). Type “.hh dbgerr001” for details
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {8735807c, 0, f994abe9, 0}
Probably caused by : Fastfat.sys
Followup: maybe_
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except,
it must be protected by a Probe. Typically the address is just plain bad
or it
is pointing at freed memory.
Arguments:
Arg1: 8735807c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: f994abe9, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
READ_ADDRESS: 8735807c Nonpaged pool
FAULTING_IP:
Fastfat!FatOpenExistingFcb+a1
f994abe9 0f84985b0000 je Fastfat!FatOpenExistingFcb+0xa8
(f9950787)
MM_INTERNAL_CODE: 0
IMAGE_NAME: Fastfat.sys
MODULE_NAME: Fastfat
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
TRAP_FRAME: f5eba698 – (.trap fffffffff5eba698)
ErrCode = 00000000
eax=00000001 ebx=810d6008 ecx=00000000 edx=815485f8 esi=e1d94688
edi=e1d94780
eip=f994abe9 esp=f5eba70c ebp=f5eba764 iopl=0 nv up ei ng nz ac pe
cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010293
Fastfat!FatOpenExistingFcb+a1:
f994abe9 0f84985b0000 je Fastfat!FatOpenExistingFcb+0xa8 (f9950787)
[br=0]
Resetting default context
LAST_CONTROL_TRANSFER: from f994ae56 to f994abe9
STACK_TEXT:
f5eba764 f994ae56 810d6008 815485f8 8163a118
Fastfat!FatOpenExistingFcb+0xa1
f5eba9c0 f9944f5e 810d6008 81611c68 00200064 Fastfat!FatCommonCreate+0x7ce
f5ebaa04 804ee04f 8163a020 81611c68 00000001 Fastfat!FatFsdCreate+0x52
f5ebaa14 f997e51a 81611c78 817349c8 815485f8 nt!IopfCallDriver+0x31
f5ebaa60 804ee04f 81675b18 815485f8 81611c68 sr!SrCreate+0x12a
f5ebaa70 80576663 8176bdb0 80f96524 f5ebac18 nt!IopfCallDriver+0x31
f5ebab54 8057269c 8176bdc8 00000000 80f96480 nt!IopParseDevice+0xa17
f5ebabd8 80574d6b 00000000 f5ebac18 00000040 nt!ObpLookupObjectName+0x56a
f5ebac2c 80576a10 00000000 00000000 f5ebac01 nt!ObOpenObjectByName+0xe9
f5ebaca8 80576ac1 05ebe864 80100080 05ebe804 nt!IopCreateFile+0x407
f5ebacf0 8057af0d 05ebe864 80100080 05ebe804 nt!IoCreateFile+0x36
f5ebad30 804d6e91 05ebe864 80100080 05ebe804 nt!NtCreateFile+0x2e
f5ebad30 7ffe0304 05ebe864 80100080 05ebe804 nt!KiSystemService+0xc4
05ebe85c 00000000 00000000 00000000 00000000
SharedUserData!SystemCallStub+0x4
FOLLOWUP_NAME: maybe_
STACK_COMMAND: .trap fffffffff5eba698 ; kb
BUCKET_ID: 0x50_IMAGE_Fastfat.sys_DATE_8_17_2001