Possible fix for those experiencing the Fatal D3D error (24) and (25) crash.

[Josh313]

So I was tearing my hair out this past week since I couldn't go for more than at least 3 hunts before I'd get the random D3D crash out of nowhere in a hunt, tried adding the folders to my antivirus, setting maximum performance, disabling overclocks, stopping rivatuner, etc.

For whatever reason what seems to have fixed it for me was setting my resolution scale to 100% from 150%, turning off High-Resolution Textures, and setting shadow quality to average. Been playing for over 5 hours straight and been through about 25+ hunts and no crashes, hope this helps anyone experiencing this frustrating issue.

[アンジェル]

What is rivatuner?

[Josh313]

引用自 アンジェル：

What is rivatuner?

Rivatuner is a program typically installed alongside MSI Afterburner for overclocking your GPU. With Rivatuner you can use it to see CPU and GPU utilization, framerate, temperatures, etc. in game with a little HUD in a corner of your screen.

Sometimes having Rivatuner display that information in games can cause issues so it has to be disabled, although it doesn't seem to be an issue in MH:Rise since disabling it didn't fix the D3D error, lowering settings that lowered VRAM usage seemed to do the trick.

[アンジェル]

Oh! That is some very helpful information! Thank you so much for explaining it to me the way you did! That was easy to understand for me.

Also, I think you are right with your solution. It seems to be a lot VRAM related with many cases.

[Josh313]

You're welcome, and yea I'm wondering if there's a memory leak or something because even when I'm not close to the VRAM limit I'd keep crashing until I lowered those settings, haven't crashed since thankfully.

[アンジェル]

引用自 Josh313：

You're welcome, and yea I'm wondering if there's a memory leak or something because even when I'm not close to the VRAM limit I'd keep crashing until I lowered those settings, haven't crashed since thankfully.

I am too inexperienced about that "memory leak" of thing. But I know there are some optimisation profiles the game is using. Slight derivations from it cause the rest of the game to be troubled like a chain reaction.

[Leondre]

The problem is that it's hard to test. I can go 12 hrs straight without a single crash, or crash several times within an hour.

I've made many of the suggested changes I've seen, played a few hours without any issues thinking it's been solved, then the next day start crashing again.

I'll give this suggestion a shot but honestly not expecting anything different to happen.

For reference: 10850k, 32gb ram (set to garbage timings and frequency to rule out memory issues, then memtested for days), 1080ti, nothing oc'd.

[Josh313]

引用自 Leondre：

The problem is that it's hard to test. I can go 12 hrs straight without a single crash, or crash several times within an hour.

I've made many of the suggested changes I've seen, played a few hours without any issues thinking it's been solved, then the next day start crashing again.

I'll give this suggestion a shot but honestly not expecting anything different to happen.

For reference: 10850k, 32gb ram (set to garbage timings and frequency to rule out memory issues, then memtested for days), 1080ti, nothing oc'd.

I agree it's hard to test, but I literally tried all the other fixes I've seen and guessed what might be causing the issues, I'd literally get the D3D crash anywhere from 1-5 hunts in, it would happen anywhere from the first 10 minutes to an hour in.

Saw someone suggest turning off high-res textures which seemed to prolong the crash so I also turned down some settings that use up VRAM (resolution scale and shadows) and sunk 15+ hours in over the past few days with no crashes so I'm pretty happy but disappointed I can't run the game at max even though my system is more than capable of doing so.

It's the only thing that's worked for me and I hope that other people try it as well that have the same issue and can report back to say whether it worked for them or not.

My PC: Ryzen 3800X, GTX 980ti, 48gb RAM with nothing OC'd.