Randomly freezing and crashing since new update

[Mikedot]

Recently ever since the new update dropped into MHW: IB, my game has been crashing, freezing and sometimes causing BSODs (even though I believe the BSOD thing could be unrelated) and has overall made the game a worrying experience. I am not quite sure how or why this is happening as the screen just freezes for a brief moment and then just closes back to the desktop.

There doesn't seem to be any rhyme or reason as to when the crashing and freezing happens, though. Sometimes it will happen in the middle of a hunt (One time I was hunting a Barioth for the Guild Palace weapons and near the tail end of a hunt when I was clutch claw attacking the monster, the game just randomly froze and crashed), another time when I was heading off toward a new quest, the game BSODd on me and another time today, when I was just talking to my housekeeper NPC, the game just froze and crash.

My PC details:

Operating System - Windows 10 Pro 64-bit
CPU - Intel Core i9 9900K @ 3.60GHz (Kaby Lake 14nm Technology)
RAM - 32.0GB
Motherboard - MSI MPG Z390 GAMING PRO CARBON (MS-7B17) (U3E1)
Monitor - AORUS AD27QD PC Monitor(2560x1440@60Hz) w/ HDR ON
GPU - 4095MB NVIDIA GeForce RTX 2070 SUPER (MSI)
Storage - 167GB INTEL SSDSC2CW180A (SATA (SSD))
Optical Drives - No optical disk drives available
Audio - Realtek High Definition Audio

*Note that my PC has two other HDDs and one SSD where the OS is installed, but my intel SSD is where MHW: IB is currently installed on.

As you can see my PC is well above the recommended system requirements and before this update, this game was running fine. My GPU load and temps were fine and my CPU only hit around 40-60% load while the game was active. Even now, the game doesn't seem to have any load percentage problems like many other people are having but the crashing is still a huge issue.

All of my SSDs have their latest firmware installed and all of my important drivers are up to date, as well as my Windows 10 being up to date.

[💀 Deadward 💀]

