Explorer.exe repeated crashes on Win7 64bit Home Premium

Let's start with examining the crash dump from the apphang: https://www.sevenforums.com/crash-loc...g-process.html

The kernel32.dll (and other) file symbol could not be located. As I've been doing analysis' with this copy of Debugging Tools for about 6 months, I don't think that my symbols would be incorrect.

Here's a copy of the memory dump output from the Debugging Tools:

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR\Downloads\explorer\explorer.DMP]
User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Windows 7 Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Machine Name:
Debug session time: Sat May 29 07:49:47.000 2010 (GMT-4)
System Uptime: 0 days 0:06:18.327
Process Uptime: 0 days 0:02:40.000
................................................................
................................................................
.......................
Loading unloaded module list
...................
user32!ZwUserWaitMessage+0xa:
00000000`76febf5a c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for TC Device Mgmt.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for tlib_log.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for boost_log-vc80-mt-1_33.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FM.dll - 
*** ERROR: Module load completed but symbols could not be loaded for FXSRESM.dll
*** ERROR: Module load completed but symbols could not be loaded for mfc80ENU.dll
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00000000000003fc

DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT

PROCESS_NAME:  explorer.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER:  from 000007fefddb4402 to 0000000076febf5a

STACK_TEXT:  
00000000`0027f6e8 000007fe`fddb4402 : 00000000`046b8310 00000000`0462f520 00000000`00000000 00000000`00000000 : user32!ZwUserWaitMessage+0xa
00000000`0027f6f0 000007fe`fdd27ab5 : 00000000`0462f520 00000000`0462f520 00000000`00000000 00000000`00000000 : shell32!CDesktopBrowser::_MessageLoop+0x51
00000000`0027f730 00000000`ffb60e97 : 000007fe`f81431c0 80000000`04010000 00000000`00000000 00000000`0462f520 : shell32!SHDesktopMessageLoop+0x7e
00000000`0027f770 00000000`ffb5c2b9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!wWinMain+0xb08
00000000`0027fe20 00000000`76ecf56d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : explorer!DelayLoadFailureHook+0x208
00000000`0027fee0 00000000`77103281 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`0027ff10 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP: 
shell32!CDesktopBrowser::_MessageLoop+51
000007fe`fddb4402 ebe8            jmp     shell32!CDesktopBrowser::_MessageLoop+0x1c (000007fe`fddb43ec)

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  shell32!CDesktopBrowser::_MessageLoop+51

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: shell32

IMAGE_NAME:  shell32.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4b7cf381

FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_shell32.dll!CDesktopBrowser::_MessageLoop

BUCKET_ID:  X64_APPLICATION_FAULT_STATUS_BREAKPOINT_shell32!CDesktopBrowser::_MessageLoop+51

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/explorer_exe/6_1_7600_16450/4aebab8d/unknown/0_0_0_0/bbbbbbb4/80000003/00000000.htm?Retriage=1

Followup: MachineOwner
---------

Is your system legitimate?
Have you updated Windows recently (if not, please do so now)?
Have you run SFC.EXE /SCANNOW?
Have you run the activation wizard? If not, go to Start and type in "activate" (without the quotes) and press Enter - then follow the instructions.


Also, try to locate these files and see if they point to any 3rd party programs (non-Windows) that may be running. This presumes that they are mentioned because they are involved (in some way) with the hang.:

Code:

tlib_log.dll
boost_log-vc80-mt-1_33.dll
FM.dll
FXSRESM.dll
mfc80ENU.dll

Symbol errors point to difficulties with the system - the questions that I asked are the most common reasons for symbol errors to occur.

The .dll files that I mentioned were listed this way in the dump file:

Code:

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for TC Device Mgmt.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for tlib_log.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for boost_log-vc80-mt-1_33.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for FM.dll - 
*** ERROR: Module load completed but symbols could not be loaded for FXSRESM.dll

When I see these I guess that they are being looked at (and the symbols were needed) because they are present in the stack text - and as such, they were involved in the vicinity of the crash.

Next, I suppose that Windows files are OK - because they're protected by SFC.EXE
That leaves the 3rd party .dll's that can be at fault (assuming that all my assumptions are correct).
So, looking up the 3rd party programs that these .dll's point to may help to resolve the issues. If any of the .dll's are Windows files, then they can safely be ignored.

The first thing to do would be to search your system for these files.
Then right click on them, select Properties, then select the Details tab.
That should give you some info as to what program that they belong to (and the path to the .dll may also help if it's in the Program Files directory).

Once you know that, you can remove the program(s) to see if that fixes the problem.

So, here's what I found:

TC Device Mgmt.dll belongs to a program either from Popwire or a Sony-Ericson mobile phone software program.
tlib_log.dll belongs to Telecalib Logging from Popwire or to a Sony-Ericson mobile phone applicaton
boost_log-vc80-mt-1_33.dll belongs to Application Launcher" made by "Teleca Sweden AB
FM.dll more Sony-Ericson stuff (http://www.renjusblog.com/2008/03/ho...-ericsson.html )
FXSRESM.dll belongs to Microsoft Fax Resource Library (since it's a Windows file, it can be disregarded).

So, the majority of this error making stuff is due to your mobile phone software. Uninstall it completely, then check to make sure that all of the .dll's are gone (if not, rename them to .BAK) - DO NOT remove/rename the FXSRESM.dll file since it's a Windows file.

Once that's done, use this free program ( http://technet.microsoft.com/en-us/s.../bb963902.aspx ) to make sure that the phone .dll's aren't trying to load at startup (which may cause slowness or error messages when starting).