Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Reset the game if you used mods, as described in the section Troubleshooting: Reset Your Game
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
If the issue persists, share a DxDiag report
I take the screenshots as well for checking if you are willing to share them.
Hm... that is odd. The essentials with your PC is absolutely fine. And the last memory leak issue affected your Cyberpunk 2077 but not Monster Hunter Wilds.
There is some common error though, which might be related to VC++, but it is odd that you are having it now, if you wrote it works fine before.
Can you list the mods you have used?
Were there any system changing files among the "mods" ?
Please also confirm that you did tip #6 - check if the settings are correct as seen with tip #6 in the guide.
Then run for good measures these commands in terminal as administrator for a system checkup.
After that is done restart your PC and try again.
sfc /scannow
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /Online /Cleanup-image /AnalyzeComponentStore
DISM.exe /Online /Cleanup-image /StartComponentCleanup
chkdsk /f /r
watch especially with the first two commands, if the PC tells you that everything is either okay or something needs to be repaired - we need that information for later to determine the cause
If the issue persists after that, share a new DxDiag report and I check whether it is good to tackle to BEX64 error on your PC which appeared recently.
The mods I tried were
Wilds OPTIMIZER FPS BOOST LOW CPU CLEANER VISUALS AND BETTER STABILITY
Which is when the issue started if i remember correctly which involved changing the config file
REFramework
I doubt is the culprit since people say its harmless and in fact helps
Wilds Rehydrated - ReShade
I downloaded these in this order but the issue sprouted with he first since i opened the game to test these mods individually
The new DxDiag report https://pastebin.com/gExxjk4t
let me make another DxDiag report in case that doesnt help at all https://pastebin.com/4G10njYN
and some screenshots
https://steamcommunity.com/sharedfiles/filedetails/?id=3444472579
https://steamcommunity.com/sharedfiles/filedetails/?id=3444466979
It is harmless, if it would have been explained properly... that explains the weird errors, and fits your descriptions, though.
One thing about the mod description bothers me a lot. So I need you to share a screenshot of your game's folder's content for additional checking. Better would be a crash report, but unless you crash that does not get generated.
Because of the mod usage - I just downloaded the mod to check it - I need you also to use tip#1 in the guide, to address the driver issue which has occured.
Regarding your PC and your intentions, I recommend instead you using the tips from my guide, as most are based upon Windows and has nothing to do with turning the game bad looking. You might also notice explainations which you have not read before, despite they are important when using mods.
To sum it up
1. screenshot (and if available) crash report from your game's folder's content
2. #1 usage of DDU to address the graphics driver error
3. tip#2 + #4 + #7 + #8 + #19 + #20 (#3 is good too, but optional)
-- in general I recommend all tips from my guide (obviously), but those are specifically chosen to address your specific issues and intentions
4. use the installers you can find here, for the other issues which have been noticed by DISM and scandisk - https://www.nexusmods.com/helldivers2/mods/93
you can ignore the DLLs for now, but if you want to be on the safe side, you can also try them out by following the Troubleshooting: Replace DLLs section.
You just then need to redo the terminal commands if you do replace the DLLs.
5. Last but not least, once more, delete the shader cache file in your game's folder. That step is necessary to be done after all the changes made, because every time a change is made the shader cache becomes outdated.
Let me know how it works and good luck!
https://dochub.com/m/shared-document/lucas-freire-af4q8x/8adOrbPVQpxlOGYK24Mj7D/screenshot-2025-03-15-013257-png?dt=nAd2zbxMq2Ze4goH3Zi1
I cannot tell you for sure if those two methods will resolve it.
The DLLs replacement I have mentioned is also something else than DLSS replacement. Do not mix it up, please, as that would mess up things while troubleshooting.
REFramework in combination with the DirectStorage update can help significantly with the way how the game loads. Hence the high recommendation on that, alongside the warning that you must keep it up to date all the time or know when to remove it.
I like you to delete the config.ini file and once more the shader.cache2 file and try it again.
Start at launch the game textures to medium at max and check if the stutters still occur, before increasing it slowly.
If it still does not get better than before you used mods, then we need to take the DLL replacement into consideration. But it would be also good to share a fresh DxDiag report to check if the related issue has been mended or still appears.
Here is a DxDiag report before the DLL Replacement just in case.
https://pastebin.com/mb3vHZY7
Sounds not so bad - halfway solved.
For clarification: do you / did you have the high resolution texture pack installed?
Are you using the same settings as you did before the issue occured?
Framegen/upscaling automatically reduce some quality in favour of more FPS - did you try turning it off and check?
In theory, your game should be back in vanilla state now, after all the steps - better than vanilla state with the DirectStorage upgrade, and no effect to the graphics.
So I am baffled that even after all the shader resets it still did not get back how you used to have it.
I feel we are missing something, but I do not know what since we do not have the config.ini from before you tried the initial changes. We can therefore only guess at this point.
Your Nvidia app is not autooptimising the game either and overwritting your settings in doing so, correct?
I feel that this is a very rare issue or its something very strange it seems like its only with Monster Hunter too.
and i don't believe so cause when i open the NVIDIA app it says its not optimized and that i can.
here are some screen shots of the graphic settings im using Ill be doing the DLL replacement now.
https://steamcommunity.com/sharedfiles/filedetails/?id=3445302564
https://steamcommunity.com/sharedfiles/filedetails/?id=3445302527
https://steamcommunity.com/sharedfiles/filedetails/?id=3445302511
https://steamcommunity.com/sharedfiles/filedetails/?id=3445302485
https://steamcommunity.com/sharedfiles/filedetails/?id=3445302614
Here are some screenshots of the setting and ingame
I like to recommend to you trying with uninstalling the texture pack and try again without in max. high resolution without texture pack.
Make sure after uninstalling to delete the shader cache file again for best results.
Not sure if that is the culprit, but it would not be the first time for that pack to cause unexpected issues.
Plus: your settings indicate the texture pack will do more harm to your setup than it actually helps.
I also recommend to disable upscaling while testing for this issue.
Depth of Field and S4 Scattering I recommend to disable as well.
For the moment it is better to check how we can make it look good again, before fine tuning.
Maybe the DLSS replacement in tip #21 can be meaningful. But I would like to focus on that AFTER removing the high res. texture pack first.
If you need a pointer how to do that, you can check section Trivia: High Res Textures Requirements