protonscr

Avowed

protonopen appid 2457220Game compatibility - UnofficialXAudio2
ValveSoftware/Proton#8488 · opened 2025-03-01 by spslabo · updated 2025-03-03 · 8 comments · github · game page · search this game
Sspslabo 2025-03-01 github

Compatibility Report

  • Name of the game with compatibility issues: Avowed
  • Steam AppID of the game: 2457220

System Information

I confirm:

  • [x] that I haven't found an existing compatibility report for this game.
  • [x] that I have checked whether there are updates for my system available.

steam-2457220.log

Edit: This one is about 30 mins after launching the game and getting into a fight:
steam-2457220.log

Symptoms

Game is crashing randomly, no specific action is done in game, it can be while walking, talking to NPC, in a fight, etc. Sometimes it's a full crash to desktop other times it freezes

Reproduction

  1. Launch game
  2. Play the game
  3. Game will either crash to desktop or freeze
Kkisak-valve maintainer 2025-03-01 github

Avowed (2457220)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/8490.
@ncpa0cpl posted on 2025-03-01T14:06:22:

Compatibility Report

  • Name of the game with compatibility issues: Avowed
  • Steam AppID of the game: 2457220

System Information

I confirm:

  • [ ] that I haven't found an existing compatibility report for this game.
  • [ ] that I have checked whether there are updates for my system available.

Symptoms

Operating System crashes and the PC reboots.
I found this in the journal:

mar 01 14:43:56 owner-ms7b89 steam[2552]: wine: using kernel write watches, use_kernel_writewatch 1.
mar 01 14:43:56 owner-ms7b89 steam[2552]: Adding process 3670 for gameID 2457220
mar 01 14:43:56 owner-ms7b89 steam[2552]: wine: setpriority 2 for pid -1 failed: 3
mar 01 14:43:57 owner-ms7b89 steam[2552]: Fossilize INFO: Overriding serialization path: "/mnt/game-drive/SteamLibrary/steamapps/shadercache/2457220/fozpipelinesv6/steamapprun_p>
mar 01 14:43:59 owner-ms7b89 steam[2552]: Fossilize INFO: Overriding serialization path: "/mnt/game-drive/SteamLibrary/steamapps/shadercache/2457220/fozpipelinesv6/steamapprun_p>
mar 01 14:43:59 owner-ms7b89 steam[2552]: 03/01 14:43:59 minidumps folder is set to /tmp/dumps
mar 01 14:43:59 owner-ms7b89 steam[2552]: 03/01 14:43:59 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20250128005041)/tid(3742)
mar 01 14:43:59 owner-ms7b89 steam[2552]: 03/01 14:43:59 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(3742)
mar 01 14:43:59 owner-ms7b89 steam[2552]: wine: setpriority -10 for pid -1 failed: 3
mar 01 14:43:59 owner-ms7b89 steam[2552]: wine: setpriority -10 for pid -1 failed: 3
mar 01 14:44:02 owner-ms7b89 steam[2552]: wine: setpriority -10 for pid -1 failed: 3
mar 01 14:44:04 owner-ms7b89 geoclue[1483]: Service not used for 60 seconds. Shutting down..
mar 01 14:44:04 owner-ms7b89 systemd[1]: geoclue.service: Deactivated successfully.
mar 01 14:44:09 owner-ms7b89 systemd[1630]: Starting Virtual filesystem metadata service...
mar 01 14:44:10 owner-ms7b89 systemd[1630]: Started Virtual filesystem metadata service.
mar 01 14:44:10 owner-ms7b89 kernel: traps: steamwebhelper[3014] trap invalid opcode ip:761f802cabcf sp:7fff33bff8b0 error:0 in libcef.so[66c9bcf,761f7bfed000+a36d000]
mar 01 14:44:10 owner-ms7b89 systemd-coredump[3796]: Process 3014 (steamwebhelper) of user 1000 terminated abnormally with signal 4/ILL, processing...
mar 01 14:44:10 owner-ms7b89 systemd[1]: Created slice Slice /system/systemd-coredump.
mar 01 14:44:10 owner-ms7b89 systemd[1]: Started Process Core Dump (PID 3796/UID 0).
mar 01 14:44:13 owner-ms7b89 (sd-parse-elf)[3801]: Could not parse core file, dwfl_core_file_report() failed: (null)
mar 01 14:44:13 owner-ms7b89 (sd-parse-elf)[3801]: Failed to inspect core file: Invalid argument
mar 01 14:44:13 owner-ms7b89 systemd-coredump[3798]: [🡕] Process 3014 (steamwebhelper) of user 1000 dumped core.
mar 01 14:44:13 owner-ms7b89 systemd[1]: [email protected]: Deactivated successfully.
mar 01 14:44:13 owner-ms7b89 systemd[1]: [email protected]: Consumed 3.165s CPU time, 1.2G memory peak.
mar 01 14:44:24 owner-ms7b89 steam[2552]: wine: setpriority -1 for pid -1 failed: 3
-- Boot 54b09ccc6b83413cbafb838b6a213182 --

