RTS crash on XP (ver. 10.11)

[Marks]

Hello, my RTS crash on my Windows XP SP3 on 2 machines.
In others, it won't crash or maybe once a month but on this 2 PCs it's like once a day. I have the dump file of the crash but with 770000 lines I can't get the error.
I've noticed few errors like setupapi.dll that is missing or like my server name is too long to be connected.
I can't really share my dump file because it contain sensitive data like my DNS name.
Do you have any idea of this error ?

Thank you

[Marks]

UPADATE : I opened the dump file with WinDbg but I have symbols issue. Indeed, kernel32.pdb and ntdll.pdb can't be finded by the system.
I can't use the server path of Microsoft because I work offline.
I can't get the error code btw in WinDbg because of the symbol issue.
Does anyone have an idea of how I can solve this ?
Thanks.

[Marks]

UP : Anyone to help me ?
I use like 20 PCs, but RTS crash only on 2 PCs (XP SP2 and 3) with 10.11 version of RTS.
I don't know how to see what's going on with crashs and what causing crash of RTS.

[xCSxXenon]

Same two PCs?
Fixed the issues as described in the dump file?

[therube]

(I'll just note, that from time to odd time, my XP RTS also crashes.
No clue what precipitates that?
The XP box basically acts as a server, so unless I actually looked - which I never do, I'd not even realize that it had crashed. Instead, I'll periodically take a look, remotely, at the log files to confirm that they're being generated, currently. And if they are, I know FFS hasn't crashed.)

[Marks]

UPDATE : I used WinDbg to find why RTS crash.
This is the output of !analyze -v command :
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 518

Key : Analysis.Init.CPU.mSec
Value: 4984

Key : Analysis.Init.Elapsed.mSec
Value: 162437

Key : Analysis.Memory.CommitPeak.Mb
Value: 122

Key : Timeline.OS.Boot.DeltaSec
Value: 100269

Key : Timeline.Process.Start.DeltaSec
Value: 100187

Key : WER.Process.Version
Value: 10.11.0.0


FILE_IN_CAB: RealTimeSync_XP.exe 10.11 CrashDump 2022-09-26 174608.dmp

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
eax=0012f084 ebx=0012f12c ecx=00000000 edx=2d3b0002 esi=0012f118 edi=007f7644
eip=7c812fd3 esp=0012f080 ebp=0012f0d4 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000206
kernel32!RaiseException+0x52:
7c812fd3 5e pop esi
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 7c812fd3 (kernel32!RaiseException+0x00000052)
ExceptionCode: e06d7363 (C++ EH exception)
ExceptionFlags: 00000001
NumberParameters: 3
Parameter[0]: 19930520
Parameter[1]: 0012f12c
Parameter[2]: 007f7644
unable to find C-Runtime symbols, even with unqualified search

PROCESS_NAME: RealTimeSync_XP.exe

ERROR_CODE: (NTSTATUS) 0xe06d7363 - <Unable to get error code text>

EXCEPTION_CODE_STR: e06d7363

EXCEPTION_PARAMETER1: 19930520

EXCEPTION_PARAMETER2: 0012f12c

