starred/mumble-mumble-voip
1
0
Fork 0
mirror of https://github.com/mumble-voip/mumble.git synced 2026-03-03 00:46:56 -05:00
Code Issues 459 Projects Packages Wiki Activity

murmur 1.5.857.0 crashing after a while on win dc 2019 #3099

New issue
Open
opened 2026-02-20 22:18:02 -05:00 by deekerman · 7 comments
deekerman commented 2026-02-20 22:18:02 -05:00
Owner
Copy link

Originally created by @zapy85 on GitHub (Feb 13, 2026).

The issue

Hi, running mumble server on DC2019 single instance and it crashes randomly.
from eventlog:

Faulting application name: mumble-server.exe, version: 1.5.857.0, time stamp: 0x68ea9657
Faulting module name: ucrtbase.dll, version: 10.0.17763.6189, time stamp: 0xbc3e3f37
Exception code: 0xc0000409
Fault offset: 0x000000000006e77e
Faulting process id: 0x1b84
Faulting application start time: 0x01dc9540d9019b94
Faulting application path: C:\Program Files\Mumble\server\mumble-server.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: 3c644861-bf14-4643-941c-fe8830193c2d
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 2154316963927479387, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: mumble-server.exe
P2: 1.5.857.0
P3: 68ea9657
P4: ucrtbase.dll
P5: 10.0.17763.6189
P6: bc3e3f37
P7: 000000000006e77e
P8: c0000409
P9: 0000000000000007
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER224B.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER299F.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29CF.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29CD.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29EE.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mumble-server.ex_e2bdbb6ac1342cd71ca0ff7b893033977dce_86cf6138_54002d58

Analysis symbol:
Rechecking for solution: 0
Report Id: 3c644861-bf14-4643-941c-fe8830193c2d
Report Status: 268435456
Hashed bucket: b70e948d8018ae1f3de5abdd587ed45b
Cab Guid: 0

Mumble version

1.5.857.

Mumble component

Server

OS

Windows

Additional information

No response

Originally created by @zapy85 on GitHub (Feb 13, 2026). ### The issue Hi, running mumble server on DC2019 single instance and it crashes randomly. from eventlog: Faulting application name: mumble-server.exe, version: 1.5.857.0, time stamp: 0x68ea9657 Faulting module name: ucrtbase.dll, version: 10.0.17763.6189, time stamp: 0xbc3e3f37 Exception code: 0xc0000409 Fault offset: 0x000000000006e77e Faulting process id: 0x1b84 Faulting application start time: 0x01dc9540d9019b94 Faulting application path: C:\Program Files\Mumble\server\mumble-server.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: 3c644861-bf14-4643-941c-fe8830193c2d Faulting package full name: Faulting package-relative application ID: Fault bucket 2154316963927479387, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: mumble-server.exe P2: 1.5.857.0 P3: 68ea9657 P4: ucrtbase.dll P5: 10.0.17763.6189 P6: bc3e3f37 P7: 000000000006e77e P8: c0000409 P9: 0000000000000007 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER224B.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER299F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29CF.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29CD.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29EE.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_mumble-server.ex_e2bdbb6ac1342cd71ca0ff7b893033977dce_86cf6138_54002d58 Analysis symbol: Rechecking for solution: 0 Report Id: 3c644861-bf14-4643-941c-fe8830193c2d Report Status: 268435456 Hashed bucket: b70e948d8018ae1f3de5abdd587ed45b Cab Guid: 0 ### Mumble version 1.5.857. ### Mumble component Server ### OS Windows ### Additional information _No response_
deekerman commented 2026-02-20 22:18:05 -05:00
Author
Owner
Copy link

@Krzmbrzl commented on GitHub (Feb 15, 2026):

As written on Matrix, I am afraid that without a full backtrace there is not much we can do to figure out what's going on 👀

@Krzmbrzl commented on GitHub (Feb 15, 2026): As written on Matrix, I am afraid that without a full backtrace there is not much we can do to figure out what's going on 👀
deekerman commented 2026-02-20 22:18:05 -05:00
Author
Owner
Copy link

@Snowknight26 commented on GitHub (Feb 17, 2026):

