Forum Discussion

Re: Game crash when changing Anti Aliasing

Try manually editing the settings file..

  1. Go to %USERPROFILE%\Documents\Need For Speed(TM) Unbound\settings
  2. Open the file PROFILEOPTIONS_profile in a text editor (ex. Notepad)
  3. Find GstRender.AntiAliasingPost, change the value to 0
  4. File > Save
  5. Launch game

GstRender.AntiAliasingPost 0 = Off

GstRender.AntiAliasingPost 1 = FXAA

GstRender.AntiAliasingPost 2 = TAA

11 Replies

  • @0CRKrJAK whilst this is a workaround to fix the problem, it's still unacceptable to relaunch your game just for some settings to apply. Especially when there is no ingame benchmark to test and verify that your settings have been applied.
  • Thank you for the suggestion. Unfortunately, setting this value to 0 or 1 causes the game to crash when launching.

    It gets as far as a black screen and then the process crashes, and returns to the EA launcher. Something is going on where the game will not run on my system without TAA enabled. When returned to a value of 2, the game loads normally. Both the OP and I have Nvidia 40 series graphics cards and Ryzen processors, perhaps there is a clue there, or maybe it's something else entirely.

    I do have 6 fresh new mdmp files in the crashdumps folder from trying this out. I have no idea if these files are being submitted automatically or not. If anyone working on the game finds this thread and wants the dumps, I'm holding onto them for now.

  • Thanks for the offer, but I figured might as well do it myself. I have 20 crashdumps, from the 20 times I've tried to change the AA settings to anything other than TAA. I loaded up about half of them, at random, and they all cited the same thing.

    ExceptionAddress: 0000000142985fac (NeedForSpeedUnbound!ffxFsr2ResourceIsNull+0x00000000007f591c)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000000000008
    Attempt to read from address 0000000000000008
    PROCESS_NAME: NeedForSpeedUnbound.exe
    READ_ADDRESS: 0000000000000008
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    EXCEPTION_CODE_STR: c0000005
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 0000000000000008
    ADDITIONAL_DEBUG_TEXT: Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]
    STACK_TEXT:
    00000000`00000000 00000000`00000000 memory_corruption!NeedForSpeedUnbound.exe+0x0
    STACK_COMMAND: ** Pseudo Context ** ManagedPseudo ** Value: ffffffff ** ; kb
    SYMBOL_NAME: memory_corruption!NeedForSpeedUnbound.exe
    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE_256_c0000005_memory_corruption!NeedForSpeedUnbound.exe

    The game runs great as long as I leave TAA alone. Everything maxed out at 4K with no DLSS frame gen or upscaling.

  • @0CRKrJAK I've tried this before as stated in the original post and am getting the same result as @joshuacant ... The game refuses to launch when this setting is changed
  • 0CRKrJAK's avatar
    0CRKrJAK
    3 years ago

    @joshuacantthis is quite odd as MEMORY_CORRUPTION_LARGE_256_c0000005_memory_corruption typically points to unstable RAM. I don't think this would fix it, but just to rule it out, try running your RAM/FCLK at a slower speed....and/or loosen timings.

    Also, have you tried older versions of GPU drivers?

  • @0CRKrJAK there shouldnt be any reason to have to go into the BIOS and change settings to change AA on a game.... I think this might also mean when AA is changed there is a memory leak possibly? Regardless if its something that can only be fixed at a bios level, maybe a patch is warranted

  • My RAM is fine. As I have mentioned a few times, the game runs incredibly well otherwise. I played for 4 hours yesterday, not a single issue.

    GPU drivers could have an impact, but I'm only interested in playing the game, not the DDU/driver install shuffle for a couple hours to try checking for regressions.

    My hope is that this report will get passed up a chain somewhere and a dev will go "ah ha, I know what's causing that" and fix it in a future release. For now I will live with TAA blur and ghosting because whining here is the limit of effort I'm willing to put in.

  • 0CRKrJAK's avatar
    0CRKrJAK
    3 years ago

    @Solfermoney wrote:

    @0CRKrJAK there shouldnt be any reason to have to go into the BIOS and change settings to change AA on a game.... I think this might also mean when AA is changed there is a memory leak possibly? Regardless if its something that can only be fixed at a bios level, maybe a patch is warranted


    Agreed...there shouldn't be any reason for this thread to exist in the first place, but unfortunately here we are.

    There was another user on the Steam forums that reported a memory leak. So it's possible, however, I haven't experienced it even after gaming sessions that lasted multiple hours. 

  • joshuacant's avatar
    joshuacant
    3 years ago

    Sometimes whining and hoping works. Patch just came out, I'm able to switch to FXAA and OFF now without any crashing.

    @Solfermoney give it a try, hopefully it's fixed for you too.

  • omg thank you so much @joshuacant I read this and IMMEDIATLEY got back on the game lol. Works great!! Thank you NFS devs!!!

About NFS Unbound Technical Issues & Bugs

Need support with tech, game or connectivity issues in Need for Speed™ Unbound? Join us to discuss troubleshooting.2,222 PostsLatest Activity: 29 days ago