Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
it's the ubisoft's server.
Can I just check if the kind advice Dan the Man has shared has helped others also launch the game?
Many thanks in advance
I suppose the game is trying to talk to either EAC, steam.dll or even Uplay Client itself, it fails to communicate and then game silently closes.
In procmon logs the game crashes right after accessing .\Trials Rising\datapack\uplay_r1_loader64.dll. I see trialsrising.exe is doing CreateFileMapping on this dll three times (each results in "FILE LOCKED WITH ONLY READERS") after which I see multiple threads are exiting and process create operation for WerFault.exe. However, it could be a false lead since the game has already successfully called load image operation on this dll couple seconds before.
I wasn't able to catch crash dump but I found wer fault entry for it - Fault Module Name: shell32.dll. Looking for shell32.dll in procmon I see that the game successfully loaded the dll but later failed with buffer overflow on QuerySecurityFile operation. However, the very next event is the same op but result is success.
Since I have 14th gen Intel CPU I did couple of launches with down clocked processor to make sure I will isolate any stability issues related to Intel.
Everything is installed on the main C drive.
Just purchased the game, fresh install.
Ubi - can you please just give up your darn launcher, it's been a problem on PC from day 1.