Official MH:W & Iceborne Troubleshooting/Reporting Thread

[Capcom Customer Service]

”Wait…that is no island…it’s a landmass!” – The Handler, Monster Hunter World: Iceborne

We hope you’re all enjoying or will be enjoying Monster Hunter: World and the massive Iceborne expansion! While we hope all of our fans will have a great time with the game, there may be some cases here and there where the game may not function correctly under certain environments and / or hardware combinations.

We’ve set up this feedback thread for you all to share any technical issues you may be having with the game. We’ll use this thread as a place for tracking these problems, and pass on the feedback gathered here to our team for further investigation.

Before providing any reports, please ensure you've followed the steps below to rule out problems with your PC, Steam or the game’s files. We have also included a breakdown of error codes at the end of this post.

Troubleshooting Steps

1. Check the game’s system requirements

Please make sure you meet the minimum requirements for the game, outlined on the bottom of the game’s Steam Store page for MH:W and Iceborne; if you do not meet the minimum requirements for the game, this may result in poor framerate, or the game not running.

If you do meet the minimum specifications but not the recommended specifications, you may want to try turning down the graphics settings, if you haven't already. Please note that most graphical settings changes require the game to be restarted in order for the changes to take effect.

Some high end integrated graphics chips and modern laptop integrated GPUs may work, but have not been tested, nor are they officially supported by Capcom. If you’re using a laptop with a dual GPU dedicated graphics card and integrated graphics processor, we recommend disabling your integrated graphics via the BIOS settings prior to launching the game. For more information on accessing your BIOS, please see your laptop/motherboard manufacturer manual.

If you’re using a multi-GPU setup such as NVIDIA’s SLI or ATI’s Crossfire technologies, we recommend experimenting with disabling these settings, as they may cause compatibility issues with the game.

Capcom does not warrant nor officially provide technical support for PCs that do not meet the official, minimum system requirements.

2. Add the game’s folder and files to your anti-virus program’s exception / exclusion list

Some launching issues may be attributed to certain Anti-Virus software preventing the game executable from launching due to a false-positive error. We recommend users add all of the following files and folders to the Anti-virus and Firewall exclusion list to prevent this issue. If these files and folders were already added previously, try removing them from the exclusion list and re-adding them.

Note: To quickly access the following folders, press Windows Key + R then copy and paste the folder URL below.

MonsterHunterWorld.exe:
Default Location: C:\Program Files (x86)\Steam\steamapps\common\Monster Hunter World

Steam.exe:
Default Location: C:\Program Files (x86)\Steam

Steam AppData
Default Location: C:\Users\%USERNAME%\AppData\Local\Steam

For a guide on adding exceptions to your anti-virus software, please visit one of the following links:

1. Windows Defender[support.microsoft.com]
   
2. Microsoft Security Essentials[answers.microsoft.com]
   
3. Malwarebytes[www.malwarebytes.com]
   
4. Avast Antivirus[www.avast.com]
   
5. AVG Antivirus[support.avg.com]
   
6. Kaspersky Anti-Virus[support.kaspersky.com]
   
7. Webroot SecureAnywhere[www5.nohold.net]
   
8. McAfee Antivirus (Steam Support guide)
   
9. Bitdefender*[www.bitdefender.com]

*For Bitdefender, you will need to also add the MonsterHunterWorld.exe file to the program’s Whitelist. To do this, follow these steps:

1. Open Bitdefender
   
2. Go to the Protection tab
   
3. Click “View Feature”
   
4. Click the gear icon inside the “Advanced Thread Defense” box
   
5. Select “Add applications to the whitelist”
   
6. Browse and navigate to the MonsterHunterWorld.exe file:
   
7. C:\Program Files (x86)\Steam\steamapps\common\Monster Hunter World
   
8. Once the .exe file is added, close Bitdefender and relaunch the game

3. Give administrator privileges to Steam and the game

Some users can get the game running properly by running Steam.exe in administrator mode. This can be done by right-clicking on the .exe file and selecting “Run as administrator.” If that doesn’t work, try running the game’s .exe file in administrator mode as well.

4. Update your Video/Graphics Drivers and Windows Operating System

Try updating your video card drivers, as oftentimes outdated drivers can cause a variety of issues ranging anywhere from in-game graphical problems, to the game not starting, and more.

For the latest NVIDIA drivers, click here[www.nvidia.com].
For the latest AMD drivers, click here[support.amd.com].

