Help needed!!! The game crashes my entire pc!!!

[General Kenobi]

Hey I'd like some help with my issue. The first time I booted up the game I played for 7 hours straight with no issues.
I then booted it up again after a few hours, I was doing the black flame fight. However my entire pc crashes after about 10 minutes into the fight. After trying a few times and doing the following things it seemed fixed:
1. Clean newest driver install (the new one with mhwilds support)
2. Granting admin priviledges to mhwilds
3. Lowering settings
4. Turning off upscaling and frame gen(which I already had turned off, but wanted to clarify)
5. Tuning the virtual memory page size
6. Verifying file integrity
7. Closing every other thing I have opened, including things running in the background
8. Disabled all overclocking
9. Checking my directx version
10. Forcing it to use dx11 and afterwards dx12
And after all this it still happened again.

What I now did is that I lowered my ram from 5600MHz to 5200Mhz, however I do not have time to fully test this, as it is already almost 2 am for me.

If anyone has any other tips please help! My entire pc crashes, on the motherboard when crashing it will flash the red error boot light. I have never had this happen on any other game.

These are my specs:
AMD Ryzen 9 7900x
2 x 16 gb ddr5 5600MHz corsair vengeance
AMD Radeon RX 6850XT
Asus tuf gaming b650-plus
cooler master gold 850W psu
I have the game installed on a crucial P3 1TB m.2 drive

I will be checking in again tomorrow, any help will be greatly appreciated! For all replies, thank you!

[Ragnar]

Ursprünglich geschrieben von Soulles:

latest nvidia drivers have been having issues with blackscreens and resetting PCs. this game is probably flaring up that problem because of poor optimisation . nothing to do but wait for patches or revert to older drivers and have the game run even worse lol

Thanks for mention. Because today i had the same type of crash with Darktide too, RTX On. Black screen and restart. All temps and GPU/CPU load was normal.

[vkmicro]

seeing the same thing described by others.
The entire system locks up. Freezes corresponding with network usage spikes suddenly.
Very amusing. No clue what could be causing that....

[General Kenobi]

Just tested the game again todat, with the recent patch and reinstalling it on my other drive. It still crashed after about 20 minutes, shame on ♥♥♥♥♥♥♥ capcom for releasing such a ♥♥♥♥ game on pc without properly fixing things. Guess imma wait for the next patch to try again.

[lolschrauber]

Ursprünglich geschrieben von General Kenobi:

Just tested the game again todat, with the recent patch and reinstalling it on my other drive. It still crashed after about 20 minutes, shame on ♥♥♥♥♥♥♥ capcom for releasing such a ♥♥♥♥ game on pc without properly fixing things. Guess imma wait for the next patch to try again.

That explains why hunts are so fast. They knew and needed to squeeze hunts in those tiny time windows

/s

[アンジェル]

Ursprünglich geschrieben von Runey5:

Ursprünglich geschrieben von アンジェル:

The worst which can happen with faulty driver, would be an app crash. But a system crash is a fatal error where it affects more than what the graphics card can handle.

well, it actually is the game itself, reloaded monster hunter wilds, it did its crashreport tool, spat out its own dmp file and according to windbg it says the games crash report showing "C0000005 Access Violation" and that it crashed from within the game.

its also not a hardware issue due to it ONLY happening within MHW, if it were a hardware i'd be seeing it not just within one specific game.

I read that claim so often, it lost all meaning.

[Runey5]

Ursprünglich geschrieben von アンジェル:

Ursprünglich geschrieben von Runey5:

well, it actually is the game itself, reloaded monster hunter wilds, it did its crashreport tool, spat out its own dmp file and according to windbg it says the games crash report showing "C0000005 Access Violation" and that it crashed from within the game.

its also not a hardware issue due to it ONLY happening within MHW, if it were a hardware i'd be seeing it not just within one specific game.

I read that claim so often, it lost all meaning.

i like to repeat what i said to someone else.
1. high temps can cause thermal protection to shutdown a pc
2. a failing psu can cause a pc to shutdown.
3. bad drivers and other software absolutely can cause a full system hard crash without a bsod

now, i like to add this
1. immediately jumping to "hardware failure" implies someones system has inherent instability without any investigation. and if someones system were unstable, they'd be experiencing these issues outside of an isolated case such as the game.

2. windows dmp file showed me (VIDEO_TDR_FAILURE) pointed to nvlddmkm (nvidia driver) which @lolschrauber informed you pointed out it COULD be hardware but doesn't mean it is, your response to this is woefully misleading and misinformed

3. wilds dmp file showed me (C0000005 Access Violation) which happened inside wilds executable, which you've dismissed with "I read that claim so often, it lost all meaning."

4. in previous messages i've sent, i explained how i fixed these issues for myself in particular, i'll rehash them. I had used DDU to remove any traces of old nvidia drivers and reinstalled new clean drivers which fixed the full system crash.

tl;dr
don't be misleading, disingenuous, and dismissive when your go to response is to immediately jump to "hardware failure" when someone reports a full system crash without a bsod when evidence points to anything but hardware failure.

[Carpe Noctem]

Ursprünglich geschrieben von アンジェル:

Ursprünglich geschrieben von Runey5:

well, it actually is the game itself, reloaded monster hunter wilds, it did its crashreport tool, spat out its own dmp file and according to windbg it says the games crash report showing "C0000005 Access Violation" and that it crashed from within the game.

its also not a hardware issue due to it ONLY happening within MHW, if it were a hardware i'd be seeing it not just within one specific game.

I read that claim so often, it lost all meaning.

I’ve read so many useless responses from you that they’ve lost meaning. You gonna talk about dxdiag reports again or accuse anymore people of having failing hardware? Talk about a capcom meat rider…

