Well, I uninstalled SEP using CleanWipe. Then reinstalled the latest SEP. Also ran SFC and it found no problems. Came back to my office and my phone rang...it was the user stating that explorer.exe had stopped working again. I am attaching the latest dump file. FYI: I did updated the NIC driver via Intel's website.
explorer.exe is not crashing on boot.....it crashes when the user has explorer open, such as a folder on the root of C: or in My Documents
Hello,
Still it's pointing to Symantec Shell dlls like VpShellRes.dll, vpshell2.dll, SnacNp.dll. Make sure you run the cleanup Tool.
Hope this helps,Code:*** WARNING: Unable to verify timestamp for explorer.exe *** WARNING: Unable to verify timestamp for ContextMenu.dll *** ERROR: Module load completed but symbols could not be loaded for ContextMenu.dll *** WARNING: Unable to verify timestamp for WZSHLSTB.DLL *** ERROR: Module load completed but symbols could not be loaded for WZSHLSTB.DLL *** WARNING: Unable to verify timestamp for msoshext.dll *** ERROR: Module load completed but symbols could not be loaded for msoshext.dll *** WARNING: Unable to verify timestamp for SnacNp.dll *** ERROR: Module load completed but symbols could not be loaded for SnacNp.dll *** WARNING: Unable to verify timestamp for mfc80u.dll *** WARNING: Unable to verify timestamp for ccL608.dll *** ERROR: Module load completed but symbols could not be loaded for ccL608.dll *** WARNING: Unable to verify timestamp for vpshell2.dll *** ERROR: Module load completed but symbols could not be loaded for vpshell2.dll *** WARNING: Unable to verify timestamp for VpShellRes.dll *** ERROR: Module load completed but symbols could not be loaded for VpShellRes.dll *** WARNING: Unable to verify timestamp for mfc80ENU.dll *** ERROR: Module load completed but symbols could not be loaded for mfc80ENU.dll *** WARNING: Unable to verify timestamp for IPHLPAPI.DLL *** ERROR: Module load completed but symbols could not be loaded for IPHLPAPI.DLL *** WARNING: Unable to verify timestamp for slc.dll *** ERROR: Module load completed but symbols could not be loaded for slc.dll *** WARNING: Unable to verify timestamp for msxml5.dll *** ERROR: Module load completed but symbols could not be loaded for msxml5.dll
Captain
thanks for the info. I looked at the "mfc80u.dll" and noticed "mfc80ENU.dll." Found a Microsoft article where these .dll's can become corrupted if one version tries to overwrite the other. I downloaded a hotfix and have not heard back from the user yet (keeping fingers crossed). I do have 2 more .dmp files from the other two PC's. Can you analyze those as well? Thanks again for all of your help.
Here :
Steve:
Denise:Code:*** WARNING: Unable to verify timestamp for ue32ctmn.dll *** ERROR: Module load completed but symbols could not be loaded for ue32ctmn.dll *** WARNING: Unable to verify timestamp for ContextMenu.dll *** ERROR: Module load completed but symbols could not be loaded for ContextMenu.dll *** WARNING: Unable to verify timestamp for mbamext.dll *** ERROR: Module load completed but symbols could not be loaded for mbamext.dll *** WARNING: Unable to verify timestamp for SnacNp.dll *** ERROR: Module load completed but symbols could not be loaded for SnacNp.dll *** WARNING: Unable to verify timestamp for ccL608.dll *** ERROR: Module load completed but symbols could not be loaded for ccL608.dll *** WARNING: Unable to verify timestamp for mfc80u.dll *** WARNING: Unable to verify timestamp for MSOHEVI.DLL *** ERROR: Module load completed but symbols could not be loaded for MSOHEVI.DLL *** WARNING: Unable to verify timestamp for VpShellRes.dll *** ERROR: Module load completed but symbols could not be loaded for VpShellRes.dll *** WARNING: Unable to verify timestamp for vpshell2.dll *** ERROR: Module load completed but symbols could not be loaded for vpshell2.dll *** WARNING: Unable to verify timestamp for mfc80ENU.dll *** ERROR: Module load completed but symbols could not be loaded for mfc80ENU.dll *** WARNING: Unable to verify timestamp for IPHLPAPI.DLL *** ERROR: Module load completed but symbols could not be loaded for IPHLPAPI.DLL *** WARNING: Unable to verify timestamp for slc.dll *** ERROR: Module load completed but symbols could not be loaded for slc.dll
Hope this helps,Code:*** WARNING: Unable to verify timestamp for explorer.exe *** WARNING: Unable to verify timestamp for SnacNp.dll *** ERROR: Module load completed but symbols could not be loaded for SnacNp.dll *** WARNING: Unable to verify timestamp for IPHLPAPI.DLL *** ERROR: Module load completed but symbols could not be loaded for IPHLPAPI.DLL *** WARNING: Unable to verify timestamp for slc.dll *** ERROR: Module load completed but symbols could not be loaded for slc.dll *** WARNING: Unable to verify timestamp for shell32.dll *** WARNING: Unable to verify timestamp for msxml5.dll
Captain
now working with Microsoft on this issue. Seems to be related to something called "NetWorkItemFactory.dll." They say it is a bug and a fix could take some time. They sent me a Process Dumper program....but it is not creating the .dmp files as it should
how can I stop dump files from being generated? I used a "program" or "reg" file that someone had on this forum that created dumps when explorer.exe crashed. Can't find the post though....thanks
Hello,
Apologize for the delayed response !
Go to
and delete Explorer.exe to stop creating the Dump.Code:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\
Thanks for posting back the reason. If you have more information about that bug please post it here. Also if they find and fix and inform you please be kind enough to post it here so others can make sure of it.
Hope this helps,
Captain
I was having the Black Screen of Death with mouser pointer and realised through Event Viwer (eventvwr.msc) that the explorer.exe crash was associated to the propsys.dll located in windows\system32 folder.
So, I managed to emulate a mini WinXP via Hiren's Boot, loaded a "health" propsys.dll from my other Windows 7 system and overwrote the corrupted one. Problem solved to me!
Quote