Crashing on Windows 10

[Lee]

Hi,

Earlier this day xplorer² started crashing. I was unable to even end the task in Task Manager and had to restart Windows again. I was on version 2.x.x.x (can't remember the exact version).

The frequency of crashes increased and as you can imagine it was hugely frustrating and time wasting. I thought maybe because the old version wasn't compatible with windows 10, so I've just paid for new Pro licence. I uninstalled the old version (including saved settings + licence) and installed the newest. Much to my horror the crashing is still continuing. Now it can't even load to get a crash report, it freezes the moment it starts.

I'm running Windows 10 (inc Anniversary update).

Here are two Windows reliability reports:

Source
xplorer² - explorer replacement
Summary
Stopped responding and was closed
Date
13/10/2016 17:34
Status
Report sent
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\zabkat\xplorer2\xplorer2_64.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: xplorer2_64.exe
Application Version: 3.3.0.1
Application Timestamp: 57fc8fcd
Hang Signature: 97bc
Hang Type: 134217728
OS Version: 10.0.14393.2.0.0.256.48
Locale ID: 2057
Additional Hang Signature 1: 97bc41ea0f520361a5d014b9fecf29f5
Additional Hang Signature 2: 7bca
Additional Hang Signature 3: 7bca65670c8c8a9277b497166cf1fa1b
Additional Hang Signature 4: 97bc
Additional Hang Signature 5: 97bc41ea0f520361a5d014b9fecf29f5
Additional Hang Signature 6: 7bca
Additional Hang Signature 7: 7bca65670c8c8a9277b497166cf1fa1b
Extra information about the problem
Bucket ID: 56b2ae90349978647928f9951ad61d51 (50)


Source
xplorer² - explorer replacement
Summary
Stopped responding and was closed
Date
13/10/2016 17:48
Status
Report sent
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\zabkat\xplorer2\xplorer2_64.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: xplorer2_64.exe
Application Version: 3.3.0.1
Application Timestamp: 57fc8fcd
Hang Signature: aae4
Hang Type: 134217728
OS Version: 10.0.14393.2.0.0.256.48
Locale ID: 2057
Additional Hang Signature 1: aae4865ba2edba4c2692dddd7851429b
Additional Hang Signature 2: 32aa
Additional Hang Signature 3: 32aaee93022f339fa5ef6657fc0ec8fc
Additional Hang Signature 4: aae4
Additional Hang Signature 5: aae4865ba2edba4c2692dddd7851429b
Additional Hang Signature 6: 32aa
Additional Hang Signature 7: 32aaee93022f339fa5ef6657fc0ec8fc
Extra information about the problem
Bucket ID: 1e3ec3500f75addb399ed0873187f5d7 (50)



Any help appreciated! I just forked out cash on an upgrade to fix this

[nikos]

it's hard for me to tell you what's wrong with this information. What are you doing when xplorer2 starts misbehaving? there are many things to consider as explained here www.zabkat.com/x2cs_bug.htm

from what you are saying, xplorer2 is STUCK and not crashing. Try to start xplorer2 in a simple mode by using a command line like:

xplorer2_64.exe /T /1 c:\

and see if you can at least get the program going.
a more radical solution would be to fully uninstall (losing your registry settings) then reinstalling in the "factory" mode

[Lee]

Thanks for getting back to me Nikos.

Yes, it's freezing rather than crashing, but eventually other windows tasks also become unresponsive e.g. clicking task bar app icons stops working.

Running

Code: Select all

xplorer2_64.exe /T /1 c:\ 

seems to be working at the moment. No crash so far.

Going to Help > Last Error shows: There is crash dump file. Windows error = 50.

[nikos]

it could have been some "bad" folder. If this happens again try to get a full memory dump of the stuck process as explained here
http://www.clausbrod.de/cgi-bin/view.pl ... ic20070630

it would be even better if you could work this tool out
www.zabkat.com/blog/procdump-debug-hung-processes.htm

[Lee]

Hey Nikos,

It's just happened again, it was working fine for an hour or so.

I've PMed you a procdump file.

Thanks

[nikos]

I saw a PM but I cannot read it. Can you email the dump to me? The support email is inside xplorer2 HELP > ONLINE SUPPORT

[Lee]

Just sent an email.

It just froze in a simple mode too.

[nikos]

your problems seems to be too many overlay icons. Sugarsync alone has 3-4 threads, whatever it's trying to do!?
anyway, if you can live without fancy overlays, use TOOLS > OPTIONS menu and from ADVANCED page tick off the option "extract icon overlays"

if you need your overlays, then you must lose many of them. A maximum of 12 are supported and I bet you have way above that, see this registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers

[Lee]

Ahh interesting. I thought excess icons were simply ignored.

I've removed a load from the registry and disabled "extract icon overlays" from the xplorer2 options for good measure.


Just restarted the machine, I'll let you know how it goes.

Thanks for your help.

[Lee]

Oh dear, it just crashed again even though I applied the above mentioned changes.

I'll send through the most recent procdump.

[nikos]

the crash information is a bit funny (corrupt?) but it points to a different cause. I cannot offer any explanation why it happened. Did you have the xplorer2 console window open at the time? (not that it is to blame, I am just trying to validate the information you sent me)

[Lee]

No, I didn't have the xplorer2 console window open. Just Tree, Dual Pain, Mini scrap, Preview.

I'll catch another procdump when it crashes again.

Thanks for you help.

[Raine]

No, I didn't have the https://www.tenderbuttons.com/crazy-bulk-review-results supplement called crazy bulk xplorer2 console window open. Just Tree, Dual Pain, Mini scrap, Preview.

I'll catch another procdump when it crashes again.

Thanks for you help.

This happens a lot to me on Windows 10 to. It's hard to figure out what the real cause is.

[nikos]

every case is usually different so please send me HELP > CRASH INFORMATION (menu command) dump file or if xplorer2 gets stuck try to get the procdump as explained above