Originally posted by Sono:

So the game crashed like crazy in TU2, forcing me to stop playing. I came back with TU4 and it actually ran without any hitches for many gog runs, but after the patch that came out a bit ago today, I am crashing again. I tried clearing my shader cache, steam overlay is disabled, i have no mods on, no HD texture pack, AMD drivers is the Capcom recommended 25.9.2, and i run my CPU at the default clocking speed.

SPECS:
Windows 11 Pro
RX 6700 XT
32 DDR4 memory
Ryzen 5 5600
NVME SSD with latest firmware

Crash Report: https://pastebin.com/iQpMKKTZ

Dxdiag: https://pastebin.com/cchhPCGH

I am running the newest chipset drivers and BIOS for my board. I am completely out of ideas. Im losing hope of this game ever remaining functional for me.

Access Violation error.

Well eithwer its your mods causing it or some 3rd party stuff tries to inject itself into the game.

3rd party stuff:
disable all overlays (steam overlay, Discord Overlay, ...) and 3rd party rerenders like ReShade, Losslesscaler, ect...

Mods:
1. backup your savegame
2. uninstall the game
3. manualy delete the whole remaining game folder and everything in it
4. reinstall the game
5. change GPU driver version to:
– NVIDIA GeForce: 581.57 or newer
– AMD Radeon: 25.9.1 or newer

6. start the game

This is like the 3rd or 4th time the steam overlay has been nuked.

Originally posted by NiamhNyx:

This is like the 3rd or 4th time the steam overlay has been nuked.

Yepp, the question is, is it the game or the latest steam client update.

Originally posted by NeoX:

Originally posted by NiamhNyx:

This is like the 3rd or 4th time the steam overlay has been nuked.

Yepp, the question is, is it the game or the latest steam client update.

I think its the game this time since it happened after the patch like 3-4 hours ago.

Originally posted by NiamhNyx:

This is like the 3rd or 4th time the steam overlay has been nuked.

Are you guys running the beta versions of the Steam client?

I constantly use the Steam Overlay and I don't think I've ever had a single problem caused by it, or at least not one that I can pinpoint to it specifically.

Wilds on the other hand has had issues with upscaling, it's had issues with frame generation, it's had issues with overlays, it's had issues with direct storage, it's had issues with drivers, and more. It still has a whole bunch of these problems, as a matter of fact.

Originally posted by Kiririn:

Originally posted by NiamhNyx:

This is like the 3rd or 4th time the steam overlay has been nuked.

Are you guys running the beta versions of the Steam client?

I constantly use the Steam Overlay and I don't think I've ever had a single problem caused by it, or at least not one that I can pinpoint to it specifically.

Wilds on the other hand has had issues with upscaling, it's had issues with frame generation, it's had issues with overlays, it's had issues with direct storage, it's had issues with drivers, and more. It still has a whole bunch of these problems, as a matter of fact.

get off your ♥♥♥♥♥♥♥♥♥♥ burner and comment with your main account otherwise your input here for wilds and the steam overlay is going to be ignored.

Originally posted by NeoX:

Originally posted by Sono:

So the game crashed like crazy in TU2, forcing me to stop playing. I came back with TU4 and it actually ran without any hitches for many gog runs, but after the patch that came out a bit ago today, I am crashing again. I tried clearing my shader cache, steam overlay is disabled, i have no mods on, no HD texture pack, AMD drivers is the Capcom recommended 25.9.2, and i run my CPU at the default clocking speed.

SPECS:
Windows 11 Pro
RX 6700 XT
32 DDR4 memory
Ryzen 5 5600
NVME SSD with latest firmware

Crash Report: https://pastebin.com/iQpMKKTZ

Dxdiag: https://pastebin.com/cchhPCGH

I am running the newest chipset drivers and BIOS for my board. I am completely out of ideas. Im losing hope of this game ever remaining functional for me.

Access Violation error.

Well eithwer its your mods causing it or some 3rd party stuff tries to inject itself into the game.

3rd party stuff:
disable all overlays (steam overlay, Discord Overlay, ...) and 3rd party rerenders like ReShade, Losslesscaler, ect...

Mods:
1. backup your savegame
2. uninstall the game
3. manualy delete the whole remaining game folder and everything in it
4. reinstall the game
5. change GPU driver version to:
– NVIDIA GeForce: 581.57 or newer
– AMD Radeon: 25.9.1 or newer

6. start the game

-I have no mods installed.
-I also have all other overlays disabled. Discord, MS/xbox, AMD.
-I am running 25.9.2. That was listed as a valid driver in their new blog posts.
-I am not reinstalling the game, as i already fresh reinstalled the game after TU4 came out. I am not doing it again for this. I also reverified the files it didnt find anything wrong with the files.
-In case you didnt see it, I did in fact clear shader cache, both the games and the GPU cache in adrenalin for a full recompile.
-I have restarted the computer a couple times

Im sorry man it is the game this time. It only started fussing after this patch. If theres nothing I can configure or edit with the game itself I dont think this is fixable until capcom rescinds the patch or makes a new one.

Edit: no i am not running the beta client, i put myself on main branch a month ago after workshop issues.