Reproduction

It seems that there are specific areas in the game that trigger this issue, I didn't had this happen a lot, but around the farmland below Fior city and when exiting the Thirdborn it would happen almost every time.

I didn't experience any similar issues with any other games.

Ssimifor 2025-03-01 github

@ncpa0cpl can you attach a save file close to the farmlands you mention?

Nncpa0cpl 2025-03-02 github

Not exactly the farmland location, but here's a save that triggers the crash almost every time I try to load it in: https://drive.google.com/file/d/1GqyphxSERS0QTHdmklwe-GN0Bn1iwe6L/view?usp=sharing

This is what happens when I load the above save:

https://github.com/user-attachments/assets/7b52ddde-d72f-4a1d-a5dd-27103e815329

after the crash, pc reboots and this message can be seen during the boot process:

Image

I have also captured the proton log:
steam-2457220.log

Ssimifor 2025-03-03 github

no luck here, tried over a dozen times and the save loaded fine every time. Just as a checkbox of sorts, verify game files, if no files are reacquired share your graphics settings, as a combination of them could be a factor on the crashing.

Also, if your system is going down, there are probably kernel logs about it. Let's say your previous boot ended up with the system shutting down, or forcing you to shut it down, then you can use this command to get the kernel logs for it journalctl -k -b -1 > kernel.log, this will put the results in a file in your terminal's current directory (should be your home folder by default). -1 represents the previous session, -2 is the session before that and so on, but your system will likely prune old logs at some point so you might not have them in your system anymore

Nncpa0cpl 2025-03-03 github

I rebooted the pc, started steam, opened the game, loaded the save, it crashed. and after reboot I grabbed the log. but the kernel logs don't seem to have any logs related to the crash:

kernel.log

here's also the whole journal log if that's any help:

journal.log

I did verify game files at some point it did not change anything.

I can share my graphic settings though I don't think it's at all related since I've tried lowering all of them and seen no improvement, it was crashing as always.

edit:

I also noticed that there are kernel logs related to this crash, but not in the same session, it seems to be the same thing as I posted earlier that showed up when booting up:

mar 03 20:12:34 owner-ms7b89 kernel: mce: [Hardware Error]: Machine check events logged
mar 03 20:12:34 owner-ms7b89 kernel: [Hardware Error]: System Fatal error.
mar 03 20:12:34 owner-ms7b89 kernel: fbcon: Taking over console
mar 03 20:12:34 owner-ms7b89 kernel: [Hardware Error]: CPU:3 (19:21:0) MC5_STATUS[-|UE|MiscV|AddrV|PCC|TCC|SyndV|-|-|-]: 0xbea0000001000108
mar 03 20:12:34 owner-ms7b89 kernel: [Hardware Error]: Error Addr: 0x0000000141b0ff3f
mar 03 20:12:34 owner-ms7b89 kernel: [Hardware Error]: IPID: 0x000500b000000000, Syndrome: 0x000000004d000000
mar 03 20:12:34 owner-ms7b89 kernel: [Hardware Error]: Execution Unit Ext. Error Code: 0
mar 03 20:12:34 owner-ms7b89 kernel: [Hardware Error]: cache level: RESV, tx: GEN, mem-tx: GEN
Ssimifor 2025-03-03 github