Seeing the same thing on Windows 10 19045.6456. What needs to be done to provide a full dump?

The logs in mumble-server.log show a lot of SSL errors before the crash.

<W>2026-02-13 11:36:09.830 1 => Ignoring connection: 45.33.x.x:49240 (Global ban)
<W>2026-02-13 11:36:10.460 1 => Ignoring connection: 45.33.x.x:49270 (Global ban)
<W>2026-02-13 11:36:10.581 1 => Ignoring connection: 45.33.x.x:49280 (Global ban)
<W>2026-02-13 11:36:14.269 1 => Ignoring connection: 45.33.x.x:49356 (Global ban)
<W>2026-02-13 21:35:59.574 1 => <0:(-1)> New connection: 185.247.x.x:45703
<W>2026-02-13 21:36:02.684 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:36:14.791 1 => <0:(-1)> New connection: 185.247.x.x:56669
<W>2026-02-13 21:36:17.792 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A00010B:SSL routines::wrong version number [13]
<W>2026-02-13 21:36:19.034 1 => <0:(-1)> New connection: 87.236.x.x:45203
<W>2026-02-13 21:36:19.039 1 => <0:(-1)> New connection: 185.247.x.x:46823
<W>2026-02-13 21:36:19.150 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-13 21:36:19.652 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:36:52.258 1 => <0:(-1)> New connection: 185.247.x.x:46181
<W>2026-02-13 21:36:52.369 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-13 21:36:52.762 1 => <0:(-1)> New connection: 87.236.x.x:36595
<W>2026-02-13 21:36:53.374 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:37:25.476 1 => <0:(-1)> New connection: 87.236.x.x:46477
<W>2026-02-13 21:37:25.587 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-13 21:37:26.484 1 => <0:(-1)> New connection: 185.247.x.x:59323
<W>2026-02-13 21:37:27.205 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:37:58.695 1 => <0:(-1)> New connection: 87.236.x.x:33513
<W>2026-02-13 21:37:58.808 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-13 21:38:00.314 1 => <0:(-1)> New connection: 185.247.x.x:52469
<W>2026-02-13 21:38:00.316 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000076:SSL routines::no suitable signature algorithm [13]
<W>2026-02-13 21:38:31.914 1 => <0:(-1)> New connection: 87.236.x.x:48143
<W>2026-02-13 21:38:32.025 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-13 21:38:33.532 1 => <0:(-1)> New connection: 87.236.x.x:37671
<W>2026-02-13 21:38:34.145 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:39:05.133 1 => <0:(-1)> New connection: 87.236.x.x:45825
<W>2026-02-13 21:39:05.136 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13]
<W>2026-02-13 21:39:07.253 1 => <0:(-1)> New connection: 87.236.x.x:58251
<W>2026-02-13 21:39:07.867 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:39:38.358 1 => <0:(-1)> New connection: 87.236.x.x:45877
<W>2026-02-13 21:39:38.469 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-13 21:39:40.977 1 => <0:(-1)> New connection: 87.236.x.x:60621
<W>2026-02-13 21:39:41.702 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:40:11.584 1 => <0:(-1)> New connection: 185.247.x.x:33729
<W>2026-02-13 21:40:11.696 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-13 21:40:14.810 1 => <0:(-1)> New connection: 185.247.x.x:48839
<W>2026-02-13 21:40:15.526 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:40:44.803 1 => <0:(-1)> New connection: 87.236.x.x:56401
<W>2026-02-13 21:40:44.805 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A0000C1:SSL routines::no shared cipher [13]
<W>2026-02-13 21:40:48.635 1 => <0:(-1)> New connection: 185.247.x.x:52173
<W>2026-02-13 21:40:49.357 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:41:18.028 1 => <0:(-1)> New connection: 185.247.x.x:39611
<W>2026-02-13 21:41:18.031 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A00006C:SSL routines::bad key share [13]
<W>2026-02-13 21:41:22.465 1 => <0:(-1)> New connection: 87.236.x.x:54435
<W>2026-02-13 21:41:23.189 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-13 21:41:56.299 1 => <0:(-1)> New connection: 87.236.x.x:46583
<W>2026-02-13 21:41:57.021 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]

then the next thing is the crash according to Windows' Reliability Monitor.