EXCEPTION_PARAMETER3: 007f7644

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
0012f0d4 0067eb28 e06d7363 00000001 00000003 kernel32!RaiseException+0x52
0012f118 0066338e 0012f12c 007f7644 0012f178 RealTimeSync_XP+0x27eb28
0012f140 00663359 00000006 0012f15c 0041029d RealTimeSync_XP+0x26338e
0012f14c 0041029d 00000001 0378b430 0012f1a0 RealTimeSync_XP+0x263359
0012f15c 00439e05 0012f1ec 1993cac0 0012f280 RealTimeSync_XP+0x1029d
0012f1a0 00439853 00000000 1993c968 03891898 RealTimeSync_XP+0x39e05
0012f208 006b0252 0012f224 1993c9c8 53eda090 RealTimeSync_XP+0x39853
0012f2a8 006c5abe 021ccee8 1993c8e8 0012f460 RealTimeSync_XP+0x2b0252
0012f388 006c57b2 0012f430 00000032 00000000 RealTimeSync_XP+0x2c5abe
0012f46c 006c7bd7 0000000a 00000000 0012f5b0 RealTimeSync_XP+0x2c57b2
0012f614 006c3ab9 1993cdf8 ffffffff 021e3c88 RealTimeSync_XP+0x2c7bd7
0012f698 006c5360 0012f8c4 1993c13c ffffffff RealTimeSync_XP+0x2c3ab9
0012fa5c 006bb762 0012faac 1993c0b8 001989e8 RealTimeSync_XP+0x2c5360
0012fbd8 005b718f 001d17e0 0012fc04 005b6547 RealTimeSync_XP+0x2bb762
0012fbe4 005b6547 001989e8 006bb090 00000000 RealTimeSync_XP+0x1b718f
0012fc04 005aef01 001989e8 001e5a98 001d17e0 RealTimeSync_XP+0x1b6547
0012fc1c 005af9d1 001a1790 001989e8 001d17e0 RealTimeSync_XP+0x1aef01
0012fc48 005afd94 001d17e0 00000000 001d17e0 RealTimeSync_XP+0x1af9d1
0012fc64 005aee15 001d17e0 1993c7f8 001d17e0 RealTimeSync_XP+0x1afd94
0012fc98 005af44c 001d17e0 1993c630 00198b10 RealTimeSync_XP+0x1aee15
0012fd50 005b7d0e 001b2fd8 001b2fe8 001b2fd8 RealTimeSync_XP+0x1af44c
0012fd94 005ee63a 1993c6a8 001b2fd8 001989e8 RealTimeSync_XP+0x1b7d0e
0012fdc8 005b7253 1993c69c 00000000 0078fe18 RealTimeSync_XP+0x1ee63a
0012fdfc 006bacfd 1993c580 00000000 0078fe18 RealTimeSync_XP+0x1b7253
0012fee0 005f3d1c 1993c474 00000000 0078fe18 RealTimeSync_XP+0x2bacfd
0012ff14 005e2972 008113f4 00169140 1993c42c RealTimeSync_XP+0x1f3d1c
0012ff4c 004dcf28 008113f4 00169140 0012ff74 RealTimeSync_XP+0x1e2972
0012ff5c 006bbf37 00400000 00000000 00000000 RealTimeSync_XP+0xdcf28
0012ff74 00666809 00400000 00000000 00152348 RealTimeSync_XP+0x2bbf37
0012ffc0 7c816037 0012f840 7c925c49 7ffdb000 RealTimeSync_XP+0x266809
0012fff0 00000000 0066688d 00000000 78746341 kernel32!RegisterWaitForInputIdle+0x49


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: realtimesync_xp+27eb28

MODULE_NAME: RealTimeSync_XP

IMAGE_NAME: RealTimeSync_XP.exe

FAILURE_BUCKET_ID: CPP_EXCEPTION_e06d7363_RealTimeSync_XP.exe!Unknown

OSPLATFORM_TYPE: x86

OSNAME: Windows XP

IMAGE_VERSION: 10.11.0.0

FAILURE_ID_HASH: {91114986-39a1-6ea0-db47-3cb7ecbbeb21}

Followup: MachineOwner
---------

If someone can explain me where is the error ?
Thanks.

[xCSxXenon]

Looks like a bunch of useless info unfortunately. Have you verified that the hardware is healthy? It wouldn't be unexpected if the hardware running Windows XP is having issues. Check SMART data for the drives, run a memtest to verify that the RAM isn't failing.

[Al3sk]

Hello,

I'm following up on the work done by Marks on these crash problems, which are still going on.

Modifications have been made to the computers where the problem occurs too often, without a solution having been found.

SMART and RAM are good.

If it helps, I'll send you the dump file.

Thanks for your help.

[xCSxXenon]

That dumps produces the same useless info as above lol
Try running a stack trace?
https://freefilesync.org/faq.php#trace

[Zenju]

FreeFileSync/RealTimeSync on XP is beyond dead at this point.

That said, your dmp file shows that RTS is crashing due to a failed memory allocation of 64 kB. So apparently your system ran out of memory.

[Plerry]

> FreeFileSync/RealTimeSync on XP is beyond dead

<pun>That almost sounds like a resurrection or reincarnation of FFS/RTS on XP ... </pun>

[xCSxXenon]

That said, your dmp file shows that RTS is crashing due to a failed memory allocation of 64 kB. So apparently your system ran out of memory.

Using Windbg, I am not getting anything close to that error. It reports:
"0xe06d7363 - <Unable to get error code text>"
What are you using to analyze the dmp file(s)?

[Al3sk]

Hello,

Thank you for your help. I work in a company with a few Windows XP (not modifiable for the moment, but the wish is there).

Following your reply, RAM has been added to the machine. We'll keep an eye on it :).

[Al3sk]

Hello,

Despite the RAM increase, the application keeps crashing, with empty dumps on the desktop and sometimes with the error message: a device attached to the system is not working properly”.

Note that the copy is made on a network drive with RealTimeSync (only local drives are monitored).

Thanks for your help.