1.5.4 x64 Client crash


#1

I’ve installed 1.5.4 x64 server running on WinSrv2016 and using 1.5.4 x64 Win 10 Pro client but the client keeps on crashing after a while.
The client got a pretty clean install and I had no problem with this on 1.5.2.

Attaching screenshot and debug.



#2

What is strange is that normally Netcam Studio Client (just like Netcam Studio X) uses a crash detection library so normally when this occurs if offers a nice dialog allowing you to send the crash report and so that I can know where it comes from.

Here it’s not the case and I don’t know why, like it’s really at another level and not directly inside the Client.

Unfortunately with this stack trace and such little information, it looks pretty complicated to tell where it’s coming from…


#3

Maybe it could be the .Net framework or something (since it’s mentioned)? I’ve updated the Windows 10 Pro with latest patches.
If you want to troubleshoot further directly I can send you an PM with teamviewer/rdp User/Pass.

Regards
Mads


#4

Well if it doesn’t crash within the scope that it can be catched by the app, there isn’t much that I can diagnose

Most of us run windows 10 with the latest patches and I haven’t seen this one before so yes you can try to reinstall .net 4.6 but either we need steps to reproduce or logs which speak a bit more than just clr.dll crashing.


#5

I have the same problem with Client 1.5.4 X 64 on windows 7.
I’ve tried this version on 3 different pc with windows 7 and they all crashed.

Problem signature:
Problem Event Name: APPCRASH
Application Name: NetcamStudio.Client.exe
Application Version: 1.5.4.0
Application Timestamp: 59146bdf
Fault Module Name: clr.dll
Fault Module Version: 4.6.1099.0
Fault Module Timestamp: 58d874f8
Exception Code: c00000fd
Exception Offset: 000000000000a5f0
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0dfb
Additional Information 2: 0dfbd0c4c999b58f86e39c666f1a1108
Additional Information 3: a5b6
Additional Information 4: a5b6520d46e25bd49dffebe6271e2283


#6

Still got the problem, even after installing .Net Framework 4.6.
Currently using web, but it seams to have a memory leak. (At least when I checked this morning).
I’ll try again tonight.

Regards
Mads


#7

Still looking forward for steps to reproduce.

So it’s not directly on startup but really while using it ?

On what screen is it when it occurs and while doing what ?

I need details here. How did you check memory ? is it when using client on same computer (than service) or another one?

What is the content of your program files\netcam studio - 64 bit ? (send a screenshot).

Also if it is on a Windows N edition, did you install / reinstall after moving to the creators update the windows media pack ?


#8

Hi,

I got the exact same with the client on my camserver (running Windows 2012 r2 x64) for a couple of times.

Naam van toepassing met fout: NetcamStudio.Client.exe, versie: 1.5.4.0, tijdstempel: 0x59146bdf
Naam van module met fout: clr.dll, versie: 4.0.30319.34209, tijdstempel: 0x5348a1ef
Uitzonderingscode: 0xc00000fd
Foutmarge: 0x0000000000009257
Id van proces met fout: 0x7218
Starttijd van toepassing met fout: 0x01d2ce2891a888f9
Pad naar toepassing met fout: C:\Program Files\Netcam Studio - 64-bit\NetcamStudio.Client.exe
Pad naar module met fout: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Rapport-id: 7418f907-3a66-11e7-8108-000c294c4fb2
Volledige pakketnaam met fout: 
Relatieve toepassings-id van pakket met fout: 

In my case, these were the steps I did:

  • Connected via RDP to the camera server
  • Started the client
  • Opened the library
  • Looked trough the library to find some specific videos
  • Played a couple of videos
  • Left the library GUI (and RDP session) open when I left

I opened the client around 9:00. And it crashed not until 20:30. So the client was untouched for more then 11 hours, before it crashed. Since the client was in library view, it was not displaying live cam views.


#9

Ok, will try to reproduce based on theses steps. Thanks.


#10

Some extra info. I tested this also with the same result on win 7 home edition. The crash is for me that the client just Exit. It doesn´t hang or crash the OS or an end task is not necessary. It just Exit.
Also, when the client was in viewing mode showing live video this happened just after a few hours. The same situation, but now showing the Event log, i.e.e no video, it has been running for hours.


#11

Would be good to try to reproduce using the x86 version on one system that does it.

Maybe there it will offer to send a crash report.


#12

This morning it had crashed again. Tried to install .NET 4.7 without any improvement.

Directory output from Program Files:

Adding the crash rapport:

