ID:2508980
 
(See the best response by Lummox JR.)
I played before, and played many time. After start a game it's crash with nothing, launcher continue work stability. Just game crashing in loaded. And after i redownloaded computer BYOND saves to notebook, i seen this problem. I know i can fix it if i register a new account but still i don't want it.


*I know what it's was not full description of my problem. Just website don't loaded my text full.*
You didn't actually say what the problem is.
In response to Lummox JR
Check, if you can help.
The Windows event viewer should have a log of the crash. Can you post the details?
I have this same problem, I finished a windows 10 update last night and now tonight I can't get Dreamseeker to open any Space Station 13 servers, or any server on any game. When I try, Dreamseeker opens momentarily, then closes and is not found in Task Manager.

I did track down the Event Viewer and saw the crashes, I don't understand the code but I did copy the XML version for the most recent:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-09-13T04:21:53.084909400Z" />
<EventRecordID>1027</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-HMHJH5N</Computer>
<Security />
</System>
- <EventData>
<Data>dreamseeker.exe</Data>
<Data>5.0.512.1479</Data>
<Data>5d66c181</Data>
<Data>byondwin.dll</Data>
<Data>5.0.512.1479</Data>
<Data>5d66c15a</Data>
<Data>c0000005</Data>
<Data>000b68d1</Data>
<Data>251c</Data>
<Data>01d569eac2f9c479</Data>
<Data>C:\Program Files (x86)\BYOND\bin\dreamseeker.exe</Data>
<Data>C:\Program Files (x86)\BYOND\bin\byondwin.dll</Data>
<Data>4e8274ba-d802-4575-bfa3-a2b8c429e211</Data>
<Data />
<Data />
</EventData>
</Event>
Also have the general version:

Faulting application name: dreamseeker.exe, version: 5.0.512.1479, time stamp: 0x5d66c181
Faulting module name: byondwin.dll, version: 5.0.512.1479, time stamp: 0x5d66c15a
Exception code: 0xc0000005
Fault offset: 0x000b68d1
Faulting process id: 0x251c
Faulting application start time: 0x01d569eac2f9c479
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\byondwin.dll
Report Id: 4e8274ba-d802-4575-bfa3-a2b8c429e211
Faulting package full name:
Faulting package-relative application ID:
That info should help; thanks.
In response to Alanoth
Curious: This crash is happening at the last step in the render process, when using hardware graphics. The crash should never happen because it's basically telling me that a var has become invalid that shouldn't have had a chance to.

What graphics card do you have?

You might want to try updating your graphics drivers to see if those are somehow broken. If that doesn't do the trick, see if you can get me a minidump file; I can use that for further investigation.

I also recommend trying to create and edit an icon in Dream Maker, which uses the hardware graphics now too for the icon editor. I'm curious if you get the same result.
In response to Lummox JR
I use an Nvidia GTX 1060 6GB for a Graphics card, I hadn't thought about looking at the graphics drivers. I'll try updating those and see what happens. I'll also try to create and edit an icon in Dream Maker, never done that before. No idea what a minidump file is but I'll google it
In response to Lummox JR
I've updated my graphics drivers, but to no effect. My computer still works fine, except for Dreamseeker. I've looked up minidump, and minidump files are enabled, but my computer doesn't seem to be making any in C:\Windows, as there is no minidump folder. I've never had a major crash, so I couldn't find one. I need to get ready for work, but afterward, I will attempt to create an icon in Dream Maker and see what the Event Viewer shows.

Here's the event viewer logs from the last attempt to launch Space Station 13:

Faulting application name: dreamseeker.exe, version: 5.0.512.1479, time stamp: 0x5d66c181
Faulting module name: byondwin.dll, version: 5.0.512.1479, time stamp: 0x5d66c15a
Exception code: 0xc0000005
Fault offset: 0x000b68d1
Faulting process id: 0x210c
Faulting application start time: 0x01d56a51417ea923
Faulting application path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
Faulting module path: C:\Program Files (x86)\BYOND\bin\byondwin.dll
Report Id: 4ea84721-4545-49a1-b44a-f2a831892220
Faulting package full name:
Faulting package-relative application ID:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/ event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2019-09-13T16:35:41.413550000Z" />
<EventRecordID>1085</EventRecordID>
<Channel>Application</Channel>
<Computer>DESKTOP-HMHJH5N</Computer>
<Security />
</System>
- <EventData>
<Data>dreamseeker.exe</Data>
<Data>5.0.512.1479</Data>
<Data>5d66c181</Data>
<Data>byondwin.dll</Data>
<Data>5.0.512.1479</Data>
<Data>5d66c15a</Data>
<Data>c0000005</Data>
<Data>000b68d1</Data>
<Data>210c</Data>
<Data>01d56a51417ea923</Data>
<Data>C:\Program Files (x86)\BYOND\bin\dreamseeker.exe</Data>
<Data>C:\Program Files (x86)\BYOND\bin\byondwin.dll</Data>
<Data>4ea84721-4545-49a1-b44a-f2a831892220</Data>
<Data />
<Data />
</EventData>
</Event>
In response to Alanoth
I've reached out on Stack Overflow about this, but I strongly suspect that another program on your system is hooking DirectX and it's causing the problem. Are you running any special software that's designed to interface with games?
In response to Lummox JR
Not that I can think of, the only things that are ever running in the background of my computer are the Nvidia Control Panel, Steam, Origin, BYOND, Discord, and MSI Afterburner
In response to Alanoth
Best response
You have to look at the Details tab of your task manager; the list of programs is kept simple. It's potentially possible that Afterburner could be involved in some way, though.
In response to Lummox JR
I don't see how, Afterburner is only used to keep my GPU cool after my last GPU nearly melted. But, I'll take your insight to heart and attempt to run a connection to SS13 while having the details tab open, I'll try to make a dump file for both BYOND and Dreamseeker if i can
In response to Lummox JR
I watched Dreamseeker launch and it did appear in the Details tab of Task Manager briefly, then declared itself suspended for half a second before it crashed. I did manage to set up a dump file, I'll attempt to post the results.
In response to Lummox JR
https://www.filehosting.org/file/details/821774/ dreamseeker%20(2).DMP
That's really too big a dump file for me to work with. I don't need it to include the entire application memory. It shouldn't be bigger than just a few MB at most.
In response to Lummox JR
I have no idea how this occurred, maybe you know? But when I disabled MSI Afterburner, DreamSeeker worked immediately and quickly. How does a program that monitors GPU fans interfere with DirectX? I've had Afterburner on my computer for months, almost a year actually, and BYOND has been on and previously used while Afterburner was enabled in the background.
My guess is it's doing something to hook DirectX, and an issue in the program was causing it to release the Direct3D device interface prematurely.
I was also having this same exact issue and it was rivatuners statistic server's overlay (paired with MSI afterburner) causing the instant crash right before entering the game,strange that byond suddenly doesn't like it after several years of it being fine.
Page: 1 2

Login to reply.