Game not launching anymore

[NICO]

Last time I played the game was on July 31, and tried starting it up again yesterday but it wasnt working. I tried all day yesterday to fix it, such as:

Disabling Antivirus
Exclusion with Firewall
Verifying game files
Reinstalling steam
Reinstalling the game
Deleting files/Verifying the game again
Updated Windows
Updated graphics card

Literally so many things ive sort of lost track

I'm just dont know what to do at this point and i wonder if its a issue with the game itself since it was working fine days ago but now isnt. I havent added anything or done anything with my pc since then either. Hope they can fix it or if there's any solutions I havent tried yet id be willing to.

[Zonatailurus]

this is taking forever...

[jkteddy77]

Not sure if these instructions were posted earlier in the thread, but Capcom sent this to me on the 3rd support update. This is how you can provide the devs with the log of what's happening on your machine- and we can view it ourselves too:

●How to output a dump file
Please refer to the following steps for editing settings so that a dump file can be output. When a "Dump" folder will be created, please share it with us.
*Please let us know if the folder will not be created after following the steps below.

＜Steps to edit in a config. ini file ＞

Edit "DumpType=NONE" to "DumpType=MINI" in a config.ini file.
【A path for a config.ini file】
C:Program Files (x86)\\Steam\\steamapps\\common\\Monster Hunter World
*The above path is a default installation path.

Play the game until you encounter the issue you reported. Once you've encountered the issue, please quit and close the game.
Once a "Dump" folder has been created in the installation folder, please make a backup of it and then upload it to the site described in the later part.
Note: A dump file will be output when the crash occurs after editing the config.ini file in step 1.


I believe they just want you to attach the dump file to your open support ticket, the wording seems to be pulled from a troubleshooting guide of theirs.

[NineTailedCoven]

Escrito originalmente por jkteddy77:

Not sure if these instructions were posted earlier in the thread, but Capcom sent this to me on the 3rd support update. This is how you can provide the devs with the log of what's happening on your machine- and we can view it ourselves too:

●How to output a dump file
Please refer to the following steps for editing settings so that a dump file can be output. When a "Dump" folder will be created, please share it with us.
*Please let us know if the folder will not be created after following the steps below.

＜Steps to edit in a config. ini file ＞

Edit "DumpType=NONE" to "DumpType=MINI" in a config.ini file.
【A path for a config.ini file】
C:Program Files (x86)\\Steam\\steamapps\\common\\Monster Hunter World
*The above path is a default installation path.

Play the game until you encounter the issue you reported. Once you've encountered the issue, please quit and close the game.
Once a "Dump" folder has been created in the installation folder, please make a backup of it and then upload it to the site described in the later part.
Note: A dump file will be output when the crash occurs after editing the config.ini file in step 1.


I believe they just want you to attach the dump file to your open support ticket, the wording seems to be pulled from a troubleshooting guide of theirs.

They sent me this too, but it never actually produced the dump file for me. I responded and told them that and haven't heard from them since. Did you actually get the dump folder to create? I feel like the game isn't even launching long enough for me to get it to work.

[TheGentlemanOrc]

Escrito originalmente por Kai Iona:

Escrito originalmente por jkteddy77:

Not sure if these instructions were posted earlier in the thread, but Capcom sent this to me on the 3rd support update. This is how you can provide the devs with the log of what's happening on your machine- and we can view it ourselves too:

●How to output a dump file
Please refer to the following steps for editing settings so that a dump file can be output. When a "Dump" folder will be created, please share it with us.
*Please let us know if the folder will not be created after following the steps below.

＜Steps to edit in a config. ini file ＞

Edit "DumpType=NONE" to "DumpType=MINI" in a config.ini file.
【A path for a config.ini file】
C:Program Files (x86)\\Steam\\steamapps\\common\\Monster Hunter World
*The above path is a default installation path.

Play the game until you encounter the issue you reported. Once you've encountered the issue, please quit and close the game.
Once a "Dump" folder has been created in the installation folder, please make a backup of it and then upload it to the site described in the later part.
Note: A dump file will be output when the crash occurs after editing the config.ini file in step 1.


I believe they just want you to attach the dump file to your open support ticket, the wording seems to be pulled from a troubleshooting guide of theirs.

They sent me this too, but it never actually produced the dump file for me. I responded and told them that and haven't heard from them since. Did you actually get the dump folder to create? I feel like the game isn't even launching long enough for me to get it to work.

Just got the same email today after a week of waiting for them to get back. Lets see how this goes...

[juandice75]

Escrito originalmente por ElTiggyDaKaiju:

Escrito originalmente por Kai Iona:

They sent me this too, but it never actually produced the dump file for me. I responded and told them that and haven't heard from them since. Did you actually get the dump folder to create? I feel like the game isn't even launching long enough for me to get it to work.

Just got the same email today after a week of waiting for them to get back. Lets see how this goes...

I also just got this today after a week of no response and no it does not create a dump file

[Onion Friend]

Been playing fine for a few days now. What fixed for me was uninstalling nvidia driver in safe mode with DDU. Then installing new driver while offline. Can't install nvidia drivers in Offline Safe Mode so you gotta do a normal boot but unplug/turn off your wifi and make sure it cant connect to anything when you come out of safe mode. Then after driver install u can reboot and come online.

[[☥] - CJ -]

Escrito originalmente por Mr. ♥♥♥♥♥♥♥:

Been playing fine for a few days now. What fixed for me was uninstalling nvidia driver in safe mode with DDU. Then installing new driver while offline. Can't install nvidia drivers in Offline Safe Mode so you gotta do a normal boot but unplug/turn off your wifi and make sure it cant connect to anything when you come out of safe mode. Then after driver install u can reboot and come online.