Additionally, please ensure that Windows Update has been run and that all the latest updates have been installed on your operating system.

If you still experience issues, you may want to try performing a clean installation of the video driver set. This will remove any extraneous driver DLL files or game profiles that existed with the previous driver installation.

To do a clean video driver install, many enthusiasts use a third-party program called Display Driver Uninstaller[www.guru3d.com] (DDU), which completely removes components that were part of the original driver installation package.

1. Run DDU and uninstall old video driver.
   
2. Install the latest OEM video card driver and reboot your PC.
   
3. Run the latest DirectX installer package[www.microsoft.com] and reboot your PC.

IMPORTANT! Please don't forget to reboot Windows upon completing a video driver installation. This will help reinitialize the driver and the graphics card using the new driver.

5. Check your graphics driver settings & computer power settings

To reiterate, some high end integrated graphics chips and modern laptop class discrete GPUs may work, but have not been tested, nor are they officially supported by Capcom. Laptops with dual GPUs, such as an Intel Integrated Graphics Processor + NVIDIA Dedicated Graphics Card, may need additional configuration in the event the integrated processor is overriding the dedicated graphics drivers.


If using a dual NVIDIA / Intel GPU, follow these steps:

1. Install the latest Intel integrated drivers[downloadcenter.intel.com]
   
2. Reboot your PC
   
3. Open NVIDIA Control Panel
   
4. Click 'Manage 3D Settings'
   
5. Go to 'Program Settings' and then select ‘Monster Hunter: World’ (if it is not in the list you can add it manually by clicking 'Add')
   
6. Scroll down to 'Power Management Mode'
   
7. Set it to 'Prefer Maximum Performance' / ‘High Performance Processor’ instead of 'Adaptive'
   
8. Close NVIDIA Control Panel and launch Monster Hunter: World

If using a dual AMD “Switchable Graphics” GPU, follow these steps:

1. Open AMD Catalyst Control Center
   
2. Under “Switchable Graphics”, select the High Performance section and select ‘Monster Hunter: World’ (if it is not in the list you can add it manually by clicking 'Browse')
   
3. Click ‘Apply’
   
4. Close AMD Catalyst Control Center and launch Monster Hunter: World

Additionally, double-check your desktop / laptop’s power settings by performing the following:

1. If using a laptop, ensure the charger is connected
   
2. Open Control Panel
   
3. Select Power Options
   
4. Select “Change Plan Settings”
   
5. Select “Change advanced power settings”
   
6. From within the dropdown menu, select “High performance” and click ‘Apply’ then ‘OK’
   
7. Launch Monster Hunter: World

6. Update DirectX

We recommend downloading and running the DirectX End-User Runtime Web Installer[www.microsoft.com] to ensure DirectX is fully up to date.

7. Verify the game’s cache in Steam

Try verifying the game's cache in Steam. You can do so by following the steps outlined in this Steam support article (reposted below). This may find missing or damaged files that need to be repaired, even if you've just installed the game. You may also try temporarily disabling your anti-virus while verifying the cache or launching the game, as on occasion anti-virus programs may flag games or the files necessary to play them as a virus.

To verify the game’s cache, follow these steps:

1. Restart your computer and launch Steam
   
2. From the “Library” section, right-click on the game and select “Properties” from the menu.
   
3. Select the “Local files” tab and click the “Verify integrity of game files...” button.
   
4. Steam will verify the game's files - this process may take several minutes.
   
5. Important: One or more files may fail to verify. This is normal for most Steam games. The files that fail to verify are local configuration files that should not be replaced as part of this process. You can safely ignore this message.

This process allows the Steam client to scan every single file you downloaded for this game, verify checksum of each, and compare that against the file manifest data on Steam's content server. If the file is missing or has a different checksum value, you will receive a message stating "X files failed to validate and will be reacquired." What this means is that some files have either been deleted, or may have been corrupted. Click “Close,” and Steam will automatically download and / or replace the problematic files.

8. Original Installation

Please ensure the installed base game, DLCs, and any official title updates are rolled back to their unaltered original state as provided by Capcom and Steam Store. If the problem still persists, please contact Capcom customer service for additional assistance.

If you still experience visual / audio-related issues or crashes, please help the dev team by providing the detailed information below.

The more samples and data points we receive, the better we are able to narrow down and determine the root cause of these problems. Here’s what we need:

