Hello,

I'm experiencing a hard crash (Access Violation) right upon launching EOF v1.8RC16. The window opens up black, but the GUI fails to render properly (it gets stuck minimized into a microscopic pixel area at the top right, and clicking anywhere causes an immediate application crash).

Here is the Windows Event Viewer crash log:

Plaintext

Faulting application name: eof.exe, version: 0.0.0.0, time stamp: 0x6ae168e0
Faulting module name: eof.exe, version: 0.0.0.0, time stamp: 0x6ae168e0
Exception code: 0xc0000005
Fault offset: 0x000c1bb5
Faulting process id: 0x1cd8
Faulting application path: C:\eof1.8RC16\eof.exe

System Specifications:

• OS: Windows 10 Pro 64-bit

• Processor: Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz

• Graphics: Intel(R) HD Graphics 4600

• RAM: 16.0 GB

Application Log

089: Logging started during program initialization at 10/28/26 09:47:59
089: EOF v1.8RC16
089: eof_controller_load_config() entered
089: eof_controller_read_button_names() entered
089: eof_controller_load_config() entered
089: eof_controller_read_button_names() entered
089: Logging level set to normal
089: 	Importing chord shape definitions
089: eof_load_chord_shape_definitions() entered
089: 	169 chord shape definitions imported
089: eof_set_display_mode() entered
089: eof_load_data() entered
089: eof_init_colors() entered
089: create_silence_sample() entered
089: save_wav() entered
089: 	Opening file for writing:  "silence.wav"
089: save_wav_fp() entered
089: eof_copy_file() entered
089: 	Copying file "silence.ogg" to "silence2.ogg"
089: 	Buffer copying 4324 bytes
089: 	Copy successful
089: eof_undo_reset() entered
089: 	Initializing audio
089: eof_mix_init() entered
089: 	Loading audio samples
089: 	Checking for crash recovery files
089: eof_check_update() entered
089: 	Detected online version:  1816, hotfix date:  0
089: 	Detected running version:  1816, date:  0
089: 	Entering main program loop

It seems like an internal memory access violation (0xc0000005) related to how the Allegro graphics backend/window initialization is handling the display buffer on older Intel integrated graphics.

Has anyone found a workaround for this build, or is there a patched binary/hotfix available for this crash?

Thanks in advance!

That's very odd. If you're used EOF before, did it previously work for you? If so, did it work on this computer or on a different one? I wonder if there are any video settings in the Intel driver that may be causing EOF some problems. Does the Intel driver allow you to create a profile on a per-application level, such as to allow changing different settings just for eof.exe? In the past, it had been seen that some of the more exotic Nvidia features could cause problems in EOF.