Originally posted by NiamhNyx:

Originally posted by Kiririn:

Are you guys running the beta versions of the Steam client?

I constantly use the Steam Overlay and I don't think I've ever had a single problem caused by it, or at least not one that I can pinpoint to it specifically.

Wilds on the other hand has had issues with upscaling, it's had issues with frame generation, it's had issues with overlays, it's had issues with direct storage, it's had issues with drivers, and more. It still has a whole bunch of these problems, as a matter of fact.

get off your ♥♥♥♥♥♥♥♥♥♥ burner and comment with your main account otherwise your input here for wilds and the steam overlay is going to be ignored.

Who says this is my burner account?

Seriously, it's just rather strange. There was a single instance, from what I recall, of the beta branch of the Steam Client overlay causing an issue with Monster Hunter Wilds. Which is to be expected when you're running beta software. The stable branches of the Steam Client are another matter.

Originally posted by Sono:

Originally posted by NeoX:

Access Violation error.

Well eithwer its your mods causing it or some 3rd party stuff tries to inject itself into the game.

3rd party stuff:
disable all overlays (steam overlay, Discord Overlay, ...) and 3rd party rerenders like ReShade, Losslesscaler, ect...

Mods:
1. backup your savegame
2. uninstall the game
3. manualy delete the whole remaining game folder and everything in it
4. reinstall the game
5. change GPU driver version to:
– NVIDIA GeForce: 581.57 or newer
– AMD Radeon: 25.9.1 or newer

6. start the game

-I have no mods installed.
-I also have all other overlays disabled. Discord, MS/xbox, AMD.
-I am running 25.9.2. That was listed as a valid driver in their new blog posts.
-I am not reinstalling the game, as i already fresh reinstalled the game after TU4 came out. I am not doing it again for this. I also reverified the files it didnt find anything wrong with the files.
-In case you didnt see it, I did in fact clear shader cache, both the games and the GPU cache in adrenalin for a full recompile.
-I have restarted the computer a couple times

Im sorry man it is the game this time. It only started fussing after this patch. If theres nothing I can configure or edit with the game itself I dont think this is fixable until capcom rescinds the patch or makes a new one.

Edit: no i am not running the beta client, i put myself on main branch a month ago after workshop issues.

all other overlays, does that include steam as well, cause if you have not tried disabling it yet, do so.

Originally posted by Sono:

Originally posted by NeoX:

Access Violation error.

Well eithwer its your mods causing it or some 3rd party stuff tries to inject itself into the game.

3rd party stuff:
disable all overlays (steam overlay, Discord Overlay, ...) and 3rd party rerenders like ReShade, Losslesscaler, ect...

Mods:
1. backup your savegame
2. uninstall the game
3. manualy delete the whole remaining game folder and everything in it
4. reinstall the game
5. change GPU driver version to:
– NVIDIA GeForce: 581.57 or newer
– AMD Radeon: 25.9.1 or newer

6. start the game

-I have no mods installed.
-I also have all other overlays disabled. Discord, MS/xbox, AMD.
-I am running 25.9.2. That was listed as a valid driver in their new blog posts.
-I am not reinstalling the game, as i already fresh reinstalled the game after TU4 came out. I am not doing it again for this. I also reverified the files it didnt find anything wrong with the files.
-In case you didnt see it, I did in fact clear shader cache, both the games and the GPU cache in adrenalin for a full recompile.
-I have restarted the computer a couple times

Im sorry man it is the game this time. It only started fussing after this patch. If theres nothing I can configure or edit with the game itself I dont think this is fixable until capcom rescinds the patch or makes a new one.

Edit: no i am not running the beta client, i put myself on main branch a month ago after workshop issues.

And I'm assuming you have no overclocks?

Because the particular error that you are getting can be caused by crashes due to overclocking hardware. It's not guaranteed, but it's a possibility.

Originally posted by Kiririn:

And I'm assuming you have no overclocks?

Because the particular error that you are getting can be caused by crashes due to overclocking hardware. It's not guaranteed, but it's a possibility.

No. CPU is running all default settings, since i installed drivers, GPU settings are on "default" profile settings no tweaks at all. The only thing is my memory is running an XMP profile but its the profile for the speeds theyre specified for on the box. I actually thought NOT having this on was causing me crashing way back when, when someone told me to enable it, it had no effect one way or the other on whether it crashed or not.

Originally posted by Sono:

Originally posted by Kiririn:

And I'm assuming you have no overclocks?

Because the particular error that you are getting can be caused by crashes due to overclocking hardware. It's not guaranteed, but it's a possibility.

No. CPU is running all default settings, since i installed drivers, GPU settings are on "default" profile settings no tweaks at all. The only thing is my memory is running an XMP profile but its the profile for the speeds theyre specified for on the box. I actually thought NOT having this on was causing me crashing way back when, when someone told me to enable it, it had no effect one way or the other on whether it crashed or not.

Yeah, it was just a question because I've gotten that exact error, not in Wilds, but in other games when I've done things such as be a little overzealous on my GPU overclock.

