Fatal error?

[Titanofdoom]

About 30 secs after leaving the sewers, crashes with fatal error!

Game is running beaitifully on auto detect settings (all to ultra).

Crashed 3 times, card fully updated running any other game well.

[Titanofdoom]

BUMP

[StickyFingers]

I got fatal error on exit. Booted it back up and boom my manual and auto saves were all gone.

[Cowboy Tanaka]

Originally posted by StickyFingers:

I got fatal error on exit. Booted it back up and boom my manual and auto saves were all gone.

Same

[Poltergeist]

Happening to a lot of people. AFAIK no confirmed fixes.

[Cowboy Tanaka]

Check your windows notifications and you will see one Windows Security regarding the game.

Expand that and allow access to the folder through the actions tab.

It's so scuffed because access to it's own folder is being blocked

[Cloud]

To fix fatal error on closing Oblivion Remastered:

Windows security >
Virus & threat protection >
Manage ransomware protection >
Allow an app through controlled folder access >
+ Add an allowed app. >
recently blocked apps.

It should be in the list as OblivionRemastered-Win64-Shipping.exe.
Add it to the list and it should no longer have a Fatal error when exiting the game.

[racist kuze]

Originally posted by Cloud:

To fix fatal error on closing Oblivion Remastered:

Windows security >
Virus & threat protection >
Manage ransomware protection >
Allow an app through controlled folder access >
+ Add an allowed app. >
recently blocked apps.

It should be in the list as OblivionRemastered-Win64-Shipping.exe.
Add it to the list and it should no longer have a Fatal error when exiting the game.

I don't even have ransomware protection enabled, and it still crashes 😴

[Faton]

In the event manager you can see this details of the "fatal error",

<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
<WindowsNTVersion>10.0</WindowsNTVersion>
<Build>26100</Build>
<Product>(0x30): Windows 10 Pro</Product>
<Edition>Professional</Edition>
<BuildString>26100.3775.amd64fre.ge_release.240331-1435</BuildString>
<Revision>3775</Revision>
<Flavor>Multiprocessor Free</Flavor>
<Architecture>X64</Architecture>
<LCID>3082</LCID>
<BuildLayers>
<BuildLayer LayerName="26100.1.amd64fre.ge_release.240331-1435" OsMajorVersion="10" OsMinorVersion="0" BuildNumber="26100" QfeNumber="3775" IsTopLevel="1" IsChecked="0" BuildStamp="240331-1435" BuildBranch="ge_release" BuildArch="amd64" BuildLab="26100.ge_release.240331-1435" BuildLabEx="26100.1.amd64fre.ge_release.240331-1435"/>
<BuildLayer LayerName="26100.1.amd64fre.ge_release.240331-1435" OsMajorVersion="10" OsMinorVersion="0" BuildNumber="26100" QfeNumber="3775" IsTopLevel="0" IsChecked="0" BuildStamp="240331-1435" BuildBranch="ge_release" BuildArch="amd64" BuildLab="26100.ge_release.240331-1435" BuildLabEx="26100.1.amd64fre.ge_release.240331-1435"/>
<BuildLayer LayerName="26100.3775.amd64fre.ge_release_svc_prod1.250405-0010" OsMajorVersion="10" OsMinorVersion="0" BuildNumber="26100" QfeNumber="3775" IsTopLevel="0" IsChecked="0" BuildStamp="250405-0010" BuildBranch="ge_release_svc_prod1" BuildArch="amd64" BuildLab="26100.ge_release_svc_prod1.250405-0010" BuildLabEx="26100.3775.amd64fre.ge_release_svc_prod1.250405-0010"/>
<BuildLayer LayerName="26100.3775.amd64fre.ge_release_svc_prod1.250405-0010" OsMajorVersion="10" OsMinorVersion="0" BuildNumber="26100" QfeNumber="3775" IsTopLevel="0" IsChecked="0" BuildStamp="250405-0010" BuildBranch="ge_release_svc_prod1" BuildArch="amd64" BuildLab="26100.ge_release_svc_prod1.250405-0010" BuildLabEx="26100.3775.amd64fre.ge_release_svc_prod1.250405-0010"/>
</BuildLayers>
</OSVersionInformation>
<ProblemSignatures>
<EventType>MoAppCrash</EventType>
<Parameter0>BethesdaSoftworks.ProjectAltar_1.0.3.0_x64__3275kfvn8vcwc</Parameter0>
<Parameter1>praid:AppUEGameShipping</Parameter1>
<Parameter2>5.3.2.0</Parameter2>
<Parameter3>00000000</Parameter3>
<Parameter4>KERNELBASE.dll</Parameter4>
<Parameter5>10.0.26100.3775</Parameter5>
<Parameter6>6e2fc3bb</Parameter6>
<Parameter7>00008000</Parameter7>
<Parameter8>00000000000c933a</Parameter8>
</ProblemSignatures>
<DynamicSignatures>
<Parameter1>10.0.26100.2.0.0.256.48</Parameter1>
<Parameter2>3082</Parameter2>
<Parameter22>4bc8</Parameter22>
<Parameter23>4bc835af53440d3a0db136764debce92</Parameter23>
<Parameter24>d0b4</Parameter24>
<Parameter25>d0b418ad20ab6dced3cdc0c6382b7dea</Parameter25>
</DynamicSignatures>

this will need a patch I think, as is an error with the kernel library.

[The1st$keletonKing]

Has anyone had this issue on xbox app? I have gamepass and thought this game would bring back memories but instead brought anger and disappointment.

[Bobby]

It’s a standard error with UE5. Go look at Fernbus, Tourist Bus, Robocop forums. All upgraded or use UE5 and it’s common with anybody regardless of RTX 4090, 30,20 series. If you can turn off lumen - if it’s in the game (UE feature) that may make it stable.

I sorted my Robocop by defaulting the graphics and turning lumen reflections off. Then playing as-is. It’s crap, but playable.
I HATE UE and will not tolerate any more games with it.

[Schwarzwald]

Any fix?

[pinpongcake]

Originally posted by The1st$keletonKing:

Has anyone had this issue on xbox app? I have gamepass and thought this game would bring back memories but instead brought anger and disappointment.

Have the same issue. I got the game pass on pc. Cannot even load the game. Crashes at the launch screen.

[jason2042]

Originally posted by pinpongcake:

Originally posted by The1st$keletonKing:

Has anyone had this issue on xbox app? I have gamepass and thought this game would bring back memories but instead brought anger and disappointment.

Have the same issue. I got the game pass on pc. Cannot even load the game. Crashes at the launch screen.

Same here. Tried adding the app to the folder allow list in windows security, but no joy. Tried repairing game files in Xbox app, as well as repairing Xbox gaming services - still no joy. Pretty annoying...

[ELiMs]

Originally posted by Cowboy Tanaka:

Check your windows notifications and you will see one Windows Security regarding the game.

Expand that and allow access to the folder through the actions tab.

It's so scuffed because access to it's own folder is being blocked

-This worked, wild times.

[Faton]

Originally posted by ELiMs:

Originally posted by Cowboy Tanaka:

Check your windows notifications and you will see one Windows Security regarding the game.

Expand that and allow access to the folder through the actions tab.

It's so scuffed because access to it's own folder is being blocked

-This worked, wild times.

Not for people that not uses Windows Security and uses another Security suite, and not havr ransomware protection active. 100% sute that this isnt the main reason, can be one but noy the main.