Penumbra: Overture mid-game crash - JENS TAKE A LOOK PLEASE

[Bludo]

The same anomalies tend to happen with Intel HD cards. Or at least similar. Can you try the shader suggestions for these cards mentioned in the troubleshooting guide?

I tried your suggestion, using the settings recommended for Intel cards in the Troubleshooting Guide. It did not resolve the crash, unfortunately.

Looking at the hpl.log file, it has similar errors every time a hard crash occurs. Unfortunately, because of Windows or the way crashes are handled, I don't get an exception, so there isn't much to work from. This is the end of the latest log after the crash, more or less:

WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
WARNING: Texture 'blinn4-fx' was not found!
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
ERROR: Couldn't create material '.mat'
WARNING: Could not load material ''
Loading map ...

Clearly, only the devs can be sure what's going on in there, but it appears to be attempting to create a material file that has no name, and subsequently fails to load it. Is it possible to circumvent having these files generated dynamically? I'd try a dummy file, but since it has no name, that doesn't really seem to make sense. Furthermore, I don't know if these log messages are even related to the crash.

Further assistance/guidance would be much appreciated. I don't suppose it would be possible to get a debug build of the executable with the debug symbols would it? I could at least try and narrow down the location of the crash in the stack.