just my 2cents from the peanut gallery, as iāve seen a few, less troubling, more spurious crashes/hangs personallyā¦
Though it strikes me that Russ was on the right track wrt sharing the Win10 OS crashing reporting details. eg. users can find them via typing āprivacyā in the search box and then selecting, āPrivacy settingsā and within that Settings applet selecting āDiagnostics & feedbackā and then scrolling down and selecting the āOpen Diagnostic Data Viewerā button which opens some WinUI which among other things highlights the diagnostic/crash reports sent to MS.
For example, here is one i recently saw:
Netcam Studio Service
Description
Faulting Application Path: C:\Program Files (x86)\Netcam Studio\NetcamStudio.Service.exe
Creation Time: 6/26/2020 5:58:14 PM
Problem: Stopped working
Status: Report sent
Problem signature
Problem Event Name: APPCRASH
Application Name: NetcamStudio.Service.exe
Application Version: 1.9.1.0
Application Timestamp: 5e430f49
Fault Module Name: avcodec-58.dll
Fault Module Version: 58.54.100.0
Fault Module Timestamp: 5da947ed
Exception Code: c0000005
Exception Offset: 0149e201
Extra information about the problem
Bucket ID: 4c6ad32c1e5985ea999c804fe0852fbf (1845491027872657343)
(fyi, the two other issues i experienced recently as client hangs, and in ability to in the client UI disable motion detection and thus could not turn off recordingā¦ resulting in my going to service manager and attempting to shut down the service which further failed/hungā¦ resulting in my opening task manager and killing the service are seen in the screenshot, and live under Bucket ID: fe107f6baf6fa3a4948f134e34e1cdb5 (1481424029043772853) & Bucket ID: 418e112b8c177d930b04ce1e33ebe983 (1946907568046336387)
While monitoring/addressing these might not result in immediate āsupportā for a given user, hopefully Henrik et al at NCS you ARE monitoring these buckets available to you with Windows Error Reporting (WER), and are appropriately prioritizing and addressing the crashes seen on a discrete, deterministic basis.
I did notice (per his crash report) Russ was running the 64bit version, whereas i am running the 32bit ver (more because initially i was running the ServerX/client and just figuring the 32bit client might be less problematicā¦ eg. i run 32bit Office & Adobe Acrobat/Photoshop clients v. 64 as do most folks, despite running 64bit Win10). Is it your recommendation to run the 64bit v. 32bit NCS Service, based on where engineering is focusing? and if so can you clarify briefly the advantages we might expect to see running 64bit v32 or visa versa, depending on which you recommend in terms of stability, reliability, perf, testing & bug fix prioritization, etc?
(on further surfing i see this thread on 32v64 bitā¦ though to extent youāve had any further experience in the past 3 yrs since that thread was last updated on one v. the other, or to the extent either takes a priority for you wrt testing & bug fix investment and/or prioritizationā¦ iād be interested in running whichever you believe is what you consider the āprimaryā self-host platform which you develop/test on. In my case, iām using a ācustomā rtsp url, for some cheap CN cams, so gather the driver question doesnāt apply to me)