new install: crash when compiling shaders

[Storybook Villain]

Fresh install, just bought the game last night to add to my 15+ year career as a monster hunter. devastatingly, unable to even launch the game, crashes immediately upon trying to compile shaders.
Rly hoping someone is able to help :)

Troubleshooting steps done:
As mentioned in this post:
- Clean reinstalled graphics drivers as per instructions in this guide
- also from the guide: virtual memory, maximum power & memory leak
- as posted in the above thread, ran these commands through terminal
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
No change :(

Reports/diagnostics:
DxDiag[we.tl]
Crash report[we.tl]

Ryzen 5 2600X
4x 16GB 3200 RAM
Radeon VII

[アンジェル]

Originally posted by Storybook Villain:

new install: crash when compiling shaders
Fresh install, just bought the game last night to add to my 15+ year career as a monster hunter. devastatingly, unable to even launch the game, crashes immediately upon trying to compile shaders.
Rly hoping someone is able to help :)

Troubleshooting steps done:
As mentioned in this post:
- Clean reinstalled graphics drivers as per instructions in this guide
- also from the guide: virtual memory, maximum power & memory leak
- as posted in the above thread, ran these commands through terminal
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
No change :(

Reports/diagnostics:
DxDiag[we.tl]
Crash report[we.tl]

Ryzen 5 2600X
4x 16GB 3200 RAM
Radeon VII

Share a screenshot of your virtual memory settings. There is something amiss according to your DxDiag report.

[AmaiAmai]

GPU not supported

[アンジェル]

Going to bed now: long story short - your C: drive is full

Do tip #2 from here
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
only for D: drive

Move everything you can from C: to D: / E:

reinstall your GPU drivers as described in tip#1

Try again - better: get a new C: drive - all your storage is too low

[Storybook Villain]

Originally posted by アンジェル:

Going to bed now: long story short - your C: drive is full

Do tip #2 from here
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
only for D: drive

Move everything you can from C: to D: / E:

reinstall your GPU drivers as described in tip#1

Try again - better: get a new C: drive - all your storage is too low

ah...of course.....i will just eat the cost of a new ssd tomorrow and reinstall windows i think and update if that has solved it. thank you for your help!!!

[アンジェル]

Originally posted by Storybook Villain:

Originally posted by アンジェル:

Going to bed now: long story short - your C: drive is full

Do tip #2 from here
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
only for D: drive

Move everything you can from C: to D: / E:

reinstall your GPU drivers as described in tip#1

Try again - better: get a new C: drive - all your storage is too low

ah...of course.....i will just eat the cost of a new ssd tomorrow and reinstall windows i think and update if that has solved it. thank you for your help!!!

After you switched to a 1TB or 2 TB C: NVMe drive, and using all the tips in the guide, you should not have ever the problem again. If it comes again, share a new DxDiag report. Good luck!

[AmaiAmai]

Originally posted by Storybook Villain:

Originally posted by アンジェル:

Going to bed now: long story short - your C: drive is full

Do tip #2 from here
https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664
only for D: drive

Move everything you can from C: to D: / E:

reinstall your GPU drivers as described in tip#1

Try again - better: get a new C: drive - all your storage is too low

ah...of course.....i will just eat the cost of a new ssd tomorrow and reinstall windows i think and update if that has solved it. thank you for your help!!!

Your GPU really is NOT supported, and shaders crashing have little to do with your storage.

[アンジェル]

Originally posted by AmaiAmai:

Originally posted by Storybook Villain:

ah...of course.....i will just eat the cost of a new ssd tomorrow and reinstall windows i think and update if that has solved it. thank you for your help!!!

Your GPU really is NOT supported, and shaders crashing have little to do with your storage.

I am not convinced by your claim.
Could you share your source/ reference please?

[AmaiAmai]

Originally posted by アンジェル:

Originally posted by AmaiAmai:

Your GPU really is NOT supported, and shaders crashing have little to do with your storage.

I am not convinced by your claim.
Could you share your source/ reference please?

It's quite simple: the GPU has an older shader model than what's required to run the game. It's not magic, it's not supported based on the fact that the GPU doesn't support the shader model required by the game.

Now, maybe they can get it to work but that doesn't change the fact that the GPU being unsupported means that it can stop working at any point and the devs won't help.

Maybe they can also get it to work with DXVK or in Linux, but again, it's still not a supported GPU.

[アンジェル]

Originally posted by AmaiAmai:

Originally posted by アンジェル:

I am not convinced by your claim.
Could you share your source/ reference please?

It's quite simple: the GPU has an older shader model than what's required to run the game. It's not magic, it's not supported based on the fact that the GPU doesn't support the shader model required by the game.

Now, maybe they can get it to work but that doesn't change the fact that the GPU being unsupported means that it can stop working at any point and the devs won't help.

Maybe they can also get it to work with DXVK or in Linux, but again, it's still not a supported GPU.

Well, for me it is confusing, as a quick checkup via search engine gave out several tests results of people testing that GPU with Monster Hunter Wilds. So I am taking those as orientation.

And the GPU, from what I have seen, should be strong enough for the game as well.

[Storybook Villain]

Originally posted by アンジェル:

After you switched to a 1TB or 2 TB C: NVMe drive, and using all the tips in the guide, you should not have ever the problem again. If it comes again, share a new DxDiag report. Good luck! :MHRISE_OK:

- I installed a new HDD and migrated my C: drive to a 1TB SSD as well (including the MHW install)
- at first I still had the instant crash, then I tried launching the game .exe directly as admin and it gave me several missing .DLL errors that turned out to be from missing Visual C++ files. I reinstalled C++ and for a moment thought the issue had been fixed - finally the game didn't crash instantly!!!
- unfortunately after about 1-2 minutes of "compiling shaders" loading, I experienced another crash. :( I've uploaded the dxdiag and crash report here, perhaps you could take a look and see if you can see anything out of the ordinary again? https://we.tl/t-39oZ1Hjwhd

[アンジェル]

Originally posted by Storybook Villain:

Originally posted by アンジェル:

After you switched to a 1TB or 2 TB C: NVMe drive, and using all the tips in the guide, you should not have ever the problem again. If it comes again, share a new DxDiag report. Good luck!

- I installed a new HDD and migrated my C: drive to a 1TB SSD as well (including the MHW install)
- at first I still had the instant crash, then I tried launching the game .exe directly as admin and it gave me several missing .DLL errors that turned out to be from missing Visual C++ files. I reinstalled C++ and for a moment thought the issue had been fixed - finally the game didn't crash instantly!!!
- unfortunately after about 1-2 minutes of "compiling shaders" loading, I experienced another crash. :( I've uploaded the dxdiag and crash report here, perhaps you could take a look and see if you can see anything out of the ordinary again? https://we.tl/t-39oZ1Hjwhd

I am about to head out for treatment, so I do not have much time. But I intend to see you through it, so I bookmarked this thread.

As adhoc approaches:

- check your virtual memory settings, make sure it uses only C: drive and there is no automanangement for any other drive

- your DxDiag report is showing me you did everything correctly regarding the C++ issue

- for reasons I cannot tell yet, your AMD drivers are acting up: I recommend you do tip#1 from the guide and reinstall the graphics drivers from the scratch using DDU

I still cannot imagine that the graphics card is unsupported, as I have checked before and there were test reports with MHW using that card, but we shall look into it if the issue persists after you used DDU and reinstalled your graphics card driver from scratch.

Important: make sure to delete the shader.cache2 file in your game's directory, as that file is unusable for now.

Will check on this again later. Until then I wish you good luck!

[Storybook Villain]

Originally posted by アンジェル:

hello and thanks again for taking the time to help me out. sorry for the slow replies, i do not often have time to mess around with the pc on work days.

have reinstalled the graphics driver after uninstalling with DDU. i am not sure what the error is about because I haven't had any glitches or issues with performance in any other games or programs.

i did have the old system SSD set up for virtual memory which i have now changed, it is just using the C: drive now.

here is the crash log, including DxDiag, as well as a screenshot of where the progress bar is at when it crashes (consistently, and after the monitor flashes black for a second, my second monitor is unaffected) https://we.tl/t-pCL9eazB9W
-> interestingly when i run the .exe directly as admin...it crashes immediately again before it has even loaded the progress screen. so perhaps the screenshot is not actually useful argh!!!

shader.cache2 file has not been created during any of my launches so far. I also tried validating the game files and nothing changed

i agree with you, it doesn't make any logical sense that my GPU should be the problem here. my friend is running the game on her laptop with a 2070 which has similar specs to the VII so i don't really see why it would be the cause of failure (with the exception of the driver acting up mystery)

anyway thank you again for your persistence, i really appreciate it!! let's hope we can sort this out eventually :)

[アンジェル]

Originally posted by Storybook Villain:

Originally posted by アンジェル:

hello and thanks again for taking the time to help me out. sorry for the slow replies, i do not often have time to mess around with the pc on work days.

have reinstalled the graphics driver after uninstalling with DDU. i am not sure what the error is about because I haven't had any glitches or issues with performance in any other games or programs.

i did have the old system SSD set up for virtual memory which i have now changed, it is just using the C: drive now.

here is the crash log, including DxDiag, as well as a screenshot of where the progress bar is at when it crashes (consistently, and after the monitor flashes black for a second, my second monitor is unaffected) https://we.tl/t-pCL9eazB9W
-> interestingly when i run the .exe directly as admin...it crashes immediately again before it has even loaded the progress screen. so perhaps the screenshot is not actually useful argh!!!

shader.cache2 file has not been created during any of my launches so far. I also tried validating the game files and nothing changed

i agree with you, it doesn't make any logical sense that my GPU should be the problem here. my friend is running the game on her laptop with a 2070 which has similar specs to the VII so i don't really see why it would be the cause of failure (with the exception of the driver acting up mystery)

anyway thank you again for your persistence, i really appreciate it!! let's hope we can sort this out eventually :)

I am always hoping not reading from you for a while means that you already found a solution. A few days earlier I stumbled upon across these information pieces
https://www.reddit.com/r/MonsterHunter/comments/1j0jdea/fix_to_play_monster_hunter_wilds_on_older_gpus_rx/
https://www.reddit.com/r/MonsterHunter/comments/1inzjbm/just_a_heads_up_for_amd_gpu_users_regarding_wilds/?tl=de
In short:
- AMD driver 25.2.1 can help
- compatibility mode
- preset config.ini file settings
- one approach is even to disable the crash reporter by e.g. replacing it with an empty file of the same name

At this point I am also thinking it might be worth to consult [e-mail] via email for any pointers, if there is a known issue regarding the card, despite it seemingly fulfills the requirements.

Again, I am baffled and I do remember AmaiAmai's remark. But then it confuses me even more that there are seemingly test results for the graphics card to be found showing benchmarking for the game to begin with.

[Storybook Villain]

ah i actually found the same reddit threads!! using compatibility mode i DID manage to get the shaders to finish compiling. however then the game crashes instantly if i run it without compat mode. playing in compatability mode is not possible because of the severe texture glitching (here is a video, not mine, for reference of the glitching which can trigger my chronic migraine https://x.com/PixelCNinja/status/1896234324892201343)

the optional update is sadly not supported for radeon vii, so i am guessing that the only option for me now is to wait and hope that capcom implement a fix from their end as i cannot upgrade adrenaline to 25.2.1.
otherwise i guess i begin saving up for a supported GPU even though mine OUGHT to be able to run it.

it looks like this is the same problem other older AMD GPU users are having so perhaps in future someone will mod a fix if capcom does not.
according to other older GPU users the game WAS able to run in beta but since launch, shader instructions have changed and hence all these older cards are now crashing. i'm guessing this was probably the case with the viis you saw running the game.

still i appreciate your patience and support with trying to look into this :) i guess for now i will stop trying and just cross my fingers that capcom will kindly patch whatever the shader problem is

edit to add: according to one of the threads you linked the same problem was present at launch for dragon's dogma 2 - capcom eventually patched it 3 months later lol i guess that is what i get for playing with an old card!!

[アンジェル]

Originally posted by Storybook Villain:

ah i actually found the same reddit threads!! using compatibility mode i DID manage to get the shaders to finish compiling. however then the game crashes instantly if i run it without compat mode. playing in compatability mode is not possible because of the severe texture glitching (here is a video, not mine, for reference of the glitching which can trigger my chronic migraine https://x.com/PixelCNinja/status/1896234324892201343)

the optional update is sadly not supported for radeon vii, so i am guessing that the only option for me now is to wait and hope that capcom implement a fix from their end as i cannot upgrade adrenaline to 25.2.1.
otherwise i guess i begin saving up for a supported GPU even though mine OUGHT to be able to run it.

it looks like this is the same problem other older AMD GPU users are having so perhaps in future someone will mod a fix if capcom does not.
according to other older GPU users the game WAS able to run in beta but since launch, shader instructions have changed and hence all these older cards are now crashing. i'm guessing this was probably the case with the viis you saw running the game.

still i appreciate your patience and support with trying to look into this :) i guess for now i will stop trying and just cross my fingers that capcom will kindly patch whatever the shader problem is

Last question: do you have Resizable BAR / CAM / SAM in BIOS activated? Does the issue with the glitching texture still occurs when it is enabled?