Hello,
The crash signature you describe is consistent with a recursion loop inside adsldpc.dll when the common File Open dialog queries “Previous Versions” or DFS availability against Active Directory. The fact that it only occurs under a domain account and not a local account is a critical indicator: the ADSI LDAP provider is being invoked because the domain context triggers directory lookups, while a local account bypasses that path entirely.
The stack overflow (0xC00000FD) suggests that the LDAP provider is repeatedly traversing attributes or referrals without terminating. This can happen if there are malformed or circular references in AD objects, DFS namespace entries, or Group Policy–applied network share mappings. In practice, the File Open dialog is trying to enumerate shadow copies and DFS links, and if the ADSI provider encounters a recursive referral chain, it will continue until the stack is exhausted.
To diagnose, you should enable LDAP debug logging on the client (HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics) and capture traces with ETW providers for ADSI and comdlg32. This will confirm whether the recursion is triggered by a specific attribute or DFS referral. On the AD side, inspect the DFS namespace configuration and any custom attributes on the user objects. Pay particular attention to msDFS-TargetList and linked attributes that could form loops.
Corrective action usually involves cleaning up DFS referrals or Group Policy drive mappings that point back to themselves or to non‑existent shares. If the recursion is caused by user attributes, you may need to export and review the LDAP object with ldp.exe to identify circular references. Microsoft has documented similar cases where ADSI enters infinite recursion due to misconfigured DFS links or duplicate shadow copy entries.
Since this is not Office code, the resolution will be at the Windows/AD layer. If you can reproduce consistently, I recommend isolating the DFS and GPO configurations applied to the affected domain accounts, and testing with a clean OU policy to confirm whether the recursion disappears. That will narrow down whether the trigger is DFS, Group Policy, or a specific AD attribute.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
DV.