Jump to content
Want to report an issue? Have a bug to report? Please look here first!!!! Read more... ×

Archived

This topic is now archived and is closed to further replies.

Game Crashing Randomly (not just at start up) [ZX]

Recommended Posts

I5-3570k / 1070 430.86 driver / Win 10

Game crashes at start in DX12.

Game sometimes crashes at start in DX11

Steam Overlay turned off. Nvidia overlay off. MSI Afterburner closed.

Sometimes game starts, I went through driver creator, options, but when i went to customization and loaded the car liveries it crashes everytime.

Guess I can't play until hotfix?

Share this post


Link to post
Share on other sites

I have the same problem. The crashes hit randomly. It simply opens a report window and closes. I confess that I have not yet been able to change myself with this release.

Share this post


Link to post
Share on other sites

Hi all and thanks for posting,

First of all, can you make sure the issue isn't one in our known issues list?

If it's not one of them, and if you've not already done so, can you try verifying your game? You can do this by following the below:

Validating F1 2019 downloaded correctly

  • Open Steam and go to the Library tab
  • Right click on F1 2019 and select Properties
  • Go to the Local Files tab and click Verify Integrity Of Game Files

For those who have not tried running the game in DX11, please try running the game in DX11 instead of DX12.

If that doesn't work, can you try lowering your graphic settings to see if that does anything?

If it's still crashing after that, can you grab any crash dumps you have, your DXDiag and hardware settings and send them to us so we can take a further look? You can send them to us at community@codemasters.com. Thanks!

Share this post


Link to post
Share on other sites

I am running in DX11 and Ive already gone through the known issues list thats why I posted that I was running DX11 with no steam overlay, no nvidia overlay and no MSI Afterburner. That was in my first post, though not real clear. After the game crashed at startup using DX12, i switched to DX11, and I was able to get into the menus for a time, but then it crashed.

I'll verify my game in steam and then if i can get in i'll lower my graphics settings to low and see if that does anything.

 

Share this post


Link to post
Share on other sites

Update: I verified the integrity of the game files. It completed successfully. I started the game in DX11 and was able to get to the graphics options. I turned everything to low. I went over the time trial and tried to start a time trial at Australia. While loading the track the game crashed.

I'm not sure what else to do, but I have paid for Legends edition and basically cannot play any part of the game. Its 2019 and Ive never had this bad of a launch issue with a game Ive purchased.

Share this post


Link to post
Share on other sites

Até agora eu era capaz de jogar sem ter o problema novamente, o que eu fiz foi desativar o "painel Steam In-Game" nas configurações do aplicativo Steam, bem como a sobreposição nvidia na experiência geforce. Eu não sei exatamente qual deles funcionou porque eu desliguei os dois ao mesmo tempo, mas consegui tocar tanto o DX11 quanto o DX12.

Captura de Tela (4).png

Captura de Tela (5).png

Share this post


Link to post
Share on other sites
5 hours ago, SkyArtur said:

Até agora eu era capaz de jogar sem ter o problema novamente, o que eu fiz foi desativar o "painel Steam In-Game" nas configurações do aplicativo Steam, bem como a sobreposição nvidia na experiência geforce. Eu não sei exatamente qual deles funcionou porque eu desliguei os dois ao mesmo tempo, mas consegui tocar tanto o DX11 quanto o DX12.

Captura de Tela (4).png

Captura de Tela (5).png

Please remember the primary language of this board is English. I've translated this for others, it's a known issue 🙂

Quote

So far I was able to play without having the problem again, what I did was disable the "Steam In-Game panel" in the Steam application settings as well as the nvidia overlay in the geforce experience. I do not know exactly which one worked because I turned them both off at the same time, but I was able to play both the DX11 and the DX12.

 

Share this post


Link to post
Share on other sites

Hi @Sojourner, thanks for taking the time to go through the list. Could you try one final thing for me? Could you try running the game in Safemode?

  • Right-click on the F1 2019 game in the Steam Library and select Properties
  • Press the "Set Launch Options..." button on the first tab.
  • Enter -safemode into the text box and press OK to confirm.
  • Launch the game.

Let me know if that lets you play. 

If it doesn't, then please do send through any crash dumps, your DXDiag and your Hardware settings to community@codemasters.com so that we can take a further look. Thanks!

Share this post


Link to post
Share on other sites

