Was able to play till the escape (with 3 crashes), after the cutscene where i got an arrow into my leg, the game crashes with no real error message. Deinstalled the HD soundpack and checked/repaired the install via gog galaxy. Tested with and wihtout heapsize command. Newest AMD drivers. 18.9.3. Crashes happend with predecessor drivers and newest optional drivers.

CPU: Intel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
16 GB RAM
Radeon RX 470
Win 10 64bit

log from crash:
Local time is 17:48:05 10/06/18, system running for 21 minutes
16325MB physical memory installed, 13611MB available, 134217727MB virtual memory installed, 16 percent of memory in use
PageFile usage: 80MB, Working Set: 71MB, Peak PageFile usage: 80MB,
Current display mode is 1920x1080x32, (Unknown graphics card)

log from "working" gameplay:
Local time is 15:21:17 10/03/18, system running for 7040 minutes
16325MB physical memory installed, 10755MB available, 134217727MB virtual memory installed, 34 percent of memory in use
PageFile usage: 80MB, Working Set: 71MB, Peak PageFile usage: 80MB,
Current display mode is 1920x1080x32, (Unknown graphics card)

-------

Running machine spec auto detect (64 bit)...
- Windows 10 64 bit (build 10.0.16299)
- System memory
--- 16324 MB
- Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
--- Number of available cores: 4 (out of 4)
--- Number of logical processors: 8
- Radeon (TM) RX 470 Graphics (vendor = 0x1002, device = 0x67df)
--- Dedicated video memory: 4041 MB
--- Feature level: DX11 (SM 5.0)
- Final rating: Machine class 3

Last couple of lines of the current log file:
============================ Loading level rataje ============================
Pak 'data\levels\rataje\level.pak' is opened, root: 'data\levels\rataje\'
Pak 'data\levels\rataje\recast.pak' is opened, root: 'data\levels\rataje\'
Pak 'data\levels\rataje\svo.pak' is opened, root: 'data\levels\rataje\'
ShadowPlayHighlights init...
* Creating Core...
Closing pak 'data\_fastload\startup.pak'
Closing pak 'data\_fastload\startup_animations.pak'
Closing pak 'data\_fastload\startup_characters.pak'
Closing pak 'data\_fastload\startup_graphics.pak'
Closing pak 'engine\shadercachestartup.pak'
Sequence Music Engine runs via FMOD Event 'event:/music/music'

Havent played it since my last ERRORreport. Great game. NOT!

Actually the game is great! Rushed and buggy at the beginning, but quite stable with latest patches (but still could be better optimised). Since the day it was released I had like 3 crashes and 1 infinite loading bug (solved by latest patch), for over 300 hours played.

First of all check radiators on CPU and GPU and clean them (compressed air would be nice). Game is very taxing on hardware.
Second - check logs (system and application logs) and see what is really causing the problems.

Its a brand new gaming PC. This is the only game causing problems, and the crash happens at the very same (cut)scene. With all uptodate drivers. There is no problem exploring the world until that cutscene.

And I have old PC and virtually zero problems with the game.
Without checking logs, speaking about potential problems is like Tasseomancy.
So: help us, help you.

Well i provided all relevant info from the logs (you dont want me to spam the forums with useless lines like:
[MFX] Loading FXLib 'collisions' ...
[MFX] Loading FXLib 'destructibles' ...
[MFX] Loading FXLib 'foleys' ...
[MFX] Loading FXLib 'foleys_npc' ...
[MFX] Loading FXLib 'foleys_player' ...
[MFX] Loading FXLib 'footstep' ...
[MFX] Loading FXLib 'footsteps_horse' ...
[MFX] Loading FXLib 'footsteps_horse_npc' ...
[MFX] Loading FXLib 'footsteps_horse_player' ...
[MFX] Loading FXLib 'footsteps_npc' ...
[MFX] Loading FXLib 'footsteps_player' ...
[MFX] Loading FXLib 'player_fx' ...
[MFX] Loading FXLib 'vegetation' ...

There are NO errormessages! If there where errormessages, i would post them.

The only thing that makes me curious is that on one point it says: "Current display mode is 1920x1080x32, (Unknown graphics card) " and soon after it knows about "- Radeon (TM) RX 470 Graphics (vendor = 0x1002, device = 0x67df)" (and yes, i know its only a 470, but thanks to all those bitcoin miners i was lucky that i at least was able to get this card).

But thanks for answering. :) If you got ideas, let me hear it please.

Those are logs from game, I'm talking about Windows logs (right click on windows logo and choose manage system / computer or sth like that, next event viewer and operating system logs). There you will have two most importants logs: system and application. Note the time, run the game and proceed to said cutscene. Now look in those logs for anything around that time. Usually there will be an error regarding some library.

You might try playing up to a point just before the cutscene you are talking about, and saving the game there. Then load the game and continue on to see if the game is still crashing. Sometimes certain bug conditions stay resident in ram until some catalyst causes them to manifest--and the game crashes at the same spot over and over. By saving the game as close to the cutscene as you can get without triggering it, and then reloading it, you cause the game to purge any error similar condition which may be present in your current game. (I once has a game which in which sometimes the characters in the scenes, or the attacking monsters/beasts, would suddenly become invisible--they were solid and could interact in the game as normal--you could hear them and see footprints--but otherwise were invisible...;) The fix? Save and reload the game immediately--fixed it every time it happened, which was fine because it wasn't a common occurrence.)


Also, if you haven't already done so, download the directx 9.0c installable direct from Microsoft--every gamer should have this in his system if he is running anything from Vista x64 or newer, imo. Installing this only adds files to Win10--it doesn't overwrite the D3d files the OS ships with, etc.

https://www.microsoft.com/en-us/download/details.aspx?id=34429

Good luck...;)

I almost forgot about this game. But it seems, one of the last (or the last?) patch fixed the problem. Was able to continue. But the ride was hard and i had to restart often. Maybe i forgot or missed something, but my pursuers killed me all the time. But after i did some forest and meadow zig zag and trying to make my stupid horse jump out of a 10 cm creek, i finally escaped and arrived at the garnisson.