Re: Game files missing or corrupt

There wasn't an update needed, but I did end up running cmd - sfc /SCANNOW. This at least got me past the missing files error.  However, the game is now crashing with the below error.

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000000011bb67ad2

WRC
WRC
WRC
WRC
WRC
kernel32
ntdll

XML file contains this, all others are isCrashed>false. Not sure if this is helpful

<Thread>
<CallStack>ntdll 0x00007fff729f0000 + 9d064 KERNELBASE 0x00007fff70290000 + 230ce WRC 0x0000000140000000 + 22a8ea0 WRC 0x0000000140000000 + 52e2c2e VCRUNTIME140 0x00007fff4e980000 + f0e0 ntdll 0x00007fff729f0000 + a23af ntdll 0x00007fff729f0000 + 514b4 ntdll 0x00007fff729f0000 + a0ebe WRC 0x0000000140000000 + 2354986 WRC 0x0000000140000000 + 235d0b1 WRC 0x0000000140000000 + 244e54f WRC 0x0000000140000000 + 22baac7 WRC 0x0000000140000000 + 22b4ad1 KERNEL32 0x00007fff72080000 + 17344 ntdll 0x00007fff729f0000 + 526b1 </CallStack>
<IsCrashed>true</IsCrashed>
<Registers />
<ThreadID>7616</ThreadID>
<ThreadName>GCReentrantWorkerThread 0</ThreadName>
</Thread>

If you have advice for this that would be awesome, if not I'll search more and make a new topic if needed.

Thanks!

I'm getting the same crashes with the same code 

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000000011c2f0008

WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
WRC
kernel32
ntdll  

Still going to have to play more to confirm long term, but I may have got it working. In addition to what was mentioned above (cmd for system files and verifying game files), I also ran Steam as an administrator, cleared out my download cache (steam > settings > downloads) and used the repair library function (steam > settings > storage > select drive and three dots to repair).

Unfortunately, this is still happening with the above error that we are both getting.

Going to use this thread to track things I've done. Currently dropped VRAM clock on my GPU by 60mhz, been running for 3 time trials in a row (knock on wood).

https://www.reddit.com/r/unrealengine/comments/13pi0de/every_unreal_engine_game_crashes_on_my_pc/

Dude, you were right to try reducing Vram clocks. The Access violation error that you are getting is usually invoked by either System Ram clock too high, or more rarely by Vram clock too high. In my experience though, too high Vram clock usually results in the game just closing to desktop with no error logged or a 'Device Removed' error & crash. System ram clock too high will allways give the 'Access Violation' error with a BSOD.

Try lowering system ram clock by 100mhz at a time & testing. If using XMP profiles (automatic Ram OC), Switch back to default ram timings (Auto) & test.

Good luck whatever the case.

FYI 1 : I've had this error only once in my entire play time so far. I believe that the issue arose due to me manually updating the nvngx.dll (DLSS) from 3.1.x.x to the latest 3.5.10. After a file verify corrected the .dll library, I have had no issues.

FYI 2 : Regarding any stutter you may have, I lowered shadows to medium. Everything else on Epic (disabled motion blur in game option), & that's it. No more stutter & locked to 60fps (emphasis on 'locked') as my 55" Sony is 4k 60hz.

System is : I9 9900k @ 5.0ghz (360 Rad LC), EVGA FTW3 2080ti Hybrid LC @ 2055mhz GPU, 8200mhz Vram, 32gb ddr4 3100mhz @XMP trident RGB, Corsair 1000watt modular PSU. Sony 55" 4k 60hz HDR for display.

*** Point to note ***

My GPU Vram clock is overclocked by offset +1200mhz. This takes it from stock 7000mhz to 8200mhz. I have yet to have a game crash (WRC) with 'my' Vram this high, pointing at very good stability with regard to Vram speed / timings sensitivity. Hence why I have advised you to review your system Ram settings.

Does it work for you now?

I have lowered the Memory by 100Mhz as well and it was stable until now.

The same error "Game files missing or corrupt".

- SFC /scannow passes without any errors, patched Windows 11 to the current release (already did that a couple of days ago)

- verify game files integrity -> no errors

The funny thing is, it happens after the stage, only seconds before the game tries to save the game (or maybe tries to access the cloud savegame),

never whilst driving.

ok, it happened while driving too...

Still hit or miss for me, but way better now.  Dropped car reflections and shaders to ultra low to help with stability and lack of stutter. Good call on the system ram too. I found the HP omen hub was overclocking my ram by default so that's back to default.

It's also worth watching the Eventviewer for critical Logs, such like WHEA Errors and (in my case) NVME Storage Controller Errors.

I bougt an WD NVME M2 SSD (was very cheap on Black Friday last year) and many people were complaining, maybe you have this one too.

The solution was to update the SSD-Firmware.

You also usually have 2 XMP-Profiles in your System Bios, maybe try the other one.
I did all the previous things mentioned above, and will tell if that did the trick.

The solution regarding the SSD-Firmware makes sense too, because the game is shader-chaching (hard load for SSD, at C:\ Drive)

Same crap as starting the ps5 in safe mode… it is the console or PC and not eh game that is a totally unfinished product which should have never being released… but yes. Try to update, swith off and on, unplug from the power supply… next will be change the tv or monitor. 

Same crap as starting the ps5 in safe mode… it is the console or PC and not eh game that is a totally unfinished product which should have never being released… but yes. Try to update, swith off and on, unplug from the power supply… next will be change the tv or monitor.

Resizeable Bar was enabled all the time.
Yes, it's quite annoying, driving a good round in an official event --> boom, crash...

In fact, if you have activated the resize bar from the bios and update your nvidia drivers, you must always check that the resize bar is activated in the general nvidia profile. To activate and verify the resize bar you need to use nvidiaInspector.

You can check it in your NVIDIA nvidia control panel as well, just go to system info and look for the line "resizeable bar", no need for nvidiaInspector.

https://youtu.be/1zYjoLbrDF4?si=CKakit_z9cO67e4G

You're wrong, to use it in games you have to use nvidiaInspector and activate it. I also got your error and had the resize bar activated by the bios, but if I didn't activate it also with nvidiaInspector it gave me your error.

OK then, thx for providing the link, every hint helps 🙌

still happening, 3 times in a row now.

---

@knOWN_1337 wrote:

still happening, 3 times in a row now.

---

Problem solved after doing this

ok I will give it a try, thx. Also happened right now after the official patch!

Hey there,

The Game Team is investigating this issue, but they are going to need more info. Could you please gather information on a Dxdiag and attach it here?

How to gather information on your PC using DxDiag

dxdiag attached for further inspection.

that's the error message which occurs while crashing

I also uninstalled the whole GIGABYTE Control Center package because it was causing me the error "video scheduler internal error"
I don't know which of you have installed this kind of monitoring but it could be the cause.
Let me know thanks!!!

Hiya,

I had a crash in clubs last night, please see attached.

Thanks