Forum Discussion

Re: RayTracing Causes Game to Crash!

 
got a huge update on this case:
 
Deactivating all applications on startup to do a clean boot didn't help. The game crashed soon after starting a session. The GPU clock is not overclocked by me. I don't know if it's overclocked by factory. It's a founders edition card. I also checked the temperature in game and it didn't raised above 75/76°C.
 
I managed to get rid of the crashes soon after playing a session. I could play for hours straight until the graphics card driver crashed. No DX12 error message anymore.
 
So, this is the procedure I did, and I am not 100% what the cause is….
I've launched the game and changed the resolution from 4k to 1080p. This made me play the game for way longer without a crash, so I increased the resolution to 1440p midgame (I also changed VSync to off, since I am using GSync, turn off "future frame prediction" and "Frame limiter" to 60) and played for a little while, went to the kitchen and after I came back, I saw the windows desktop. It crashed without an error message.
 
This made me thinking that the VRAM could be faulty. So, I tried out to find a tool to verify VRAM for errors, but I couldn't find a satisfying tool checking all of the 11GB VRAM. So, I started Watchdogs 2 with MAX settings (i.e. TXAA 8x and so on). Game crashed on loading the world without an error message.
 
I check the usage via the task manager and saw that the GPU has 11 GB of dedicated VRAM and 8 GB shared memory which sums it up to 19 GB of Memory for the GPU. Not sure where the 8 GB are coming from or where they are configured. So, I randomly checked the page file size for virtual memory (I used to manually fix the value) and it was only at 2 GB. That's way too low, so I increased it to 10 GB on both partitions.
 
I also downloaded MSI Afterburner (to have a better check on memory and temperature usage). I launched Watchdogs 2 with TXAA 4x this time and it loaded just fine. VRAM usage was on 10 GB VRAM, already.  Ran like ****, but didn't crashed. So, I launched BF 5 with 1440p.. played a while, seems good. Increased the Resolution to 4k and played for some hours straight. Multiplayer as well as Singleplayer. After the end of a singleplayer campaign, the graphics card driver crashed. It was at the scene in Norway where the submarine blew up. So, far, I didn't had another crash.
 
I will certainly keep an eye on it and post if I encounter more crashes. So, far, the game seems to run stable and I can enjoy a lot by playing with DXR enabled.
 
Will keep you updated.
 
Thanks so far for your support.
 
Edit: My post was gone after submitted it, so I repost it. 

3 Replies

  • EA_Barry's avatar
    EA_Barry
    Icon for Community Manager rankCommunity Manager
    7 years ago

    @Peh1984

    Thank you so much for posting!

    Yes, either setting the Pagefile to 2x your RAM or just letting Windows take care of that is usually the way to go, a 2GB pagefile/swapfile is definitely too small.

    Thanks again.

  • Peh1984's avatar
    Peh1984
    7 years ago

    After some check, it's definitely the page file size. I used to have a bigger one on a different partition, but since a few month ago I change the SSD completely into a Raid 0 configuration. I guess that Windows just removed it completely since the partition wasn't there anymore instead of allocating a new one. 

    Welp, I would say.. case closed 🙂

  • WRONG. Tried all modes - auto and manual - up to twice the amount of memory that my system has.

    Plays longer but still crashes like the GARBAGE this pile of code is proving itself to be.

About Battlefield V

Join the Battlefield V community to learn all you need to know. Find game information and updates, talk tactics and share Battlefield moments.15,403 PostsLatest Activity: 2 hours ago