My PC keeps crashing in multiplayer or longer sessions for no apparent reason. anyone else or can guide me to a sollution

[TheDutchman]

Since the start of the game my system and this game do not match well.
Its not the game instance crashing, but my entire PC. While singleplayer mostly works, whenever im in a multiplayer quest, the screen goes black, sound keeps playing in the background. my PC reboots itself but gives an error light on the motherboard for the GPU. upon resetting the PC and rebooting manually the GPU boots up again and works without issue.

ive downclocked the GPU (AMD RX6800XT) but thats not the issue. Ive had sessions of hours in singleplayer without any issues, no overheating, no excessive ram usage nothing.

but joining Multiplayer, even just with NPC's somehow shuts off my system. No other game has this, only Monster Hunter and its seriously sucking all the fun out of the game. Just starting it feels depressing because im afraid its just going to crash.

disabled second monitor, disabled screen overlays. Still crashes.
running all the latest drivers and Win10 updates. TDR delay is set to 60 seconds incase the issues was somewhere there. Also still crashes.

VRAM is maxing out at 12.5/16 GB at most. RAM saw at most 16/32 GB. CPU 5800X3D temps and load is normal. same for GPU. ran HWinfo to keep track of things, nothing seems out of the ordinary. the only thing i havent tried is turn off stuff like XMP and AMD Smart Memory. but its not the game crashing, but GPU simply stops working, and something reboots the PC because of that. and to cripple performance just for one game doesnt seem worth

cant find anything in Windows Event Log, theres no BSOD that is happening since BlueScreenView shows no logs.

[SweatersInSummer]

youre not alone, im having the same issues, but have yet to id the problem or find a solution

[xenter]

Since the first patch after release the game started restarting my stationary PC randomly after a few hunts. As I see it, either your game runs without issues like it does for half the player base, or it doesn't like it does for the other half.

By all means feel free to spend countless of hours memtesting, upgrading/downgrading drivers, disabling Bluetooth and Playstation controllers, or flashing your bios. I just don't think it's anyone's but Capcum's job to fix the optimization.

[アンジェル]

Originally posted by TheDutchman:

My PC keeps crashing in multiplayer or longer sessions for no apparent reason. anyone else or can guide me to a sollution
Since the start of the game my system and this game do not match well.
Its not the game instance crashing, but my entire PC. While singleplayer mostly works, whenever im in a multiplayer quest, the screen goes black, sound keeps playing in the background. my PC reboots itself but gives an error light on the motherboard for the GPU. upon resetting the PC and rebooting manually the GPU boots up again and works without issue.

ive downclocked the GPU (AMD RX6800XT) but thats not the issue. Ive had sessions of hours in singleplayer without any issues, no overheating, no excessive ram usage nothing.

but joining Multiplayer, even just with NPC's somehow shuts off my system. No other game has this, only Monster Hunter and its seriously sucking all the fun out of the game. Just starting it feels depressing because im afraid its just going to crash.

disabled second monitor, disabled screen overlays. Still crashes.
running all the latest drivers and Win10 updates. TDR delay is set to 60 seconds incase the issues was somewhere there. Also still crashes.

VRAM is maxing out at 12.5/16 GB at most. RAM saw at most 16/32 GB. CPU 5800X3D temps and load is normal. same for GPU. ran HWinfo to keep track of things, nothing seems out of the ordinary. the only thing i havent tried is turn off stuff like XMP and AMD Smart Memory. but its not the game crashing, but GPU simply stops working, and something reboots the PC because of that. and to cripple performance just for one game doesnt seem worth

cant find anything in Windows Event Log, theres no BSOD that is happening since BlueScreenView shows no logs.

Sounds like either a memory issue or network issue.