![]() ![]() ![]() If uploading the dmp file is not going to help, then how do I use these programs to pinpoint the offender? I don't see anything that would indicate the offending party. Note: the faulting module stated isn't always the same, so I'm not sure it really is the module causing the problem.Īs far as the Nirsoft sofware.I installed both the Shellmenu and the Shellview but have no understanding how these two programs can help tell me which shell is the offending party. 16385, time stamp: 0x4a5bdfbaįaulting application start time: 0x01d14c70d2ff657aįaulting application path: C:\Windows\Explorer.EXEįaulting module path: C:\Windows\system32\msutb.dll 17567, time stamp: 0x4d672ee4įaulting module name: msutb.dll, version. In addition the Event log will show, after each crash, the following:įaulting application name: Explorer.EXE, version. And quickly become usable again once Explorer is restarted. The screen that you are on, when the crash occurs, is still there as are most of the system tray icons. The computer is not usable until I click restart Explorer, in the same way if you were to go into Task Manager and kill Explorer and then reload it. ![]() The only thing that happens is a message pops up saying something about Explorer has crashed with an options to check online for solutions or restart Explorer. ![]() I just don't know how to read and interpret it. I can open it in the Windows Debugging tool for Windows 64bit. When Explorer crashes, it does leave a dmp file (C:\user\my computer\appdata\local\crashdumps\explorer.exe.#.dmp ). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |