Mhw complete pc Freeze

[Nox]

Just had it happen, blamed it on the techncial state, but figured I would ask here too.

Anyone else had this happen to them?
Mhw just completely freezes your pc, you will have frozen screen with the last frame of your gameplay, eventually its needed to Hard restart pc manually.

[Kiririn]

xenter님이 먼저 게시:

So tired of these "mUsT bE yOuR haRdWaRe" comments. The game literally runs ass, probably because it's ported from console and the developers haven't done enough optimization and compatibility fixes. Yet it's amazing that after the recent patch now, the game will restart my computer, and I can't remember the last time I played a game did that.

It's clear as day that this game has serious problems regardless of whether or not the defenders see that.

[Nox]

Even though this is just my assumption I'm just gonna post a tip, what was a hint for my freeze back then.

I haven't touched the game since, because I just don't wanna risk bricking my system, so I'll wait for a patch.

BUT - if this game normally runs smooth for you and during anytime you notice that every few minutes you get a serious fps drop for 0.5 - 1 second, I'd advise you to quit the game as those fps drops were then followed by a complete pc freeze.

And I seriously doubt it's a hdw issue. If this would be the only demanding game then I would think so, but for example I'm running KCD2 on Ultra and it's smooth as butter, so I think it's more of a Wilds issue.

[FabledGumbo]

do you have your RAM overclocked or have XMP/EXPO set in BIOS? If you do I'd try resetting your BIOS to default settings and see if it happens again.

[Kyderra]

NeoX님이 먼저 게시:

Kyderra님이 먼저 게시:

I
- Using REFramework for UltraWide support (will uninstall now to see if it helps)

Out of own experience, the last version of ReFramework is the issue. This time they did not adjust it properly. Former version did run perfectly:
https://www.youtube.com/watch?v=zdpA3aEEirA

I have come back from further testing, with every step, the game still crashed my whole PC into a freeze.

- Removed any mods
- Reinstalled the game and removed whole folder
- Switched Nvidia drivers to a more stable driver version (studio)
- Removed overclocking from CPU (that I have been running for years), reset my Bios
- Turned off Frame gen
- Turns games settings to high / medium
- Turned off Discord and any other app to save resources.

Ran multiple Benchmarks to see if I can reproduce the issue outside of monster hunter, I have yet to do so.

Issue thus far appears when fighting Arkvelt / Gore Magala.
Location It crashes in: Oilwell Basin, Ruins of Wyveria and Wounded Hollow
More Often seen to happen the moment the monster does a BIG shout that throws a big blur Shader on the screen, but it also randomly happens during the fight
Amount of crashing: About every Fight. sometimes twice or three times in the same fight.

Gameplay type: 2 player multiplayer hunts

Specs: RTX 3090 / 32GB Ram / Intel i7-12700K

Currently test is setting everything to max low, still waiting for the game to crash on those settings.

If anyone is experiencing the same issue's with these condition's, that would be helpfull.
My current assessment is that the game is broken for some hardware and it's not our fault or something we can solve.
I'll leave an update if any new tests change this conclusion.

[NeoX]

Kyderra님이 먼저 게시:

NeoX님이 먼저 게시:

Out of own experience, the last version of ReFramework is the issue. This time they did not adjust it properly. Former version did run perfectly:
https://www.youtube.com/watch?v=zdpA3aEEirA

I have come back from further testing, with every step, the game still crashed my whole PC into a freeze.

- Removed any mods
- Reinstalled the game and removed whole folder
- Switched Nvidia drivers to a more stable driver version (studio)
- Removed overclocking from CPU (that I have been running for years), reset my Bios
- Turned off Frame gen
- Turns games settings to high / medium
- Turned off Discord and any other app to save resources.

Ran multiple Benchmarks to see if reproduce the issue outside of monster hunter, I have yet to do so.

Issue thus far appears when fighting Arkvelt / Gore Magala.
Location It crashes in: Oilwell Basin, Ruins of Wyveria and Wounded Hollow
More Often seen to happen the moment the monster does a BIG shout that throws a big blur Shader on the screen, but it also randomly happens during the fight

Gameplay type: 2 player multiplayer hunts

Specs: RTX 3090 / 32GB Ram / Intel i7-12700K

Currently test is setting everything to max low, still waiting for the game to crash on those settings.

If anyone is experiencing the same issue's with these condition's, that would be helpfull.
My current assessment is that the game is broken for some hardware and it's not our fault or something we can solve.
I'll leave an update if any new tests change this conclusion.

A shot into the dark:

