Explorer.exe crashing all the time

Discussion in 'Windows 7' started by Patricko, Jul 17, 2009.

  1. Patricko

    Patricko MDL Novice

    Jul 17, 2009
    36
    0
    0
  2. joontje

    joontje MDL Novice

    Jul 15, 2009
    37
    1
    0
    maybe looking into your eventlog will help more then a hijackthis log
     
  3. Patricko

    Patricko MDL Novice

    Jul 17, 2009
    36
    0
    0
    Probably this will sound very stupid and dumb, but how to make an eventlog?
    How to export it into a textfile?
     
  4. yaluza1967

    yaluza1967 MDL Member

    Jun 6, 2009
    199
    3
    10
    Hi, check your ram with memtest, explorer crash often with overclock ! try to give more voltage but monitoring temperature.

    YkZ
     
  5. Patricko

    Patricko MDL Novice

    Jul 17, 2009
    36
    0
    0
    #5 Patricko, Jul 17, 2009
    Last edited by a moderator: Apr 20, 2017
    (OP)
    Here is the eventlog from crashing of explorer (I think this is what You mean):

    Code:
    Faulting Application Name: explorer.exe, version 6.1.7600.16384, time stamp: 0x4a583578
    Name of the module that caused the error: ntdll.dll, version 6.1.7600.16384, time stamp: 0x4a584c72
    Code exception: 0xc0000005
    Transfer error: 0x0000000000051da0
    Process ID causing the error: 0xf54
    Time to start the application causing the error: 0x01ca06d30ae2ade2
    Faulting Application Path: C: \ Windows \ explorer.exe
    The path module causing the error: C: \ Windows \ System32 \ ntdll.dll
    Report ID: 5355a642-72c6-11de-9e69-002215b1a012
    And I wasnt overclocking the CPU.
    Its notebook, Im not playing with oc on it.
    I was using it with Win Vista x64 for few months, and everything was fine.
    Problems occured just few days ago.
     
  6. Lenmaer

    Lenmaer MDL Addicted

    Jul 3, 2009
    579
    3
    30
    Make explorer to launch in a separate process everytime, maybe this will help.
     
  7. Patricko

    Patricko MDL Novice

    Jul 17, 2009
    36
    0
    0
    Lenmaer, how to do that?
     
  8. yaluza1967

    yaluza1967 MDL Member

    Jun 6, 2009
    199
    3
    10
    ok, try this :

    In Event Viewer, an Error level log is been recorded, and has the details similar to below:

    Faulting application name: Explorer.EXE, version: 6.1.7000.0, time stamp: 0×49431f06
    Faulting module name: ntdll.dll, version: 6.1.7000.0, time stamp: 0×49433e67
    Exception code: 0xc0000005 or 0xc015000f
    Fault offset: 0×0007f6d6
    Faulting process id: 0×56c
    Faulting application start time: 0×01c97968a23fc032
    Faulting application path: C:\Windows\Explorer.EXE
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: f314a30c-e55b-11dd-83d9-001e375c9a5c

    The cause of the Windows Explorer crash and MSI failure is possible related to SQM Client, which is part of the Customer Experience Improvement Program (CEIP). Under the default setting, where MachineThrottling is enabled in the registry, any calls to WinSqmStartSession in ntdll.dll file will cause Explorer to crash, or Windows Installer installation to fail.

    Thus, while waiting for hotfix or update from Microsoft, in order to fix the issue, just remove and delete the MachineThrottling registry entry from system registry. The MachineThrottling registry entry is located inside the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SQMClient\Windows\DisabledSessions

    Alternatively, just download the Win7-Explorer-Fix.zip, unpack and run the Win7-Explorer-Fix.cmd as administrator to automatically delete the registry key away.


    => http://www.mydigitallife.net/2009/0...rer-stopped-working-and-restart-in-windows-7/

    YkZ
     
  9. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,171
    10,931
    340
    #10 Yen, Jul 17, 2009
    Last edited: Jul 17, 2009
    I don't think it's a virus, and I don't think it's the HDD.
    I think it's hardware related, IMO there is something wrong with your physical memory..........

    yaluza1967 got a good idea...run memtest, before make sure the defaults are loaded and saved at bios setup, no wrong settings.....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Patricko

    Patricko MDL Novice

    Jul 17, 2009
    36
    0
    0
    Okey.

    I will try this fix which yaluza1967 have posted.
    Explorer now is also running in separate processes.

    We will see how it will go, if it fails, than I will run memtest.
     
  11. Patricko

    Patricko MDL Novice

    Jul 17, 2009
    36
    0
    0
    I found that DEP function can make problems.
    I tried disable it by adding only explorer.exe to the exception list.
    But in 64bit systems its impossible, so I disabled whole DEP function.

    Im testing it right, but I want to know is DEP function really important?
    Can I have it disabled?
     
  12. zwaldowski

    zwaldowski MDL Novice

    Jan 4, 2009
    32
    0
    0
    It's a security thing that, in my experience, does more harm than good. I have the same problem with Explorer crashing randomly on my laptop... I'll try this too.
     
  13. Patricko

    Patricko MDL Novice

    Jul 17, 2009
    36
    0
    0
    Ehh..
    It didnt worked for me :/

    Im getting really nervous on this thing...
     
  14. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,171
    10,931
    340
    No need to getting nervous.

    Just do a new clean Vista install, it should disappear. Get SP2 from a trusted source and install it, it should appear again. So you'll be sure it's an SP2 issue.....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. siloujr

    siloujr MDL Novice

    Jun 28, 2009
    2
    0
    0
    hi guys..i also got a same prob...when i use mozilla firefox, its owez has been suddenly crash...juz want to know..i have been reading your comment and is it same solution fo m prob??sorry guys..i am a newbie...:confused:
     
  16. tomorrow

    tomorrow MDL Addicted

    Jul 3, 2008
    723
    262
    30
    If as he said he had this problem also with Vista x64 then i doubt clean install will help.Looks like a HW issue