MHW caused my PC to crash

[Spirb]

All I did was going to main menu, wait for a few moments, and bam, BSOD. Before the crash, Err12 happened and after I restarted the game, the BSOD happened. Any help?
Nvidia GTX 1050Ti
i3 6100

[V1CT1MIZED]

When this game crashes it normally goes to desktop.

Having a BSOD sounds hardware related, is your hardware overclocked?

[Fang]

Games cannot be the root cause of a BSOD, they can only reveal an issue with hardware, drivers, or the OS.

[⎛⎝♕✪Tramadol Addict✪♕⎠⎞]

i had this same issue with my oc'ed i5 6600k, i checked my system with aida 64 and had no problem.. i tried tuning up my vcore voltage, and no bsod afterwards, but it crashed to desktop. i put more vcore voltage and it s working flawlessly now..
conclusion: this game is better than aida 64 for checking your rig's stability!

[WTFantastico]

I usually get the old ERR12 message, but sometimes it crashes the whole steam client hard. Once, it crashed the entire computer, monitor went 'no signal', and entire PC unresponsive. No sound, either. I monitor hardware temps, and neither CPU nor GPU went anywhere close to dangerous.

[withyouforyou]

Can you please post your full windows event viewer log for the crash? All or any of you, I will reply.

[Spirb]

Somehow this only happens when discord is on. Once I closed discord, it runs well. However, this problem only come out recently, yesterday it was fine with discord on

[withyouforyou]

Anchovios の投稿を引用：

Somehow this only happens when discord is on. Once I closed discord, it runs well. However, this problem only come out recently, yesterday it was fine with discord on

That would indicate either an OS or an audio driver issue.

[withyouforyou]

Anchovios の投稿を引用：

Somehow this only happens when discord is on. Once I closed discord, it runs well. However, this problem only come out recently, yesterday it was fine with discord on

I also would still like to see the event viewer log so I might be able to tell you.

[Spirb]

withyouforyou の投稿を引用：

Anchovios の投稿を引用：

Somehow this only happens when discord is on. Once I closed discord, it runs well. However, this problem only come out recently, yesterday it was fine with discord on

I also would still like to see the event viewer log so I might be able to tell you.

I'm not so sure which one to give you, so here's one:

Log Name:      Application
Source:        Application Error
Date:          25/08/2018 20:48:39
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-779KEP0
Description:
Faulting application name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5b76a1c6
Faulting module name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5b76a1c6
Exception code: 0xc0000409
Fault offset: 0x00000000028f301c
Faulting process ID: 0x2c40
Faulting application start time: 0x01d43c79ea53a5a9
Faulting application path: I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Faulting module path: I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Report ID: b250cde2-7c47-417c-aafa-5c66b8b4e1bd
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-08-25T13:48:39.942985200Z" />
    <EventRecordID>18802</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-779KEP0</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MonsterHunterWorld.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>5b76a1c6</Data>
    <Data>MonsterHunterWorld.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>5b76a1c6</Data>
    <Data>c0000409</Data>
    <Data>00000000028f301c</Data>
    <Data>2c40</Data>
    <Data>01d43c79ea53a5a9</Data>
    <Data>I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe</Data>
    <Data>I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe</Data>
    <Data>b250cde2-7c47-417c-aafa-5c66b8b4e1bd</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

And here's another:

Log Name:      Application
Source:        Application Hang
Date:          25/08/2018 21:03:01
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-779KEP0
Description:
The program MonsterHunterWorld.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 788
 Start Time: 01d43c7be12282ce
 Termination Time: 4294967295
 Application Path: I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
 Report Id: 2b48c3af-32a5-4f3d-b559-e98798ac9e98
 Faulting package full name: 
 Faulting package-relative application ID: 

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-08-25T14:03:01.145979700Z" />
    <EventRecordID>18860</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-779KEP0</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MonsterHunterWorld.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>788</Data>
    <Data>01d43c7be12282ce</Data>
    <Data>4294967295</Data>
    <Data>I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe</Data>
    <Data>2b48c3af-32a5-4f3d-b559-e98798ac9e98</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>54006F00700020006C006500760065006C002000770069006E0064006F0077002000690073002000690064006C00650000000000</Binary>
  </EventData>
</Event>

[Sofia]

Hey guys, before you spew your uninformed bullocks about "games cannot cause BSOD", please understand what a BSOD is. BSOD are not hardware-only - they can be caused by software which incorrectly interacts with your hardware or causes an essential piece of your OS to crash. So yes, a game can, in fact, cause a BSOD.

Monster Hunter World in particular has a high chance to cause a BSOD if you play in full screen mode and alt-tab, or if you alt-tab during the start-up sequence. There are hundreds of players who have reported this happening. Crypt of the Necrodancer had the exact same issue, and it was eventually patched.

[withyouforyou]

Dri の投稿を引用：