A) Your System Specs
1) CPU name & model
2) Name / model of the desktop or laptop (if available)
3) Graphics card / chip model and the amount of VRAM
4) Video driver version number
5) System memory size (e.g., 16GB)
6) OS version (Windows 7, 8, 10, 64-bit/32-bit, etc. Please make special note in your specs if you are running Windows "N" and "K" editions that do not come with Windows Media Player.)
7) Anti-virus software name and version
8) Your region (continent and/or country)

B) Give as many details about your issue as possible
Please share your specific issue and the location(s) where you’re experiencing the issues – for example, if you’re having problems with the framerate, is it happening constantly, or is it during certain modes, during gameplay, etc. The following information can greatly help as well:

• Have you confirmed that you’ve met at least the minimum system requirements for the game (See Step 1)?
  
• What were the characters doing when this issue occurred?
  
• Did the issue resolve itself when you rebooted the game?
  
• Please also attach any screenshots or video of your issue, preferably via a Dropbox[www.dropbox.com], Google Drive[www.google.com], or OneDrive[www.onedrive.live.com] link.

C) Detailed reproduction steps, if consistently reproducible
This step particularly is very useful for the development team. The more detailed info you can provide, the quicker the team can reproduce the error state and investigate the issue further.

D) DxDiag Report
A good deal of the aforementioned system information, such as the OS version, graphics card model, and video driver, are available by running a DxDiag report.

To create a DxDiag report:

1. Open a "Run" dialog in Windows. This can either be done by typing "run" into Start Search, or by holding the Windows key and pressing "R." (Either method works in Windows 7, 8, 8.1, and 10.)
   
2. Type "dxdiag" (with or without quotes) into the box that comes up.
   
3. From the DirectX Diagnostic Tool window, wait for the tool to gather the information it needs, then click "Save All Information..." which will ask you to save a text file, named "DxDiag.txt" by default. Save this file somewhere where it will be easy to find, then attach it in your response.

E) Graphics Settings configuration file
The graphics_option.ini file contains graphics options selected in your game. The file is located in the directory below:

Default Location: C:\Program Files (x86)\Steam\steamapps\common\Monster Hunter World\

Please upload the graphics_option.ini file along with the DxDiag.txt file to the file hosting sites noted above and submit URL along with other relevant information from sections A, B, and C.

Common Errors / Error Codes

"networking error. Lost network connection (1201)"

This error occurs when you are logged out of Steam during gameplay. Please log into Steam again, then restart Monster Hunter: World.

Flickering display on monitor during gameplay

In some configurations, a flickering issue may occur when a user selects the framerate priority setting within the Graphics Options. This setting may cause frequent resolution changes based on the user's PC specs. Try changing this setting to "High" or "Prioritize Resolution" to resolve the issue.

Launch / Crash at launch issue when playing for the first time

Please try the following in the event you experience a launching or crash-at-launch issue at initial launch:

1. Restart Steam.
   
2. Remove the save file from your Steam ID, located in the following folder: Program Files (x86)\Steam\userdata\[steam id]\582010
   
3. Relaunch the game.

Offline gaming

When launching the game for the first time, please ensure you are connected online. Once you make it to the Title Screen, offline mode can be used to launch the game.

ERR01: Failed to create Directinput device

There is a possibility DirectX 11 hasn't been installed, or .dll files are missing / corrupted. Please download and install the latest Windows Updates.

ERR03 : Failed to initialize DirectX11

There maybe several reasons causing this error.

• DirectX 11 has not been installed on the PC
  
• Using a graphics card incompatible with DirectX11
  
• OS is not supported by platform, e.g., Windows 7, 8, 8.1, and 10.
  
• To resolve, please ensure Windows Update has been run.

ERR04 : Failed to get display info.

This error happens if there is no available resolutions / color modes for the monitor / display, or no output is found for DirectX. Please check that the graphics card meets the system requirements for the game. If the graphics card meets the system requirements, ensure the driver is fully up-to-date. Please ensure the game is being launched on the local machine as opposed to remote access / streaming.

ERR08 : Memory overrun.

There is not enough system memory / graphics card memory to run the game. Try lowering the resolution / graphics settings of the game. Please ensure the graphics card has at least 2GB of video memory.

ERR10 : Unsupported DXGI request

There may be a possibility that the graphics card does not support the necessary functions required for the game to run. Please confirm the graphics card is compatible with Monster Hunter: World and install the latest drivers and Windows Updates.

ERR11 : Invalid DXGI call

