Crashing on DriectX and Driver during 2042 startup

[poodlebb]

I've been playing this game for 90+ hours fine, until after the recent update it is now crashing on startup with DirectX and driver. I have checked and already updated to the latest graphic card driver and DirectX, game reinstalled and verified, but it just does not start!

[OzyMan👽]

run sfc /scannow with admin rights
edit: i was using msi ab with low voltage curve so by raising voltage fix the crashing issue

[asl pls thx]

Having the same issue - out of nowhere it's crashing every game with a DirectX error. Other games running fine. Windows 11 Pro (latest updates)/4090 FE (latest drivers).

[Zapman99]

Same for me I have tried fresh install and all tips I found on the web.
I have newest public win 11 Pro
13900ks
4090
64 GB 6000 MT/S CL30

[poodlebb]

I found out the root of problem from another thread of discussions. It came out that the latest GeForce Game Ready drivers do not work with 2042!!! I tried and finally downgraded to version 528.49, 2042 can start to play again.

[d3fct]

Originally posted by poodlebb:

I found out the root of problem from another thread of discussions. It came out that the latest GeForce Game Ready drivers do not work with 2042!!! I tried and finally downgraded to version 528.49, 2042 can start to play again.

I think you are correct, it's the latest drivers but I don't think you had to roll back that far.

The past couple days i've had some random crashes/freezes, I couldn't even play for more than 5-10 mins without a lockup.

I instantly thought the worst, ran memtest, cpu stress tests, and gpu stress tests with no errors or freezes...

I uninstalled the latest NV drivers (536.67) with DDU (https://www.guru3d.com/files-details/display-driver-uninstaller-download.html)

Then I went here (https://www.nvidia.com/en-us/geforce/drivers/) and searched for my gpu's "Game Ready Drivers", and I chose the driver that was previous to 535.67, which was 536.40.


So far so good, played 2 full rounds of 2042, night and day difference in the stability. Will post back if it goes back to crashing/freezing every 5-10 mins.

[Jez]

Originally posted by d3fct:

I chose the driver that was previous to 535.67, which was 536.40.

[d3fct]

Originally posted by d3fct:

I chose the driver that was previous to 535.67, which was 536.40.


So far so good, played 2 full rounds of 2042, night and day difference in the stability. Will post back if it goes back to crashing/freezing every 5-10 mins.

So, it's not the driver had multiple freezes lastnight on multiple diff drivers.

Every time it would crash it recorded it to system logs in the event viewer, I would get a "volume manager error 161" something about the dump file blah blah.

I've tried all the fixes on the interwebs, even reinstalled windows with the windows 10 repair option to retain my personal files.

I have been trying random things, and so far I've gotten a few games out of opening steam first then ea desktop and opening 2042 from ea desktop.

It still took me three tries to get it to start, but again I'm a couple rounds in with no freeze. Will report back if I find something diff I spose.

[d3fct]

Nope got a freeze, played a long time 2 hours plus before I finally got one this time. Might just give it up.

Repaired (reinstalled windows), reinstalled(rolled back) NV drivers, reinstalled 2042, stress tested all HW components, Me thinks something is broken in the game this all started mysteriously when the archangel event ended...

In event viewer the error is logged as "Event 161 Volmgr" "Dump file creation failed due to error during dump creation."

Done all the "fixes" nothing works (fixes) and nothing even comes up as corrupted/broken in a scan.

[d3fct]

Bump.

Anyone else getting this error?

3900x
2080ti
asus x570-e gaming
32gb g.skill @ 3600 xmp
Corsair RM850
m.2 Corsair nvme mp600

[Jez]

i've played quite a lot on the new driver and had 2 DX crashes, but recently I've been running a custom resolution and so it may be related to that because it was a pain setting up between nVIDIA & Windows & HDR & in-game settings, now it's been okay for a while.

Since 2042 released i've had less crashes over time and now it's like straight never.

some comments above mention they're running the RTX 4000, some motherboard manufacturers released a BIOS to address issues

[d3fct]

Originally posted by Jez:

i've played quite a lot on the new driver and had 2 DX crashes, but recently I've been running a custom resolution and so it may be related to that because it was a pain setting up between nVIDIA & Windows & HDR & in-game settings, now it's been okay for a while.

Since 2042 released i've had less crashes over time and now it's like straight never.

some comments above mention they're running the RTX 4000, some motherboard manufacturers released a BIOS to address issues

Bios was updated aswell, 2080ti older gen here.

Almost 160 hours, didn't play a whole lot on release just recently came back for the archangel directive.

Didn't have a single freeze until they stopped that event, now it's guaranteed to freeze.

[Siegfried]

Just brought this game and I got that error.
My NVIDIA driver version is 528.24...

[d3fct]

Originally posted by Siegfried:

Just brought this game and I got that error.
My NVIDIA driver version is 528.24...

Well that sucks, I feel your pain.

Last night I formatted my C: and re-installed windows 10, played for a couple hours without a freeze.

Unfortunately my internet was out for 12 plus hours today (thanks spectrum), So I was unable to do anything earlier today.

I will give it some time tonight to see if I can get a freeze on a fresh install with everything updated to latest versions.

[Jeffrios]

The only fix for me is to just reboot and launch it again. That works. Otherwise I get the same error.

[d3fct]

Originally posted by Jeffrios:

The only fix for me is to just reboot and launch it again. That works. Otherwise I get the same error.

So, it is somewhat common...
I couldn't find any specific 2042 stuff related to the error codes on the interwebs.

I'm leaning towards some sort of conflict of drivers/software, it just mysteriously started happening one day.