Last night I made sure my Windows 10 was fully updated. I reinstalled my 430.86 driver. Started game in DX11 mode and got a new failure icon, " texture allocation failure - insufficient video memory".

Im not sure what this means, maybe that the game is confused and switching to use my CPU onboard GPU which is causing the crash? Either way Im guessing it is something the Nvidia driver not talking to the game correctly and causing the crash.

I will try safemode tonight and see what happens. If I get an error I'll send over the information from the DXDiag as well as my Hardware Settings.

Share this post


Link to post
Share on other sites
2 hours ago, Faya said:

Hi @Sojourner, thanks for taking the time to go through the list. Could you try one final thing for me? Could you try running the game in Safemode?

  • Right-click on the F1 2019 game in the Steam Library and select Properties
  • Press the "Set Launch Options..." button on the first tab.
  • Enter -safemode into the text box and press OK to confirm.
  • Launch the game.

Let me know if that lets you play. 

If it doesn't, then please do send through any crash dumps, your DXDiag and your Hardware settings to community@codemasters.com so that we can take a further look. Thanks!

I tried -safemode and it still doesn't work.

Windows 7, AMD Radeon R9 200 Series, Directx 11

Share this post


Link to post
Share on other sites

The game still crashed on safemode when I went to load a track, changed the resolution or scanned through the menus too long. I sent an email with some info.

Share this post


Link to post
Share on other sites

I have not been able to fully test yet as I am at work and just ran through the menus of the game remoting in, however I was back tracking in my mind about what I could have done to cause a problem. I realized I had set my windows pagefile to a smaller size trying to free up some space on my main drive. I think I accidentally made it too small for this game.

I had went back and tried F1 2018 which I never had issues with and realized that it was also crashing.

From what I can tell this completely solved my issue. Like I said I haven't played fully but i was getting slow loading in textures just looking at the liveries and now they are loading instantly and no crashes.

For the developers, could this actually be an issue that the game is wanting some virtual memory and if it is set too low could causes crashes?

Share this post


Link to post
Share on other sites
34 minutes ago, Sojourner said:

I have not been able to fully test yet as I am at work and just ran through the menus of the game remoting in, however I was back tracking in my mind about what I could have done to cause a problem. I realized I had set my windows pagefile to a smaller size trying to free up some space on my main drive. I think I accidentally made it too small for this game.

I had went back and tried F1 2018 which I never had issues with and realized that it was also crashing.

From what I can tell this completely solved my issue. Like I said I haven't played fully but i was getting slow loading in textures just looking at the liveries and now they are loading instantly and no crashes.

For the developers, could this actually be an issue that the game is wanting some virtual memory and if it is set too low could causes crashes?

I have the page file set at automatic and it still crashed for me. Game files validated 100%.

Locked up at Bahrain during TT.

  • A short description of the problem: Game crashed randomly
  • Platform you’re on (PS4, Xbox One, PC, Steam): PC Steam
  • Game Version (Shown on the Start screen in the bottom left hand corner): 1.03
  • Game Mode, including if it was Single Player or Multiplayer (Time Trial, Career, Grand Prix, Custom Game etc): TT
  • If in Multiplayer, how many players and how many AI?: n/a
  • What happened in the lead up to the problem?: Going into T1 first hotlap
  • If you get an error message, the exact wording of the error message you're receiving: "Application F1_2019_dx12.e has been blocked from accessing Graphics hardware."
  • Any accessories you are using (wheel, pad, etc): T300, TM Open Wheel Rim

I've attached the full shizz. @Faya

DxDiag.txt

hardware_settings_config.xml

crash_dump#539003-20190628-164359-0.zip

Share this post


Link to post
Share on other sites

Yup, restarted after bug upload etc. Crashed again before completing a lap at Bahrain. Gonna DDU and try driver again.

Share this post


Link to post
Share on other sites
On 6/26/2019 at 5:13 AM, Sojourner said:

I5-3570k / 1070 430.86 driver / Win 10

Game crashes at start in DX12.

Game sometimes crashes at start in DX11

Steam Overlay turned off. Nvidia overlay off. MSI Afterburner closed.

Sometimes game starts, I went through driver creator, options, but when i went to customization and loaded the car liveries it crashes everytime.

Guess I can't play until hotfix?

I had this problem on f1 2018 but not in 2019.

Share this post


Link to post
Share on other sites
38 minutes ago, veetip said:

I had this problem on f1 2018 but not in 2019.