Version=1
EventType=APPCRASH
EventTime=131388991303643134
ReportType=2
Consent=1
UploadTime=131388991309883495
ReportIdentifier=a76352e8-358a-11e7-a75f-80ee7316c73d
IntegratorReportIdentifier=5f1d9e74-4045-4187-a0a9-539818c143e1
WOW64=1
NsAppName=NetcamStudio.Client.exe
AppSessionGuid=00001b14-0001-001d-c464-a36897c9d201
TargetAppId=W:000683a1d79923dd113f16f8f96b865285a600000000!0000a78dc6e29d4018ec5bb0814e8ea30a9aac0e6070!NetcamStudio.Client.exe
TargetAppVer=2017//05//08:19:55:39!24c6da!NetcamStudio.Client.exe
BootId=4294967295
Response.BucketId=74faebf621986fe5743f392758172987
Response.BucketTable=1
Response.LegacyBucketId=108910307307
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=NetcamStudio.Client.exe
Sig[1].Name=Application Version
Sig[1].Value=1.5.2.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5910cd3b
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.1066
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58d9f07f
Sig[6].Name=Exception Code
Sig[6].Value=e0434352
Sig[7].Name=Exception Offset
Sig[7].Value=000da932
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1044
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=2beb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=7273
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=7273133d7919ab6498a93f4829d54f16
UI[2]=C:\Program Files (x86)\Netcam Studio\NetcamStudio.Client.exe
UI[3]=Netcam Studio Client has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\Netcam Studio\NetcamStudio.Client.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\System32\KERNEL32.dll
LoadedModule[4]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\apphelp.dll
LoadedModule[6]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[7]=C:\Windows\System32\msvcrt.dll
LoadedModule[8]=C:\Windows\System32\sechost.dll
LoadedModule[9]=C:\Windows\System32\RPCRT4.dll
LoadedModule[10]=C:\Windows\System32\SspiCli.dll
LoadedModule[11]=C:\Windows\System32\CRYPTBASE.dll
LoadedModule[12]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[13]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[14]=C:\Windows\System32\SHLWAPI.dll
LoadedModule[15]=C:\Windows\System32\combase.dll
LoadedModule[16]=C:\Windows\System32\ucrtbase.dll
LoadedModule[17]=C:\Windows\System32\GDI32.dll
LoadedModule[18]=C:\Windows\System32\gdi32full.dll
LoadedModule[19]=C:\Windows\System32\USER32.dll
LoadedModule[20]=C:\Windows\System32\win32u.dll
LoadedModule[21]=C:\Windows\System32\IMM32.DLL
LoadedModule[22]=C:\Windows\System32\kernel.appcore.dll
LoadedModule[23]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[24]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[25]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[26]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\f06d35cdb58e63c8a25f1658f23fd20d\mscorlib.ni.dll
LoadedModule[27]=C:\Windows\System32\ole32.dll
LoadedModule[28]=C:\Windows\system32\uxtheme.dll
LoadedModule[29]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[30]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[31]=C:\Windows\System32\msvcp_win.dll
LoadedModule[32]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Netcam Studio Client
AppPath=C:\Program Files (x86)\Netcam Studio\NetcamStudio.Client.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=35A9FBEB2D0D9790418072E9386FCCCA
MetadataHash=-112563689

Attaching screenshot of dump directory, might be crashing within some intervals or something?

Crashfiles can be found here https://ufile.io/2hzd5

Regards
Mads


#13

In my case netcam client 1.5.4 x64 crashed when I attempted to connect to server, the connection was not able to established.
I was able to connect with web client though.

Thanks


#14

I have a crash dump generated by Microsoft on windows 7 64bit ( not by the application ), would you be interested ( about 10M compressed 2M) ?
If yes how can I send it to you ?

Thanks


#15

No need to send such logs, they don’t really help.

I really need to be able to reproduce the problem locally (which wasn’t the case so far).


#16

I found the issue with my problem ( netcam client crashed at login ).

The user I used to connect had only view permission ( I was able to connect with web client ) .
I just added permission Edit Settings and it was able to connect with netcam client

It seems like netcam client handles permission error by crashing.

With that same user ( with view and edit settings ) once connected, I was able to change camera settings.
However as soon as I clicked on Connected Users or Library it crashed again.

On another note, web client did freeze a few times .
For viewing purposes I do prefer the web client full screen ( live ) than the client ( now that I’m able to connect with it )

Thanks


#17

Still haven’t been able to reproduce (even with limited permissions) however my 2 systems are already on 1.5.5 and so where the clients I have been using as well so i’ll probably try to build a 1.5.5 to try on your end.

I’ve anyway protected a bit more some parts which I may suspect so that it should logs cleans errors rather than crashing if something happens there.


#18

I have similar issues, one thing I notice is:

I have no external access set up so why is there a command to a URL? These errors coincide with the client crashing (192.168.1.155)

Sorry I should learn to read, mine is the 32bit client


#19

If you have crash issue on the Client, you can give a try to 1.5.5:

I don’t guarantee it will solve the problem since I didn’t manage to reproduce it on any of my system however i’ve tried to secure some parts around the background tasks (as it seems to occur even when the user does nothing).

In case of crash it should either log something or offer the possibility to send report so there is something strange with this 1.5.4 that was published, hopefully this one will act a bit differently :slight_smile:


#20

Any news on this?

Somebody still having such issues with 1.5.5 / 1.5.6?