@Snowknight26 commented on GitHub (Feb 17, 2026): Seeing the same thing on Windows 10 19045.6456. What needs to be done to provide a full dump? The logs in `mumble-server.log` show a lot of SSL errors before the crash. ``` <W>2026-02-13 11:36:09.830 1 => Ignoring connection: 45.33.x.x:49240 (Global ban) <W>2026-02-13 11:36:10.460 1 => Ignoring connection: 45.33.x.x:49270 (Global ban) <W>2026-02-13 11:36:10.581 1 => Ignoring connection: 45.33.x.x:49280 (Global ban) <W>2026-02-13 11:36:14.269 1 => Ignoring connection: 45.33.x.x:49356 (Global ban) <W>2026-02-13 21:35:59.574 1 => <0:(-1)> New connection: 185.247.x.x:45703 <W>2026-02-13 21:36:02.684 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:36:14.791 1 => <0:(-1)> New connection: 185.247.x.x:56669 <W>2026-02-13 21:36:17.792 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A00010B:SSL routines::wrong version number [13] <W>2026-02-13 21:36:19.034 1 => <0:(-1)> New connection: 87.236.x.x:45203 <W>2026-02-13 21:36:19.039 1 => <0:(-1)> New connection: 185.247.x.x:46823 <W>2026-02-13 21:36:19.150 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-13 21:36:19.652 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:36:52.258 1 => <0:(-1)> New connection: 185.247.x.x:46181 <W>2026-02-13 21:36:52.369 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-13 21:36:52.762 1 => <0:(-1)> New connection: 87.236.x.x:36595 <W>2026-02-13 21:36:53.374 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:37:25.476 1 => <0:(-1)> New connection: 87.236.x.x:46477 <W>2026-02-13 21:37:25.587 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-13 21:37:26.484 1 => <0:(-1)> New connection: 185.247.x.x:59323 <W>2026-02-13 21:37:27.205 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:37:58.695 1 => <0:(-1)> New connection: 87.236.x.x:33513 <W>2026-02-13 21:37:58.808 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-13 21:38:00.314 1 => <0:(-1)> New connection: 185.247.x.x:52469 <W>2026-02-13 21:38:00.316 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000076:SSL routines::no suitable signature algorithm [13] <W>2026-02-13 21:38:31.914 1 => <0:(-1)> New connection: 87.236.x.x:48143 <W>2026-02-13 21:38:32.025 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-13 21:38:33.532 1 => <0:(-1)> New connection: 87.236.x.x:37671 <W>2026-02-13 21:38:34.145 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:39:05.133 1 => <0:(-1)> New connection: 87.236.x.x:45825 <W>2026-02-13 21:39:05.136 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13] <W>2026-02-13 21:39:07.253 1 => <0:(-1)> New connection: 87.236.x.x:58251 <W>2026-02-13 21:39:07.867 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:39:38.358 1 => <0:(-1)> New connection: 87.236.x.x:45877 <W>2026-02-13 21:39:38.469 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-13 21:39:40.977 1 => <0:(-1)> New connection: 87.236.x.x:60621 <W>2026-02-13 21:39:41.702 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:40:11.584 1 => <0:(-1)> New connection: 185.247.x.x:33729 <W>2026-02-13 21:40:11.696 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-13 21:40:14.810 1 => <0:(-1)> New connection: 185.247.x.x:48839 <W>2026-02-13 21:40:15.526 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:40:44.803 1 => <0:(-1)> New connection: 87.236.x.x:56401 <W>2026-02-13 21:40:44.805 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A0000C1:SSL routines::no shared cipher [13] <W>2026-02-13 21:40:48.635 1 => <0:(-1)> New connection: 185.247.x.x:52173 <W>2026-02-13 21:40:49.357 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:41:18.028 1 => <0:(-1)> New connection: 185.247.x.x:39611 <W>2026-02-13 21:41:18.031 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A00006C:SSL routines::bad key share [13] <W>2026-02-13 21:41:22.465 1 => <0:(-1)> New connection: 87.236.x.x:54435 <W>2026-02-13 21:41:23.189 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-13 21:41:56.299 1 => <0:(-1)> New connection: 87.236.x.x:46583 <W>2026-02-13 21:41:57.021 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] ``` then the next thing is the crash according to Windows' Reliability Monitor.
deekerman commented 2026-02-20 22:18:05 -05:00
Author
Owner
Copy link

