Multi Commander > Support and Feedback

Crash upon opening Multicommander

(1/7) > >>

Susan G:
Hi-

I get a crash upon opening Multicommander. This started happening yesterday. As a result, I can't save changes to how much info the crash log saves, but if it's any help, Event Viewer reports:

Faulting application name: MultiCommander.exe, version: 6.1.0.2125, time stamp: 0x570a19e7
Faulting module name: MCAudioTools.dll, version: 1.2.0.0, time stamp: 0x570a1810
Exception code: 0xc0000409
Fault offset: 0x000000000002d978
Faulting process id: 0x2bc8
Faulting application start time: 0x01d1a30f4449da65
Faulting application path: C:\Program Files\MultiCommander (x64)\MultiCommander.exe
Faulting module path: C:\Program Files\MultiCommander (x64)\Extensions\MCAudioTools\MCAudioTools.dll
Report Id: c365656a-b4ce-464e-af34-f66bf88e1165
Faulting package full name:
Faulting package-relative application ID:

I rebooted my PC and tried again, but that didn't help. I have the latest update.

I'm running Windows 10 x64. Please let me know if I can provide any further info. The only thing I can think of that I changed was to save a new default column layout.

Thanks-

-Susan

AlanJB:
Hi Susan.

Two suggestions:

1)  Install the Portable version temporarily (in, say, C:\Temp\), change NO configuration whatsoever & see what result you get.  If it does not crash (I see no reason why it should), then something that you have changed likely has caused the crash.  You can delete the temporary installation when you have finished testing or keep it for further testing; it will not trample on your full install.

or

2)  If you are confident about this (I'd try it!):  create a backup copy of the file "MultiCommander.xml" (probably in the MultiCommander folder in your windows profile - I can't check because I only use the Portable version).

Open "MultiCommander.xml" in your favourite text editor and identify the line that begins "<crashdumpformat value=", in my copy of this file it is on line 212.  Set the value to 4 so the line reads "<crashdumpformat value="4"/>".  This will set Crash dump format to "Crash dump with maximum information (20+ MB)".  Repeat your tests - at least you have a fighting chance of sending a Crash dump.

HTH

Alan

Susan G:
Hi Alan-

Thanks so much for your detailed reply :)!

I was able to fix it once I knew where to look. I removed the "Default" columnset from the bottom of ColumnSets.xml in my text editor and everything seems to be normal.

I've had a few crashes before, but it only stopped working totally after I saved a columnset as "Default" from within the program.

BTW, my crashdumpformat value is "4", so apparently that change was saved before it crashed last time.

Thanks again!

-Susan

Mathias (Author):
The faulting module is MCAudioTools.dll

So maybe the updater failed to update that file ?

If you try AlanJB's suggestion of trying the portable version.. If that works try replace that file from the portable package.

(edit)
Did one of the new columns had anything to do with audio ?

Susan G:

--- Quote from: Mathias (Author) on May 02, 2016, 19:54:50 ---
Did one of the new columns had anything to do with audio ?

--- End quote ---
Hi Mathias-

Yes. I use the "Length" column regularly and wanted to move it left.

Thanks-

-Susan

Navigation

[0] Message Index

[#] Next page