There might be a possibility the graphics card doesn't support necessary functions required to run the game. Please confirm the graphics card is compatible with Monster Hunter: World. Please check that the graphics card meets the system requirements for the game. If the graphics card meets the system requirements, ensure the driver is fully up-to-date and download and install the latest Windows Updates.

ERR12 : Graphics device crashed

There might be a possibility the graphics card doesn't have the latest drivers. Please visit your graphics card manufacturer's website and download and install the latest drivers, then download and install the latest Windows Updates.

ERR13 : Graphics driver internal error

There might be a possibility the graphics card doesn't have the latest drivers. Please visit your graphics card manufacturer's website and download and install the latest drivers, then download and install the latest Windows Updates.

ERR14 : Graphics API not implemented

This error occurs when the current graphics card driver is not the latest version, or a certain function with DirectX isn't working properly. Please refer to your graphics card manufacturer's website to download and install the latest drivers. Please ensure you are not using a USB / Video converter display adapter, then download and install the latest Windows Updates.
Thank you for your patience and support, and Happy Hunting!

Best Regards,

Capcom USA Customer Support

Please note that this thread is only for posting issues with the game and specifications for Monster Hunter: World; in the interest of helping the development team better investigate these issues, any extraneous discussion or derailment may be removed.

Note: The old "Monster Hunter: World Troubleshooting Thread" will be locked and unpinned but can still be access here.

[Hakana]

Was In the Rotten Vale, the host left and me and my friend disconnected. I then had a visual bug where the scoutflies appeared in a giant glitching green orb. Didn't think much of it at first, until I moved to another level and the orb kept expanding and it looked like my monitor became a strobe light flashing multiple colours. I don't know if this is a hardware specific problem, but it definitely needs to be looked into right away if it's a bug within the game. I can provide a screenshot to prove if necessary, don't want anyone to suffer from a stroke or epileptic fit from this bug.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. Froze, sound cut off, closed itself and went back to desktop.

I was doing the quest "50 Shades of White" with one of my friend. We were 5mins into the hunt, everything was fine and then at some point the Barioth toppled from attacks in the middle of the arena and I was against his face starting to attack it and the game crashed right there.

[loveysick]

A)
1) i7 8700
2) custom built desktop
3) Gainward Phoenix RTX 2060 GS 6GB ( without any custom OC )
4) 442.19 ( I know it's not the latest one, however there is no note in the driver update notes of this bug having been fixed in 442.50 ( the most recent one as of today, mind 442.50 is the successor of 442.19, so there's no version inbetween ))
5) 16GB
6) Windows 10 Professional
7) no anti-virus running ( disabled Windows Defender )
8) Europe, Germany ( playing the game fully in english )


B) and C)
Game crashes when I try to clutch onto a Nightshade Paolumu in the desert ( at night, playing duo, weapons were the Holy Guild Knight fully upgraded ( can't remember the exact name ) and the Girros MR armor ( beta beta alpha beta alpha ordered top-down ), notable render effects by skills were a Mega Demondrug and full sleep resistance.
I reproduced this ( accidentally ) twice, the crash occurs on the exact moment the clutch claw connects, from what I am guessing a client-sided particle rendering error as my friend never crashed all three times when I did this )

I can not provide any video or screenshot, as my GPU seems to "crash" when this happens ( I have a stream running with Hardware Acceleration on my second monitor, it always crashes too ) so the recorded video will get corrupted when I try it.


D)
DxDiag:
https://1drv.ms/t/s!Al6rTgkZXkWshrZSVrjrvgOiHWElhQ?e=aL0qgO


E)
Graphics Options:
https://1drv.ms/u/s!Al6rTgkZXkWshrZTGfUBSouPdXL6ZQ?e=PgdWqT
^ this was the last try where I restarted Steam and then rejoined.
On try one it was the same settings + SSAO High + DX12
On try two it was DX11 + low everything ( still 1920x1080 ) + High Res textures OFF
The crash occured in every graphics configuration at the same time, as written in B) / C)

Note: When using DX12 I get the ERR12 : Graphics device crashed error, in DX11 the game crashes without any error code.

edit: typos

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. Froze, sound cut off, closed itself and went back to desktop.

I was doing the "Fury of El Dorado" quest, in a almost full lobby and the quest had 4 hunters in it. We were in the third phase of the hunt and maybe 2mins in the 3rd phase she screamed right on top of me (we were next to the entry point of the third phase) and that's exactly when the game crashed.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. Froze, sound cut off, closed itself and went back to desktop.

