none
Windows 7 Explorer keeps crashing throughout the day

    Question

  • I have a user who's been complaining about explorer crashing and restarting repeatedly throughout the day.  Looking through the event viewer this event is occurring 5-10 times a day.

    Faulting application name: explorer.exe, version: 6.1.7601.17567, time stamp: 0x4d6727a7
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x01d3fac8
    Faulting process id: 0xa80
    Faulting application start time: 0x01cd1328363e6079
    Faulting application path: C:\Windows\explorer.exe
    Faulting module path: unknown
    Report Id: d2106c56-7f1b-11e1-9332-78acc0c37cb9

    Thursday, April 05, 2012 3:09 PM

Answers

  • Start with system scanning

    sfc /scannow

    Regards

    Milos

    Thursday, April 05, 2012 5:18 PM
  • Hi,

    Please also try to check how it works in Clean Boot mode.

    Alex Zhao

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Alex Zhao

    TechNet Community Support

    Friday, April 06, 2012 6:36 AM
    Moderator
  • I have a user who's been complaining about explorer crashing and restarting repeatedly throughout the day.  Looking through the event viewer this event is occurring 5-10 times a day.

    Faulting application name: explorer.exe, version: 6.1.7601.17567, time stamp: 0x4d6727a7
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x01d3fac8
    Faulting process id: 0xa80
    Faulting application start time: 0x01cd1328363e6079
    Faulting application path: C:\Windows\explorer.exe
    Faulting module path: unknown
    Report Id: d2106c56-7f1b-11e1-9332-78acc0c37cb9

    The above exception parameter is called a memory exception.

    It is typically caused by bad ram, or more frequently a driver.  Please run the below tests to find out which.

    -Given the memory exception parameter I would run memtest for 6-8 passes and driver verifier.

    -If you are overclocking anything reset to default before running these tests

    1-Memtest-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. "http://www.memtest.org/#downiso

    -Boot from the CD, and leave it running for at least 5 or 6 passes.

    -Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    -Test the sticks individually, and if you find a good one, test it in all slots.

    -Any errors are indicative of a memory problem.

    -If a known good stick fails in a motherboard slot it is probably the slot

    2-Driver verifier

    -Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver.

    -Other times it'll crash before you can log in to Windows

    .-If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    -I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature)

    -In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    -Then, here's the procedure:

    - Go to Start and type in "verifier" (without the quotes) and press Enter-

    -Select "Create custom settings (for code developers)" and click "Next"

    - Select "Select individual settings from a full list" and click "Next"

    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"

    Select "Select driver names from a list" and click "Next"Then select all drivers NOT provided by Microsoft and click "Next"

    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly.

    -The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    -If you can't get into Windows because it crashes too soon, try it in Safe Mode.

    -If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    -Further Reading"http://support.microsoft.com/kb/244617"]Using Driver Verifier to identify issues with Windows drivers for advanced users




    Thursday, April 12, 2012 1:36 AM
    Moderator

