Seafile Client does not start [Windows]

Seagull1 · March 22, 2023, 7:09am

Hi,

after the recent Windows 11 update, the Seafile + Drive client client’ won’t start. I re-installed, uninstalled & cleaned the registry. Nothing helps.
I see dmp-files in the crash-applet folder, but no more logs after I uninstalled everything. The last log entry I remember before the uninstall was that seafile lost the connection.
Any idea how to solve the issue?

Thanks

aracelitwillis · March 22, 2023, 3:28pm

Never met that. Sounds strange

Seagull1 · May 5, 2023, 2:04pm

Update: Still the same issue.
Did a Windows clean start - doesn’t help.
Deleted any RegEdit entry - doesn’t help.
Keep both seadrice & seafile uninstalled for a week - reinstallation afterwards doesn’t help.
Tried to install Seadrive 1.0.12 - client starts and I can enter my login data, but I’ll get an error message that the drive letter cannot be created - app crash.

I’m pretty sure it’s something about a Windows update. But cannot tell what it is. Is there someone able to read the dmp-file? Here is the analysis of WinDbg:

                   Exception Analysis                                   *

KEY_VALUES_STRING: 1

Key  : AV.Dereference
Value: NullClassPtr

Key  : AV.Fault
Value: Write

Key  : Analysis.CPU.mSec
Value: 562

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3574

Key  : Analysis.IO.Other.Mb
Value: 18

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 25

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

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

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

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

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

Key  : WER.OS.Branch
Value: co_release

Key  : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z

Key  : WER.OS.Version
Value: 10.0.22000.1

Key  : WER.Process.Version
Value: 3.0.2.0

