DFS BSOD mup.sys

Discussion in 'File Systems' started by Damian, Nov 12, 2008.

  1. Damian

    Damian Guest

    Hello - I have sucessfully deployed DFS across two w2k3 R2 servers and was
    able to replicate and verify using diagnosic report that data is present on
    both target paths.

    When I now try testing failover by removing primary & active target DFS
    server and then writing a file to the DFS share I get a BSOD ( blue screen of
    death ) pertaining to mup.sys and DFS at address 0xB9DEC894, 0xBDED424,
    0x00000000, 0x00000000. I restarted my windows XP pro system that BSOD'd and
    reconnected the primary system. When I check the DFS info on
    \\testcompany.local\share it says that the active target is now the server
    that was just reconnected. If I check failover by simply disconnecting the
    active target and looking at DFS info for the share, I do see that the active
    target changes. I now can not write files to either active target. Each
    time I do I get the same BSOD. I saw an article that mentioned the length of
    the last component being longer than the DFS share and tested it by trying to
    create a file 1.txt and got the same BSOD.

    Any idea's would help.

    Also, the inital data was on the server in a standard share before I created
    the DFS namespace if that means anything.
    Damian, Nov 12, 2008
    1. Advertisements

  2. Damian

    Damian Guest

    Additional info:

    I added a second xp pro client to the mix and I am not having the same BSOD
    error... great? now I have a problem that I will likely have in the future
    but am unable to make reoccure 100%....
    Damian, Nov 12, 2008
    1. Advertisements

  3. Damian

    Damian Guest

    I attached the dumpchk file from the last crash today from the first system.

    C:\Program Files\Support Tools>dumpchk.exe

    Loading dump file c:\windows\Minidump\Mini111208-04.dmp
    ----- 32 bit Kernel Mini Dump Analysis

    MajorVersion 0000000f
    MinorVersion 00000a28
    DirectoryTableBase 0b1c0620
    PfnDataBase 81fc6000
    PsLoadedModuleList 8055d720
    PsActiveProcessHead 805638b8
    MachineImageType 0000014c
    NumberProcessors 00000002
    BugCheckCode 00000082
    BugCheckParameter1 b9dec894
    BugCheckParameter2 b9ded424
    BugCheckParameter3 00000000
    BugCheckParameter4 00000000
    PaeEnabled 00000001
    KdDebuggerDataBlock 8054d2e0
    MiniDumpFields 00000dff

    ServicePackBuild 00000300
    SizeOfDump 00010000
    ValidOffset 0000fffc
    ContextOffset 00000320
    ExceptionOffset 000007d0
    MmOffset 00001068
    UnloadedDriversOffset 000010a0
    PrcbOffset 00001878
    ProcessOffset 000024c8
    ThreadOffset 00002728
    CallStackOffset 00002980
    SizeOfCallStack 0000104c
    DriverListOffset 00003c60
    DriverCount 000000a4
    StringPoolOffset 00006d10
    StringPoolSize 000016e0
    BrokenDriverOffset 00000000
    TriageOptions 00000041
    TopOfStack a6188fb4
    DebuggerDataOffset 000039d0
    DebuggerDataSize 00000290
    DataBlocksOffset 000083f0
    DataBlocksCount 00000006

    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86

    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Nov 12 11:20:37 2008
    System Uptime: 0 days 0:18:24
    start end module name
    804d7000 806e4000 nt Checksum: 001FBC56 Timestamp: Thu Aug 14
    33:13 2008 (48A3FBD9)

    Unloaded modules:
    ba777000 ba778000 drmkaud.sys Timestamp: unavailable (00000000)
    a6982000 a69ad000 kmixer.sys Timestamp: unavailable (00000000)
    a709d000 a70aa000 DMusic.sys Timestamp: unavailable (00000000)
    a6bf5000 a6c03000 swmidi.sys Timestamp: unavailable (00000000)
    a69ad000 a69d0000 aec.sys Timestamp: unavailable (00000000)
    ba638000 ba63a000 splitter.sys Timestamp: unavailable (00000000)
    ba3c8000 ba3d0000 pinnmb.sys Timestamp: unavailable (00000000)
    ba390000 ba395000 lvuvcflt.sys Timestamp: unavailable (00000000)
    ba1f8000 ba208000 serial.sys Timestamp: unavailable (00000000)
    b8b30000 b8b34000 kbdhid.sys Timestamp: unavailable (00000000)
    ba4b0000 ba4b5000 Cdaudio.SYS Timestamp: unavailable (00000000)
    ba1a8000 ba1b1000 LVUSBSta.sys Timestamp: unavailable (00000000)
    ba138000 ba141000 LVUSBSta.sys Timestamp: unavailable (00000000)
    ba318000 ba321000 LVUSBSta.sys Timestamp: unavailable (00000000)
    ba308000 ba311000 LVUSBSta.sys Timestamp: unavailable (00000000)
    ba2f8000 ba301000 LVUSBSta.sys Timestamp: unavailable (00000000)
    ba2e8000 ba2f1000 LVUSBSta.sys Timestamp: unavailable (00000000)
    ba2d8000 ba2e1000 LVUSBSta.sys Timestamp: unavailable (00000000)

    Finished dump check

    C:\Program Files\Support Tools>
    Damian, Nov 12, 2008
  4. Hello,

    The error described at the Technet link is for issues with DFS Namespaces
    links. Do you get this same behavior if you disable replication?


    John Angel [MSFT], Nov 17, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.