Is that kernel log from that same session? The date indicates it's from
today.

Regarding the MCE error you see it's just as it says, it suggests a likely
hardware issue. This could be an issue with the CPU or the RAM, if you've
tweaked them in some way I recommend getting them back to stock, I'd also
temporarily disable xmp for the RAM to see if the problem persists

On Mon, Mar 3, 2025, 3:03 PM Szymon Bretner @.***>
wrote:

I rebooted the pc, started steam, opened the game, loaded the save, it
crashed. and after reboot I grabbed the log. but the kernel logs don't seem
to have any logs related to the crash:

kernel.log https://github.com/user-attachments/files/19058335/kernel.log

here's also the whole journal log if that's any help:

journal.log
https://github.com/user-attachments/files/19058454/journal.log

I did verify game files at some point it did not change anything.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8488#issuecomment-2695295226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EA7EIPIAVW4626VUET2SSRQZAVCNFSM6AAAAABYDSWTGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJVGI4TKMRSGY
.
You are receiving this because you commented.Message ID:
@.***>
[image: ncpa0cpl]ncpa0cpl left a comment (ValveSoftware/Proton#8488)
https://github.com/ValveSoftware/Proton/issues/8488#issuecomment-2695295226

I rebooted the pc, started steam, opened the game, loaded the save, it
crashed. and after reboot I grabbed the log. but the kernel logs don't seem
to have any logs related to the crash:

kernel.log https://github.com/user-attachments/files/19058335/kernel.log

here's also the whole journal log if that's any help:

journal.log
https://github.com/user-attachments/files/19058454/journal.log

I did verify game files at some point it did not change anything.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8488#issuecomment-2695295226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EA7EIPIAVW4626VUET2SSRQZAVCNFSM6AAAAABYDSWTGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJVGI4TKMRSGY
.
You are receiving this because you commented.Message ID:
@.***>

Nncpa0cpl 2025-03-03 github

the kernel.log and journal.log should be from the same session, the mce error I got from a later session. Also I only see this mce error message after a crash, I don't think I've ever seen in any other scenario, that's why I thought it's worth mentioning

Ssimifor 2025-03-03 github

this kind of hardware error takes down the system immediately so it's
normal the related mce error only appears on the next boot. I strongly
advise you to restore the default settings for your cpu and ram in the bios
before doing anything taxing with the system.

On Mon, Mar 3, 2025, 4:46 PM Szymon Bretner @.***>
wrote:

the kernel.log and journal.log should be from the same session, the mce
error I got from a later session. Also I only see this mce error message
after a crash, I don't think I've ever seen in any other scenario, that's
why I thought it's worth mentioning

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8488#issuecomment-2695498281,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EFLAZA4XWCYT4PRJL32SS5TZAVCNFSM6AAAAABYDSWTGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJVGQ4TQMRYGE
.
You are receiving this because you commented.Message ID:
@.***>
[image: ncpa0cpl]ncpa0cpl left a comment (ValveSoftware/Proton#8488)
https://github.com/ValveSoftware/Proton/issues/8488#issuecomment-2695498281

the kernel.log and journal.log should be from the same session, the mce
error I got from a later session. Also I only see this mce error message
after a crash, I don't think I've ever seen in any other scenario, that's
why I thought it's worth mentioning

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8488#issuecomment-2695498281,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EFLAZA4XWCYT4PRJL32SS5TZAVCNFSM6AAAAABYDSWTGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJVGQ4TQMRYGE
.
You are receiving this because you commented.Message ID:
@.***>

Proton versions

Upstream links