So this is a very strange bit of crash data, as it's saying the crash is happening on an instruction that isn't capable of it, right after a fairly innocuous call. Something more is going on that's causing the crash, but it isn't showing up here.

I would suggest trying to get a minidump of Dream Seeker. A minidump file should be in the range of 500K to around 20 MB (it shouldn't be in the 100 MB range or more), and will have information I can run through a debugger.

By default, crash dumps should go to %LOCALAPPDATA%\CrashDumps, so you can type %LOCALAPPDATA%\CrashDumps into your start menu and it'll take you right to it. Those dumps should all be minidumps already, which are the sort I need. You should see files like dreamseeker.exe.[numbers].dmp. If you can arrange to send me one of those I can look into it in more detail.

I'll take a look and see what I can find.

I manage to play without crashes entirely for a very long time, and then randomly crash once. I'm unsure how to reproduce it as it just.. happens. without me doing anything really. I have closed some other background programs/apps just in case it was causing interferences but doesn't seem that it did much

Could this perhaps be tied to using ambient occlusion setting? thats the only recent thing i remember changing

Lummox JR wrote:

The good news is I was able to use those dumps to get some information. The bad news is I hit a dead end. The crashes are happening during the render process. That's all I was able to figure out.

If you're able to reproduce this more reliably with a test case I can take a look, but without that I don't know that there's anything else I can do.

So, i have completely re-installed windows at this point, fresh install. Fresh install of byond. Drivers and everything should be up to date.

And i'm getting this on event viewer whenever dreamseeker crashes.

- System

- Provider

[ Name] Application Error
[ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57}

EventID 1000

Version 0

Level 2

Task 100

Opcode 0

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2025-01-11T20:19:35.3946167Z

EventRecordID 1324

Correlation

- Execution

[ ProcessID] 8212
[ ThreadID] 6840

Channel Application

Computer Emiix

- Security

[ UserID] S-1-5-21-1009416156-847252523-4177674808-1001


- EventData

AppName dreamseeker.exe
AppVersion 5.0.516.1650
AppTimeStamp 67804c2d
ModuleName d3dcompiler_43.dll
ModuleVersion 9.29.952.3111
ModuleTimeStamp 4bf73239
ExceptionCode c0000005
FaultingOffset 000ac25e
ProcessId 0x35f8
ProcessCreationTime 0x1db64661f46c230
AppPath C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
ModulePath C:\WINDOWS\SYSTEM32\d3dcompiler_43.dll
IntegratorReportId 5f94cee3-b3c1-4f07-b71b-8a516229e6f0
PackageFullName
PackageRelativeAppId

This time it points to the system d3compiler dll rather than unknown on the module path, tho, the original crash pointed to no module and labeled it unknown like my first post, but when i tried reopening the game it crashed twice, pointing to the d3dcompiler. Any idea how to fix this? It's all on a fresh install so i don't know what else to do now.

I did also swap to the beta branch this time. Currently on 516.1650

EDIT:
________

- EventData

AppName dreamseeker.exe
AppVersion 5.0.516.1650
AppTimeStamp 67804c2d
ModuleName nvd3dum.dll
ModuleVersion 32.0.15.6636
ModuleTimeStamp 674f5df7
ExceptionCode c0000005
FaultingOffset 00120295
ProcessId 0x32c4
ProcessCreationTime 0x1db6470a6d5aab9
AppPath C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
ModulePath C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_ amd64_9425e4c3b1ac1c47\nvd3dum.dll
IntegratorReportId 5143459c-c66e-415c-8285-f05b939821e2
PackageFullName
PackageRelativeAppId

From a different crash today pointing to a different dll