You dont need to undo your internet when using DDU
On first use it disables Windows driver updates, and if it doesnt the option to do so is in the settings.

You also dont need to reboot after installing the driver UNLESS for whatever reason it asks you to.

[Zonatailurus]

Escrito originalmente por Mr. ♥♥♥♥♥♥♥:

Been playing fine for a few days now. What fixed for me was uninstalling nvidia driver in safe mode with DDU. Then installing new driver while offline. Can't install nvidia drivers in Offline Safe Mode so you gotta do a normal boot but unplug/turn off your wifi and make sure it cant connect to anything when you come out of safe mode. Then after driver install u can reboot and come online.

I finally got time to do this and I was able to get in game! I'm not sure it will let me back in after i close it, so I'm going to play for a bit.

Edit: It did not let me back in...
Edit 2: I did the same steps again and it's letting me back in. I dont know if I want to keep doing this for every session to play the game...

[AKing2033]

I have consistently got into the game In safe mode with networking...(not exactly playable but it’s progress (for me at least...))

What I did was I uninstalled both of my graphics drivers then reinstalled them offline on safe mode (I don’t know if it affected anything)

I then looked up “ how to disable driver updates windows 10” (I use Windows) and then followed the instructions on the first thing that shows up.

And after confirming by restarting my computer then switching to safe mode with networking 3 times and the game successfully loading in each. I made this post

I don’t know if any of what I said at the start affected anything but I wanted to throw my 2 cents to try and help out as this has given me some hope.

The question is obvious as it’s something that’s deactivated in safe mode that’s causing the problem (for me at least) to load it normally.

I am now going to do some trial and error and see what happens.

I hope this helps a bit.

[Hammer Of Evil]

if you're on windows 10 or windows 7

attempt to run the application as usual, after it fails

press windows key + R, type eventvwr

this opens the event viewer for your pc. dont delete anything here, we're just gathering intel.

on the left menu expand windows logs

then click application.

scroll to one of the red circle exclamation points that says 'error' and read the text.

if it says 'faulting application name :MonsterHunterWorld.exe' you can read it for information for what caused the crash if you're interested.

it might give another angle on the problem.

[AKing2033]

I’m looking at it but I unfortunately don’t know what to get from this

Should I post it here or would that be unwise?

[Hammer Of Evil]

Escrito originalmente por Aking0401:

I’m looking at it but I unfortunately don’t know what to get from this

Should I post it here or would that be unwise?

click the 'information' log above the 'error' log, for a nice summary.

no, no point posting it here, but tell me "yes" if you see 'WRDll.x64.dll', as i have a suspicion.

it reports error in a fashion similar to .net framework crashes.

p1- process name
p2 - process version
p3- process timestamp
p4-module name
p5- module version
p6-module timestamp
p7- exception code
p8- exception offset from the start of the module
p9 - unused
p10- unused

at this point you can use the exception offset with a map or cod file to determine the crash breakpoint, or attach a debugger to the process that crashed to figure out what is at the offset.

if you dont know how to do this, dont worry, i was just explaining what the jarble you're looking at means.

[torqueblue]

Dunno what to say other then it's not letting me play. Haven't played in a while. I booted it up and Black screen followed by crash.
Updated my mods= crash
Removed my mods= crash
Installed new drivers for Nvida= crash

Seems mods isn't the issue here and not sure about this DDU I keep reading about, But I have little time as it is to try and Fix this. Wasted too much time on my day off trying to get the Saboteur to work only for it to just sit there on my HDD. I did mess around with some files to get it to work and thought maybe it might of Done something to MHW but doesn't seem to be the case.

[torqueblue]

Escrito originalmente por Hammer of Evil:

Escrito originalmente por Aking0401:

I’m looking at it but I unfortunately don’t know what to get from this

Should I post it here or would that be unwise?

click the 'information' log above the 'error' log, for a nice summary.

no, no point posting it here, but tell me "yes" if you see 'WRDll.x64.dll', as i have a suspicion.

it reports error in a fashion similar to .net framework crashes.

p1- process name
p2 - process version
p3- process timestamp
p4-module name
p5- module version
p6-module timestamp
p7- exception code
p8- exception offset from the start of the module
p9 - unused
p10- unused

at this point you can use the exception offset with a map or cod file to determine the crash breakpoint, or attach a debugger to the process that crashed to figure out what is at the offset.

if you dont know how to do this, dont worry, i was just explaining what the jarble you're looking at means.

I didn't see any 'WRDll.x64.dll' in my event report.

I thought it might've been a .net framework issue aswell seeing as I was messing around with that crap a couple of weeks back. Not that problem for me it seems.

[AKing2033]

Escrito originalmente por Hammer of Evil:

Escrito originalmente por Aking0401:

I’m looking at it but I unfortunately don’t know what to get from this

Should I post it here or would that be unwise?

click the 'information' log above the 'error' log, for a nice summary.

no, no point posting it here, but tell me "yes" if you see 'WRDll.x64.dll', as i have a suspicion.

it reports error in a fashion similar to .net framework crashes.

p1- process name
p2 - process version
p3- process timestamp
p4-module name
p5- module version
p6-module timestamp
p7- exception code
p8- exception offset from the start of the module
p9 - unused
p10- unused

at this point you can use the exception offset with a map or cod file to determine the crash breakpoint, or attach a debugger to the process that crashed to figure out what is at the offset.

if you dont know how to do this, dont worry, i was just explaining what the jarble you're looking at means.

Thank you ,but I do not see 'WRDll.x64.dll'.

Thanks for the explanation though