I went back into the same lobby that I mentionned in my post just above 15mins ago. Once I got back in, started a quest, got disconnect from the hunt 5mins in. Started another one and we got a full party, 1min in, got in front of the Kulve Taroth when she was looking around right in the middle of the phase one zone of the map. She was right in front of me further I ran toward her and then connection was lost and half a second later the game crashed again.

Btw, this was also around the 5th or 6th time I got disconnected from a hunt since the friday rush hour started!!! Just before that from like 17:00 till maybe 18:30ish got no disconnections whatsoever!

This is soooo tiring and brings back exactly my point about the Safi'Jiiva siege that's going to be a total nightmare to complete and grind when it's going to be out if nothing of this is fixed. Between the crashed and the disconnections it's a complete mess!!!

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. As usual, it froze, sound cut off, closed itself and went back to desktop.

This time I was in the coral locale of the guiding lands against a Tempered Silver Rathalos. Everything was going well, cut off his tail, was about 5mins into the fight I'd say. We were in the middle of the "nest" area. Can't remember exactly what was happening, it was pretty hectic and I was pissed off by this third crash today so soon that I kinda didn't pay attention.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game YET crashed again. As usual, it froze, sound cut off, closed itself and went back to desktop.

A FANTASTIC DAY FOR CRASHES.

Loaded the game back up. Went into the guiding lands camp #3. Killed myself twice to activate Fortify two times. Got my Water Element Insect Glaive set, ate for elemental resist with a gourmet voucher, got out of the camp, asked my palico to signal for tailraders, was gulping down on a mega armorskin potion and they got here. Then as soon as I did a roll out of the last frames of the anymation for the potion to then gulp down a mega demondrug potion the game crashed. I was rolling towards the coral locale right outside of camp #3.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. Froze, sound cut off, closed itself and went back to desktop.

Was doing the MR quest in the Ancient Forest to upgrade the glider mantle for a friend (the one where you fight a Rathalos and a Nargacuga). Within less than 5mins we slayed the Rathalos (we were a full party) and then I went to camp #8 to see if the Nargacuga was around but at the moment I touched the ground the game crashed.

Btw the disconnections issues from earlier today were definitely because of the online rush hours of friday because when I started playing again around midnight and in multiplayer with friends it stopped happening.

[Candy Rush]

I also have the same situation,No error message, just the screen that froze, sound cut off, then game closed back to the desktop.
The game crashed and did not leave any notice
Time occurred is random
A
1) Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz (6 CPUs), ~2.9GHz
2) DESKTOP-IVNIFPM
3) GeForce RTX 2070 8GB (Nvidia)
4) 442.50 latest driver
5) 16Gb Ram
6) Windows 10 Home 64-bit
7) Viet Nam (Asia)

B
I could enter the game, But the game crashed randomly

Video Error
/url https://drive.google.com/open?id=1ona5IrahzbcQtsiCDu9wSBm--_ebLtdQ
/url https://drive.google.com/open?id=1_ogci5JCgCP-T5LaAMNkIvnkrjEcCHGm


D
/url https://drive.google.com/open?id=1wEuH0rCu67vFBdYGBk3YUPfvvt2z8JTB
dxdiag


E
/url https://drive.google.com/open?id=1gEPAplaMcP6gHoFQhTkDen5rxo5hcHji

and error code from Event view

Faulting application name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5e463c73
Faulting module name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5e463c73
Exception code: 0xc0000005
Fault offset: 0x0000000020598c70
Faulting process id: 0x2654
Faulting application start time: 0x01d5e8e18121bc5c
Faulting application path: D:\Steam\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Faulting module path: D:\Steam\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Report Id: 48a93af3-1601-4873-aaf2-faabb599bb05
Faulting package full name:
Faulting package-relative application ID

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. Froze, sound cut off, closed itself and went back to desktop.

Just came back from a quest with two of my friends. Went to do my safari in Seliana quickly. As soon as I talked to the housekeeper at his stand outside the house it crashed.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed yet again! This time it crashed my whole PC! It's the second time the game gives me a BSOD.

I was playing with two friends, we were maybe 4mins into the quest. We were in Hoarfrost Reach doing an optional quest to hunt 14 boaboas. I was alone in the middle of area 9 killing some boaboas. A Viper Tobi-Kadachi was lurking around too. I paralyzed the boaboas and killed some of them and as I was hitting the last ones the game crashed. The image froze, the sound just became a super loud buzz and then it completely crashed my PC! Straight up gave me a BSOD!

