Dreamseeker.exe crashing moments after launch anytime I try to join a server in byond. No dreamseeker window appears and there are no visual indicators of it launching, however I can see it appearing in the process manager and crashing momentarily after. The issue seems to occur in byondcore.dll, however I have no idea what might be causing it. The crash occurs on byond 5.0.515.1636. Crash eventData from windows event viewer attached below.
2086733357384671200
1
APPCRASH
Unavailable
0
dreamseeker.exe
5.0.515.1636
66181d57
byondcore.dll
5.0.515.1636
66181d38
c000041d
0025e8d3
?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F0E.tmp.dmp ?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9F9B.tmp.WERInt ernalMetadata.xml ?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FBC.tmp.xml ?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FBC.tmp.csv ?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9FFB.tmp.txt
?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_ dreamseeker.exe_6b2b7f5c8e6e1726c84fe1ad8fb33ecacf61298_2ef9 1cfe_e3abd869-7050-4971-a67f-c21dfcb1885b
0
8ce7a08f-d728-4f61-b282-f2bdf039237c
268435456
e9c98215ff4ac9d4fcf590eebbdf1fe0
0
Hey, thanks for getting back so fast. I am sure that the problem has nothing to do with vcruntime as I have reinstalled it using the link from the byond website multiple times. Here I attached the dump file and its contents below:
https://mega.nz/file/ UL9CQQJK#b-C_6Vqq3zscHffhA6YUW2CTq4eRGF9-zFFMdYiwyaM Dump file: dreamseeker.exe.14228.dmp : C:\dump\dreamseeker.exe.14228.dmp Last write time: 03.05.2024 23:49:42 Process name: C:\games\SS13\BYOND\bin\dreamseeker.exe "byond://BYOND.world.549002202" -pager Process architecture: x86 Exception code: 0xc0000005 Exception information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access. Heap information: Present Error information: | |
I'll take a look. It appears that's actually a full dump rather than a minidump, which is usually too big, but I'll try to make sense of it.
| |
Login to reply.
If that fails to fix the problem, then the next step is to try to get a minidump of the process. Instructions for how to set that up are here:
https://stackoverflow.com/questions/20237201/ best-way-to-have-crash-dumps-generated-when-processes-crash