Re: Lag/Freezing game NFS payback
Hello guys, I just want to share the things that worked for me; basically I had the same issue on PC, total freezes and unplayable game.
I downloaded the DX11 package from Microsoft.com (named DirectX June 2010 or something like that) and ran the .exe in the folder. What this does is completing the files of DirectX that you currently have on your PC. Windows 10 has DX12 preinstalled but NFS is not compatible with it, then you can have this kind of issues.
The second thing I did was underclocking my GPU with AfterBurner: -50Mhz on core and -100Mhz on memory . This brought some stability and I achieved 2 sessions of continuous gameplay 6 hours each, no errors at all.
If even these solutions still bring an error, search for something called TdrLevel in the registry (location can be found via Google), if it doesnt exist create a D_WORD key (32 bits) and set its value to 0 then reboot. Basically What this does is about the interaction between your OS and the GPU, testing if it's responding in 2s by default. Problem is when your card is busy with the game it does not respond To the system and gets reset, causing a crash.
My setup:
i5 3570k @4Ghz
GTX 680 Lightning 2GB
16GB DDR3
1080p Medium preset on NFS, 65FPS average, no drops at all.
Hope this can help you !
Best regards
I downloaded the DX11 package from Microsoft.com (named DirectX June 2010 or something like that) and ran the .exe in the folder. What this does is completing the files of DirectX that you currently have on your PC. Windows 10 has DX12 preinstalled but NFS is not compatible with it, then you can have this kind of issues.
The second thing I did was underclocking my GPU with AfterBurner: -50Mhz on core and -100Mhz on memory . This brought some stability and I achieved 2 sessions of continuous gameplay 6 hours each, no errors at all.
If even these solutions still bring an error, search for something called TdrLevel in the registry (location can be found via Google), if it doesnt exist create a D_WORD key (32 bits) and set its value to 0 then reboot. Basically What this does is about the interaction between your OS and the GPU, testing if it's responding in 2s by default. Problem is when your card is busy with the game it does not respond To the system and gets reset, causing a crash.
My setup:
i5 3570k @4Ghz
GTX 680 Lightning 2GB
16GB DDR3
1080p Medium preset on NFS, 65FPS average, no drops at all.
Hope this can help you !
Best regards
