Client Log Analysis?

[greg4168@gmail.com]

Hi - I'm struggling with the Windows client cra$ng on me quite frequently.  Running a pretty clean Windows 10 machine with plenty of resources and nothing but Jamkazam, Addictive Drums 2, and Universal Control for Presonus installed and the app crashes multiple times during every session.  Wondering if there's someone that could help analyze the log file to determine where there's a fault.

Thanks

[greg4168@gmail.com]

Hi - I'm struggling with the Windows client cra$ng on me quite frequently.  Running a pretty clean Windows 10 machine with plenty of resources and nothing but Jamkazam, Addictive Drums 2, and Universal Control for Presonus installed and the app crashes multiple times during every session.  Wondering if there's someone that could help analyze the log file to determine where there's a fault.

Thanks

Seeing some telltale signs in the log file possibly pointing to some issues me and many others are having with the application cra$ng randomly.  These are in the log file just before a crash:

SessionAlert- type:1 msg: <User> reports network is mangling your source port information.   (name removed)
Receiving probe Pkts but no audio packets from <User>


Here's my system info from the log file, wondering if anyone has suggestions based on it:

SYSTEM INFO
<usage>
<machash>hidden</machash>
<version>2.00</version>
<release>"1.0.3843"</release>
<os>Win32</os>
<osver>6.2.9200.1</osver>
<qt>5.5.1</qt>
<is64bit>1</is64bit>
<cpu_id>GenuineIntel</cpu_id>
<cpu_extid>Intel® Core™ i7-6770HQ CPU @ 2.60GHz</cpu_extid>
<cpu_sse2>1</cpu_sse2>
<cpu_threads>8</cpu_threads>
<paralleldecode>1</paralleldecode>
<paralleldecodethreads>7</paralleldecodethreads>
<audioin>AudioBox ASIO Driver</audioin>
<audiointype>3</audiointype>
<painputlatency>4.30839</painputlatency>
<audioout>AudioBox ASIO Driver</audioout>
<audioouttype>3</audioouttype>
<paoutputlatency>2.49433</paoutputlatency>
<monitor>JamKazam Virtual Monitor</monitor>
<mon_audioouttype>3</mon_audioouttype>
<mon_paoutputlatency>2.49433</mon_paoutputlatency>
<chatin></chatin>
<chatintype>-1</chatintype>
<pachatinputlatency>-1</pachatinputlatency>
<ftuelatencymean>-1</ftuelatencymean>
<ftuelatencyvar>0</ftuelatencyvar>
</usage>

[greg4168@gmail.com]

Is there someone from JK that can review system info and tell us if we're missing something that could be leading to frequent crashes? I have a pretty powerful machine but am very open to recommendations if it results in being able to use the software reliably.

Here's my info. It is interesting that it says win32 when I'm running a 64 bit OS:
SYSTEM INFO
<usage>
<machash>c9c872a2d8b5c726f87d4d67cd2c7c53754ceed8</machash>
<version>2.00</version>
<release>"1.0.3903"</release>
<os>Win32</os>
<osver>6.2.9200.1</osver>
<qt>5.5.1</qt>
<is64bit>1</is64bit>
<cpu_id>GenuineIntel</cpu_id>
<cpu_extid>Intel® Core™ i7-6770HQ CPU @ 2.60GHz</cpu_extid>
<cpu_sse2>1</cpu_sse2>
<cpu_threads>8</cpu_threads>
<paralleldecode>1</paralleldecode>
<paralleldecodethreads>7</paralleldecodethreads>
<audioin>AudioBox ASIO Driver</audioin>
<audiointype>3</audiointype>
<painputlatency>-1</painputlatency>
<audioout>AudioBox ASIO Driver</audioout>
<audioouttype>3</audioouttype>
<paoutputlatency>-1</paoutputlatency>
<monitor>JamKazam Virtual Monitor</monitor>
<mon_audioouttype>3</mon_audioouttype>
<mon_paoutputlatency>-1</mon_paoutputlatency>
<chatin></chatin>
<chatintype>-1</chatintype>
<pachatinputlatency>-1</pachatinputlatency>
<ftuelatencymean>-1</ftuelatencymean>
<ftuelatencyvar>0</ftuelatencyvar>
</usage>