FATAL D3D ERROR (6, e_outofmemory, 0x8007000e)

[Sleepyfawkes]

Game was working with relatively few issues on Launch, now wont get passed shaders.

7900XTX 24G VRAM, 64G DDR5 RAM, 4TB NVMe Samsung 990 SSD, Ryzen 7 9800x3d

I've Updated Bios, Ran in compatibility mode for windows 7 and 8, Adjusted virtual RAM, Verified game files, reinstalled game, used Direct Driver Uninstaller then reinstalled several different graphics drivers, repaired windows, ran as admin, turned off all overlays, ran -dx11/ -dx12/ and -D3D in steam launch, updated DirectX, deleted crash reporter and its .dll, reset shader cache, turned off EXPO in BIOS, disabled my overclocks and undervolts, changed cpu core affinities, disabled vanguard, bypassed app in firewalls, removed steam version.dll, set dedicated gpu, installed c++, cleaned download cache, adjusted windows timeout detection and recovery, swapped monitors, fixed config typos, launched from Adrenalin, underclocked my GPU, and possibly a few other things I can't think of again.

I also just ran another benchmark with no issues, 34688 204FPS on Ultra 1440. Any help would be appreciated. And yes, I've submitted a ticket.

[SUPERBEAST]

Same here. If I put resolution higher than 1080p the game crashes after some time. Also, I followed a suggestion to remove affinity to core 1 and it seems to help. Everything went downhill when I decided to try to increase resolution to 1440p. It eventually crashed after this after playing for 1 or 2 hours without issues in 1080p.

Btw, I use a 6800xt with 16gb of ram. It shouldnt be an issue. Temperature is very good and performance is good with frame gen. Anyway...back to 1080p I guess.

[Ragnell Avalon VTuber]

If you're getting e_outofmemory then it means DirectX was unable to allocate the block of memory the program requested.[learn.microsoft.com] This can only happen if you're 1. exceeding the program's memory budget 2. actually out of memory (this is RAM, not VRAM) or 3. you have a bad RAM stick (but that would usually cause your computer to power off or cycle).
I did see one suggestion that you may want to make sure that your pagefile[learn.microsoft.com] is working, if you use one.

[Sleepyfawkes]

Originally posted by Ragnell Avalon VTuber:

If you're getting e_outofmemory then it means DirectX was unable to allocate the block of memory the program requested.[learn.microsoft.com] This can only happen if you're 1. exceeding the program's memory budget 2. actually out of memory (this is RAM, not VRAM) or 3. you have a bad RAM stick (but that would usually cause your computer to power off or cycle).
I did see one suggestion that you may want to make sure that your pagefile[learn.microsoft.com] is working, if you use one.

I was tracking my ram useage in my performance tab during launches of wilds, and it did not exceed 30g of my 61.6g. Ram sticks are close to brand new, and Im not having any issues with any other games. I just ran the Wilds benchmark with no issues, and was playing Rivals and Baldurs Gate 3 earlier. How can I see if I'm exceeding the memory budget, and can I set it higher?

[Ragnell Avalon VTuber]

I've had a 'brand new' RAM stick turn out dead before (that's why they sell them in pairs...), but bear in mind that even if you 'have' a lot of RAM, it may not all be available for use, and the actual program's budget may not make use of all of it.
I... actually do not know how to check for that, I'm sorry.

[Sleepyfawkes]

Originally posted by Ragnell Avalon VTuber:

I've had a 'brand new' RAM stick turn out dead before (that's why they sell them in pairs...), but bear in mind that even if you 'have' a lot of RAM, it may not all be available for use, and the actual program's budget may not make use of all of it.
I... actually do not know how to check for that, I'm sorry.

I gotcha, yeah it shows as 50g currently available, no issues with any of it in bios, so i have no doubt my RAM is working. It seems like Wilds specifically is the only issue, and Capcoms "Help" post p much says, "Dang your cpu prob sucks"

[Ragnell Avalon VTuber]

This is a longshot, but have you tried updating to the latest version of DirectStorage? https://www.nuget.org/packages/Microsoft.Direct3D.DirectStorage

[IchimoKurin]

I have encountered this issue as well. It is seemingly random when the crash occurs, the only thing that resembles a pattern in my instance is that it occurs after multiple hours of the game running. for instance yesterday I had played the game all day and had it happened near the end of the day, whereas today I made the effort to shut down the game for a bit then starting again, and haven't experienced the crash. It almost like (and this might not make too much sense its just how I perceive it) that the system is slowly gathering gunk in the memory until it doesn't have enough to run the game any more? I'm sure someone who's more PC literate can make sense of it. I ended up DDU-ing Andrenalin as well to see if it improves. Hopefully something can be down sooner rather than later.
For reference I run a R7 5700X RX6750XT and 32GB RAM

[Sleepyfawkes]

Originally posted by Ragnell Avalon VTuber:

This is a longshot, but have you tried updating to the latest version of DirectStorage? https://www.nuget.org/packages/Microsoft.Direct3D.DirectStorage

I have, no change. :((