none
Faulting application Explorer

    Question

  •  

    hi,

    every time I'm receiving message that Exeplorer will stop now restart or find solution on internet, there is no solution on internet and anyway all windows will closed because exporer restarted

     

    I'm using Windows Vista Ultimate Edition

     

    I found the following EVEnt:

    Event ID: 1000
    Source: Application Error

     

    Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp 0x46d230c5, faulting module SHELL32.dll, version 6.0.6000.16513, time stamp 0x4681c95d, exception code 0xc0000005, fault offset 0x0014607a, process id 0x1260, application start time 0x01c8458f42750bd0.

     

    Regards

     

    Sunday, December 23, 2007 6:35 PM

All replies

  • I get the same message:

     

    Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp 0x46d230c5, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x074836a7, process id 0x11d0, application start time 0x01c84d753c724ea5.

     

    Could someone from Microsoft look into this and get back about it.

    I am starting to consider Linux alternative due to bugs like this...

     

    Please help.

    Wednesday, January 02, 2008 7:37 PM
  • You aren't alone.  Like Clockwork...

     

    Faulting application Explorer.EXE, version 6.0.6000.16549, time stamp 0x46d230c5, faulting module SHELL32.dll, version 6.0.6000.16513, time stamp 0x4681c95d, exception code 0xc0000005, fault offset 0x0014607a, process id 0x12b4, application start time 0x01c84e914b42e9c0.

    I'm getting ready to give Linux a shot. I guess we should be happy not to get a Blue Screen of Death - however - this is really annoying. 

     

    Could someone from Microsoft look into this and get back about it.

     

    While you're at it how about fixxing the endless sleep mode my computer goes into too.  The computer wakes up but the video doesn't.  How long has Vista been out?

     

    Please help.

    Friday, January 04, 2008 5:48 AM
  • I'm getting this same error in Windows XP using Windows Explorer. Today was the first day I have ever experienced this problem. I'm pasting the errors below.

    1/5/2008 5:23 PM    Application Hang    Hanging application explorer.exe, version 6.0.2900.3156, hang module hungapp, version 0.0.0.0, hang address 0x00000000.


    1/5/2008 8:57 PM    Application Error    Faulting application explorer.exe, version 6.0.2900.3156, faulting module shell32.dll, version 6.0.2900.3241, fault address 0x0002af74.




    Sunday, January 06, 2008 2:42 AM
  • I have been getting the same errors on Windows XP for some time. Windows Explorer crashes several times a day and no one has yet come up with a solution. Glad to know I'm not the only one.

    Can someone from Microsoft please look into this with some urgency? Your support site contains nothing relevant at all.
    Tuesday, February 19, 2008 4:53 PM
  • Typicall this problem is caused by non Microsoft Explorer Shell Extensions and you can troubleshoot 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

     

    Please post additional details of the  problem on Windows Microsoft Vista in a new thread by following these steps.

     

    1.  Open Problem Reports and Solutions by clicking the Start button , clicking Control Panel, clicking System and Maintenance, and then clicking Problem Reports and Solutions.

    2.  In the left pane, click View problem history.

    3. Find the occurrence of the problem and Right Click On it.

    4. Right Click on the problem and click "Check for Solution"

    5.  If it says "Solution Available", Right Click and click "View Solution"

    6.  If not, Double-click the problem that you want to view. 

    7.  Use the "Copy to clipboard" link in the lower left corner and paste a reply or start a new thread if you didn't start this one.

    -

    John

     

    I work at Microsoft. These are my opinions and not my employers.

    This posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by MSY_ Tuesday, May 22, 2012 7:48 PM
    Wednesday, February 20, 2008 10:45 AM
  • I get the same error with Windows XP.  The error message from the event viewer is

     

    Faulting application explorer.exe, version 6.0.2900.3156, faulting module , version 0.0.0.0, fault address 0x00000000.

     

    This is followed by information

     

    "The shell stopped unexpectedly and Explorer.exe was restarted."

     

    So it does sound like a shell problem.  I have downloaded AUTORUNS and unchecked all the items under the Explorer tab, but the problem has not been solved.  Do you have any more suggestions, John?  This  is really annoying (every 6 1/2 minutes or so).

     

     

    Thursday, February 21, 2008 2:14 PM
  • Thanks, this made a big difference to how often Windows Explorer was crashing. I stopped all the non-microsoft extensions, and now only get an occasional crash, usually after a delete which gets done and then the dialogue just hangs. I can live with the problem now, but it is still annoying when I am multi-tasking with several explorer windows open to copy large batches of files, and they all get shut down, leaving me to recover from the partially completed copies.

     

    This was the latest failure:

     

    Product

    Internet Explorer

    Problem

    Stopped responding and was closed

    Date

    10/06/2008 07:41

    Status

    Report Sent

    Description

    A problem caused this program to stop interacting with Windows.

    Problem signature

    Problem Event Name: AppHangB1

    Application Name: iexplore.exe

    Application Version: 7.0.6001.18000

    Application Timestamp: 47918f11

    Hang Signature: dbca

    Hang Type: 6148

    OS Version: 6.0.6001.2.1.0.256.1

    Locale ID: 2057

    Additional Hang Signature 1: 25a8425115c7020dc782d30b3e0f817f

    Additional Hang Signature 2: be97

    Additional Hang Signature 3: 706d0948eab2a345c930f695f3cc422c

    Additional Hang Signature 4: 0d1a

    Additional Hang Signature 5: 8d47690ffd8bc6a59d5783d3ab3a67c2

    Additional Hang Signature 6: e847

    Additional Hang Signature 7: 0143f47ac3c6fbc865e7e902dfc17654

    Extra information about the problem

    Bucket ID: 248171066

    I am suspicious of the Creative Labs Soundblaster Xfi software, in relation to this problem, but I don't want to shut it down any more than I already have done, and I have An OEM version so I can't use Creatives own support.

     

    Regards,

     

    Jim Brodie

    Thursday, June 12, 2008 9:16 AM
  • Hi

    Go to this address it is not what you want but it sais about the ntdll.dll file

    http://support.microsoft.com/default...b;EN-US;314503

    Friday, June 13, 2008 10:51 AM
  •  

    I had this problem with XP Pro. I created a new user profile and it went away, so then I performed a failure cause analysis and determined the fault to be a dll file from a program called Pagis 2.0.

     

    I went into C:\Program Files\Xerox\Pagis

     

    and at the command prompt I typed:

    REGSVR32 /U PGFOLDER.DLL

     

    Problem has been fixed and the delay at shutdown that used to occur before the error is gone. Shutdown is now much, much faster and I no longer need the extra profile I created so I removed it and all is well.

     

    more info:

    http://www.pcreview.co.uk/forums/thread-374867.php

     

    Carey Holzman

    Co-Host / Producer: Computer America Show

    http://www.ComputerAmerica.com

     

    Tuesday, June 17, 2008 10:06 AM
  •  Abduljalil Abolzahab wrote:

     

    I,m getting same error , i;m using Vista Home premium service pack 1 updated on my HP notebook, i have tried system recovery re installing windows and everything it went well for a few days, and now the annoying error message is back.
    this is a major setback for vista user, Win XP Pro is far more better and Stable. I hope microsoft should do something about this, I have no choice because my hardware drivers only supports Vista there non for XP.

    PLEASE HEEELPPP!!!!

     

    Faulting application Explorer.EXE, version 6.0.6001.18000, time stamp 0x47918e5d, faulting module SHELLvRTF.dll, version 1.1.0.8, time stamp 0x46d83e7c, exception code 0xc0000005, fault offset 0x000057ab, process id 0xc5c, application start time 0x01c8d9e895a6b808.

     

    TNX!

    Sunday, June 29, 2008 2:54 PM
  •  

    I guess it is my turn for Vista to fail me...

     

    Faulting application explorer.exe, version 6.0.6001.18000, time stamp 0x47918e5d, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000374, fault offset 0x000b015d, process id 0xa0c, application start time 0x01c8e45e0ace158f.

     

    This happens every time I right click on an EXE or try to pin something on the Start menu.

     

    Saturday, July 12, 2008 8:32 PM
  •  

    I had a similar problem today with Windows XP Pro on a Dell Vostro 1510 laptop.

     

    Like others this machine suffered and Event id: 1000 with the faulting application explorer.exe.

     

    I looked into the various solutions including reinstalling the NIC drivers (suggested elsewhere) but to no avail.

     

    However I have now found a solution for my version of this issue:

     

    There is a clash between the LAN and WLAN cards when accessing network content. Disabling the WLAN and performing a logoff/on resolved the issue immediately.

    On this laptop there is a physical switch for WLAN and Bluetooth. To avoid compromising Bluetooth functionality it is better to disable the WLAN from the system tray rather than using the physical switch.

     

    Why this happens I'm not entirely sure - none of our other laptop users with similar configs have had the issue - yet.

    However it was notable that the WLAN signal is particularily weak in both the users normal desk location and the area we tested.

     

    Frankly I should have spotted it much earlier - hopefully others can now add this to their trouble-shooting for this problem.

    Wednesday, November 26, 2008 11:07 AM
  • I am getting a similar problem, and its become difficult to deal with as it locks out both explorer.exe and iexplorer.exe. I had to use a different browser just to check for solutions.

    Here is the pisser, I tried going to Windows Updates to see if I could find a hotfix, but for some reason Windows Updates will only allow me to access it through Internet Explorer, which crashes when I attempt to open it, and I can't open Control Panel because Explorer crashes as soon as I attempt to open that.

    Running in safe mode, I find that explorer.exe works, I will try safe mode with networking to see if that enables iexplorer.exe to work as well.

    This problem started occurring just a few days ago, no new programs have been installed. Ran Anti-virus and everything checks out clean.

    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    iexplore.exe
      Application Version:    7.0.6000.16757
      Application Timestamp:    48e4238e
      Fault Module Name:    StackHash_61b5
      Fault Module Version:    6.0.6000.16386
      Fault Module Timestamp:    4549bdc9
      Exception Code:    c0000374
      Exception Offset:    000af1c9
      OS Version:    6.0.6000.2.0.0.256.6
      Locale ID:    1033
      Additional Information 1:    61b5
      Additional Information 2:    f29f2170c024eae28bca32d89e10bf9e
      Additional Information 3:    b028
      Additional Information 4:    5f4dcdc8519f9e51678edb1da87ff98f

    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    explorer.exe
      Application Version:    6.0.6000.16549
      Application Timestamp:    46d230c5
      Fault Module Name:    StackHash_c445
      Fault Module Version:    6.0.6000.16386
      Fault Module Timestamp:    4549bdc9
      Exception Code:    c0000374
      Exception Offset:    000af1c9
      OS Version:    6.0.6000.2.0.0.256.6
      Locale ID:    1033
      Additional Information 1:    c445
      Additional Information 2:    35cdf1b68d18bcbc0b137bcfd329926f
      Additional Information 3:    5abb
      Additional Information 4:    6d55998b5079f125a4ce245768e6e746

    Wednesday, January 21, 2009 1:38 PM
  •  

      A long shot, but worth a try. . . .


     The Bottom line is to use a compatibility wizard in
     the control panel and let it figure out the correct
     settings.

     The below instructions are for Ms Access 2003
     aka Office11.

     = = = = = = = = = = = = = = = = = = = = = = = = = = =

    When dealing with older Microsoft programs that have
    trouble function correctly within Windows-7 64 bit
    Professional there is a feature in the Control-Panel
    that might help.

    That feature used is the System and Security find and fix.

    In the case of using Microsoft Access 2003, 32 bit,
    under Windows-7, 64 bit, with complex code you can
    expect to have AppHangB1 errors, AppCrash errors, or
    in the case of early binding to Excel, from Access 2003
    VBA, to have the application simply freeze up.

    The Steps

    1). Open up the Control Panel in View by Category.

    2). Search for the ‘System and Security’ topic.

    3). Under the System and Security topic select the
        Find and Fix problems item.

    4). When the Troubleshooting window opens, select the
        Programs category.

    5). Then in the Compatibility window, click the Next.

        That feature will try to guess what program is
        having the problem.

    6). In the case of Access 2003, it didn’t show up in
        the list.  Therefore, you will have to click the
        Not-Listed category.  Then click the Next button.

    7). A Browse window will appear.

    8). Click the Browse button and go to the drive that has
        the application installed on it.  In this case select
        Computer and work your way to the C: drive.

    9). Since this is a 32 bit Microsoft application select
        the \Program Files(x86)\ folder.

    10). Next select the \Microsoft Office\ folder.

    11). Since we are using Office 2003, select the \Office11\ folder.

    12). Scroll down until you find the MsAccess.exe program.
         Click it and then click the Open button.

    13). You should see ->
            C:\Program Files(x86)\Microsoft Office\Office11\MsAccess.exe
        in the Browse line.
        Click the Next Button.
     
    14). Select ‘Try recommended settings’

    15). The Compatibility feature selected ‘XP mode (service pack 2)’.
         Click the Next button.

    16). Click ‘Yes, save these settings for this program’, and Click Next.

    17). You can also go to ->
           C:\Program Files(x86)\Microsoft Office\Office11\MsAccess.exe
         And do a Right-Mouse Click.

         Select Proprieties, then select compatibility tab.
         Check box ‘Run this program compatibility mode for:’
         And select Windows XP(Service Pack 2).

         Additionally turn on the ‘Run this program as an Administrator’.
         Select the ‘Change settings for all users’ button and Re-enter
         in all the information.

         Then you should be up and running.


    Ed505

    • Edited by Ed505 Monday, December 12, 2011 4:18 PM
    • Proposed as answer by Ed505 Monday, December 12, 2011 4:18 PM
    • Unproposed as answer by Ed505 Monday, December 12, 2011 4:18 PM
    • Proposed as answer by Ed505 Monday, December 12, 2011 4:18 PM
    Monday, December 12, 2011 4:17 PM
  • Typicall this problem is caused by non Microsoft Explorer Shell Extensions and you can troubleshoot 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

    Please post additional details of the  problem on Windows Microsoft Vista in a new thread by following these steps.

    1.  Open Problem Reports and Solutions by clicking the Start button , clicking Control Panel, clicking System and Maintenance, and then clicking Problem Reports and Solutions.

    2.  In the left pane, click View problem history.

    3. Find the occurrence of the problem and Right Click On it.

    4. Right Click on the problem and click "Check for Solution"

    5.  If it says "Solution Available", Right Click and click "View Solution"

    6.  If not, Double-click the problem that you want to view. 

    7.  Use the "Copy to clipboard" link in the lower left corner and paste a reply or start a new thread if you didn't start this one.

    -

    John

    I work at Microsoft. These are my opinions and not my employers.

    This posting is provided "AS IS" with no warranties, and confers no rights.


    You got it! It was a runaway shell extension for us. Thank you, John!
    Tuesday, May 22, 2012 7:49 PM
  • Description
    Faulting Application Path: C:\Windows\explorer.exe

    Problem signature
    Problem Event Name: APPCRASH
    Application Name: explorer.exe
    Application Version: 6.1.7601.17567
    Application Timestamp: 4d672ee4
    Fault Module Name: StackHash_f3f6
    Fault Module Version: 6.1.7601.17725
    Fault Module Timestamp: 4ec4aa8e
    Exception Code: c0000374
    Exception Offset: 00000000000c40f2
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 2052
    Additional Information 1: f3f6
    Additional Information 2: f3f6d409e246509d7b0e81ab464b79bb
    Additional Information 3: 3475
    Additional Information 4: 3475c7715a003c9bc2200c6576aa7cb8

    help me~ im having the same question~!!!!! email me triplek_1996@hotmail.com

    Tuesday, August 07, 2012 8:24 AM
  • YOUR FOOL!

    This is not working! :@

    Where is the solution, how do I find "unknown module faulding"?????????????????

    Thursday, October 04, 2012 4:16 PM