These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_BethesdaSoftwork_0bee12e71d833c6a9a936aa1d39329bbf9847_aa12295b_95d9956b-1753-43b8-b80a-49fa5560cee4
The game seems to be very sensitive to CPU (and possibly memory) overclocking and was crashing for me the same way until I went back to default settings. Even though everything else had been rock solid, it caused oblivion remaster, stalker 2, and Indiana Jones to crash at launch.
Double check if your bios is doing any automated overclocking or revert any manual overclocking that you're doing.
Googling MoAppCrash, one of the things that stands out in you log callstack, leads to multiple people experiencing issues on win 10, even unrelated to an Unreal game. The windows version noted, is the latest one? Can't properly check, I'm on my phone.
Try to Google this:
Fault bucket 2270348712785277475, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Maybe including unreal, even oblivion in the search terms.
Without looking at the other files of the report, that's probably your best bet.
I think it may be due to the middleware they used to bridge the old code with unreal. This is not an Unreal game per se, they are using unreal for rendering graphics and ui mostly, every other thing is literally the same code as the original, with a bridge. I think the middleware is fucked up in your system, and probably is related to the other issues reported for win 10 on the error I pointed out.
If you are not capable of searching in the log files for specific clues, you can try upload them to chatgpt. It's useful if they are extensive, and the task is like finding a needle in a haystack.
If you don't want to do any forensics, I would suggest a clean OS install. Probably something in your system is interacting poorly with the chimera oblivion is. Without any forensics, you will never know what it is. That or hardware issue.
The exception code you are getting appears to indicate some code is trying to execute something very low level (e.g. direct device access) when it isn't allowed.
This isn't a widespread issue, so it seems reasonable to assume that it is specific to your machine.
My guesses are:
Corrupt game files, try deleting the user data for the game. Not sure where that lives.
Corrupt install but I think you've addressed that.
Corrupt windows, a scan disk check might repair something.
Corrupt drivers:
Fresh install of GPU drivers, using amd's tool or ddu.
Update chipset drivers if there are any.
Disable or uninstall anything that controls additional devices. E.g. led or fan controllers like Armoury crate or MSI afterburner.
Any other app that injects itself into the process. Game overlay, antivirus. Amd adrenaline does this, as can steam and gamebar.
Upvoted, I hope someone can help you here. But also a bit of condescending, it's been solid as a rock for me on linux :D But, seriously hope you figure it out, it's frustrating having a new game not work
It's working on Linux? Was it straightforward to setup? I've given up buying games on steam because of their terrible Linux support, and I'd seen a lot of comments about the steam deck version sucking, so I'd assumed the Linux version wasn't great. But maybe the deck hardware is the issue?
Beyond selecting a proton version it was no more difficult to set up than any windows game. Deck hardware I've heard issues with, but I'm not surprised. The deck is essentially a mid level right from about 8 years ago. The remaster struggles on my 3090. I was finally able to get 60fps after tweaking graphical settings for a while, but none of that was because of Linux.
Try moving it out of your Program Files folder. Some programs don’t do well in those folders, because writing requires admin rights. It looks like the game is trying to do some sort of operation on a game file, and that operation is failing because it can’t actually access the file. Maybe move it to something like C:\Games instead, which won’t require admin rights to access. You probably shouldn’t be installing games to Program Files anyways.
I suppose the quick and dirty way to test would be to run the game as administrator. If that solves the issue, you know it’s likely something to do with Program Files being write-protected.
As someone else said, installing things outside of Program Files is generally only necessary if they were made for XP or older, and the developers didn't test on Vista or newer or read the bit of the Windows documentation that said not to write to an application's installation directory because it might not work on future versions that was there since the early nineties. Regular Oblivion works fine in Program Files (although it makes it more of a pain to mod) and the Remaster was obviously made post-Vista.
All that said, none of this is relevant because you've got the Windows App version, which uses a completely different system and works in a partial sandbox so doesn't interact with the rest of the computer like a traditional program would.
Out of curiosity, what's your install path for the game? Some games don't cooperate with Program Files or Program Files (x86), so if it's in there, try installing it to a different location and see if the problem persists.
I completely uninstalled steam after moving all of my games to a different drive through steams settings. Then installed steam itself into a c:/games folder and then moved back over the games I wanted on my SSD.
Pretty much only games that were made pre-permission restrictions on Program Files because they try to write to the install folder. I think that was added around XP/Vista. Anything remotely recent shouldn't have this problem (especially if it's the default install directory).
(The error code 0xc0000096 (Privileged instruction) also doesn't indicate this at all but hey, there's been weirder cases of errors caused by completely unrelated seeming conditions.)