Personally, I would start with at least disabling at startup NZXT CAM (unless you're using one of their AIO coolers), Dragon Center, MSI Mystic Light, and Logitech G Hub. They're all things that are great to play around with, but when it's time to play are just bloat and another potential source of conflicts. With the exception of CAM if you're using an NZXT cooler (and only if you're using their coolers), none of the other software I mentioned is necessary.

This is only a personal anecdote, and while every machine is different, I run *nothing* in the background when gaming. The only things in my system tray are usually Steam and Nvidia control panel. Maybe Spotify depending on the game. If I'm playing with friends I'll have Discord running. I have had precisely 0 crashes in almost 800 hours of MHW, and I very, very rarely have crashes in any other game.

[Mikedot]

Yeah, I am using the a Kraken AIO cooler with my setup, so I should leave that on. I could try and see how everything works after disabling those things, as well.

[Mikedot]

Not more than a few seconds after I posted this message and turned off those apps, my computer blue screen'd on me again...

I am getting fed up with this. I am this close to just saying ♥♥♥♥ it and just resetting the whole thing. I already went out earlier today to get a backup drive and some new SSDs to replace the old ones. It's about time I replaced them anyway since i had them since college and that was well over four years ago.

[💀 Deadward 💀]

Did you check Event Viewer after the BSOD?

[Mikedot]

Yeah, I have but it hasn't been giving me anything useful. Instead I have been using WhoCrashed to try and find out details. I could give you my reset crash reports from it if you'd like.

---
On Fri 1/31/2020 9:30:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: pshed.dll (PSHED!PshedBugCheckSystem+0x10)
Bugcheck code: 0x124 (0x0, 0xFFFFAA8231D7F028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\pshed.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Platform Specific Hardware Error Driver
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 1/31/2020 5:11:54 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013120-26703-01.dmp
This was probably caused by the following module: mcupdate_genuineintel.dll (0xFFFFF80338E3C8D3)
Bugcheck code: 0xD1 (0xFFFFF80338E3C8D3, 0x2, 0x8, 0xFFFFF80338E3C8D3)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\mcupdate_genuineintel.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Intel Microcode Update Library
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 1/31/2020 4:33:29 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013120-24453-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFFAD2EA66991C6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFAD2EA66991C6, 0xFFFFA88959071D60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 1/31/2020 2:29:48 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013120-44000-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF803792F92ED, 0xFFFFF6863BF8F598, 0xFFFF8180D617B930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 1/31/2020 9:30:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013120-25546-01.dmp
This was probably caused by the following module: hal.dll (hal+0x47FF8)
Bugcheck code: 0x124 (0x0, 0xFFFFAA8231D7F028, 0xBE000000, 0x800400)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 1/31/2020 9:10:06 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\013120-43140-01.dmp
This was probably caused by the following module: hal.dll (hal+0x47FF8)
Bugcheck code: 0x124 (0x0, 0xFFFFA88C75967028, 0xB2000000, 0x30005)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


---

[💀 Deadward 💀]

I didn't even think to ask, but since you mentioned you old drives were...well, old, it made me think about other parts you may have held onto from an old build: What PSU do you have?

[Mikedot]

I am using an EVGA 850 GQ Gold PSU. It's another new part that I got with the rest of my build. The only parts that i carried other from my older build are my HDDs and SSDs. Everything else in my PC is new (relatively speaking)

(also answering messages from my smartphone now. The BSODs are striking too much.)

[💀 Deadward 💀]

Try booting into Windows, then hold down Shift while you click Start -> Power -> Restart. Should get you to the Windows Recovery Environment. Then choose Troubleshoot -> Advanced Options -> Startup Repair.

[Mikedot]

Oh yeah I remember trying that earlier. The startup repair didn't seem to do anything sadly. At this point the only expression have towards this mess of a computer is the expression that my profile picture is making right now.

[Mikedot]

I gave up. I decided that I would much rather backup my important files to a passport drive and reset my pc. I have a whole weekend ahead of me and I would much rather spend a few hours reinstalling a few things instead of dealing with BSODs all weekend long.

But I really do appreciate all the help you have given me! Thank you very much for your time and efforts.

[💀 Deadward 💀]

Mikedot a écrit :

I gave up. I decided that I would much rather backup my important files to a passport drive and reset my pc. I have a whole weekend ahead of me and I would much rather spend a few hours reinstalling a few things instead of dealing with BSODs all weekend long.

But I really do appreciate all the help you have given me! Thank you very much for your time and efforts.

Hah! I was just about done basically saying that, and I'll still post it here. The suggestion below is for a complete and thorough reinstall. IF simply using the Windows 10 'Reset this PC' option doesn't work, I'd follow that. Computers can be a real pain the ass when they're acting up. Sometimes the only way to get it back under control is a clean slate, one way or another.

The last thing you *might* try to at least narrow down what's causing the BSODs is running the Intel CPU diagnostic tool[downloadcenter.intel.com]. That's if it'll let you without crashing.

But really, I would do a clean install at this point.
I'd start by grabbing the latestWindows Media Creation Tool[go.microsoft.com] and prepping a USB stick with it.

Disconnect *all* your drives, and attach only the one that'll serve as your boot drive (hopefully an M.2 SSD).

Enter the BIOS and reset to optimized defaults. Save and exit.

Install Windows via the USB stick you prepped earlier.

Do all of the updates, latest chipset and device drivers, etc.

DON'T install CAM or any of the MSI junk. I just looked and your motherboard has a dedicated water pump connector. You can use that and control the pump speed in BIOS. Then use BIOS to also control the fan curves.

Once everything is fully updated and ready to go, shut down the machine and reconnect all your other drives.

Power on and enter BIOS. Make sure the default boot drive is still the one with the fresh Windows install. If it's not, change it. Save and exit.

Once in Windows, do all the things with your data. Backup and move as necessary. Create Steam libraries if necessary and point them at your games. I would grab anything off the drive with the old Windows install that's important and then format that drive.

One thing I like to do is change all my Windows libraries (Downloads, Documents, Pictures, Music, and Videos) to point to locations on secondary drives. That way I don't really have to worry about backing up if I need to reinstall or reformat my system drive.

If you do all that and *still* get BSODs, I would be at a complete loss.

[Mikedot]

Sadly it seems like despite clearing my PC up of the BSODs once and for all, along with replacing both of my system OS and gaming storage with brand new SSDs, it seems like my game client is still crashing, sadly.

---
Faulting application name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5e27ffbf
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000100000001
Faulting process id: 0x1ef8
Faulting application start time: 0x01d5d978058f8212
Faulting application path: F:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Faulting module path: unknown
Report Id: b38303e7-f080-4794-a224-ca5fcfdb055d
Faulting package full name:
Faulting package-relative application ID:
---

[💀 Deadward 💀]

Mikedot a écrit :

Sadly it seems like despite clearing my PC up of the BSODs once and for all, along with replacing both of my system OS and gaming storage with brand new SSDs, it seems like my game client is still crashing, sadly.

---
Faulting application name: MonsterHunterWorld.exe, version: 0.0.0.0, time stamp: 0x5e27ffbf
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000100000001
Faulting process id: 0x1ef8
Faulting application start time: 0x01d5d978058f8212
Faulting application path: F:\SteamLibrary\steamapps\common\Monster Hunter World\MonsterHunterWorld.exe
Faulting module path: unknown
Report Id: b38303e7-f080-4794-a224-ca5fcfdb055d
Faulting package full name:
Faulting package-relative application ID:
---

That...just...what...huh...no. That...doesn't make any sense.

[💀 Deadward 💀]

Now that you've done all of that, have you tried verifying integrity of game files since moving MHW to the new SSD?

[💀 Deadward 💀]

What about other USB devices? I've had all kinds of devices cause issues over the years with different games and programs. Things like games crashing or refusing to even start if I had a Wacom tablet, iPad, or even just my cell phone plugged in.