@chris-mosley commented on GitHub (Feb 17, 2026):

Same here.

<W>2026-02-17 05:13:35.364 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-17 05:13:35.380 1 => <0:(-1)> New connection: 167.94.x.x:15842
<W>2026-02-17 05:13:41.683 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-17 05:13:45.460 1 => <0:(-1)> New connection: 167.94.x.x:15060
<W>2026-02-17 05:14:13.203 1 => <0:(-1)> Client version 1.5.0 ( : )
<W>2026-02-17 05:14:43.796 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-17 05:14:45.287 1 => <0:(-1)> New connection: 167.94.x.x:51074
<W>2026-02-17 05:14:45.930 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1]
<W>2026-02-17 05:14:47.244 1 => <0:(-1)> New connection: 167.94.x.x:51080
<W>2026-02-17 05:14:47.401 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13]
<W>2026-02-17 05:14:49.111 1 => <0:(-1)> New connection: 167.94.x.x:51096
<W>2026-02-17 05:14:49.329 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13]
<W>2026-02-17 05:14:50.869 1 => <0:(-1)> New connection: 167.94.x.x:51110
<W>2026-02-17 05:14:51.609 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A00018C:SSL routines::version too low [13]
<W>2026-02-17 05:14:53.526 1 => <0:(-1)> New connection: 167.94.x.x:60374
<W>2026-02-17 05:14:53.972 1 => <0:(-1)> Connection closed: The remote host closed the connection [1]
<W>2026-02-17 05:14:55.441 1 => <0:(-1)> New connection: 167.94.x.x:60382
<W>2026-02-17 05:14:55.598 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13]
<W>2026-02-17 05:14:57.126 1 => <0:(-1)> New connection: 167.94.x.x:60388
<W>2026-02-17 05:14:57.220 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13]
<W>2026-02-17 05:14:58.379 1 => Ignoring connection: 167.94.x.x:60392 (Global ban)
<W>2026-02-17 19:23:40.045 1 => <0:(-1)> New connection: x.x.x.x:55141
#```
@chris-mosley commented on GitHub (Feb 17, 2026): Same here. ```<W>2026-02-17 05:13:31.795 1 => <0:(-1)> New connection: 167.94.x.x:15800 <W>2026-02-17 05:13:35.364 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-17 05:13:35.380 1 => <0:(-1)> New connection: 167.94.x.x:15842 <W>2026-02-17 05:13:41.683 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-17 05:13:45.460 1 => <0:(-1)> New connection: 167.94.x.x:15060 <W>2026-02-17 05:14:13.203 1 => <0:(-1)> Client version 1.5.0 ( : ) <W>2026-02-17 05:14:43.796 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-17 05:14:45.287 1 => <0:(-1)> New connection: 167.94.x.x:51074 <W>2026-02-17 05:14:45.930 1 => <0:(-1)> Connection closed: The TLS/SSL connection has been closed [1] <W>2026-02-17 05:14:47.244 1 => <0:(-1)> New connection: 167.94.x.x:51080 <W>2026-02-17 05:14:47.401 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13] <W>2026-02-17 05:14:49.111 1 => <0:(-1)> New connection: 167.94.x.x:51096 <W>2026-02-17 05:14:49.329 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13] <W>2026-02-17 05:14:50.869 1 => <0:(-1)> New connection: 167.94.x.x:51110 <W>2026-02-17 05:14:51.609 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A00018C:SSL routines::version too low [13] <W>2026-02-17 05:14:53.526 1 => <0:(-1)> New connection: 167.94.x.x:60374 <W>2026-02-17 05:14:53.972 1 => <0:(-1)> Connection closed: The remote host closed the connection [1] <W>2026-02-17 05:14:55.441 1 => <0:(-1)> New connection: 167.94.x.x:60382 <W>2026-02-17 05:14:55.598 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13] <W>2026-02-17 05:14:57.126 1 => <0:(-1)> New connection: 167.94.x.x:60388 <W>2026-02-17 05:14:57.220 1 => <0:(-1)> Connection closed: Error during SSL handshake: error:0A000102:SSL routines::unsupported protocol [13] <W>2026-02-17 05:14:58.379 1 => Ignoring connection: 167.94.x.x:60392 (Global ban) <W>2026-02-17 19:23:40.045 1 => <0:(-1)> New connection: x.x.x.x:55141 #```
deekerman commented 2026-02-20 22:18:05 -05:00
Author
Owner
Copy link