I have the issue and I run AMD. So it's not just Nvidia.

Share this post


Link to post
Share on other sites
4 hours ago, steviejay69 said:

Yup, restarted after bug upload etc. Crashed again before completing a lap at Bahrain. Gonna DDU and try driver again.

DDUed back to 19.6.2 and 19.5.2 recommended (this build ran the beta fine). Still crashes out, so can replicate. 19.5.2 I nearly got 3 laps in.

Share this post


Link to post
Share on other sites

Thanks for all the info, everyone! I'll get it over to the team. 

Share this post


Link to post
Share on other sites

Yes the game has worked perfectly for me in dx11 and dx12 once I changed my pagefile. Thanks for the help! 

Share this post


Link to post
Share on other sites
22 hours ago, Sojourner said:

I have not been able to fully test yet as I am at work and just ran through the menus of the game remoting in, however I was back tracking in my mind about what I could have done to cause a problem. I realized I had set my windows pagefile to a smaller size trying to free up some space on my main drive. I think I accidentally made it too small for this game.

I had went back and tried F1 2018 which I never had issues with and realized that it was also crashing.

From what I can tell this completely solved my issue. Like I said I haven't played fully but i was getting slow loading in textures just looking at the liveries and now they are loading instantly and no crashes.

For the developers, could this actually be an issue that the game is wanting some virtual memory and if it is set too low could causes crashes?

 

1 hour ago, Sojourner said:

Yes the game has worked perfectly for me in dx11 and dx12 once I changed my pagefile. Thanks for the help! 

What did you change your pagefile setting to? How much RAM do you have? What was the low setting you restricted it to before adjusting?

Mine is set to automatic, there should really be no need to adjust it.

https://www.howtogeek.com/126430/htg-explains-what-is-the-windows-page-file-and-should-you-disable-it/ (I know this says don't disable it, but the essence is you really should leave it alone)

The pagefile should automatically resize as required. 

https://support.microsoft.com/en-us/help/2860880/how-to-determine-the-appropriate-page-file-size-for-64-bit-versions-of

Minimum (for my 16GB RAM) would be 2.3GB (RAM/8 + minimum small crash dump) to 32GB (for my 250GB SSD) (RAMx3, limited to Volume size/8).

Share this post


Link to post
Share on other sites

I have 8gb of ram so i set it to 1024*8*1.5 = 12188 or something. I had accidentally set it to 1912 before. I don't know what the minimum is for it not to crash, but i would try setting it manually like that equation shows for your ram.

Share this post


Link to post
Share on other sites

same problem, 70 EUR that have been 4 days thrown away it seems incredible to me that the codemaster does not test his products well. 2 friends with the same problem, is it a joke?

Neither DX11 nor DX12, crash, crash and more crash ...

Share this post


Link to post
Share on other sites

OK, so I tried DX11 and guess what? Bahrain TT does not crash!

Here is the text of the EGODump

Quote