All replies

  • Start with system scanning

    sfc /scannow

    Regards

    Milos

    Thursday, April 05, 2012 5:18 PM
  • Very often exlorer errors could be linked to viruses and malware.

    I would recommand installing all windows updates and running full scan on your computer for viruses in addition to the "sfc /scannow" step.


    • Edited by Brano Lukic Thursday, April 05, 2012 6:58 PM
    Thursday, April 05, 2012 5:27 PM
  • An additional thought, does the user know the approximate period of time that this problem began?  (Or can you see it in the logs?)  Perhaps a system restore to a date before then might take care of it?

    Like was said above me, it sounds like malware, but it could also be corruption, etc, which would be the domain of the System File Checker (sfc), like Milos stated. 


    • Edited by davidtheweb Thursday, April 05, 2012 5:56 PM
    Thursday, April 05, 2012 5:53 PM
  • Hi,

    Please also try to check how it works in Clean Boot mode.

    Alex Zhao

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Alex Zhao

    TechNet Community Support

    Friday, April 06, 2012 6:36 AM
    Moderator
  • Hi,

    Do you have any update about this issue?

    Regards,

    Alex Zhao

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Alex Zhao

    TechNet Community Support

    Monday, April 09, 2012 1:18 AM
    Moderator
  • I have a user who's been complaining about explorer crashing and restarting repeatedly throughout the day.  Looking through the event viewer this event is occurring 5-10 times a day.

    Faulting application name: explorer.exe, version: 6.1.7601.17567, time stamp: 0x4d6727a7
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x01d3fac8
    Faulting process id: 0xa80
    Faulting application start time: 0x01cd1328363e6079
    Faulting application path: C:\Windows\explorer.exe
    Faulting module path: unknown
    Report Id: d2106c56-7f1b-11e1-9332-78acc0c37cb9

    The above exception parameter is called a memory exception.

    It is typically caused by bad ram, or more frequently a driver.  Please run the below tests to find out which.

    -Given the memory exception parameter I would run memtest for 6-8 passes and driver verifier.

    -If you are overclocking anything reset to default before running these tests

    1-Memtest-Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. "http://www.memtest.org/#downiso

    -Boot from the CD, and leave it running for at least 5 or 6 passes.

    -Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

    -Test the sticks individually, and if you find a good one, test it in all slots.

    -Any errors are indicative of a memory problem.

    -If a known good stick fails in a motherboard slot it is probably the slot

    2-Driver verifier

    -Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver.

    -Other times it'll crash before you can log in to Windows

    .-If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

    -I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature)

    -In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    -Then, here's the procedure:

    - Go to Start and type in "verifier" (without the quotes) and press Enter-

    -Select "Create custom settings (for code developers)" and click "Next"

    - Select "Select individual settings from a full list" and click "Next"

    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"

    Select "Select driver names from a list" and click "Next"Then select all drivers NOT provided by Microsoft and click "Next"

    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly.

    -The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    -If you can't get into Windows because it crashes too soon, try it in Safe Mode.

    -If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    -Further Reading"http://support.microsoft.com/kb/244617"]Using Driver Verifier to identify issues with Windows drivers for advanced users




    Thursday, April 12, 2012 1:36 AM
    Moderator
  • Hi,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

    BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

    Regards,

    Alex Zhao

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Alex Zhao

    TechNet Community Support

    Friday, April 13, 2012 2:39 AM
    Moderator
  • Method1:

        Go to the Start button.
        In the Search box, type “regedit” (without quotes) and press Enter.
        Browse the following registry key: “HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\ SQMClient\Windows\DisabledSessions”.
        On the right window pane, delete the subkey: “Machine Throttling”.
        Reboot your computer.

    Method 2:

    In Administrator mode, At the command prompt, type “chkdsk /r /f” (without quotes) and press Enter. Restart the System.

    Method 3:
     
     Incompatible Drivers installed while updating the Sound Card,Graphics Card, LAN Drivers etc. So Roll back the driver that you installed recently.It may also happen due to old drivers. Go the official download page for the respective hardware  to get the driver updated.

    Method 4 :

        Press the key combination Windows logo key + R to open the Run dialog.
        Type gpedit.msc in the Run dialog and press Enter.
        In the Local Group Policy Editor navigate to
        Computer Configuration → Administrative Templates → System → Internet Communication Management → Internet Communication Settings.
        You would find a setting on the right hand side pane — Turn Off Windows Customer Experience Improvement program
        Double-click on this setting and choose Enabled and then click OK.
        Close the Local Group Policy Editor windows



    Regards Jinish.K.G|HCL Infosystems LTD

    • Proposed as answer by Jinish KG Wednesday, September 25, 2013 3:53 AM
    Tuesday, May 15, 2012 9:04 AM
  • https://public.bay.livefilestore.com/y1pNlPSxUsRTzWDFauWn0DsH6HrrPMZYpApRMWbAywzcbfhFq6ON_bVvKSg8NFo-RswupDoSmnBvAogdF_8o2U72w/5-13-2012%2010-29-08%20PM.png?psid=1
    Wednesday, May 16, 2012 4:12 AM
    Moderator