Another Crashing Thread

[Nezu]

Turning to the forms because Ive been on a trip with crashing and Monster Hunter Wilds and I have reached a point where I'm genuinely stuck.

Latest DxDiag https://pastebin.com/NBzuvirR
Latest CrashReport https://pastebin.com/tqWq1M73
minidump.dmp analysis https://pastebin.com/eQPuzSr6

PC Specs
cpu:Ryzen 9 5900x
gpu: Radeon™ RX 7900 XTX GAMING OC 24G
ram: 4x16 64gb G.SKILL Ripjaws
board: ROG CROSSHAIR VIII Dark Hero

-Whats going on:
Basically at this point I can start the game; start hunts, but can't complete a hunt as I'll get a crash about half way through any hunt about 95% of the time. I'm struggling to determine root cause because the CrashReport doesn't point to a specific error (Windows Last Error : 0x0000000000000000 Message : *nothing*).

-Run down of what was tried:
Note* this list is incomplete because I'm not a QA game tester so this may be all over the place and Ive tried probably more things than I can remember to list; ill start from what seemed most promising.

https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664

In the guide above did tips 1-11 as notated. 12-13 skipped; use Edge and OneDrive for work from time to time

14-Slammed my settings to the ground, running settings on lowest and especially dropped things like shadow quality, bloom ect to either low or disabled if possible for the sake of seeing if I can halt crashes.

I found the latter half of the guide wasn't too applicable in my usecase from what I could see as I dont use REframework and the game is un-modded and I'm running an RX 7900XTX so the nvidia dlss i've paid no mind to. Whats left for me to try is to upgrade to windows 11 and try the Dstorage update item.

I looked at the minidump.dmp and found that it pointed to ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. Historically folks have pointed to bad memory or a bunch of different things, but I haven't seen any solution specific to MHWilds.

I also wanted to rule out power issues so Ive upgraded my PSU to an NZXT 1200w supply and really dont want to buy much more hardware than that because I cant justify it for a game ive purchased twice and have also bought a Geforce now sub for ^^; as a work around.

Additionally, in the AMD Adrenaline software I've set the max clock to 2200mhz, power limit -10 because last patch it seemed to help, but since the last patch it doesn't seem to matter.

I feel like there has got to be something I'm missing in these diagnostics and reporting, any help would be greatly appreciated.

[Aldroen]

I have the same Mobo as you and same GPU. Though I am on Linux so cant speak to much on Windows end of things but here are some things I did to help me stabilise the MHW.

You might need to bump your RAM voltage as that board and Asus overall likes to run the voltages on lower end with the XMP profiles. For example my RAM is rated at 1.35V and the board would be pushing 1.345 so I bumped it manually to 1.355 so it stays at 1.35.

Second thing check if CSM is off in bios as from some reason that was enabled on my board preventing re bar from working. If it was off and re bar enabled try disabling re bar.

And last thing try setting your VRAM frequency to be at is default max (Not overclock) and see if that helps.

[Omega X]

From what I understand the game code has a pointer error or a run away memory leak. When it references that part of the memory, its not there and it crashes.

I've found that most of my crashes happened in the Guardian area. I also found that clearing the Shader Cache has made the game more stable. But it still crashes eventually with the same pointer error.

The only other game that I've seen that had random issues like this sometimes is Helldivers 2. And its usually after they issue a content update.

[アンジェル]

Originally posted by Nezu:

Another Crashing Thread
Turning to the forms because Ive been on a trip with crashing and Monster Hunter Wilds and I have reached a point where I'm genuinely stuck.

Latest DxDiag https://pastebin.com/NBzuvirR
Latest CrashReport https://pastebin.com/tqWq1M73
minidump.dmp analysis https://pastebin.com/eQPuzSr6

PC Specs
cpu:Ryzen 9 5900x
gpu: Radeon™ RX 7900 XTX GAMING OC 24G
ram: 4x16 64gb G.SKILL Ripjaws
board: ROG CROSSHAIR VIII Dark Hero