[01-07-2019 11:08:50] - ##################################################
[01-07-2019 11:08:50] - EGO dumper
[01-07-2019 11:08:50] - processId=2452, threadId=3148, exceptionPointers=000000000910F000, buildId=539003
[01-07-2019 11:08:50] - ##################################################
[01-07-2019 11:08:50] - Suspending threads of process 2452
[01-07-2019 11:08:50] - tempPath=C:\Users\stevi\AppData\Local\Temp\
[01-07-2019 11:08:50] - dumpFilename = C:\Users\stevi\AppData\Local\Temp\539003-20190701-110850.dmp
[01-07-2019 11:08:50] - offsetsFilename = C:\Users\stevi\AppData\Local\Temp\539003-20190701-110850.off
[01-07-2019 11:08:50] - infoFilename = C:\Users\stevi\AppData\Local\Temp\info.txt
[01-07-2019 11:08:50] - zipFilename = C:\Users\stevi\AppData\Local\Temp\539003-20190701-110850-0.zip
[01-07-2019 11:08:51] - 0x140000000: F1_2019_dx12.exe
[01-07-2019 11:08:51] - 0x7FF897300000: ntdll.dll
[01-07-2019 11:08:51] - 0x7FF896F30000: KERNEL32.DLL
[01-07-2019 11:08:51] - 0x7FF894D70000: KERNELBASE.dll
[01-07-2019 11:08:51] - 0x7FF8954A0000: advapi32.dll
[01-07-2019 11:08:51] - 0x7FF895720000: msvcrt.dll
[01-07-2019 11:08:51] - 0x7FF895680000: sechost.dll
[01-07-2019 11:08:51] - 0x7FF895550000: RPCRT4.dll
[01-07-2019 11:08:51] - 0x7FF895020000: crypt32.dll
[01-07-2019 11:08:51] - 0x7FF891C10000: amd_ags_x64.dll
[01-07-2019 11:08:51] - 0x7FF8942C0000: ucrtbase.dll
[01-07-2019 11:08:51] - 0x7FF8830D0000: bink2w64.dll
[01-07-2019 11:08:51] - 0x7FF894270000: MSASN1.dll
[01-07-2019 11:08:51] - 0x7FF895E00000: USER32.dll
[01-07-2019 11:08:51] - 0x7FF896DD0000: gdi32.dll
[01-07-2019 11:08:51] - 0x7FF895390000: win32u.dll
[01-07-2019 11:08:51] - 0x7FF894BD0000: gdi32full.dll
[01-07-2019 11:08:51] - 0x7FF896920000: ole32.dll
[01-07-2019 11:08:51] - 0x7FF8952A0000: msvcp_win.dll
[01-07-2019 11:08:51] - 0x7FF896A80000: combase.dll
[01-07-2019 11:08:51] - 0x7FF896E00000: oleaut32.dll
[01-07-2019 11:08:51] - 0x7FF8943C0000: bcryptPrimitives.dll
[01-07-2019 11:08:51] - 0x7FF882D80000: d3d12.dll
[01-07-2019 11:08:51] - 0x7FF895990000: setupapi.dll
[01-07-2019 11:08:51] - 0x7FF870170000: d3dcompiler_47.dll
[01-07-2019 11:08:51] - 0x7FF895340000: cfgmgr32.dll
[01-07-2019 11:08:51] - 0x7FF883030000: dinput8.dll
[01-07-2019 11:08:51] - 0x7FF894290000: bcrypt.dll
[01-07-2019 11:08:51] - 0x7FF892F20000: dxgi.dll
[01-07-2019 11:08:51] - 0x7FF895FA0000: shell32.dll
[01-07-2019 11:08:51] - 0x7FF8957C0000: shcore.dll
[01-07-2019 11:08:51] - 0x7FF8903D0000: gpuopen_depthoffieldfx_x64.dll
[01-07-2019 11:08:51] - 0x7FF892E30000: hid.dll
[01-07-2019 11:08:51] - 0x7FF894450000: windows.storage.dll
[01-07-2019 11:08:51] - 0x7FF894230000: profapi.dll
[01-07-2019 11:08:51] - 0x7FF8937A0000: iphlpapi.dll
[01-07-2019 11:08:51] - 0x7FF8941E0000: powrprof.dll
[01-07-2019 11:08:51] - 0x7FF8941D0000: UMPDC.dll
[01-07-2019 11:08:51] - 0x7FF896FF0000: shlwapi.dll
[01-07-2019 11:08:51] - 0x7FF892190000: WINMM.dll
[01-07-2019 11:08:51] - 0x7FF894250000: kernel.appcore.dll
[01-07-2019 11:08:51] - 0x7FF895220000: cryptsp.dll
[01-07-2019 11:08:51] - 0x7FF88FFB0000: VCRUNTIME140.dll
[01-07-2019 11:08:51] - 0x7FF896700000: ws2_32.dll
[01-07-2019 11:08:51] - 0x7FF892160000: WINMMBASE.dll
[01-07-2019 11:08:51] - 0x7FF892E90000: dxcore.dll
[01-07-2019 11:08:51] - 0x75A60000: steam_api64.dll
[01-07-2019 11:08:51] - 0x7FF875160000: tobii.gameintegration.dll
[01-07-2019 11:08:51] - 0x7FF885E50000: wininet.dll
[01-07-2019 11:08:51] - 0x7FF88EC20000: winhttp.dll
[01-07-2019 11:08:51] - 0x7FF8909A0000: wtsapi32.dll
[01-07-2019 11:08:51] - 0x7FF888CE0000: xinput1_4.dll
[01-07-2019 11:08:51] - 0x7FF893FD0000: DEVOBJ.dll
[01-07-2019 11:08:51] - 0x7FF881CB0000: gfsdk_ssao_d3d12.win64.dll
[01-07-2019 11:08:51] - 0x7FF893C10000: CRYPTBASE.DLL
[01-07-2019 11:08:51] - 0x7FF895870000: IMM32.DLL
[01-07-2019 11:08:51] - 0x7FF870920000: gameoverlayrenderer64.dll
[01-07-2019 11:08:51] - 0x7FF895670000: PSAPI.DLL
[01-07-2019 11:08:51] - 0x7FF88C1F0000: inputhost.dll
[01-07-2019 11:08:51] - 0x7FF892080000: CoreMessaging.dll
[01-07-2019 11:08:51] - 0x7FF88FA20000: wintypes.dll
[01-07-2019 11:08:51] - 0x7FF8904F0000: PROPSYS.dll
[01-07-2019 11:08:51] - 0x7FF88F490000: CoreUIComponents.dll
[01-07-2019 11:08:51] - 0x7FF893280000: ntmarta.dll
[01-07-2019 11:08:51] - 0x7FF895240000: WINTRUST.dll
[01-07-2019 11:08:51] - 0x7FF895910000: imagehlp.dll
[01-07-2019 11:08:51] - 0x7FF859C50000: steamclient64.dll
[01-07-2019 11:08:51] - 0x7FF88F130000: VERSION.dll
[01-07-2019 11:08:51] - 0x7FF882FB0000: vstdlib_s64.dll
[01-07-2019 11:08:51] - 0x7FF86FFF0000: tier0_s64.dll
[01-07-2019 11:08:51] - 0x7FF893A40000: MSWSOCK.dll
[01-07-2019 11:08:51] - 0x7FF880F20000: Secur32.dll
[01-07-2019 11:08:51] - 0x7FF8940C0000: SSPICLI.DLL
[01-07-2019 11:08:51] - 0x7FF8924B0000: uxtheme.dll
[01-07-2019 11:08:51] - 0x7FF893600000: rsaenh.dll
[01-07-2019 11:08:51] - 0x7FF88BD60000: D3DSCache.dll
[01-07-2019 11:08:51] - 0x7FF892670000: twinapi.appcore.dll
[01-07-2019 11:08:51] - 0x7FF8940F0000: USERENV.dll
[01-07-2019 11:08:51] - 0x7FF892AD0000: RMCLIENT.dll
[01-07-2019 11:08:51] - 0x7FF85CDF0000: atiadlxx.dll
[01-07-2019 11:08:51] - 0x7FF896DC0000: NSI.dll
[01-07-2019 11:08:51] - 0x7FF88FA00000: dhcpcsvc6.DLL
[01-07-2019 11:08:51] - 0x7FF88F9E0000: dhcpcsvc.DLL
[01-07-2019 11:08:51] - 0x7FF8937E0000: DNSAPI.dll
[01-07-2019 11:08:51] - 0x7FF897180000: MSCTF.dll
[01-07-2019 11:08:51] - 0x7FF8932F0000: WINSTA.dll
[01-07-2019 11:08:51] - 0x7FF845DE0000: amdxc64.dll
[01-07-2019 11:08:51] - 0x7FF88C6C0000: amdihk64.dll
[01-07-2019 11:08:51] - 0x7FF8919A0000: dcomp.dll
[01-07-2019 11:08:51] - 0x7FF8929C0000: dwmapi.dll
[01-07-2019 11:08:51] - 0x7FF88C300000: TextInputFramework.dll
[01-07-2019 11:08:51] - 0x7FF88A770000: iertutil.dll
[01-07-2019 11:08:51] - 0x7FF897050000: clbcatq.dll
[01-07-2019 11:08:51] - 0x7FF88BDF0000: MMDevApi.dll
[01-07-2019 11:08:51] - 0x7FF883D50000: AUDIOSES.DLL
[01-07-2019 11:08:51] - 0x7FF8928D0000: resourcepolicyclient.dll
[01-07-2019 11:08:51] - 0x7FF8903C0000: Windows.Gaming.Input.dll
[01-07-2019 11:08:51] - 0x7FF88EF80000: Windows.Gaming.Input.dll
[01-07-2019 11:08:51] - 0x7FF86FE00000: mssps.dll
[01-07-2019 11:08:51] - 0x7FF888170000: MSACM32.dll
[01-07-2019 11:08:51] - 0x7FF859250000: wmvcore.dll
[01-07-2019 11:08:51] - 0x7FF882BD0000: WMASF.DLL
[01-07-2019 11:08:51] - 0x7FF868070000: mfperfhelper.dll
[01-07-2019 11:08:51] - 0x7FF8590F0000: spsreng.dll
[01-07-2019 11:08:51] - 0x7FF875070000: srloc.dll
[01-07-2019 11:08:51] - 0x7FF882B80000: wdmaud.drv
[01-07-2019 11:08:51] - 0x7FF86ACD0000: ksuser.dll
[01-07-2019 11:08:51] - 0x7FF8900B0000: AVRT.dll
[01-07-2019 11:08:51] - 0x7FF887EE0000: msacm32.drv
[01-07-2019 11:08:51] - 0x7FF887ED0000: midimap.dll
[01-07-2019 11:08:51] - 0x7FF88A000000: urlmon.dll
[01-07-2019 11:08:51] - 0x7FF875020000: tmpid.dll
[01-07-2019 11:08:51] - 0x7FF883320000: DINPUT.dll
[01-07-2019 11:08:51] - 0x7FF88C3A0000: Windows.UI.dll
[01-07-2019 11:08:51] - 0x7FF891740000: d3d11.dll
[01-07-2019 11:08:51] - 0x7FF8748C0000: d3d11on12.dll
[01-07-2019 11:08:51] - 0x7FF85C910000: dxilconv.dll
[01-07-2019 11:08:51] - 0x7FF893640000: DPAPI.DLL
[01-07-2019 11:08:51] - 0x7FF8857A0000: webio.dll
[01-07-2019 11:08:51] - 0x7FF88F480000: WINNSI.DLL
[01-07-2019 11:08:51] - 0x7FF88DE40000: rasadhlp.dll
[01-07-2019 11:08:51] - 0x7FF88F870000: fwpuclnt.dll
[01-07-2019 11:08:51] - 0x7FF893530000: schannel.DLL
[01-07-2019 11:08:51] - 0x7FF87FA10000: mskeyprotect.dll
[01-07-2019 11:08:51] - 0x7FF893D10000: ncrypt.dll
[01-07-2019 11:08:51] - 0x7FF893CD0000: NTASN1.dll
[01-07-2019 11:08:51] - 0x7FF87E670000: ncryptsslp.dll
[01-07-2019 11:08:51] - Writing callstacks for threads of process: 2452
[01-07-2019 11:08:51] - Thread: 7960
[01-07-2019 11:08:51] - Thread: 9040
[01-07-2019 11:08:51] - Thread: 5084
[01-07-2019 11:08:51] - Thread: 3148
[01-07-2019 11:08:51] - Thread: 9660
[01-07-2019 11:08:51] - Thread: 8584
[01-07-2019 11:08:51] - Thread: 8592
[01-07-2019 11:08:51] - Thread: 4784
[01-07-2019 11:08:51] - Thread: 796
[01-07-2019 11:08:51] - Thread: 9012
[01-07-2019 11:08:51] - Thread: 1844
[01-07-2019 11:08:51] - Thread: 10652
[01-07-2019 11:08:51] - Thread: 5088
[01-07-2019 11:08:51] - Thread: 1012
[01-07-2019 11:08:51] - Thread: 4280
[01-07-2019 11:08:51] - Thread: 4668
[01-07-2019 11:08:51] - Thread: 9576
[01-07-2019 11:08:51] - Thread: 8096
[01-07-2019 11:08:51] - Thread: 10312
[01-07-2019 11:08:51] - Thread: 6328
[01-07-2019 11:08:51] - Thread: 8376
[01-07-2019 11:08:51] - Thread: 6216
[01-07-2019 11:08:51] - Thread: 10212
[01-07-2019 11:08:51] - Thread: 3580
[01-07-2019 11:08:51] - Thread: 4548
[01-07-2019 11:08:51] - Thread: 6924
[01-07-2019 11:08:51] - Thread: 2764
[01-07-2019 11:08:51] - Thread: 924
[01-07-2019 11:08:51] - Thread: 6460
[01-07-2019 11:08:51] - Thread: 1592
[01-07-2019 11:08:51] - Thread: 10100
[01-07-2019 11:08:51] - Thread: 6252
[01-07-2019 11:08:51] - Thread: 9480
[01-07-2019 11:08:51] - Thread: 7268
[01-07-2019 11:08:51] - Thread: 7272
[01-07-2019 11:08:51] - Thread: 2752
[01-07-2019 11:08:51] - Thread: 5588
[01-07-2019 11:08:51] - Thread: 10320
[01-07-2019 11:08:51] - Thread: 5148
[01-07-2019 11:08:51] - Thread: 8320
[01-07-2019 11:08:51] - Thread: 9852
[01-07-2019 11:08:51] - Thread: 9292
[01-07-2019 11:08:51] - Thread: 1244
[01-07-2019 11:08:51] - Thread: 9452
[01-07-2019 11:08:51] - Thread: 8832
[01-07-2019 11:08:51] - Thread: 7164
[01-07-2019 11:08:51] - Thread: 1596
[01-07-2019 11:08:51] - Thread: 5312
[01-07-2019 11:08:51] - Thread: 8484
[01-07-2019 11:08:51] - Thread: 5932
[01-07-2019 11:08:51] - Thread: 6940
[01-07-2019 11:08:51] - Thread: 4732
[01-07-2019 11:08:51] - Thread: 3120
[01-07-2019 11:08:51] - Thread: 7284
[01-07-2019 11:08:51] - Thread: 9936
[01-07-2019 11:08:51] - Thread: 8456
[01-07-2019 11:08:51] - Thread: 6064
[01-07-2019 11:08:51] - Thread: 3032
[01-07-2019 11:08:51] - Thread: 5624
[01-07-2019 11:08:51] - Thread: 9048
[01-07-2019 11:08:51] - Thread: 2996
[01-07-2019 11:08:51] - Thread: 7932
[01-07-2019 11:08:51] - Thread: 7216
[01-07-2019 11:08:51] - Thread: 9804
[01-07-2019 11:08:51] - Thread: 6000
[01-07-2019 11:08:51] - Thread: 4632
[01-07-2019 11:08:51] - Thread: 5788
[01-07-2019 11:08:51] - Thread: 6344
[01-07-2019 11:08:51] - Thread: 9204
[01-07-2019 11:08:51] - Thread: 4892
[01-07-2019 11:08:51] - Thread: 7544
[01-07-2019 11:08:51] - Thread: 9228
[01-07-2019 11:08:51] - Thread: 9848
[01-07-2019 11:08:51] - Thread: 7840
[01-07-2019 11:08:51] - Thread: 9056
[01-07-2019 11:08:51] - Thread: 8352
[01-07-2019 11:08:51] - Thread: 8004
[01-07-2019 11:08:51] - Thread: 1656
[01-07-2019 11:08:51] - Thread: 8920
[01-07-2019 11:08:51] - Thread: 6712
[01-07-2019 11:08:51] - Thread: 6508
[01-07-2019 11:08:51] - Thread: 32
[01-07-2019 11:08:51] - Thread: 6192
[01-07-2019 11:08:51] - Thread: 5800
[01-07-2019 11:08:51] - Thread: 7900
[01-07-2019 11:08:51] - Thread: 5152
[01-07-2019 11:08:51] - Thread: 8596
[01-07-2019 11:08:51] - Thread: 9768
[01-07-2019 11:08:51] - Thread: 6824
[01-07-2019 11:08:51] - Thread: 10184
[01-07-2019 11:08:51] - Thread: 7204
[01-07-2019 11:08:51] - Thread: 8076
[01-07-2019 11:08:51] - Thread: 5236
[01-07-2019 11:08:51] - Thread: 1784
[01-07-2019 11:08:51] - Offsets file can be found at: C:\Users\stevi\AppData\Local\Temp\539003-20190701-110850.off.
[01-07-2019 11:08:51] - Writing DMP file.
[01-07-2019 11:08:51] - MiniDump can be found at: C:\Users\stevi\AppData\Local\Temp\539003-20190701-110850.dmp.
[01-07-2019 11:08:51] - Preparing ZIP file.
[01-07-2019 11:08:51] - Resuming threads of process 2452.
 

In DX11 CPU usage and memory are pretty constant, in DX12 CPU usage starts to fall then GPU core clock crashes. I will post a screenshot of AMD Link.

Other thing I notice is Bahrain looks entirely different in DX11 to DX12 at Official time. Both screenshots are with AMD 19.6.3 on High preset.

DX11 (which is what it's supposed to look like)?

20190701112311_1.jpg

 

DX12

20190701110714_1.jpg

AMD Link

IMG_0215.PNG

 

Share this post


Link to post
Share on other sites

×