Crash on startup: Fatal D3D error (40, DXGI ERROR_ACCESS_DENIED, 0x887a002b)

[Sykanic]

Had some problems earlier today with the game crashing immediately on startup. Tweaked some settings, but it's still crashing, only now I get the following error message (when beforehand I received nothing):

"RE ENGINE - Aborted
C:\ProgramFiles(x86)\Steam\steamapps\common\MonsterHunterWilds\MonsterHunterWilds.exe

Fatal D3D error (40, DXGI ERROR_ACCESS_DENIED, 0x887a002b)"

It may be worth noting that the game goes through the entire "optimizing game data" loading screen before any crash happens. In addition, the title sequence seems to run just fine as long as MHWilds isn't the window in focus; once I alt-tab to it, it crashes instantly.

Yes, I have already tried disabling all mods, I've entered "-dx11" and "-force-d3d11" in the launch options, I've made sure that my graphics drivers are up to date, I've disabled overlays like discord, steam, etc. (which I saw was a possible solution in some other discussion, for reasons unbeknownst to me), I've uninstalled/reinstalled & I've restarted my PC. I'm completely clueless as to what to do next.

I've heard some others claiming that this may be a GPU issue, so I will say that I have an RTX 4060 TI, for clarity's sake.

[The_Cenetaurus]

I have been having the same issue since launch. Though i can't even get past the black screen that starts up after you press play in steam.

[Inanegrain62]

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

[Inanegrain62]

dont use up to date drivers

[アンジェル]

Originally posted by Inanegrain62:

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

Originally posted by Inanegrain62:

dont use up to date drivers

Why do you think it has something to do with the drivers?

They most likely overplayed it.

[Inanegrain62]

Originally posted by アンジェル:

Originally posted by Inanegrain62:

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

Originally posted by Inanegrain62:

dont use up to date drivers

Why do you think it has something to do with the drivers?

They most likely overplayed it.

simple, i see "my graphics drivers are up to date" and then I look in the previous posts and it all has the issue of "new drivers suck"

you ask me, drivers have been iffy to the point it took them a long while to fix google chrome/discord appearing weirdly which made me worried till i learned on nvidia forums it was an ongoing issue till i downgraded to 560.94, maybe it was 94, i forgot.

it is completely reasonable to assume new drivers = suck to the point you'd have to get a beta driver from nvidia/forums and it may or may not work.

even amd has this issue, except i now have an issue with amd's drivers effectively disabling bios/safemode cause my monitor's too old for it and it is unable to detect my monitor just for safemode/bios, overly niche, but a quick monitor swap lets me have access at the cost of needing to borrow a monitor again whenever I wanna update drivers or do DDU twice as I still have bios/safemode once the drivers are uninstalled.

[Sykanic]

Originally posted by Inanegrain62:

Originally posted by アンジェル:

Why do you think it has something to do with the drivers?

They most likely overplayed it.

simple, i see "my graphics drivers are up to date" and then I look in the previous posts and it all has the issue of "new drivers suck"

you ask me, drivers have been iffy to the point it took them a long while to fix google chrome/discord appearing weirdly which made me worried till i learned on nvidia forums it was an ongoing issue till i downgraded to 560.94, maybe it was 94, i forgot.

it is completely reasonable to assume new drivers = suck to the point you'd have to get a beta driver from nvidia/forums and it may or may not work.

even amd has this issue, except i now have an issue with amd's drivers effectively disabling bios/safemode cause my monitor's too old for it and it is unable to detect my monitor just for safemode/bios, overly niche, but a quick monitor swap lets me have access at the cost of needing to borrow a monitor again whenever I wanna update drivers or do DDU twice as I still have bios/safemode once the drivers are uninstalled.

Maybe it's a driver issue... except I have my doubts. I left out a detail, which is my fault. The crashing began happening before I updated my drivers; I then updated my drivers in hopes of that being the problem, but doing so didn't change anything, I'm still crashing.

[Sykanic]

Originally posted by アンジェル:

Originally posted by Inanegrain62:

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

Originally posted by Inanegrain62:

dont use up to date drivers

Why do you think it has something to do with the drivers?

They most likely overplayed it.

I've seen you on some other threads and you seem much more knowledgeable about things of this nature than I am. Would you mind looking at a crash report and a DxDiag report, and if so, am I to simply paste the .txt contents right here into this discussion?

[アンジェル]

Originally posted by Sykanic:

Originally posted by アンジェル:

Why do you think it has something to do with the drivers?

They most likely overplayed it.

I've seen you on some other threads and you seem much more knowledgeable about things of this nature than I am. Would you mind looking at a crash report and a DxDiag report, and if so, am I to simply paste the .txt contents right here into this discussion?

I can. Though it might be simpler than that.

You wrote before

Fatal D3D error (40, DXGI ERROR_ACCESS_DENIED, 0x887a002b)"

That indicates that the issue is not because of your GPU drivers, nor the game.

That line says some other app is taking control over the GPU rendering and does not allow the game to work.

So the prime suspect would be an overlay like Overwolf, overplayed, discord, medal.tv, MSI Afterburner and such.

If you exit all background apps which are like that, you should not have that problem anymore.

And if you use Overwolf, you might want to check their website for updates. I read that they have a beta out which addresses the issue - until that is deployed properly I recommend to shut down that app and any other background app which might fit the bill.