-Whats going on:
Basically at this point I can start the game; start hunts, but can't complete a hunt as I'll get a crash about half way through any hunt about 95% of the time. I'm struggling to determine root cause because the CrashReport doesn't point to a specific error (Windows Last Error : 0x0000000000000000 Message : *nothing*).

-Run down of what was tried:
Note* this list is incomplete because I'm not a QA game tester so this may be all over the place and Ive tried probably more things than I can remember to list; ill start from what seemed most promising.

https://steamcommunity.com/sharedfiles/filedetails/?id=3436896664

In the guide above did tips 1-11 as notated. 12-13 skipped; use Edge and OneDrive for work from time to time

14-Slammed my settings to the ground, running settings on lowest and especially dropped things like shadow quality, bloom ect to either low or disabled if possible for the sake of seeing if I can halt crashes.

I found the latter half of the guide wasn't too applicable in my usecase from what I could see as I dont use REframework and the game is un-modded and I'm running an RX 7900XTX so the nvidia dlss i've paid no mind to. Whats left for me to try is to upgrade to windows 11 and try the Dstorage update item.

I looked at the minidump.dmp and found that it pointed to ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. Historically folks have pointed to bad memory or a bunch of different things, but I haven't seen any solution specific to MHWilds.

I also wanted to rule out power issues so Ive upgraded my PSU to an NZXT 1200w supply and really dont want to buy much more hardware than that because I cant justify it for a game ive purchased twice and have also bought a Geforce now sub for ^^; as a work around.

Additionally, in the AMD Adrenaline software I've set the max clock to 2200mhz, power limit -10 because last patch it seemed to help, but since the last patch it doesn't seem to matter.

I feel like there has got to be something I'm missing in these diagnostics and reporting, any help would be greatly appreciated.

You did great. Take that praise. It is genuine for sharing all relevant information to help you troubleshooting the issue.

What I like to know in addition:

did it work before?

you using ISLC as described?

have you checked if the issue persists with XMP/EXPO in your BIOS disabled?

Your DxDiag report is showing an error which reminds me strongly of a typical Nahimic error in the past.

I like you -just in case- to use the system repair commands as admin via terminal

sfc /scannow
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /Online /Cleanup-image /AnalyzeComponentStore
DISM.exe /Online /Cleanup-image /StartComponentCleanup
chkdsk /f /r

Pay attention if any of the commands give a positive result - positive as in, something is faulty at the time. If it does, share a new DxDiag report afterwards.

[Zeric]

Yesterday, I was getting guaranteed crashes upon file loading. Today, I updated REFramework nightly, which is seemingly an essential mod to make this game even run as I had a list of other issues back when I was trying to play without it. Today, it crashes 100% of the time on quest loading! I can run around the map just fine, fight, slay, capture, no issues, but the second that I try to select a quest and load it up, the game crashes instantly. This is unacceptable Capcom. You can count yourself lucky that I am past the cut off point for a refund.

[アンジェル]

Originally posted by Zeric:

Yesterday, I was getting guaranteed crashes upon file loading. Today, I updated REFramework nightly, which is seemingly an essential mod to make this game even run as I had a list of other issues back when I was trying to play without it. Today, it crashes 100% of the time on quest loading! I can run around the map just fine, fight, slay, capture, no issues, but the second that I try to select a quest and load it up, the game crashes instantly. This is unacceptable Capcom. You can count yourself lucky that I am past the cut off point for a refund.

You using mods. You are on your own. Capcom is not to blame for you corrupting game files.

[Nezu]

Originally posted by アンジェル:

did it work before?

you using ISLC as described?

have you checked if the issue persists with XMP/EXPO in your BIOS disabled?

Your DxDiag report is showing an error which reminds me strongly of a typical Nahimic error in the past.

I like you -just in case- to use the system repair commands as admin via terminal