FILE_IN_CAB: seadrive-gui.exe.11628.dmp

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=00007ffcb28cd410
rdx=0000000000000000 rsi=00000080e32fe2c0 rdi=00007ffcb57dc470
rip=00007ffcb1ee1cc2 rsp=00000080e32fe0d0 rbp=0000000000000012
r8=000001a1710bbe01 r9=0000000000000001 r10=000001a170fc032c
r11=00000080e32fdf90 r12=00007ffd0a94bf24 r13=00007ffd0c38da40
r14=00007ffd0c4374a0 r15=00007ffd0a94c14c
iopl=0 nv up ei pl nz na pe nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
atio6axx!IcdPresentBuffers+0x30c2:
00007ffcb1ee1cc2 48894860 mov qword ptr [rax+60h],rcx ds:0000000000000060=???
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffcb1ee1cc2 (atio6axx!IcdPresentBuffers+0x00000000000030c2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000060
Attempt to write to address 0000000000000060

PROCESS_NAME: seadrive-gui.exe

WRITE_ADDRESS: 0000000000000060

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden. (>> 0x%p links to RAM but the process was aborted)

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 0000000000000060

STACK_TEXT:
00000080e32fe0d0 00007ffcb1ee1b07 00000080e32fe170 00007ffcb1ee1775 00000080e32fe1a0 00007ffcb1edb884 00000080e32fe1d0 00007ffd0a94c18c 00000080e32fe200 00007ffd0c3919ff 00000080e32fe230 00007ffd0c39070b 00000080e32fe280 00007ffd0c393a74 00000080e32fe8e0 00007ffd0c3b2bbf 00000080e32fe920 00007ffd0c3b294b 00000080e32fe960 00007ffd0c3b25d3 00000080e32feaa0 00007ffd503764c3 00000080e32feb40 00007ffcbdee960a 00000080e32feb70 00007ffcbdee7bab 00000080e32fecd0 00007ffcbdee92ec 00000080e32fefd0 00007ffcbdeadf10 00000080e32ff080 00007ffcbdeaec01 00000080e32ff0e0 00007ffcbdead453 00000080e32ff110 00007ffcbd68ba30 00000080e32ff180 00007ffcb72c14e6 00000080e32ff1b0 00007ffcbc8a489a 00000080e32ff200 00007ffcbd65068d 00000080e32ff2a0 00007ffcc0db118f 00000080e32ff520 00007ffcc0dad3cb 00000080e32ff550 00007ff69bc6d5e8 00000080e32ff580 00007ff69bcf35d7 00000080e32ff6d0 00007ff69bcf153e 00000080e32ff760 00007ffd50d15590 00000080e32ff7a0 00007ffd52b2485b 00000080e32ff7d0 0000000000000000 : 0000000000000000 0000000000000012 00000080e32fe2c0 0000000000000000 : atio6axx!IcdPresentBuffers+0x30c2
: 00007ffcb57dc470 00007ffd0a94c14c 000001a1732f1950 00000080e32fe2c0 : atio6axx!IcdPresentBuffers+0x2f07
: 0000000000000000 00007ffcb57dc468 00007ffd0c447610 0000000000000000 : atio6axx!IcdPresentBuffers+0x2b75
: 00007ffd0c447610 0000000000000001 00000080e32fe2c0 00007ffd0c43bdf8 : atio6axx!DrvSetCallbackProcs+0x14
: 000001a170fc17b0 00007ffd0a94c084 0000000000000011 00000080e32fe2c0 : atig6pxx!DrvSetCallbackProcs+0x40
: 0000000039010ef4 00000080e32fe380 0000000000000002 0000000000000001 : opengl32!pgldrvLoadAndAllocDriverInfo+0x233
: 00007ffd51274bf0 0000000000000000 0000000000000001 0000000000000000 : opengl32!LoadAvailableDrivers+0x2a7
: ffffffff90010ed6 ffffffff90010ed6 00000080e32fe9c8 0000000000000003 : opengl32!_DescribePrimaryPixelFormat+0x24
: ffffffff90010ed6 00000080e32fea39 0000000000000000 0000008000000279 : opengl32!wglNumHardwareFormats+0x3f
: 00007ffd0c391c70 00007ffd503eb008 00007ffd0c370000 00007ffd5052e321 : opengl32!wglDescribePixelFormat+0xfb
: 000000000003034a 0000000000000000 ffffffff90010ed6 00000080e32fec70 : opengl32!wglChoosePixelFormat+0x63
: 000000000003034a ffffffff90010ed6 00007ffd0c370000 0000000000000000 : gdi32full!ChoosePixelFormat+0x43
: 00007ffcbe0006b8 0000000000000000 000000000000002f 0000000000000000 : qwindows+0x4960a
: 0000000000000000 00000000ffffffff 0000000000000000 0000000000000000 : qwindows+0x47bab
: 00007ffcbe002e60 0000000000000000 0000000000000002 0000000000000002 : qwindows+0x492ec
: 00007ffcbdffeaa8 0000000000000000 000001a171045530 000001a171045530 : qwindows+0xdf10
: 000001a170fda161 000001a171045530 0000000000000001 00000080e32f0000 : qwindows+0xec01
: 000001a171045530 000001a17104b280 00007ffcbda213d0 0000000000000000 : qwindows+0xd453
: 000001a17104b280 000001a17104b280 00000080e32ff258 0000000000000000 : Qt5Gui!QOpenGLContext::create+0x30
: 000001a1710390e0 000001a17104d4b0 00000080e32ff258 0000000000000000 : Qt5WebEngineCore!QtWebEngineCore::initialize+0x146
: 000001a170fd7800 000001a170e602bc 000001a170e60cc0 000001a1710243c0 : Qt5Core!QCoreApplicationPrivate::init+0x54a
: 000001a170fd7800 0000000000000000 0000000000000000 00000080e32ff5e0 : Qt5Gui!QGuiApplicationPrivate::init+0x3d
: 0000000000000000 000001a1710274f0 00000000fffefffe 000001a171035a70 : Qt5Widgets!QApplicationPrivate::init+0xf
: 0000000000000000 000001a1710274f0 000001a170fcb360 00007ffd52b56086 : Qt5Widgets!QApplication::QApplication+0x5b
: 0000000000000001 0000000000000000 000001a1710374c0 0000000000000000 : seadrive_gui+0x3d5e8
: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : seadrive_gui+0xc35d7
: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : seadrive_gui+0xc153e
: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x10
: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x2b

STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: atio6axx+30c2

MODULE_NAME: atio6axx

IMAGE_NAME: atio6axx.dll

FAILURE_BUCKET_ID: NULL_CLASS_PTR_WRITE_c0000005_atio6axx.dll!Unknown

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 31.0.12044.3

FAILURE_ID_HASH: {ec29a40f-7d66-9019-3157-4aae6556f223}

Followup: MachineOwner

ssgbarnes · September 16, 2023, 4:28pm

I am having a similar issue. SeaDrive will not launch after windows 11 update. I am getting the following error message in the event viewer.

Faulting application name: seadrive-gui.exe, version: 3.0.5.0, time stamp: 0x64d5f3c6
Faulting module name: atio6axx.dll, version: 31.0.12046.13002, time stamp: 0x64acc95f
Exception code: 0xc0000005
Fault offset: 0x0000000000131cc2
Faulting process id: 0x0xB3C
Faulting application start time: 0x0x1D9E8B92E509B0E
Faulting application path: C:\Program Files\SeaDrive\bin\seadrive-gui.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0393950.inf_amd64_0111bba41e572504\B393713\atio6axx.dll
Report Id: 42f3a2fc-406c-4103-9a3f-a3bc73bf7232
Faulting package full name:
Faulting package-relative application ID:

Has anyone had a similar issue and solved it?

ssgbarnes · September 16, 2023, 4:30pm

To add I have done a fresh install of Windows 11 and before updating after the install I can get seadrive to launch, after updates same behavior. Trying to open it I get the blue circle for a second or two then nothing.

ssgbarnes · September 16, 2023, 5:51pm

Figured it out, it was the atio6axx.dll driver, needed to update.