Forum Discussion

ogBilly4000's avatar
ogBilly4000
New Novice
6 days ago

Constant DirectX 12 errors

The most common is the following:

DirectX function "device2->CreatePipelineState(&psoDesc, IID_PPV_ARGS(&pipelineState))" failed with E_OUTOFMEMORY ("Direct3D could not allocate sufficient memory to complete the call."). GPU: "NVIDIA GeForce RTX 4090", Driver: 580.88. This error is usually caused by the graphics driver crashing; try installing the latest drivers. Also try closing other running applications. 

However, this is definitely not the only DirectX error that I get. Obviously, my PC is no slouch as can be inferred from the error message. I have started seeing reddit posts and youtube videos discussing the same error as well.

In any case... let me explain some of what I've done / tried... hopefully it raises the alarms that it should.

Firstly, it crashes the game, constantly. I think I've managed maybe 60 seconds in a game at virtually minimum settings (e.g.,  scaling is at like 90% but everything else is at as low as it goes). I have also tried force launching DX11 - no difference.

I have tried rolling back drivers - no difference - more crashes without error message is about the only difference.

The larger issue by far is the number of BSODs and hard system crashes that the beta has caused my PC. Somehow, at some point, one of the crashes absolutely crippled my computer, most especially the audio drivers. Issues included but were not limited to: caches, drivers, system registries, file / folder issues, etc. I know it's not perfect, but the sheer scope of the problems were astronomical. I worked with ChatGPT+ to help generate dozens of PowerShell scripts to correct the issues. Ultimately though, I had to do a complete system restore to fix the final issue (audio drivers / registries).

Again, I had to do a system restore... so I'm sure many of the potential logs are gone, but... my computer is at least working again and I've re-updated everything I could find. I'm willing to share any logs, files, system info, etc. that can help troubleshoot this issue. Just let me know.

In any case. I did try to resolve the issues, but as a developer myself (enterprise, not related to gaming) and as agreed by ChatGPT... this is not a hardware issue / limitation (initial logs show VRAM getting to barely over 8GB of use out of the available 22GB.. logs lost with restore) and is most likely an engine / development issue.

 

Any help would be appreciated :)

1 Reply

  • l501aa's avatar
    l501aa
    Seasoned Rookie
    6 days ago

    I got also a performing pc, with an Nvidia 4080, and I get the same error messages, tried same solutions, on top of having to use a new windows user account to make the **bleep** anticheat work (the usual windows user gives me the silent anticheat crash for no reason). After the 4th or 5th error of this kind, I got a pc crash, restarted, I wasn't seeing anymore my D: drive, only C: (the beta was on C: too).

    I wa slucky a simple reboot fixed the issue, and so far it hasn't presented again itself. I won't touch this beta again unless there's a fix, and hopefully they solve this mess before october launch. 

    I'd be extremely pissed to not be able to play the game I pre-ordered, while my pc satisfies all the required specs, exceeding them by far. Also hopefully Nvidia will release a driver updated including BF6 support and it will maybe solve everything.

About Battlefield 6 Beta Technical Issues & Bugs

Report bugs and get help with technical issues during the Battlefield 6 Beta.2,593 PostsLatest Activity: 3 minutes ago