New
#31
I've downloaded your dump and will look at it. The UVK scan log might or might not be useful. It could throw up a few surprises so it's worth a look.
I've downloaded your dump and will look at it. The UVK scan log might or might not be useful. It could throw up a few surprises so it's worth a look.
thank you.
btw I mean 2nd dump named
3.AnotherExplorerMiniDump_explorer.rar (510.9 KB, 0 views)
Yes that's the one I downloaded. It's the same as the first one. All it really tells us is that Explorer crashed.
The dump doesn't pinpoint which .dll(s) to suspect so I'm hoping that the other dump will appear.Code:SYMBOL_NAME: shell32!CDesktopBrowser::_MessageLoop+51 FOLLOWUP_NAME: MachineOwner MODULE_NAME: shell32 IMAGE_NAME: shell32.dll DEBUG_FLR_IMAGE_TIMESTAMP: 55c3a1b3 FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_shell32.dll!CDesktopBrowser::_MessageLoop BUCKET_ID: X64_APPLICATION_FAULT_STATUS_BREAKPOINT_shell32!CDesktopBrowser::_MessageLoop+51
In the meantime there's a long list of dll's one of which is the likely culprit.
Check this to see if it picked up any files:
https://acdsystems.desk.com/customer...ding-pictures-
Okay since I will be offline for a week from today I've asked for help on this. Maybe someone will post their analysis of the dump you provided.
Just to confirm the reg file contained this and you merged it?
Result:Code:Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\Explorer.exe] "DumpFolder"=hex(2):43,00,3a,00,5c,00,4c,00,6f,00,63,00,61,00,6c,00,44,00,75,\ 00,6d,00,70,00,73,00,00,00
I have to confess that I don't remember if the Localdumps folder gets created when merging the reg fle or only when explorer crashes.
RE: Help with crash dump. It seems that other members can't open your dump stating that it's too big.
Anyway here it is in text format.
Last post from me for now so if anyone else has ideas please post.
Thanks a lot
So as far as I understand it was 2nd time directly confirmed by your kind analysis that a culprit is likely win7 shell as shell32.dll.
And frankly speaking this your 2nd time same verdict as 'shell32 desktop browser message loop' matches a visible fact of (from my point) some abnormal growing of explorer.exe process size from some unclear moment towards its like-crash/freeze point, when I believe that in normal way operations of explorer.exe its size should be naturally growing while some explorer involved actions performed but then, when those actions are finished, explorer.exe process size should roll-back (at least partly!). However, this assumed normal way roll-back doesn't happen from that unclear point of time, which is assumed as a start of this desktop browser message loop!
Also I know that there is a long list of .dll suspects, when my list of shell extensions as visible in Autoruns or ShellMenuView or ShellExView is abnormally big! Sorry it's not intentional. This laptop is just well set business pc aimed to process any possible operation at any need.
Now still waiting for next issue in hope for a right dump.
yep I keep in mind that your plan. thanks again and have a better time offline!
as I said before this issue doesn't bother me too much when I just need to restart laptop once in 2-3-4 days depends on how much actively I use explorer operation and right click ones in particular. but it's really odd!
Oops, sorry I missed to reply to this your message earlier.
Thanks for a prompt but frankly speaking I don't think a trap is somewhere around when I guess I'm a quite uncommon user of ACDsee Ultimate - I never create any data bases in this app, even if offered. So the only 2 pic folders listed in this app are Public Pictures and My Pictures - both default of Win7
Anyhow I just found that my ver. of ACDsee Ultimate x64 was not latest as 9.3.0 build 673 and just updated it to now latest 9.3.0 build 674. It's maybe worth to mention that a build 674 is just a month younger to 673 one. It's pretty uncommon for ACDsee so maybe some obvious bag of build 673 repaired.
Last edited by laidbacktokyo; 10 Sep 2016 at 04:07.