I think I'm going to test out DirectX 11 for a day and report back. Sadly it's going to make me scale down to 1080p and I don't even know if I'm even going to have 60fps stable (vs 2K @ around 70-80fps average with DirectX 12) but if it doesn't crash at all tomorrow I'll let you know and then only let you know when it crashes next after that.


***EDIT***

Yeah, so nvm that. Switched to DirectX11 + 1080p. And as I remembered, framerate are worse dans DX12 + 2K. Can't even stay at 60fps (vs 70-80 @ 2K on DX12). During fights it often goes around 45fps where as before Iceborne it was at least stable at 60fps. On top of that I feel like I'm looking at the game through vaseline, no joke, everything is SO much more blurry.

And most importantly, the game REALLY doesn't feel as responsive. The input delay becomes massive compared to DX12 + 2K @ average of 70-80fps.

So yeah, I hated it instantly, reconfirmed what I remembered, played two quest anyways to try to stick with it and it felt so horrible I reverted back to DX12 even though I know that it's probably the main cause of my crashes. I'll just have to hope for a decent fix soon I guess.

:/

***EDIT***

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again twice since I started playing again today about an hour and a half ago. Froze, sound cut off, closed itself and went back to desktop both of those times.


The first time was maybe 30mins after I booted the game. I joined a the guiding land of someone else online through SOS. I helped him against a Tempered Glavenus in the wasteland locale. It was just the both of us. The fight was almost over, the Glavenus went up a slope to get to the sand dunes area and then turned back around immediately to go back down. As I used a tranquilizer on him while following him down the slope the game crashed.

Then i was able to find his guiding land again after booting up the game. I really wanted to get back in there since he said he would summon a Tempered Black Diablos for me after and I REALLY need it since I locked my volcano, coral and rotten locale at lvl7 and it was a PAIN to do so...yeah. So as I got back in there, he already summoned a Tempered Black Diablos. There was also a Tempered Gold Rathian around. The fight went suuuper well. Gold Rathian didn't bother us until the very end and we capture it and etc. Also while doing the hunt, we became a full party. Then after that we went for the Tempered Gold Rathian and while doing that a Ruiner Nergigante interupted the party haha. Eventually the Gold Rathian left and we went after the Ruiner Nergigante. And after being pretty far along in the fight, the Ruiner Nergigante brung the fight into the entry zone of the coral locale. While there I cut off his tail and he did his animation in relation to that. And as I was running towards him right after while the other where already on him and hitting him that's when the game crashed.

As you can see, like I presumed in my very first post. The crashes are especially more common in multiplayer online and even more so in the guiding lands.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. Froze, sound cut off, closed itself and went back to desktop.

Me and three friends started an investigation in the elder recess for a regular Seething Bazelgeuse that had 4 gold + 1 bronze spots. We did it twice beforehand without any issues. But this time when we started the quest I got right into the camp #1 and started going down the slope right in front of me and the game crashed.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. Froze, sound cut off, closed itself and went back to desktop.

I was in Seliana in the cantine. I was in the armor presets menu not even moving my cursor around talking to my girlfriend and the game crashed.

[ProutBedaine]

1) Intel i7-4790k @ 4.00Ghz
2) N/A (Custom built Desktop)
3) GeForce GTX 1080 FE (Founder's Edition)
4) 442.50 (latest drivers from Nvidia Experience)
5) 16Gb RAM
6) Windows 10 Home 64-bit (latest updates installed)
7) Canada (Québec, Châteauguay (it's near Montréal))

Other:
- The DirectX library you linked to was installed.
- I installed the game on an Samsung 860 EVO SSD.
- I play on a Samsung QLED 55" that is capable of doing 2K@120fps with V-sync on in PC games.

Settings:
- Litterally ALL of my settings are put to the maximum EXCEPT volumetric fog, depth of field and motion blur that are all turned off. I play with DirectX12 on and FidelityFX maxed out too.

---------------------------------------------------------

Game crashed again. As usual it froze, sound cut off, closed itself and went back to desktop.

It happened earlier this night while playing with a group of friends. We were in a private lobby (steam friends only can enter freely) and we weren't in a quest. In fact everyone was in the gathering hub and I was in Seliana doing Safari and other stuff. Then I decided to go back in the gathering hub. I tried going through the door just to the left of the steamworks and as soon as the loading started the game crashed.

*************************************************

I'm going to try something and don't know why I didn't think of it before. I'm going to try to reinstall the whole game and see if it helps at all. Probably won't but who knows, I might get lucky (lol).