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:
*** 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
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).