@Krzmbrzl commented on GitHub (Feb 18, 2026):

What needs to be done to provide a full dump?

To my understanding, Windows should create a dump file somewhere that should be usable to create a backtrace. If you tell me the exact version of Mumble you used, I should be able to produce symbol file for you (or you can send me the dump file and I extract the backtrace from it)

@Krzmbrzl commented on GitHub (Feb 18, 2026): > What needs to be done to provide a full dump? To my understanding, Windows should create a dump file somewhere that should be usable to create a backtrace. If you tell me the exact version of Mumble you used, I should be able to produce symbol file for you (or you can send me the dump file and I extract the backtrace from it)
deekerman commented 2026-02-20 22:18:05 -05:00
Author
Owner
Copy link

@Hartmnt commented on GitHub (Feb 18, 2026):

@zapy85 @Snowknight26 @chris-mosley So since Mumble 1.5.857 has been out for a while now, I understand that these random crashes started just recently? Presumably after a Windows update?

Would you be able to check which version of the Microsoft Visual C++ Redistributable is installed on your servers?

@Hartmnt commented on GitHub (Feb 18, 2026): @zapy85 @Snowknight26 @chris-mosley So since Mumble 1.5.857 has been out for a while now, I understand that these random crashes started just recently? Presumably after a Windows update? Would you be able to check which version of the ``Microsoft Visual C++ Redistributable`` is installed on your servers?
deekerman commented 2026-02-20 22:18:05 -05:00
Author
Owner
Copy link

@Snowknight26 commented on GitHub (Feb 18, 2026):

To my understanding, Windows should create a dump file somewhere that should be usable to create a backtrace. If you tell me the exact version of Mumble you used, I should be able to produce symbol file for you (or you can send me the dump file and I extract the backtrace from it)

Exact version is https://github.com/mumble-voip/mumble/releases/download/v1.5.857/mumble_server-1.5.857.x64.exe.

So since Mumble 1.5.857 has been out for a while now, I understand that these random crashes started just recently? Presumably after a Windows update?

Would you be able to check which version of the Microsoft Visual C++ Redistributable is installed on your servers?

VC++ 2015-2022, x86, 14.42.34438.0
VC++ 2015-2022, x64, 14.44.35211.0

It could be after an update but the machine that was running Mumble server in my case has been up for 53 days, but the crashes have seemingly only happened (twice, admittedly) starting 5 days ago.

@Snowknight26 commented on GitHub (Feb 18, 2026): > To my understanding, Windows should create a dump file somewhere that should be usable to create a backtrace. If you tell me the exact version of Mumble you used, I should be able to produce symbol file for you (or you can send me the dump file and I extract the backtrace from it) Exact version is https://github.com/mumble-voip/mumble/releases/download/v1.5.857/mumble_server-1.5.857.x64.exe. > So since Mumble 1.5.857 has been out for a while now, I understand that these random crashes started just recently? Presumably after a Windows update? > > Would you be able to check which version of the `Microsoft Visual C++ Redistributable` is installed on your servers? VC++ 2015-2022, x86, 14.42.34438.0 VC++ 2015-2022, x64, 14.44.35211.0 It could be after an update but the machine that was running Mumble server in my case has been up for 53 days, but the crashes have seemingly only happened (twice, admittedly) starting 5 days ago.
deekerman commented 2026-02-20 22:18:05 -05:00
Author
Owner
Copy link

@Snowknight26 commented on GitHub (Feb 18, 2026):

To my understanding, Windows should create a dump file somewhere that should be usable to create a backtrace. If you tell me the exact version of Mumble you used, I should be able to produce symbol file for you (or you can send me the dump file and I extract the backtrace from it)

Found some in %localappdata%\CrashDumps:

