Forum Discussion

Bono8o's avatar
Bono8o
New Traveler
1 day ago

New Patch and crashing returns again

This happened at the start of Season 3 and, once again, immediately after the update, the game crashes after 5–10 minutes of game play. I thought I'd finally resolved the issue after specifying the CPU cores in the user.cfg file, and it had been perfectly stable for a few weeks. To see this problem return is so, so disappointing.

3 Replies

  • cyberfredcobra's avatar
    cyberfredcobra
    Seasoned Veteran
    1 day ago

    same here, after a while , I have this problem :

    https://www.reddit.com/r/Battlefield/comments/1v2jx8d/updated_to_season_4_and_game_crashes_now/

  • Bono8o's avatar
    Bono8o
    New Traveler
    1 day ago

    This was the same message that popped in my last attempt to play the game, prior to that 20 mins earlier it crashed Windows with the BSOD - ntoskrnl.exe error. Sames issues during first weeks of season 3 and Season 2.

    I am not going through the BS of running a full diagnostic/system check/update/reinstall Windows for this one game. No other title in the last 30 years of my gaming has ever required this level of time wasting BS to resolve an inherent issue with the game engine.

  • Bono8o's avatar
    Bono8o
    New Traveler
    19 hours ago

    For the sake of this thread and as a reference, I'm running a 14700K at 5.7 GHz with a -0.120V undervolt offset and RTX 5070Ti at 2895mhz @ 895mV. The game either hard reset my PC or crashed out to desktop - DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). GPU: Nvidia Geforce RTX 5070Ti..

    After spending far too much time testing different fixes, the game was actually stable until the end of Season 3. I could play multiple games in succession without any problems. However, the start of Season 4 was a different story. The game would run for only 5–10 minutes before crashing to a black screen with no video signal. The fans would continue running, but the system was completely unresponsive.

    I tried many of the suggested fixes: resetting various settings, underclocking both the CPU and GPU, disabling G-SYNC, enabling/disabling XMP, and more. A lot of the suggestions didn't make much sense and made no difference. Eventually, I came across a suggested fix that addressed high CPU utilisation by adding the following entries to the user.cfg file to specify the processor cores and threads (see below).

    Thread.ProcessorCount 20
    Thread.MaxProcessorCount 20
    Thread.MinFreeProcessorCount 0
    Thread.JobThreadPriority 0
    GstRender.Thread.MaxProcessorCount 28

    The improvement was immediate. I could play for as long as I wanted without a single crash, just as I could during Seasons 1 and 2. I was also able to restore all of my custom CPU and GPU settings to their fully optimised values, which I'd spent countless hours testing and tweaking to ensure stability across benchmarking applications and my other favourite games.
    To then have the game start crashing again after the Season 4 update was extremely frustrating.

    Following the thread in the link above, I cleared the shader cache using the instructions below. I'd done this in the past and it hadn't made any difference, but I thought it was worth another try. Unfortunately, this time the game crashed while switching to fullscreen during startup, resulting in a BSOD.

    BSOD details:
    Stop code: IRQL_NOT_LESS_OR_EQUAL
    What failed: ntoskrnl.exe

    Shader cache procedure:
    1. Disable the shader cache: Open NVIDIA Control Panel → Manage 3D Settings → Shader Cache Size, set it to Disabled, then click Apply.
    2. Delete the cache files (Method 1 - Direct):
    -Press Windows + R, type %localappdata%, and press Enter.
    -Open the NVIDIA folder.
    -Delete all files inside the DXCache and GLCache folders.
    -Skip any files that are currently in use.
    3. Clear the DirectX Shader Cache:
    -Open Disk Cleanup.
    -Select your C: drive.
    -Tick DirectX Shader Cache, then click OK.
    4. Re-enable the shader cache: Return to NVIDIA Control Panel → Shader Cache Size, and set it back to Driver Default or choose a specific size (for example, 10 GB or Unlimited). I chose Unlimited.
    5. Restart your PC to allow Windows and the game to rebuild fresh shader caches.

    In light of this I then took a different approach and reduced my CPU undervolt from -0.120 V to -0.110 V. Surprisingly, I have just managed to play three games back to back without any issues. However, the fourth has failed to load properly. It failed to load the class selection screen screen. The loading square animations in the bottom right are active and there is sound, but I cannot return to the main menu, KB input is unresponisve. I will be forced to close the process using Windows Task Manager.

    This seems like progress, so I'll keep this thread updated, if things change.

Featured Places

Node avatar for Battlefield 6 Technical Issues

Battlefield 6 Technical Issues

Having issues with Battlefield 6? Join here to find help with connectivity, performance issues, crashes and more.Latest Activity: 18 minutes ago
8,561 Posts