ContextMenu64 = APPCRASH

[Zardoz2293]

If "Show 64-bit Context Menu" is checked I'm getting consistently "ContextMenu64.exe has stopped working" crash.

Code: Select all

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	ContextMenu64.exe
  Application Version:	1.1.13.1
  Application Timestamp:	5261cc00
  Fault Module Name:	StackHash_446b
  Fault Module Version:	6.1.7601.18247
  Fault Module Timestamp:	521eaf24
  Exception Code:	c0000374
  Exception Offset:	00000000000c4102
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	1033
  Additional Information 1:	446b
  Additional Information 2:	446b3f6ba33c35e5377e10dfa8694adb
  Additional Information 3:	919c
  Additional Information 4:	919ca4853ea01130e542b8cf89f0d108

[admin]

On doing what?

[Zardoz2293]

The usual culprit WinRAR v5.01 (64-bit)

Update:
Open RAR or SFX, Archive [file(s)/folder(s)], and Test Archive is what I've tested.

[admin]

Well, only WinRAR can fix that.

[Zardoz2293]

Well, only WinRAR can fix that.

Performed testing with Windows Explorer with WinRAR and no concerns. Still RAR Labs?

[admin]

It's the usual crappy shell extension thing. All file manager makers know this phenomenon. Explorer somehow does not crash (secret non-documented magic) , your file manager crashes.

[Mesh]

For what it's worth, I'm not seeing that problem here. I also have WinRAR v5.01 (64-bit) running on Win 7 x64.. I tried the Test Archive function both ways - going through the secondary 64-bit context menu when XY was configured for 32-bit, as well as when XY was configured to present the 64-bit menu by default. Both times it worked without any problems.

Perhaps your WinRAR install is corrupted? I wonder if a reinstall would have any effect.

[Zardoz2293]

For what it's worth, I'm not seeing that problem here. I also have WinRAR v5.01 (64-bit) running on Win 7 x64.. I tried the Test Archive function both ways - going through the secondary 64-bit context menu when XY was configured for 32-bit, as well as when XY was configured to present the 64-bit menu by default. Both times it worked without any problems.

Perhaps your WinRAR install is corrupted? I wonder if a reinstall would have any effect.

1. You "tested" it twice? Or two different methods many, many times?
2. WinRAR corrupted? = No, it isn't.
3. Using ZIP, RAR, RAR5, and SFX formats?

My system is ultra stable with the exception of ContextMenu64 as the only product crashing. It's a development system and all works as expected.

[TheQwerty]

My system is ultra stable with the exception of ContextMenu64 as the only product crashing. It's a development system and all works as expected.

So should we congratulate Mesh on having a super ultra stable system or whatever the correct name for a step above ultra stable.

A pasting from Various Information might be useful.
Does this happen with the same archives all the time or is it hit or miss? (If the former, can you share one?)

In my attempts I couldn't get it to crash either.

[Zardoz2293]

Whatever it's worth with XY v13.60.0011 ContextMenu64 isn't generating APPCRASH.

Related or not to this specific concern and not trying to diverge from this thread topic, I've noticed XY will periodically start acting odd. Now I understand that's a totally vague statement, but during long usage the ICON in the Windows Taskbar for XY will go blank. When this happens, icons in vary large executable files will *not* be displayed correctly in XY. There are some other weird things that happen in XY, but I usually "solve" it by terminating XY, waiting 5 seconds, then launching XY again, and all is good until next time.

[Zardoz2293]

My system is ultra stable with the exception of ContextMenu64 as the only product crashing. It's a development system and all works as expected.

So should we congratulate Mesh on having a super ultra stable system or whatever the correct name for a step above ultra stable.

A pasting from Various Information might be useful.
Does this happen with the same archives all the time or is it hit or miss? (If the former, can you share one?)

In my attempts I couldn't get it to crash either.

My system being otherwise ultra stable was in reference to there are hundreds of developer tools, VM environments, etc. and no problems. More installed higher probability conflicts.

Currently, the APPCRASH is NOT occurring in XY build 13.60.0011. When the APPCRASH was occurring it was occurred on all archives tested, but worked without fail using the native XY context menu popup (32-bit). I had processed hundreds of RAR archives, without issue, unloaded XY (13.60.0003) and installed the new XY version (13.60.0006), read about the new context menu 64-bit feature, then immediately received the APPCRASH (using the 64-bit context menu), performed various tests and it was consistent. I posted the message to this forum and contacted WinRAR.

There archives are not corrupt.

[Zardoz2293]

Just upgraded from 13.60.0011 (no APPCRASH events), to 13.60.0013 and immediately received an APPCRASH.

[TheQwerty]

Still cannot reproduce with 13.60.0013... ContextMenu64 is solid here.

[Mesh]

Still cannot reproduce with 13.60.0013... ContextMenu64 is solid here.

Same here.

I'm sorry, Zardoz2293, but I have to wonder just how ultra stable your machine really is.

For what it's worth, I have had all sorts of odd behavior in XY pop up as a result of my AV settings. And it's not just about real-time scanning - features that monitor the system for malicious changes (in KAV, it's called System Monitor) have also caused issues.

Perhaps you want to try disabling your AV software and see if that's causing a compatibility issue.

[Zardoz2293]

Still cannot reproduce with 13.60.0013... ContextMenu64 is solid here.

I'm sorry, Zardoz2293, but I have to wonder just how ultra stable your machine really is.

Obviously your right Mesh, ContextMenu64.exe isn't responsible for crashing, it's something else causing it. It does beg the question as to why ContextMenu64.exe doesn't handle the error generated gracefully.