Are you using Playstation/Dualsense controllers? Even over blueooth?
There are reports that these cause crashes since the last update. Could this be the case on your end too?

[Kyderra]

NeoX님이 먼저 게시:

A shot into the dark:

Are you using Playstation/Dualsense controllers? Even over blueooth?
There are reports that these cause crashes since the last update. Could this be the case on your end too?

I am,
I noticed the comment About it and I will be the next thing I will be testing as well, thank you for the reminder.

[Kimi Kazenagi]

I also have the same problem as well, it's definitely the game issue and it freezes my PC, forcing me to hard power off and restart my PC. I had this happened to me 6 times. After reading all the comments the root cause is the recent MH Wilds update that caused this.

I played it after it was released and progressed the story until the final boss and the post-final boss content and the rest are fine without any freezing issues, but the recent patch made me not wanting to play Wilds often until they fix this.

[LePo]

didn't read what ppl said, but happened to me today, yesterday i started it for the 1st time, no problem, i played like 3-4 hours straight. Today, trying to launch alma's quests the game completely freezes after less than 5min, tried deleting the shaders, verify the game files, restarting the pc, update nvidia's driver, disable frame gen also. NOthing seems to work

[Cable Salad]

못타쿠우님이 먼저 게시:

me too, but it started happening after the last past patch, before none

Same here. Did anyone find a fix yet?

[Krystal]

Why do i get the feeling if i asked everyone in this thread to post their pc specs+all mods they're currently running that if everyone was 100% honest, i wouldn't see a single poster running this game either that wasn't with unspported mods or pc specs lower than min specs...

[Nickaholic]

Same things happening to me, before patch never had this issue. So many people quick to blame the user, It's definitely the game just being bad. I've never had a game that would make me have to restart my computer, even cyberpunk 2077, considered one of the most buggy launches of all time, would only crash the game. Hopefully someone smarter than I can figure out what's going on

[Frill]

Nox님이 먼저 게시:

Even though this is just my assumption I'm just gonna post a tip, what was a hint for my freeze back then.

I haven't touched the game since, because I just don't wanna risk bricking my system, so I'll wait for a patch.

BUT - if this game normally runs smooth for you and during anytime you notice that every few minutes you get a serious fps drop for 0.5 - 1 second, I'd advise you to quit the game as those fps drops were then followed by a complete pc freeze.

And I seriously doubt it's a hdw issue. If this would be the only demanding game then I would think so, but for example I'm running KCD2 on Ultra and it's smooth as butter, so I think it's more of a Wilds issue.

Same Issue

[Nox]

Krystal님이 먼저 게시:

Why do i get the feeling if i asked everyone in this thread to post their pc specs+all mods they're currently running that if everyone was 100% honest, i wouldn't see a single poster running this game either that wasn't with unspported mods or pc specs lower than min specs...

No mods, No OCs
RTX 4070 super
Ryzen 7 7800X3D
32GB DDR5 6000Mhz
SSD

Monster Hunter Wilds team absolutely crapped on optimization. There is no way in hell that a game looking this bad demands 4060 as reccomended for 1080p on medium with frame gen

[TurboTired]

I just wanted to chime in and say when I upgraded to the latest nvidia drivers (572.70), this also started happening. Game would just randomly completely lock up Windows 11 to the point where it wouldn't even be able to do a memory dump, even if I managed to alt + F4 the game before it completely froze. You could tell when it was starting to crash because stuff like the music would just stop playing.
I ran Display Driver Uninstaller and reinstalled the previous drivers (572.60) and it completely fixed it for me.
This is on a stock settings 4090 + 13600K system that is otherwise completely cool and stable (I've ran various stress tests, SSD tests, and memory tests and have all come back with flying colors).
The only other game that has ever hard locked my system like this was Ratchet & Clank Rift Apart, and I think it had something to do with DirectStorage, so this may be the case here as well since DirectStorage is linked with nvidia drivers.

[SquawkNoble]

completely removed all traces of mods, fully reinstalled the game fresh, but for the past 4-5 days the game has been fully freezing my entire pc. no ctrl+alt+del, no task manager, alt+f4, nothing. just need to hard shutdown every time.

read somewhere that increasing power limit in amd adrenalin could help. thought it did but freezes have been worse today than any other. also read something about changing some streamed asset vram allocation values in the config.ini file. doesn't seem to have helped or changed much of anything. not really sure what to do at this point but I see some of you mentioning dualsense controllers. I've been using a dualsense edge half the time and remoting from my steam deck the rest of the time, although the dualsense is always plugged in so I guess I'll try unplugging it to see if that helps lmao.