Monster Hunter Wilds

Monster Hunter Wilds

View Stats:
Keep crashing right before the title page
The game keep crashing right before the title page. Previously before the Apr update still able to play. But after the Apr update it keep crashing at the same spot. Anyone has similar issue and any solution?
< >
Showing 1-6 of 6 comments
Originally posted by kumachann30:
Keep crashing right before the title page
The game keep crashing right before the title page. Previously before the Apr update still able to play. But after the Apr update it keep crashing at the same spot. Anyone has similar issue and any solution?

Try this - the reset the game part after doing step 1
https://steamcommunity.com/sharedfiles/filedetails/?id=3454351115
There are at least 5 other topics exactly like this one on the first page of this community, maybe read what they say before posting another one, that will most likely have the same answers?
Originally posted by NekoShade:
There are at least 5 other topics exactly like this one on the first page of this community, maybe read what they say before posting another one, that will most likely have the same answers?

In fact, I do not recommend that. So many issues differ so much from each other, someone trying to mix fixes can end up in a mess.

I recommend each case with their own thread and their own DxDiag report and crash report to make it clear what it is about.

Alternatively that update routine can be found in the guides section which already covers the general troubleshooting step regarding "it worked before but not after an update"
Originally posted by アンジェル:
Originally posted by NekoShade:
There are at least 5 other topics exactly like this one on the first page of this community, maybe read what they say before posting another one, that will most likely have the same answers?

In fact, I do not recommend that. So many issues differ so much from each other, someone trying to mix fixes can end up in a mess.

I recommend each case with their own thread and their own DxDiag report and crash report to make it clear what it is about.

Alternatively that update routine can be found in the guides section which already covers the general troubleshooting step regarding "it worked before but not after an update"

Looking that way, I completely agree with you.
Guess I'm the oddball that looked for information alone until I found something that worked.
Or I have trauma of lazy bums that ask first and wait for their silver platers to be served.
Originally posted by NekoShade:
Originally posted by アンジェル:

In fact, I do not recommend that. So many issues differ so much from each other, someone trying to mix fixes can end up in a mess.

I recommend each case with their own thread and their own DxDiag report and crash report to make it clear what it is about.

Alternatively that update routine can be found in the guides section which already covers the general troubleshooting step regarding "it worked before but not after an update"

Looking that way, I completely agree with you.
Guess I'm the oddball that looked for information alone until I found something that worked.
Or I have trauma of lazy bums that ask first and wait for their silver platers to be served.

I can completely relate to that sort of trauma.

Like ~ okay, crash ~ but how would I know what caused it for this or that individual as I am not omniscient and do not know what kind of PC they are using or software they are running which could be the cause.

It could be as weird as this, after all: https://i.ibb.co/tRY7Fnc/screenshot-1745838036.png
Originally posted by アンジェル:

It could be as weird as this, after all: https://i.ibb.co/tRY7Fnc/screenshot-1745838036.png

Holy moly!
And that is a FX AM3 most likely, it's one of the processors that build up the "AMD runs hot" preconception people have nowadays.

About the topic at hand, hope I didn't scare away the op.
< >
Showing 1-6 of 6 comments
Per page: 1530 50