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
Thankfully you can skip the launcher and improve your PCs stability by doing so
https://steamcommunity.com/sharedfiles/filedetails/?id=3015166965
I recommend method C for you personally
As I've stated in my OP:
"Bypassing" it doesn't seem to matter though on some level. Since I disabled it, the launcher doesn't visibly pop up when I start the game ... but some version of it must still be running or otherwise I wouldn't be getting those daily crash-reports of it.
S.
That happens only if you never restart your PC, though.
Err.. nope.. that's not it, either... PC gets restarted plenty and both Win11/BIOS quick start and hibernation are switched off on my system.
Thing is... it *was* the launcher, I think. Or more precisely, it was the method I was using to bypass it. The "skip launcher" command wasn't working - or it was only working "superficially", since the launcher didn't visibly open up any longer, but apparently still was running (and crashing) in the background.
I've switched to method C now from the post you linked and that actually did the trick of completely preventing the launcher from starting up. Launcher doesn't get triggered any longer (neither "visibly" nor in the background) and so it can't crash and cause problems.
I just finished a 3 or 4 hour session without issue and there were no events logged WRT the Larin Launcher - plus my PC didn't crash/freeze, either. Could've been just luck, but I'm feeling cautiously optimistic.
Other things I did, BTW, were to throw out a ton of other stuff that had triggered critical errors in the log in the past two weeks. Including all RGB-related stuff (MSI Mystic Light, Gigabyte Fusion). I also stopped using Open RGB and deactivated Samsung Magician.
Lastly, I disabled saving to the Steam cloud for BG3, since that regularly failed and gave me lots of sync-error messages in Steam. I only use BG3 on this one machine, so I don't need to have my save-games in the cloud.
Some of the errors I found in the Event-Logger are still popping up there though - despite me having updated pretty much all the drivers that could've been at fault (chipset, Intel LAN-adapters). But so long as these errors don't cause any crashes, I'm prepared to leave well enough alone.. :)
S.
in BG3 launch options in Steam (bg3.exe for Vulkan, bg3_dx11.exe for DirectX11). BTW: The examples in the linked article are missing the "3" from both file names ("bg.exe" when it should be "bg3.exe"), so copy-pasting them won't work.
Two 4 hour+ sessions with zero issues/crashes and Windows Reliability Monitor now has zero entries for me besides normal stuff like update-history events. No more scary red critical error entries in there.
Seems pretty clear that the lauchner is what messed things up for me.
Another interesting observation from the Reliability Monitor's timeline is that this seems to have started with the August 25th patch. On that day, my system's reliability took a huge nose-dive and since then there were at least one, more commonly two or even more, red entries/critical errors caused by the launcher-app. Plus the semi-regular, near daily, hard freezes I've talked about in my OP. That patch also gave me tons of "regular" CTDs during gameplay - those stopped with a hotfix published on Aug 26th, but the hard crashes/freezes didn't go away until I actually disabled the launcher.
According to some folks who took a look at my Windows error-codes over on a German Windows/IT-board, the launcher seems to have some sort of conflict with Windows .NET framework. At least on my system it does.
S.
This is with Win 11 23H2, OS Build 22635.2850.
edit; other possibility is that it might be linked to Asus chipsets, as this seems a particular link shared by many of us having this. My B550 board is using latest chipset drivers and bios though so *shrug*.