As far as your XMP profile is concerned, my advice would be that you shouldn't have to turn it off, but, if you are at least a little bit curious and don't mind potentially wasting a bunch of time, you could try turning it off and seeing if it has any effect. Sometimes, poorly coded software or edge cases can cause an otherwise stable-appearing XMP profile to become unstable.

I've seen cases where RAM was actually unstable at XMP settings. It's not incredibly common, but it does happen. This is why I always, every time I buy RAM or install RAM or change any RAM settings, I verify with memtest86+. And I do around 4 passes. It takes several hours.

Once again, these are general tips for computer stability and probably not needed in your case if everything else is working fine, but throwing it out there anyway.

Originally posted by Kiririn:

Yeah, it was just a question because I've gotten that exact error, not in Wilds, but in other games when I've done things such as be a little overzealous on my GPU overclock.

As far as your XMP profile is concerned, my advice would be that you shouldn't have to turn it off, but, if you are at least a little bit curious and don't mind potentially wasting a bunch of time, you could try turning it off and seeing if it has any effect. Sometimes, poorly coded software or edge cases can cause an otherwise stable-appearing XMP profile to become unstable.

I've seen cases where RAM was actually unstable at XMP settings. It's not incredibly common, but it does happen. This is why I always, every time I buy RAM or install RAM or change any RAM settings, I verify with memtest86+. And I do around 4 passes. It takes several hours.

Once again, these are general tips for computer stability and probably not needed in your case if everything else is working fine, but throwing it out there anyway.

Ill try it next time im on but im not exactly hopeful itll make a difference. I did run a memtest before and didnt find anything. Unless my ram went bad the moment this update hit, which would be quite a coincidence.

Originally posted by Sono:

Originally posted by Kiririn:

Yeah, it was just a question because I've gotten that exact error, not in Wilds, but in other games when I've done things such as be a little overzealous on my GPU overclock.

As far as your XMP profile is concerned, my advice would be that you shouldn't have to turn it off, but, if you are at least a little bit curious and don't mind potentially wasting a bunch of time, you could try turning it off and seeing if it has any effect. Sometimes, poorly coded software or edge cases can cause an otherwise stable-appearing XMP profile to become unstable.

I've seen cases where RAM was actually unstable at XMP settings. It's not incredibly common, but it does happen. This is why I always, every time I buy RAM or install RAM or change any RAM settings, I verify with memtest86+. And I do around 4 passes. It takes several hours.

Once again, these are general tips for computer stability and probably not needed in your case if everything else is working fine, but throwing it out there anyway.

Ill try it next time im on but im not exactly hopeful itll make a difference. I did run a memtest before and didnt find anything. Unless my ram went bad the moment this update hit, which would be quite a coincidence.

If you've thoroughly stress tested and verified your XMP overclock and you have no other symptoms, then it's probably not worth even bothering because RAM doesn't go bad all that often.
And when it does bad out of the blue, you'll almost certainly see symptoms system wide.

Originally posted by Sono:

Originally posted by NeoX:

Access Violation error.

Well eithwer its your mods causing it or some 3rd party stuff tries to inject itself into the game.

3rd party stuff:
disable all overlays (steam overlay, Discord Overlay, ...) and 3rd party rerenders like ReShade, Losslesscaler, ect...

Mods:
1. backup your savegame
2. uninstall the game
3. manualy delete the whole remaining game folder and everything in it
4. reinstall the game
5. change GPU driver version to:
– NVIDIA GeForce: 581.57 or newer
– AMD Radeon: 25.9.1 or newer

6. start the game

-I have no mods installed.
-I also have all other overlays disabled. Discord, MS/xbox, AMD.
-I am running 25.9.2. That was listed as a valid driver in their new blog posts.
-I am not reinstalling the game, as i already fresh reinstalled the game after TU4 came out. I am not doing it again for this. I also reverified the files it didnt find anything wrong with the files.
-In case you didnt see it, I did in fact clear shader cache, both the games and the GPU cache in adrenalin for a full recompile.
-I have restarted the computer a couple times

Im sorry man it is the game this time. It only started fussing after this patch. If theres nothing I can configure or edit with the game itself I dont think this is fixable until capcom rescinds the patch or makes a new one.

Edit: no i am not running the beta client, i put myself on main branch a month ago after workshop issues.

please see below:

Originally posted by NiamhNyx:

Originally posted by Sono:

-I have no mods installed.
-I also have all other overlays disabled. Discord, MS/xbox, AMD.
-I am running 25.9.2. That was listed as a valid driver in their new blog posts.
-I am not reinstalling the game, as i already fresh reinstalled the game after TU4 came out. I am not doing it again for this. I also reverified the files it didnt find anything wrong with the files.
-In case you didnt see it, I did in fact clear shader cache, both the games and the GPU cache in adrenalin for a full recompile.
-I have restarted the computer a couple times

Im sorry man it is the game this time. It only started fussing after this patch. If theres nothing I can configure or edit with the game itself I dont think this is fixable until capcom rescinds the patch or makes a new one.

Edit: no i am not running the beta client, i put myself on main branch a month ago after workshop issues.

all other overlays, does that include steam as well, cause if you have not tried disabling it yet, do so.

Steam-Overlay seems to be the source of the issue here.