After upgrading PC from Windows 8.1 then to 8.1 updated I receive a BSOD RDR_FILE_SYSTEM KSECDD.SYS only when I log onto Domain, I can Log onto the local PC OK and I can log on to the domain OK if I disconnect the network cable first, sign into domain and reconnect cable and all is well until I reboot again, and once again I need to disconnect for the LAN sign and reconnect, any thoughts would be greatly appreciated I have included crash dump report.

Probably caused by : ksecdd.sys ( ksecdd+a0f1 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

RDR_FILE_SYSTEM (27)
    If you see RxExceptionFilter on the stack then the 2nd and 3rd parameters are the
    exception record and context record. Do a .cxr on the 3rd parameter and then kb to
    obtain a more informative stack trace.
    The high 16 bits of the first parameter is the RDBSS bugcheck code, which is defined
    as follows:
     RDBSS_BUG_CHECK_CACHESUP  = 0xca550000,
     RDBSS_BUG_CHECK_CLEANUP   = 0xc1ee0000,
     RDBSS_BUG_CHECK_CLOSE     = 0xc10e0000,
     RDBSS_BUG_CHECK_NTEXCEPT  = 0xbaad0000,
Arguments:
Arg1: 00000000baad0073
Arg2: ffffd000208c5d78
Arg3: ffffd000208c5580
Arg4: fffff801c22910f1

Debugging Details:
------------------

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

• Edited by ZigZag3143xMVP, Moderator Wednesday, April 09, 2014 11:07 AM DBG output removed

I would like to add that I can log on locally (using local user account) on the PC while connected to the same network and no issue, So I thinking its DC/domain/GP related. Also just to add this was never an issue for Windows 7 or 8 only 8.1 and 8.1 update 1.

• Edited by Declan ONeill Wednesday, April 09, 2014 3:32 PM Further information

Ok I have checked this out on the PC with Windows 8.1 update and the rdbss.sys file version is 6.3.9600.16384.

I have now managed to resolve the issue of the RDR_FILE_SYSTEM Ksecdd.sys error BSOD on Windows 8.1 and windows 8.1 update 1, The issue was caused by a mapped drive group policy, I had gone onto our DC (Windows server 2012 R2) went into Group policy Management, expanded Domains and right clicked Default Domain Policy, select edit, I went then to User Configuration, expanded Preferences, expanded Windows settings, then to Drive maps, removed all drive mappings, closed every thing up, applied gpupdate /force in CMD on the Server, and on all Windows 8.1 and Windows 8.1 update 1 machines, and rebooted the PC'S, all PC'S have now for the first time booted up without having to disconnect the network cable or without getting the RDR_FILE_SYSTEM Ksecdd.sys error BSOD. This has fixed our issue which is good news for us, however in large company this could be a bit of an issue if drive mappings are applied via GP. Thank you ZigZag3143x and Kate for your working and helping me on the issue, I had suspected from the start that it was its DC/domain/GP related as logging on as a local user was ok and the issue only appeared when logging onto the domain. I hope what I have done can help others address this issue and if others come forward with the problem that Microsoft may also be able to address the problem, Thanks again everyone for all your help.

• Marked as answer by Declan ONeill Thursday, April 17, 2014 11:39 AM
• Edited by Declan ONeill Thursday, April 17, 2014 12:58 PM

Hi,

We have a windows 2008 32bit server that crashes with BSOD(RDR_FILE_SYSTEM Ksecdd.sys error) whenever an user logs into the server with a network drive mapped. This happens for both local and domain users. Server would not crash if the user has not mapped the drive.

This problem would not happen when the server is not in domain or in network.

Please let me know how to proceed?

Thanks