Problems running with DFS, STILL!

NTFSD
1

I’ve gotten by almost all of my problems with DFS lately, except one.

In W2K server, with SP3, when I run the DFS wizard to make a new local DFS
root, I get through to the end, just before it updates the registry, and
then it blows up, with a 00000028 failure.

I’ve included the analyze output below, in the hopes that someone
knowledgeable about DFS could give me some clue as to why this is
happening.

I’ve set breakpoints all over my code and tried running filemon, etc., and
I can’t seem to get a grip on where or why this is happening.

Here’s the output from Analyze… thanks in advance to anyone who can
help…

Greg

*** Fatal System Error: 0x00000082
(0xBFF666A6,0x8041F79F,0x00000000,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

*******************************************************************************

*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 82, {bff666a6, 8041f79f, 0, 0}

Probably caused by : Dfs.sys ( Dfs!DfsBugCheck+28 )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
80455d74 cc int 3
kd> !analyze -v
*******************************************************************************

*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

DFS_FILE_SYSTEM (82)
Arguments:
Arg1: bff666a6
Arg2: 8041f79f
Arg3: 00000000
Arg4: 00000000

Debugging Details:

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x82

LAST_CONTROL_TRANSFER: from 8042c0c3 to 80455d74

STACK_TEXT:
bb73210c 8042c0c3 00000003 bb732154 bff666a6
nt!RtlpBreakWithStatusInstruction
bb73213c 8042c487 00000003 bff61d00 00000000 nt!KiBugCheckDebugBreak+0x31
bb7324c8 bff66688 00000082 bff666a6 8041f79f nt!KeBugCheckEx+0x390
bb7324ec bff666a6 bff670b9 c0000005 bb73251c Dfs!DfsBugCheck+0x28
bb7324f0 bff670b9 c0000005 bb73251c 804605d7 Dfs!DfsExceptionFilter+0x1c
bb732c0c 8041f79f 8187a520 ff40ea48 ff40ea48
Dfs!DfsFsdFileSystemControl+0x6b
bb732c20 80499e0f ff40eab8 00000000 ff40ea48 nt!IopfCallDriver+0x35
bb732c34 8049a0ed 8187a520 ff40ea48 84fd77b8
nt!IopSynchronousServiceTail+0x60
bb732d00 80497e25 000000b4 00000000 00000000 nt!IopXxxControlFile+0x5e4
bb732d34 80465091 000000b4 00000000 00000000 nt!NtFsControlFile+0x28
bb732d34 77f83da5 000000b4 00000000 00000000 nt!KiSystemService+0xc4
WARNING: Frame IP not in any known module. Following frames may be wrong.
004ef894 0100a04a 004efabc 004efaec 00450044 0x77f83da5
004efab8 77d339c0 000783cc 00078400 00078410 0x100a04a
004efadc 77d93570 01009f9a 004efaf0 00000004 0x77d339c0
004efd48 77d94177 00000000 00000000 000798d4 0x77d93570
004efd64 77d33721 000798d4 000794f0 000798d4 0x77d94177
004efd9c 77d33667 01012cbe 000798d4 004efe40 0x77d33721
004efdf4 77d33579 0000000c 00000000 004efe40 0x77d33667
004efe14 77d3d0dd 000798d4 00000000 004efe40 0x77d33579
004efe44 77d3d013 00000000 000783c0 00079878 0x77d3d0dd
004efe58 77d3ce12 00000000 0000000c 00000001 0x77d3d013
004efe90 77d3cb33 000783a8 00000003 0000000c 0x77d3ce12
00079878 89abcdef 00000040 00000002 00000000 0x77d3cb33
77d3db68 77d3da96 77d5088a 77d3d733 77d3d6c9 0x89abcdef
77d35183 c2042444 3d830004 77d9b084 840f5600 0x77d3da96
2308418b 00000000 00000000 00000000 00000000 0xc2042444

FOLLOWUP_IP:
Dfs!DfsBugCheck+28
bff66688 c9 leave

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Dfs!DfsBugCheck+28

MODULE_NAME: Dfs

IMAGE_NAME: Dfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3c434fa6

STACK_COMMAND: kb

BUCKET_ID: 0x82_Dfs!DfsBugCheck+28

Followup: MachineOwner

2

Although I don’t know much about DFS, from the output I’d reckon that either
you have some problem in your FILE_SYSTEM IRP handling, or that you did not set the
handler for it in the DriverEntry.
Naive, but I’ve seen even more obvious bugs.
BTW, didn’t driver verifier help?

Regards, Dejan.

Greg Pearce wrote:

I’ve gotten by almost all of my problems with DFS lately, except one.

In W2K server, with SP3, when I run the DFS wizard to make a new local DFS
root, I get through to the end, just before it updates the registry, and
then it blows up, with a 00000028 failure.

I’ve included the analyze output below, in the hopes that someone
knowledgeable about DFS could give me some clue as to why this is
happening.

I’ve set breakpoints all over my code and tried running filemon, etc., and
I can’t seem to get a grip on where or why this is happening.

Here’s the output from Analyze… thanks in advance to anyone who can
help…

Greg

*** Fatal System Error: 0x00000082
(0xBFF666A6,0x8041F79F,0x00000000,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

*******************************************************************************

*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 82, {bff666a6, 8041f79f, 0, 0}

Probably caused by : Dfs.sys ( Dfs!DfsBugCheck+28 )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
80455d74 cc int 3
kd> !analyze -v
*******************************************************************************

*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

DFS_FILE_SYSTEM (82)
Arguments:
Arg1: bff666a6
Arg2: 8041f79f
Arg3: 00000000
Arg4: 00000000

Debugging Details:

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x82

LAST_CONTROL_TRANSFER: from 8042c0c3 to 80455d74

STACK_TEXT:
bb73210c 8042c0c3 00000003 bb732154 bff666a6
nt!RtlpBreakWithStatusInstruction
bb73213c 8042c487 00000003 bff61d00 00000000 nt!KiBugCheckDebugBreak+0x31
bb7324c8 bff66688 00000082 bff666a6 8041f79f nt!KeBugCheckEx+0x390
bb7324ec bff666a6 bff670b9 c0000005 bb73251c Dfs!DfsBugCheck+0x28
bb7324f0 bff670b9 c0000005 bb73251c 804605d7 Dfs!DfsExceptionFilter+0x1c
bb732c0c 8041f79f 8187a520 ff40ea48 ff40ea48
Dfs!DfsFsdFileSystemControl+0x6b
bb732c20 80499e0f ff40eab8 00000000 ff40ea48 nt!IopfCallDriver+0x35
bb732c34 8049a0ed 8187a520 ff40ea48 84fd77b8
nt!IopSynchronousServiceTail+0x60
bb732d00 80497e25 000000b4 00000000 00000000 nt!IopXxxControlFile+0x5e4
bb732d34 80465091 000000b4 00000000 00000000 nt!NtFsControlFile+0x28
bb732d34 77f83da5 000000b4 00000000 00000000 nt!KiSystemService+0xc4
WARNING: Frame IP not in any known module. Following frames may be wrong.
004ef894 0100a04a 004efabc 004efaec 00450044 0x77f83da5
004efab8 77d339c0 000783cc 00078400 00078410 0x100a04a
004efadc 77d93570 01009f9a 004efaf0 00000004 0x77d339c0
004efd48 77d94177 00000000 00000000 000798d4 0x77d93570
004efd64 77d33721 000798d4 000794f0 000798d4 0x77d94177
004efd9c 77d33667 01012cbe 000798d4 004efe40 0x77d33721
004efdf4 77d33579 0000000c 00000000 004efe40 0x77d33667
004efe14 77d3d0dd 000798d4 00000000 004efe40 0x77d33579
004efe44 77d3d013 00000000 000783c0 00079878 0x77d3d0dd
004efe58 77d3ce12 00000000 0000000c 00000001 0x77d3d013
004efe90 77d3cb33 000783a8 00000003 0000000c 0x77d3ce12
00079878 89abcdef 00000040 00000002 00000000 0x77d3cb33
77d3db68 77d3da96 77d5088a 77d3d733 77d3d6c9 0x89abcdef
77d35183 c2042444 3d830004 77d9b084 840f5600 0x77d3da96
2308418b 00000000 00000000 00000000 00000000 0xc2042444

FOLLOWUP_IP:
Dfs!DfsBugCheck+28
bff66688 c9 leave

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Dfs!DfsBugCheck+28

MODULE_NAME: Dfs

IMAGE_NAME: Dfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3c434fa6

STACK_COMMAND: kb

BUCKET_ID: 0x82_Dfs!DfsBugCheck+28

Followup: MachineOwner

You are currently subscribed to ntfsd as: xxxxx@alfasp.com
To unsubscribe send a blank email to %%email.unsub%%

–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers.
Alfa File Protector - File protection and hiding library for Win32 developers.

3

Thanks Dejan for the reply. I have run my FSD under driver verifier and
it works correctly. It just doesn’t work when I run the configuration
wizard for DFS… If DFS is disabled, the whole thing works ok.

Thanks again and regards,

Greg

4

I don’t know anything about DFS, but it looks to me like
DfsFsdFileSystemControl
is causing an access violation. Could there possibly be a bad pointer
being passed?

-Jeff

-----Original Message-----
From: Dejan Maksimovic [mailto:xxxxx@alfasp.com]
Sent: Monday, November 11, 2002 4:59 PM
To: File Systems Developers
Subject: [ntfsd] Re: Problems running with DFS, STILL!

Although I don’t know much about DFS, from the output I’d reckon that
either
you have some problem in your FILE_SYSTEM IRP handling, or that you did not
set the
handler for it in the DriverEntry.
Naive, but I’ve seen even more obvious bugs.
BTW, didn’t driver verifier help?

Regards, Dejan.

Greg Pearce wrote:

I’ve gotten by almost all of my problems with DFS lately, except one.

In W2K server, with SP3, when I run the DFS wizard to make a new local DFS
root, I get through to the end, just before it updates the registry, and
then it blows up, with a 00000028 failure.

I’ve included the analyze output below, in the hopes that someone
knowledgeable about DFS could give me some clue as to why this is
happening.

I’ve set breakpoints all over my code and tried running filemon, etc., and
I can’t seem to get a grip on where or why this is happening.

Here’s the output from Analyze… thanks in advance to anyone who can
help…

Greg

*** Fatal System Error: 0x00000082
(0xBFF666A6,0x8041F79F,0x00000000,0x00000000)

Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

****************************************************************************
***

*
*
* Bugcheck Analysis
*
*
*

****************************************************************************
***

Use !analyze -v to get detailed debugging information.

BugCheck 82, {bff666a6, 8041f79f, 0, 0}

Probably caused by : Dfs.sys ( Dfs!DfsBugCheck+28 )

Followup: MachineOwner

nt!RtlpBreakWithStatusInstruction:
80455d74 cc int 3
kd> !analyze -v

****************************************************************************
***

*
*
* Bugcheck Analysis
*
*
*

****************************************************************************
***

DFS_FILE_SYSTEM (82)
Arguments:
Arg1: bff666a6
Arg2: 8041f79f
Arg3: 00000000
Arg4: 00000000

Debugging Details:

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x82

LAST_CONTROL_TRANSFER: from 8042c0c3 to 80455d74

STACK_TEXT:
bb73210c 8042c0c3 00000003 bb732154 bff666a6
nt!RtlpBreakWithStatusInstruction
bb73213c 8042c487 00000003 bff61d00 00000000 nt!KiBugCheckDebugBreak+0x31
bb7324c8 bff66688 00000082 bff666a6 8041f79f nt!KeBugCheckEx+0x390
bb7324ec bff666a6 bff670b9 c0000005 bb73251c Dfs!DfsBugCheck+0x28
bb7324f0 bff670b9 c0000005 bb73251c 804605d7 Dfs!DfsExceptionFilter+0x1c
bb732c0c 8041f79f 8187a520 ff40ea48 ff40ea48
Dfs!DfsFsdFileSystemControl+0x6b
bb732c20 80499e0f ff40eab8 00000000 ff40ea48 nt!IopfCallDriver+0x35
bb732c34 8049a0ed 8187a520 ff40ea48 84fd77b8
nt!IopSynchronousServiceTail+0x60
bb732d00 80497e25 000000b4 00000000 00000000 nt!IopXxxControlFile+0x5e4
bb732d34 80465091 000000b4 00000000 00000000 nt!NtFsControlFile+0x28
bb732d34 77f83da5 000000b4 00000000 00000000 nt!KiSystemService+0xc4
WARNING: Frame IP not in any known module. Following frames may be wrong.
004ef894 0100a04a 004efabc 004efaec 00450044 0x77f83da5
004efab8 77d339c0 000783cc 00078400 00078410 0x100a04a
004efadc 77d93570 01009f9a 004efaf0 00000004 0x77d339c0
004efd48 77d94177 00000000 00000000 000798d4 0x77d93570
004efd64 77d33721 000798d4 000794f0 000798d4 0x77d94177
004efd9c 77d33667 01012cbe 000798d4 004efe40 0x77d33721
004efdf4 77d33579 0000000c 00000000 004efe40 0x77d33667
004efe14 77d3d0dd 000798d4 00000000 004efe40 0x77d33579
004efe44 77d3d013 00000000 000783c0 00079878 0x77d3d0dd
004efe58 77d3ce12 00000000 0000000c 00000001 0x77d3d013
004efe90 77d3cb33 000783a8 00000003 0000000c 0x77d3ce12
00079878 89abcdef 00000040 00000002 00000000 0x77d3cb33
77d3db68 77d3da96 77d5088a 77d3d733 77d3d6c9 0x89abcdef
77d35183 c2042444 3d830004 77d9b084 840f5600 0x77d3da96
2308418b 00000000 00000000 00000000 00000000 0xc2042444

FOLLOWUP_IP:
Dfs!DfsBugCheck+28
bff66688 c9 leave

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: Dfs!DfsBugCheck+28

MODULE_NAME: Dfs

IMAGE_NAME: Dfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3c434fa6

STACK_COMMAND: kb

BUCKET_ID: 0x82_Dfs!DfsBugCheck+28

Followup: MachineOwner

You are currently subscribed to ntfsd as: xxxxx@alfasp.com
To unsubscribe send a blank email to %%email.unsub%%

–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers.
Alfa File Protector - File protection and hiding library for Win32
developers.

You are currently subscribed to ntfsd as: xxxxx@concord.com
To unsubscribe send a blank email to %%email.unsub%%

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
the latest virus scan software available for the presence of computer
viruses.
**********************************************************************

5

Does DV run at that time? I.e. when you run the DFS wizard?

Greg Pearce wrote:

Thanks Dejan for the reply. I have run my FSD under driver verifier and
it works correctly. It just doesn’t work when I run the configuration
wizard for DFS… If DFS is disabled, the whole thing works ok.

Thanks again and regards,

Greg

You are currently subscribed to ntfsd as: xxxxx@alfasp.com
To unsubscribe send a blank email to %%email.unsub%%

–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers.
Alfa File Protector - File protection and hiding library for Win32
developers.

6

It doesn’t seem to make any difference if DV is running or not - it still
blue-screens when I run the Wizard.

Thanks,

Greg

7

Hi Jeff - thanks for the reply - I cant seem to figure out what IRP/call
from DFS is causing this. I turned on tracing in my FSD I just dont see
it. I was hoping someone who can read assembler better than me and knows
DFS internals could tell me what DFS is trying to do when it blows up :wink:

Thanks again

Greg

8

It mustn’t behave otherwise, but with DV it might give a more informative
bug code.

It doesn’t seem to make any difference if DV is running or not - it still
blue-screens when I run the Wizard.

–
Kind regards, Dejan M. www.alfasp.com
E-mail: xxxxx@alfasp.com ICQ#: 56570367
Alfa File Monitor - File monitoring library for Win32 developers.
Alfa File Protector - File protection and hiding library for Win32
developers.