sfc /scannow
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /Online /Cleanup-image /AnalyzeComponentStore
DISM.exe /Online /Cleanup-image /StartComponentCleanup
chkdsk /f /r

Pay attention if any of the commands give a positive result - positive as in, something is faulty at the time. If it does, share a new DxDiag report afterwards.

First, I appreciate everyone's quick responses; Im going to try the tweaks @Aldroen mentioned and also do the above, as I haven't in a bit and its a good place to start.

To answer the questions; I had problems on initial game release and after a week, found that limiting max freq. and adjusting power settings in the Adrenaline software solved my issues for a time. I was able to get alot of hours in without any crashes at all. Once patch 0005 or whatever we currently are on came out I was boned.

Also, I am still running with ISLC as describe in the guide.

My testing and crashing has been done with XMP off and whatever overclock I had on any of my hardware I removed shortly after release because I had such a hard time and haven't re-applied anything since.

Ive also updated my drivers to 25.3.2 but that didn't seem to help

[KMNODY]

https://steamcommunity.com/app/2246340/discussions/0/501693985385919083/

also i noticed in your logs many of your drivers have unknown fields, have you tried wiping your drivers and re-installing them?

I would prioritise checking your systems OS integrity, making sure you have at least 32G virtual memory set up on your game drive, and verifying your drivers are good. If all of that is good you can try to edit the game config file and change the cram settings to 0 and see if that works.

This is exactly what i was thinking by the way but they beat me to it.

Originally posted by アンジェル:

sfc /scannow
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /Online /Cleanup-image /AnalyzeComponentStore
DISM.exe /Online /Cleanup-image /StartComponentCleanup
chkdsk /f /r

Pay attention if any of the commands give a positive result - positive as in, something is faulty at the time. If it does, share a new DxDiag report afterwards.

Changing your BIOS settings for ram acceleration also has a chance of working but that would normally only work if you have a registry corruption that can not be detected or fixed, in this case i would recommend a windows reinstall.

[アンジェル]

Originally posted by Nezu:

Originally posted by アンジェル:

did it work before?

you using ISLC as described?

have you checked if the issue persists with XMP/EXPO in your BIOS disabled?

Your DxDiag report is showing an error which reminds me strongly of a typical Nahimic error in the past.

I like you -just in case- to use the system repair commands as admin via terminal

sfc /scannow
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
DISM.exe /Online /Cleanup-image /AnalyzeComponentStore
DISM.exe /Online /Cleanup-image /StartComponentCleanup
chkdsk /f /r

Pay attention if any of the commands give a positive result - positive as in, something is faulty at the time. If it does, share a new DxDiag report afterwards.

First, I appreciate everyone's quick responses; Im going to try the tweaks @Aldroen mentioned and also do the above, as I haven't in a bit and its a good place to start.

To answer the questions; I had problems on initial game release and after a week, found that limiting max freq. and adjusting power settings in the Adrenaline software solved my issues for a time. I was able to get alot of hours in without any crashes at all. Once patch 0005 or whatever we currently are on came out I was boned.

Also, I am still running with ISLC as describe in the guide.

My testing and crashing has been done with XMP off and whatever overclock I had on any of my hardware I removed shortly after release because I had such a hard time and haven't re-applied anything since.

Ive also updated my drivers to 25.3.2 but that didn't seem to help

I wish you good luck with the tweaks - based on your descriptions we are slowly reaching the point, where running "mdsched" via run / memtest is to be advised.

Though the audio driver issue is still bothering me. And seeing that resolved would be nice too.

[Tatsuyo]

same here, but now i can't make the game past 1/3 of initial optimization bar.

[Nezu]

I was just now able to play a few complete hunts after doing the following and haven't had a crash yet.

In BIOS
-Confirmed D.O.C.P enabled
-Ram voltage was 1.35000; I set it to 1.35500
-Confirmed that re bar was enabled in BIOS, disabled re bar

