View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013319 | Dwarf Fortress | General | public | 2025-11-01 23:19 | 2025-11-02 18:27 |
| Reporter | Beardy | Assigned To | |||
| Priority | low | Severity | crash | Reproducibility | unable to reproduce |
| Status | new | Resolution | open | ||
| Platform | Steam | OS | Windows 11 Pro | OS Version | 24H2 |
| Product Version | 52.05 | ||||
| Summary | 0013319: Possible crash due to daylight savings time change | ||||
| Description | During normal play, the game crashed immediately when the system clock automatically adjusted from EST (Eastern Standard Time) to EDT (Eastern Daylight Time) which caused a time change from 1:59AM to 1:00AM. This could technically be coincidental, but I have not had any crashes prior to this. I am not sure whether it's actually possible to test this by changing the system clock manually. | ||||
| Tags | No tags attached. | ||||
|
|
check for a folder called crashlogs in the main DF folder, which by default is at C:\Program Files (x86)\Steam\steamapps\common\Dwarf Fortress, if there's a file with the right date, please share the contents |
|
|
These are the full contents of "crash_2025-11-02-01-59-28.txt": Fortress mode Version 52.05 0> Dwarf_Fortress+0xA95D96 1> Dwarf_Fortress+0xA95F39 2> KERNELBASE!UnhandledExceptionFilter+0x1F3 3> ntdll!strncpy+0x2693 4> ntdll!_C_specific_handler+0x93 5> ntdll!_chkstk+0x9F 6> ntdll!RtlLocateExtendedFeature+0x597 7> ntdll!KiUserExceptionDispatcher+0x2E 8> Dwarf_Fortress+0x13D9B13 9> Dwarf_Fortress+0x8921FE 10> Dwarf_Fortress+0x88A448 11> Dwarf_Fortress+0xBF72B5 12> Dwarf_Fortress+0x8B85E3 13> Dwarf_Fortress+0x8B9AE9 14> SDL2!SDL_DYNAPI_entry+0x799D7 15> SDL2!SDL_DYNAPI_entry+0x12EEDE 16> ucrtbase!wcsrchr+0x150 17> KERNEL32!BaseThreadInitThunk+0x17 18> ntdll!RtlUserThreadStart+0x2C Advancing seasons Aging items |
|
|
The time on the file name shows it was just before the time change, and the code gurus say that code uses a different time source any way. So it was a coincidence, but that means you got hit by a random bug that corrupts data, which they havn't yet tracked down the cause of. |
