fatal d3d error ( 4, e_accessdenied, 0x80070005 )

[burger boy]

finally found out what that crash was that kept happening after the shader optimisation, around where it has the popup to check for save data.
-- thanks to the assistance of mods, because previously, it was just crashing in the exact same location, without showing the error type.

at least now i know what the crash type is called, but i've no clue how to fix it.

[Edward van Helgen]

Maybe this will help:

https://steamcommunity.com/app/2246340/discussions/0/596268022048580655

[burger boy]

sadly the ( -force-d3d11 ) fix didn't work for me.
-- thanks for trying though, guess i'll just have to wait for an patch.

[Azanimefan]

d3d is a graphic driver crash. imho turn off DLSS or FSR, those were the sources of my crashing when i was testing this game.

[burger boy]

Originally posted by Azanimefan:

d3d is a graphic driver crash. imho turn off DLSS or FSR, those were the sources of my crashing when i was testing this game.

is it possible to do that via the steam advanced launch options?
-- haven't managed to run the game long enough for any settings menus to appear.

[Azanimefan]

Originally posted by burger boy:

Originally posted by Azanimefan:

d3d is a graphic driver crash. imho turn off DLSS or FSR, those were the sources of my crashing when i was testing this game.

is it possible to do that via the steam advanced launch options?
-- haven't managed to run the game long enough for any settings menus to appear.

ooof. i never got that crash before getting in game.

yesterday i was testing the game a lot because of the issues i had and came to the conclusion that FSR/DLSS was just utterly breaking the game. but at least i could get to the menus...

worse, capcom turns both features on by default. so no, i don't know how to change those settings before startup.

[burger boy]

if nothing else, i did just find out something rather, interesting.
-- in an attempt to fix the game, i frankenstein'd the game's files an bit.

while ( monster hunter wilds ) refuses to work for me, ( monster hunter rise ) on the otherhand works near-flawlessly for me.
-- so, with that in mind, having both games setup to run the exact same way, under the exact same conditions, i grabbed the config file from ( monster hunter rise ), and replaced the config file for ( monster hunter wilds ) with an copy of it, then set that copy of the config file to read-only, so the game wouldn't overwrite it.

the result, at least for the portion of the game that does run for me ( the shader optimisation screen, and up till the " checking for save data " popup appears ) was significantly improved performance.
-- while i may not be able to run the game further, hopefully this finding helps out other players that the game does work for.

[burger boy]

\o/ found the cause of the crash \o/
-- thanks to the help of many, many players in the community.

the cause for the crashing error ( fatal d3d error ( 4, e_accessdenied, 0x80070005 ) ), at least on systems with an ( nvidia geforce rtx 4060 laptop gpu ) and an ( intel ( r ) core ( tm ) i9-14900hx 2.20 ghz ), is the steam overlay being enabled.
-- no clue what this game's issue is with the steam overly, but if the game attempts to launch with it active, it crashes immediately.

the overly from the ( nvidia geforce experience ) program however, is completely fine left active.
-- absolutely baffling, but, at least we've narrowed down an fix for it.

[Sinhud]

Originally posted by burger boy:

\o/ found the cause of the crash \o/
-- thanks to the help of many, many players in the community.

the cause for the crashing error ( fatal d3d error ( 4, e_accessdenied, 0x80070005 ) ), at least on systems with an ( nvidia geforce rtx 4060 laptop gpu ) and an ( intel ( r ) core ( tm ) i9-14900hx 2.20 ghz ), is the steam overlay being enabled.
-- no clue what this game's issue is with the steam overly, but if the game attempts to launch with it active, it crashes immediately.

the overly from the ( nvidia geforce experience ) program however, is completely fine left active.
-- absolutely baffling, but, at least we've narrowed down an fix for it.

So this is the same error I'm having, except turning off Steam overlay did NOT fix it and this was kind of my last hope

[Lumen]

Originally posted by burger boy:

-- no clue what this game's issue is with the steam overly, but if the game attempts to launch with it active, it crashes immediately.

Intresting. The Overlay works for most people. Can you change your destop settings of the screen you are launching from to something lower for testing? Size and refresh rate.

[burger boy]

Originally posted by Lumen:

Originally posted by burger boy:

-- no clue what this game's issue is with the steam overly, but if the game attempts to launch with it active, it crashes immediately.

Interesting. The Overlay works for most people. Can you change your desktop settings of the screen you are launching from to something lower for testing? Size and refresh rate.

as far as display size and refresh rate go, mine are ( 1366 x 768 ) for the resolution, and ( @59.9hrtz / @60hrtz ) for refresh rate.

as for monitor setup, it's the laptop display being copied over onto an tv as the main display.
-- as for my system's global frame rate, i've got that capped to 30fps for both active and background processes. ( via the nvidia control panel. ).

in case it helps, i'm also applying the steam advanced launch options ( -high -useallavailablecores -autoconfig -graphics-low -force-d3d9 ), without the brackets.
-- and using the ( intel graphics command centre ( beta ) ) program to further help the game run via making an profile for it with everything set to the lowest / off.
and further helping the game run via the ( nvidia geforce experience program ) to make the game utilise the latest dlss option.
-- i'm also using the " performance mode config file " from the steam guides list for this game. ( did what i could to help debug things for people. ).

if this has any impact to the outcome, i'm also using the last decent steam client version. ( from 31 / 05 / 2023, going by the version number ), and have the " steam input " set to fully disabled, since it messes with my custom controller buttonmapping.
-- though oddly, this game currently has absolutely no native controller support, as it doesn't recognise controller input without the " steam input " for whatever reason.

i've also got every version of ( directx ), ( .net ), and the ( visual c++ ) packages installed.

-- only other thing i can think to list as an potential variable for working around the crashing issue, would be the full list of system settings configurations, though that'd take awhile to dig through.

apologies for not being of more help,

[Lumen]

Access denied could mean a lot of things.
Have you disabled some system services the game could use?

[burger boy]

Originally posted by Lumen:

Access denied could mean a lot of things.
Have you disabled some system services the game could use?

the only 2 system services i've disabled, are that new annoying ( location services ) one that if active keeps shifting stuff around on the taskbar every time the icon appears.
-- and the ( automatic syncing ) on the date / time, since i use an custom time.

other than that, i can't remember explicitly setting much else to disabled.

[Foe]

Maybe you could give some more Info about your gpu driver Version and edit your top Post so other people could Profit from it.

I still can’t believe that it’s the overlays fault, it’s probably still something else.

[アンジェル]

Weird to see this thread reemerge.

Originally posted by Sinhud:

Originally posted by burger boy:

\o/ found the cause of the crash \o/
-- thanks to the help of many, many players in the community.

the cause for the crashing error ( fatal d3d error ( 4, e_accessdenied, 0x80070005 ) ), at least on systems with an ( nvidia geforce rtx 4060 laptop gpu ) and an ( intel ( r ) core ( tm ) i9-14900hx 2.20 ghz ), is the steam overlay being enabled.
-- no clue what this game's issue is with the steam overly, but if the game attempts to launch with it active, it crashes immediately.

the overly from the ( nvidia geforce experience ) program however, is completely fine left active.
-- absolutely baffling, but, at least we've narrowed down an fix for it.

So this is the same error I'm having, except turning off Steam overlay did NOT fix it and this was kind of my last hope

Share a screenshot of your startup apps from the task manager and the DxDiag report for advice

[Lumen]

You probably already found that guide on those kind of errors: https://www.minitool.com/news/monster-hunter-wilds-fatal-d3d-error.html
No clue what's going on with your system, however getting steam overlay to not crash would be my first priority as its such a standard function.
I would asume overclocking or some bad bios settings on cpu/ram are involved with it.