Found a D3D fatal error fix

[MAXR]

Go in your game folder and right click the game .exe , property and turn on windows 7 comptatibility mode , worked for me (at least for now)

[☣ Minoumimi ☣]

Before reinstalling
to save you time you could always clear out all caches and do verify

Steam\steamapps\shadercache → 1446780
Steam\steamapps\common\MonsterHunterRise → shader.cache/shader.cache2
Or
all out refresh D3D cache itself
But, Just in case
"MAKE A BACKUP"
AppData\Local\D3DSCache
Or
rarely but surely
clear Steam download cache

[adamweideman1]

Originally posted by ☣ Minoumimi ☣:

Before reinstalling
to save you time you could always clear out all caches and do verify

Steam\steamapps\shadercache → 1446780
Steam\steamapps\common\MonsterHunterRise → shader.cache/shader.cache2
Or
all out refresh D3D cache itself
But, Just in case
"MAKE A BACKUP"
AppData\Local\D3DSCache
Or
rarely but surely
clear Steam download cache

yeah couldnt tell you whats wrong, everything youve mentioned ive tried and no dice.
doesnt make sense my system is ryzen 5 3600, 1660 gpu, 32gb ram.

[☣ Minoumimi ☣]

then you most likely use xmp?
if so, have you tried playing with xmp disabled?
another person fixed his crash by disabling his ram xmp profile
so might be worth a shot unless you absolutely need the power
otherwise, rise itself sure does not need to be xmp boosted
though i am using xmp myself without issues
But,
i do not have an Asus MB
Which Has Way More Bios tweak options
which sadly also means far more potential instability issues if not tweaked perfectly
so if do have Asus might want to consider a default reset
and then reraise OC small amount at a time

But in the end..
until just a month ago,
i was still using a 2010 workstation with 2 quads and 8x2g rams sticks xD
and rise never crashed on me once
unless caused by mods
So.. if that thing was able to run it fine 😂
then we have to focus on registry/driver or oc unstabilities
And now,
that i am finally a decade more up to date
with a pretty similar setup to yours
ryzen 5800x 32g ram as well
i never had issues with this machine at all
though,
i am still stuck on a 60hz monitor and so i always cap fps
at 75 in games that gets no tearing
or
at 60 +vsync if they tear
so
i am reaaally "limiting" the power the game can use
Which
seemed to help a few people as well

which leads me to think it could be a bad port fault
basically by increasing the hardware limitations unproperly
causing leakage if left uncapped
like Tera Creation Menu that use to bum to 5000 fps...
i burned a 2 month old gtx460 in 5 minutes because of that..
ive always capped my fps ever since
Which could very well be why i never get issues at all
even back on my decade old machine

just like any engine
the more you push it near its limit
the higher the chance of failure becomes