Hey guys, before you spew your uninformed bullocks about "games cannot cause BSOD", please understand what a BSOD is. BSOD are not hardware-only - they can be caused by software which incorrectly interacts with your hardware or causes an essential piece of your OS to crash. So yes, a game can, in fact, cause a BSOD.

Monster Hunter World in particular has a high chance to cause a BSOD if you play in full screen mode and alt-tab, or if you alt-tab during the start-up sequence. There are hundreds of players who have reported this happening. Crypt of the Necrodancer had the exact same issue, and it was eventually patched.

That isn't ♥♥♥♥♥♥♥♥. Games cannot cause a BSOD. Operating system and drivers can. Please don't comment on something you don't actually understand the basis of.

[withyouforyou]

Anchovios の投稿を引用：

withyouforyou の投稿を引用：

I also would still like to see the event viewer log so I might be able to tell you.

I'm not so sure which one to give you, so here's one:

Log Name:      Application
Source:        Application Error
Date:          25/08/2018 20:48:39
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-779KEP0
Description:
Faulting application name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5b76a1c6
Faulting module name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5b76a1c6
Exception code: 0xc0000409
Fault offset: 0x00000000028f301c
Faulting process ID: 0x2c40
Faulting application start time: 0x01d43c79ea53a5a9
Faulting application path: I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Faulting module path: I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Report ID: b250cde2-7c47-417c-aafa-5c66b8b4e1bd
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-08-25T13:48:39.942985200Z" />
    <EventRecordID>18802</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-779KEP0</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MonsterHunterWorld.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>5b76a1c6</Data>
    <Data>MonsterHunterWorld.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>5b76a1c6</Data>
    <Data>c0000409</Data>
    <Data>00000000028f301c</Data>
    <Data>2c40</Data>
    <Data>01d43c79ea53a5a9</Data>
    <Data>I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe</Data>
    <Data>I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe</Data>
    <Data>b250cde2-7c47-417c-aafa-5c66b8b4e1bd</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

And here's another:

Log Name:      Application
Source:        Application Hang
Date:          25/08/2018 21:03:01
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-779KEP0
Description:
The program MonsterHunterWorld.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 788
 Start Time: 01d43c7be12282ce
 Termination Time: 4294967295
 Application Path: I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
 Report Id: 2b48c3af-32a5-4f3d-b559-e98798ac9e98
 Faulting package full name: 
 Faulting package-relative application ID: 

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-08-25T14:03:01.145979700Z" />
    <EventRecordID>18860</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-779KEP0</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MonsterHunterWorld.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>788</Data>
    <Data>01d43c7be12282ce</Data>
    <Data>4294967295</Data>
    <Data>I:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe</Data>
    <Data>2b48c3af-32a5-4f3d-b559-e98798ac9e98</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>54006F00700020006C006500760065006C002000770069006E0064006F0077002000690073002000690064006C00650000000000</Binary>
  </EventData>
</Event>

Exception code 0xc0000409 is 99% of the time caused by a corrupt windows OS registry. Try running SFC /scannow in command prompt. See what that says.

[Sofia]

withyouforyou の投稿を引用：

Dri の投稿を引用：

Hey guys, before you spew your uninformed bullocks about "games cannot cause BSOD", please understand what a BSOD is. BSOD are not hardware-only - they can be caused by software which incorrectly interacts with your hardware or causes an essential piece of your OS to crash. So yes, a game can, in fact, cause a BSOD.

Monster Hunter World in particular has a high chance to cause a BSOD if you play in full screen mode and alt-tab, or if you alt-tab during the start-up sequence. There are hundreds of players who have reported this happening. Crypt of the Necrodancer had the exact same issue, and it was eventually patched.

That isn't ♥♥♥♥♥♥♥♥. Games cannot cause a BSOD. Operating system and drivers can. Please don't comment on something you don't actually understand the basis of.

If the game interacting with your drivers is what caused the BSOD, and that game and only that game is doing it, then it may as well be the game causing the BSOD. Being semantic on this is about as stupid as saying people don't kill people, guns do.

[withyouforyou]

Dri の投稿を引用：

withyouforyou の投稿を引用：

That isn't ♥♥♥♥♥♥♥♥. Games cannot cause a BSOD. Operating system and drivers can. Please don't comment on something you don't actually understand the basis of.

If the game interacting with your drivers is what caused the BSOD, and that game and only that game is doing it, then it may as well be the game causing the BSOD. Being semantic on this is about as stupid as saying people don't kill people, guns do.

It's not being semantic. The game has nothing to do with it. Not every game will interact with your software in the same way. Everybody programs differently, everybody uses different dynamic link libraries, different codecs, etc. You can have a corrupt OS for years and you won't know about it until something interacts with that particular part of your system.

[Spirb]

withyouforyou の投稿を引用：

Exception code 0xc0000409 is 99% of the time caused by a corrupt windows OS registry. Try running SFC /scannow in command prompt. See what that says.

Windows Resource Protection did not find any integrity violations.

Huh.