locked
Application Error: Explorer.exe; faulting module name: fdWNet.dll_unloaded RRS feed

  • General discussion

  • I am using Windows 2008 R2 RDS as a Terminal server.

    Terminal Server Users sessions often experience explorer hangs issues and ask to "close the program,restart the program; When visiting the Event log it gives the following;

    Event ID:      1000
    Task Category: (100)

    Description:
    Faulting application name: Explorer.EXE, version: 6.1.7601.17567, time stamp: 0x4d672ee4 faulting module name: fdWNet.dll_unloaded, version: 0.0.0.0, time stamp: 0x4a5bdf0f
    Exception code: 0xc0000005
    Fault offset: 0x000007fefbad2d99
    Faulting process id: 0x48b8
    Faulting application start time: 0x01cd955e2c621a9c
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: fdWNet.dll
    Report Id: 62100df1-019d-11e2-a95d-d067e5ef9d19

    Will any body help.?

    thanks in Advance!

    Regards,

    prakash

    Tuesday, September 18, 2012 3:06 PM

All replies

  • Hi,

    Typically this problem is caused by non- Microsoft Explorer Shell Extensions and you can use “AutoRuns” for Windows to troubleshoot. You can disable all of the Non-Microsoft shell extensions and test to see

    if the problem occurs and then re-enable them 1 by 1 to see which one causes the problem.

    Download “AutoRuns” For Windows from the Microsoft TechNet Site

    http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

    1. Start Autoruns

    2. Click Options / Check Hide Microsoft Entries

    3. Press F5 or click the Refresh Icon

    4. Click on the Explorer Tab

    5. Uncheck All items in this List

    6. Exit Autorun

    7. Logoff and Logon to the Computer

    8. Test Windows Explorer


    Spencer

    TechNet Community Support

    Thursday, September 20, 2012 9:21 AM
  • Hi Spencer,

    Thanks for your reply!

    That seems to be the list of autoruns which all from signed vendors

    Nothing suspectable there in the list.

    Any other way to check from the root cause?

    Regards,

    Prakash.

    Thursday, October 25, 2012 11:54 AM