mumble-server-dumps.zip

@Snowknight26 commented on GitHub (Feb 18, 2026): > To my understanding, Windows should create a dump file somewhere that should be usable to create a backtrace. If you tell me the exact version of Mumble you used, I should be able to produce symbol file for you (or you can send me the dump file and I extract the backtrace from it) Found some in `%localappdata%\CrashDumps`: [mumble-server-dumps.zip](https://github.com/user-attachments/files/25400073/mumble-server-dumps.zip)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
weblate-translation-update
1.6.x
1.5.x
backport/1.5.x/pr-7080
backport/1.5.x/pr-6875
backport/1.5.x/pr-6879
backport/1.5.x/pr-6859
test-ci-win-fail
backport/1.5.x/pr-6789
backport/1.5.x/pr-6841
backport/1.5.x/pr-6832
backport/1.5.x/pr-6825
backport/1.5.x/pr-6809
backport/1.5.x/pr-6790
backport/1.5.x/pr-6777
backport/1.5.x/pr-6747
backport/1.5.x/pr-6775
backport/1.5.x/pr-6748
backport/1.5.x/pr-6769
backport/1.5.x/pr-6750
backport/1.5.x/pr-6744
backport/1.5.x/pr-6742
backport/1.5.x/pr-6728
backport/1.5.x/pr-6723
backport/1.5.x/pr-6700
backport/1.5.x/pr-6702
backport/1.5.x/pr-6703
backport/1.5.x/pr-6694
appveyor-fxc-dll-symbol-workaround
1.4.x
v1.6.870
v1.5.857
v1.5.735
v1.5.634
v1.5.629
v1.5.613
v1.5.517
v1.4.287
v1.4.274
v1.4.230
1.4.0-release-candidate-01
1.4.0-development-snapshot-006
1.4.0-development-snapshot-005
1.4.0-development-snapshot-004
1.4.0-development-snapshot-003
1.4.0-development-snapshot-002
1.3.4
1.4.0-development-snapshot-001
1.3.3
1.3.2
1.3.1
1.3.1-rc1
1.3.0
1.3.0-rc2
1.3.0-rc1
1.2.20
1.2.19
1.2.18
1.2.17
1.2.16
1.2.15
1.2.14
1.2.13
1.2.12
1.2.11
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
1.2.5
1.2.4
1.2.4-rc1
1.2.4-beta1
1.2.3
1.2.3-rc3
1.2.3-rc2
1.2.3-rc1
1.2.2
1.2.1
1.2.0
1.2.0beta2
1.2.0beta1
1.1.8
Labels
Clear labels   
GlobalShortcuts

   
Hacktoberfest

   
accessibility

   
acl

   
asio

   
audio

   
bonjour

   
bsd

   
bug

   
build

   
certificate

   
ci

   
client

   
code

   
documentation

   
external-bug

   
feature-request

   
gRPC

   
github

   
good first issue

   
help wanted

   
help-needed

   
ice

   
installer

   
linux

   
macOS

   
needs-ckeck-with-latest-version

   
needs-more-input

   
overlay

   
positional audio

   
priority/P0 - Blocker

   
priority/P1 - Critical

   
priority/P2 - Important

   
priority/P3 - Somewhat important

   
priority/P4 - Low

   
public-server-registration

   
qt

   
recording

   
release-management

   
server

   
stale-no-response

   
stale-support

   
support

   
task

   
test

   
theme

   
translation

   
triage

   
ui

   
windows

   
wontfix

   
x64
No labels
GlobalShortcuts
Hacktoberfest
accessibility
acl
asio
audio
bonjour
bsd
bug
build
certificate
ci
client
code
documentation
external-bug
feature-request
gRPC
github
good first issue
help wanted
help-needed
ice
installer
linux
macOS
needs-ckeck-with-latest-version
needs-more-input
overlay
positional audio
priority/P0 - Blocker
priority/P1 - Critical
priority/P2 - Important
priority/P3 - Somewhat important
priority/P4 - Low
public-server-registration
qt
recording
release-management
server
stale-no-response
stale-support
support
task
test
theme
translation
triage
ui
windows
wontfix
x64
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mumble-mumble-voip#3099
No description provided.