Faulting application name: dreamdaemon.exe, version: 5.0.512.1427, time stamp: 0x5b202055
Faulting module name: d3dx9_43.dll, version: 6.3.9600.18821, time stamp: 0x59ba8666
Exception code: 0xc0000135
Fault offset: 0x0009d4c2
Faulting process id: 0x1270
Faulting application start time: 0x01d4029cdf6f4e67
Faulting application path: C:\TGSTATION-SERVER-3\BYOND\bin\dreamdaemon.exe
Faulting module path: d3dx9_43.dll
Report Id: 1d1fcb1e-6e90-11e8-80f4-02000082d2f7
Faulting package full name:
This server doesn't have a video card or monitor and is remote desktop only. DD runs under the SERVICES account.
ID:2376110
![]() Jun 12 2018, 4:35 pm (Edited on Jun 12 2018, 5:04 pm)
|
|||||||||||||
Resolved
| |||||||||||||
These are the dependencies I see for that DLL:
msvcrt.dll GDI32.dll KERNEL32.dll ADVAPI32.dll |
I wouldn't be surprised if a bug in windows caused it to throw errors wrong such that the dll to be loaded shows up as the dll trying to do the loading in dll not found appcrashes. I'll run dependency mon on dreamdaemon directly in rdp to see.
Also i'm testing it on a server that once had byond installed but is also a headless vm, to confirm from that direction as well. |
I was correct.
![]() the module name is the module that failed to load. also it works correctly on the older vm image that had previously seen a byond install, and only fails on the virgin image. It's not great to make directx a requirement for the server, especially if you aren't even going to be using it (re: ID:2039888) but I guess this works for now. |
I would suggest doing a full BYOND install on that remote server, assuming that it's currently only running from an unzipped copy instead of a proper install.
Although it occurs to me, apparently you do have DirectX installed or that DLL shouldn't be able to throw an error in the first place. But it's definitely carping about some DLL not being there.