New beta crashes on start

[lole]

Hi,

I have the same problem crash directly at startup.
Have tried with clean installation of XY also.

This is my message:
Problem signature:
Problem Event Name: APPCRASH
Application Name: XYplorer.exe
Application Version: 13.70.0.113
Application Timestamp: 52f20e02
Fault Module Name: StackHash_36d4
Fault Module Version: 6.1.7601.18229
Fault Module Timestamp: 51fb1072
Exception Code: c0000374
Exception Offset: 000ce753
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1053
Additional Information 1: 36d4
Additional Information 2: 36d41f4d7908f856a6e3efb90c5a0451
Additional Information 3: 0272
Additional Information 4: 0272252eb31ba59c9ab73c22570d6c7b

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Lars-Olof

[admin]

Hm, this appears to be a Windows problem I have no control over.

I found something that might be related:
Fault Tolerant Heap and NTDLL.dll. Heap metadata can become corrupted and it has been identified by Microsoft as one of the most common causes of application failures. When an application crash shows the faulting module as ntdll.dll along with the Memory Access Violation (Exception Code) (0xc0000005), then Windows places the application on a watch list and, if the application crashes at least four times or more in an hour, the fault tolerant heap service will configure the application to use the fault tolerant heap service in the future (Source - Chapter 10, Memory Management, Windows Internals, Part 2: Covering Windows Server 2008 R2 and Windows 7 by Mark E. Russinovich, David A Solomon, and Alex Ionescu). The service is part of the Security Center service.

[admin]

So, Error 430 is fixed everywhere, right?

About the other error I currently have no clue and see no pattern.

[TheQwerty]

With a fresh v13.70.0113 I see the same crash as lole (and event log as LittleBig) but with some slight differences in versions:

EDIT: Just to add it occurs after the user clicks "Continue Evaluation" and then just after the main window is shown it "stops working".

Problem signature:
Problem Event Name: APPCRASH
Application Name: XYplorer.exe
Application Version: 13.70.0.113
Application Timestamp: 52f20e02
Fault Module Name: StackHash_36d4
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea8e7
Exception Code: c0000374
Exception Offset: 000ce753
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 36d4
Additional Information 2: 36d41f4d7908f856a6e3efb90c5a0451
Additional Information 3: 0272
Additional Information 4: 0272252eb31ba59c9ab73c22570d6c7b

XYplorer: 13.70.0103 (Pro Edition - Lifetime License Pro)
Loaded in: 649 ms at 2/4/2014 5:00:38 PM
Uptime: 17 hrs, 35 mins, 20 secs
Memory Usage: 88,740 KB, Virtual Memory Size: 57,204 KB

OS: Windows 7 Professional (Service Pack 1), 64-bit (6.1)
OS Uptime: 77 days, 18 hrs, 3 mins, 56 secs
UTC Offset: --05:00
User Role: User
Themes: Yes (Aero) RealSystem32: Yes

System Locale ID: 1033 (en-US)
Thread Locale ID: 1033 (en-US)
Default ANSI Code Page: 1252 (ANSI - Latin I)
Active Code Page: 1252 (ANSI - Latin I)
DBCS Code Page: No

DblClick Time: 550 ms
Screen DPI: 96 (100%)
Screen Color Depth: 32
UseDPIAwareIconSizes: No, Yes
Icon Size: small=16, large=32
Icon Size Recommended: small=16, large=32

[admin]

How can you get the Various Information when the app crashes on startup?

[TheQwerty]

How can you get the Various Information when the app crashes on startup?

It's from my existing v13.70.0103 and I only included it for the system information which should be the same...

[admin]

How can you get the Various Information when the app crashes on startup?

It's from my existing v13.70.0103 and I only included it for the system information which should be the same...

Whoops, now that you say it...

[binocular222]

113 works fine for me. No crash but tag.dat still goes empty all the time
Win 7 x32

[admin]

For successful upgrading your tag.dat should have this first line:

Code: Select all

XYplorer File Tags v2

After upgrading it is this:

Code: Select all

XYplorer File Tags v3

[kunkel321]

Bah-
It's busted good. Won't even start.
v13.70.0113 - 2014-02-05 11:56
Win 7.
Tried a couple different compatibility modes, but that didn't made a difference.

This situation is gonna cause more of a world-wide lul in productivity then that Google Doodle of the PacMan game a couple years ago! jk

[admin]

v13.70.0114 has some changes (low hopes though).

At least the Ubuntu error should now show a different number...

[TheQwerty]

No luck with .0114.

The crash has something to do with XYcopy.exe.
From a fresh version of v13.70.0114, starting XY yields a similar crash to the previous one.
Delete XYcopy.exe and XY will start without problem.

EDIT: This time from the latest beta (without XYCopy.exe):

XYplorer: 13.70.0114 (Pro Edition - 30-day Trial Version)
Loaded in: 839 ms at 2/5/2014 11:31:22 AM
Uptime: 5 secs
Memory Usage: 33,456 KB, Virtual Memory Size: 14,972 KB

OS: Windows 7 Professional (Service Pack 1), 64-bit (6.1)
OS Uptime: 77 days, 18 hrs, 59 mins, 24 secs
UTC Offset: --05:00
User Role: User
Themes: Yes (Aero) RealSystem32: Yes

System Locale ID: 1033 (en-US)
Thread Locale ID: 1033 (en-US)
Default ANSI Code Page: 1252 (ANSI - Latin I)
Active Code Page: 1252 (ANSI - Latin I)
DBCS Code Page: No

DblClick Time: 550 ms
Screen DPI: 96 (100%)
Screen Color Depth: 32
UseDPIAwareIconSizes: No, Yes
Icon Size: small=16, large=32
Icon Size Recommended: small=16, large=32

EDIT 2: If the difference in the crash is useful:

Problem signature:
Problem Event Name: APPCRASH
Application Name: XYplorer.exe
Application Version: 13.70.0.114
Application Timestamp: 52f2645d
Fault Module Name: StackHash_0273
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea8e7
Exception Code: c0000374
Exception Offset: 000ce753
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0273
Additional Information 2: 02735b0650ef24e696f3df7df2ecce4e
Additional Information 3: 61db
Additional Information 4: 61db371115e474076c8774b1d2b0e598

[admin]

But XYcopy.exe is not running on startup, weird.

Anyway, this is good news. I will recompile XYcopy.exe on Win 8.1 and upload again...

[TheQwerty]

But XYcopy.exe is not running on startup, weird.

Anyway, this is good news. I will recompile XYcopy.exe on Win 8.1 and upload again...

I don't think it has to do with it running so much as with you verifying it exists and is the correct version - which I assume you do when starting.

According to process monitor there's a series of events related to XYcopy.exe before the crash. Most are successful IRP_MJ_* operations, but within the bunch of them are two operations which fail on each attempt:

There are two FASTIO_NETWORK_QUERY_OPEN operations which get results of "Fast IO Disallowed".
Then a bit later a FASTIO_ACQUIRE_FOR_SECTION_SYNCHRONIZATION which results in "File locked with only readers" and details of "SyncType: SyncTypeCreateSection, PageProtection: " (yes that is the end).
Then one more FASTIO_NETWORK_QUERY_OPEN and finally another FASTIO_ACQUIRE_FOR_SECTION_SYNCHRONIZATION, for both of these the results remain the same as above.
(Between all of these are some successful events...)

What any of this means I do not know...

[serendipity]

No crash with version .0114 on XP SP3.