In Windows
-sfc /scannow
-DISM.exe /Online /Cleanup-image /Scanhealth
-DISM.exe /Online /Cleanup-image /Restorehealth
-DISM.exe /Online /Cleanup-image /AnalyzeComponentStore
-DISM.exe /Online /Cleanup-image /StartComponentCleanup
-chkdsk /f /r

and then power-cycled again and now it seems to be working better than it has historically. Im still on low settings but it seems functional.

DxDiag is still showing those Audiosrv issues; not sure how I will get rid of that. While I was doing this I also recall that I did not update the drivers for my actual monitors so those are the things that are probably showing as unknown/generic pnp monitors.

The game seems to be working which is the best I can hope for at the time being; hopefully in the future or maybe when they ease up on the DRM I can boost the settings and get more mileage out of the 7900xtx I'm using.

Thanks all who suggested fixes.

[KMNODY]

Originally posted by Nezu:

I was just now able to play a few complete hunts after doing the following and haven't had a crash yet.

In BIOS
-Confirmed D.O.C.P enabled
-Ram voltage was 1.35000; I set it to 1.35500
-Confirmed that re bar was enabled in BIOS, disabled re bar

In Windows
-sfc /scannow
-DISM.exe /Online /Cleanup-image /Scanhealth
-DISM.exe /Online /Cleanup-image /Restorehealth
-DISM.exe /Online /Cleanup-image /AnalyzeComponentStore
-DISM.exe /Online /Cleanup-image /StartComponentCleanup
-chkdsk /f /r

and then power-cycled again and now it seems to be working better than it has historically. Im still on low settings but it seems functional.

DxDiag is still showing those Audiosrv issues; not sure how I will get rid of that. While I was doing this I also recall that I did not update the drivers for my actual monitors so those are the things that are probably showing as unknown/generic pnp monitors.

The game seems to be working which is the best I can hope for at the time being; hopefully in the future or maybe when they ease up on the DRM I can boost the settings and get more mileage out of the 7900xtx I'm using.

Thanks all who suggested fixes.

Glad to hear you are able to get a few hunts in, personally because i am below specs for the game i can only get a hunt or two then i need to shut down the game to allow my GPU to cool.

In regards to the unknowns i was mentioning there is a few actual system drivers that i saw with unknown variables mostly for files. Still if you see that it and experiencing problems it does not hurt to try a fresh install.

[Waddle Dee]

Tried the BIOS and command prompt instructions in this thread, except for whatever D.O.C.P is, and the RAM voltage was 1.60000, and for a while I thought it fixed my graphics driver crashes as neither Wilds nor WoW (the only two games that caused driver crashes) crashed for several hours, but then Wilds crashed. Not sure what to do now.

[アンジェル]

Originally posted by Waddle Dee:

Tried the BIOS and command prompt instructions in this thread, except for whatever D.O.C.P is, and the RAM voltage was 1.60000, and for a while I thought it fixed my graphics driver crashes as neither Wilds nor WoW (the only two games that caused driver crashes) crashed for several hours, but then Wilds crashed. Not sure what to do now.

I do not recommend trying anything out random without checking the basics first.

[Waddle Dee]

Originally posted by アンジェル:

I do not recommend trying anything out random without checking the basics first.

I understand that, but I did try out most of the other steps beforehand, like clean driver install, repairing Wilds, changing monitor refresh rate, and removing my second monitor to see if that'd help. I'll make a new post with the dxdiag and stuff shortly, and I'll link to it here.

[アンジェル]

Originally posted by Waddle Dee:

Originally posted by アンジェル:

I do not recommend trying anything out random without checking the basics first.

I understand that, but I did try out most of the other steps beforehand, like clean driver install, repairing Wilds, changing monitor refresh rate, and removing my second monitor to see if that'd help. I'll make a new post with the dxdiag and stuff shortly, and I'll link to it here.

Feel free to add the list of things you did as well. I am always interested what people have first in mind and why they try things like that.