[Lapalex]

I have the solution : you need to disable the enhanced turbo in the BIOS ;)

[SymasCastro]

After i got a chipset update the game runs fine for 2 days now i am getting the same issu the game is frezzing or in any quest or wen i start the game

[LoudTwinkies]

Not gonna lie this game scared me. This game has caused alot of trouble for me. First couple of weeks at launch it worked flawlessly, then this weekend it ruined my SSD, game woukd stop producing sound and it would make my SSD dissappear from my pc. Im guessing it turned it into Read only. Now I got a random black screen on all monitors and its unresponsive. I hit the reset button on my case and it blacked screened again. No boot. Held the power button for a few seconds to turn it off and let it rest for a bit. Once I turned it on again it was working just fine. I had to test another game to see if my CPU or GPU were over heating but no... my 4070 super is fairly new. And my cpu hasn't given me issues before
i9 12900k.

[アンジェル]

Ursprünglich geschrieben von LoudTwinkies:

Not gonna lie this game scared me. This game has caused alot of trouble for me. First couple of weeks at launch it worked flawlessly, then this weekend it ruined my SSD, game woukd stop producing sound and it would make my SSD dissappear from my pc. Im guessing it turned it into Read only. Now I got a random black screen on all monitors and its unresponsive. I hit the reset button on my case and it blacked screened again. No boot. Held the power button for a few seconds to turn it off and let it rest for a bit. Once I turned it on again it was working just fine. I had to test another game to see if my CPU or GPU were over heating but no... my 4070 super is fairly new. And my cpu hasn't given me issues before
i9 12900k.

That is a hardware issue. Obviously. Not a game issue.

[General Kenobi]

Quick help for everyone, I solved my issue by going into event viewer, finding the crash. Then analyzing the minidump file using microsoftdbg, I used chatgpt to help me with these things(including analyzing the logs and stuff). And I solved my issues. The game itself still crashes, but that's just the ♥♥♥♥ optimization. My pc luckily does not crash anymore.

[General Kenobi]

Ursprünglich geschrieben von Runey5:

Ursprünglich geschrieben von アンジェル:

I read that claim so often, it lost all meaning.

i like to repeat what i said to someone else.
1. high temps can cause thermal protection to shutdown a pc
2. a failing psu can cause a pc to shutdown.
3. bad drivers and other software absolutely can cause a full system hard crash without a bsod

now, i like to add this
1. immediately jumping to "hardware failure" implies someones system has inherent instability without any investigation. and if someones system were unstable, they'd be experiencing these issues outside of an isolated case such as the game.

2. windows dmp file showed me (VIDEO_TDR_FAILURE) pointed to nvlddmkm (nvidia driver) which @lolschrauber informed you pointed out it COULD be hardware but doesn't mean it is, your response to this is woefully misleading and misinformed

3. wilds dmp file showed me (C0000005 Access Violation) which happened inside wilds executable, which you've dismissed with "I read that claim so often, it lost all meaning."

4. in previous messages i've sent, i explained how i fixed these issues for myself in particular, i'll rehash them. I had used DDU to remove any traces of old nvidia drivers and reinstalled new clean drivers which fixed the full system crash.

tl;dr
don't be misleading, disingenuous, and dismissive when your go to response is to immediately jump to "hardware failure" when someone reports a full system crash without a bsod when evidence points to anything but hardware failure.

I did the same things to find the fault, I don't remember if it is the exact same code, but for me my gpu driver was trying to access uninitialized memory. I fixed it by completely wiping my drivers with ddu and then reinstalling. The AMD clean install button didn't do a clean enough install apparently hahaha.

[Runey5]

Ursprünglich geschrieben von General Kenobi:

Ursprünglich geschrieben von Runey5:

i like to repeat what i said to someone else.
1. high temps can cause thermal protection to shutdown a pc
2. a failing psu can cause a pc to shutdown.
3. bad drivers and other software absolutely can cause a full system hard crash without a bsod

now, i like to add this
1. immediately jumping to "hardware failure" implies someones system has inherent instability without any investigation. and if someones system were unstable, they'd be experiencing these issues outside of an isolated case such as the game.

2. windows dmp file showed me (VIDEO_TDR_FAILURE) pointed to nvlddmkm (nvidia driver) which @lolschrauber informed you pointed out it COULD be hardware but doesn't mean it is, your response to this is woefully misleading and misinformed

3. wilds dmp file showed me (C0000005 Access Violation) which happened inside wilds executable, which you've dismissed with "I read that claim so often, it lost all meaning."

4. in previous messages i've sent, i explained how i fixed these issues for myself in particular, i'll rehash them. I had used DDU to remove any traces of old nvidia drivers and reinstalled new clean drivers which fixed the full system crash.

tl;dr
don't be misleading, disingenuous, and dismissive when your go to response is to immediately jump to "hardware failure" when someone reports a full system crash without a bsod when evidence points to anything but hardware failure.

I did the same things to find the fault, I don't remember if it is the exact same code, but for me my gpu driver was trying to access uninitialized memory. I fixed it by completely wiping my drivers with ddu and then reinstalling. The AMD clean install button didn't do a clean enough install apparently hahaha.

yup both nvidia and amd's "clean install" option isn't actually a clean install at all.

[TRAPPUSSY]

I am now on day 30 of trying to fix this issue with NVLDDMKM and truly have tried countless things. The only thing that has made any real difference was downgrading from my 4090 to an 3060 TI.
I am not overclocking, I've tried underclocking and XMP/DOCP has made no difference. I truly have no idea what to do left and am unsure If I can RMA my Zotac 4090 as I bought it on Ebay originally in 2022.