Benchmark Doesn't Work

[Reaper Scythe]

Using AMD 5800X3D with a Sapphire Pulse 7900XTX. It took 30 min for the shaders to compile using only 30% of the CPU. Meaning their compiler does not scale, or isn't.

Also would not even run the benchmark past loading the 3D environment. Each time I went into the game and clicked run benchmark it would go to black screen and crash. I tried with Frame Gen, without, adjusting GPU clocks to stock, and even lower than stock.

Benchmark just doesn't run. AMD driver, 24.12.1 -Windows 11 Pro with latest Service Updates

[Reaper Scythe]

I solved the issue with the game and the bench mark. I don't normally have a large page file set because I have a lot of RAM and VRAM. 32GB, 24GB to be exact. However, once I changed the page file to system managed I see what the problem was. Between The GPU, MB RAM, and Page-file the game needs 80GB for loaded assets and shaders.

Page File is based on your storage drive / hard-drive. You can set it to any drive with space. Based on playing the "beta" with 24GB VRAM you need an additional Page File of 36GB on the highest settings. To change your page file;
- Right click the windows icon then left click system.
- On the next page click "Advanced System Settings".
- Then under the "performance section click settings.
- On the next window click the Advanced tab.
- Then at the bottom click change in the virtual memory section.
- I recommend setting it to system managed size on your main C: drive but if you don't have room and have an acceptably fast second drive you can do it on that one too.
- Reboot the computer for it to take affect and give it another whirl.
- I recommend that you have at least 50GB of space on the page file drive as it will dynamically size as you need it.

Now that that is fixed the game runs like a dream on the highest settings with my 7900XTX at 1080P. Still odd that the game itself only uses 50% of my physical RAM on the motherboard. I would think they would want to use as much of that as possible for its transfer speed alone. I think its more that current day game developers dont want to manage memory very well, its why consoles have so much RAM.

[SpinelTonicAddict]

Originally posted by Reaper Scythe:

I solved the issue with the game and the bench mark. I don't normally have a large page file set because I have a lot of RAM and VRAM. 32GB, 24GB to be exact. However, once I changed the page file to system managed I see what the problem was. Between The GPU, MB RAM, and Page-file the game needs 80GB for loaded assets and shaders.

Page File is based on your storage drive / hard-drive. You can set it to any drive with space. Based on playing the "beta" with 24GB VRAM you need an additional Page File of 36GB on the highest settings. To change your page file;
- Right click the windows icon then left click system.
- On the next page click "Advanced System Settings".
- Then under the "performance section click settings.
- On the next window click the Advanced tab.
- Then at the bottom click change in the virtual memory section.
- I recommend setting it to system managed size on your main C: drive but if you don't have room and have an acceptably fast second drive you can do it on that one too.
- Reboot the computer for it to take affect and give it another whirl.
- I recommend that you have at least 50GB of space on the page file drive as it will dynamically size as you need it.

Now that that is fixed the game runs like a dream on the highest settings with my 7900XTX at 1080P. Still odd that the game itself only uses 50% of my physical RAM on the motherboard. I would think they would want to use as much of that as possible for its transfer speed alone. I think its more that current day game developers dont want to manage memory very well, its why consoles have so much RAM.

THANK YOU SO MUCH
I had steam on my second ssd which did not have page file allocated for some reason.
Unchecked auto page file management, added second ssd to the managing list, and put it back to auto manage. Works like a charm.

[Reaper Scythe]

Bumping this again for those who have not seen it.

I have also moved to the newest, "optional" driver for AMD 25.1.1. This suggestion above actually, also, fixed another game having the same issue, Diablo 4.