It's much better to use ram-checking software to check for faults in ram instead of running games. You could rule out your new hardware better by running mdsched.exe (part of Windows), and picking the first option to test the ram.
I'm quite sure no faults will be found. If so, could you check if reverting back to the old ram-stick fixes the issue?
If yes, please tell us it's exact type and manufacturer - I want to buy one, as I'm troubleshooting random crashes since release, and nothing posted on this forum helped so far. I feel the only possible fix I've yet to try is changing random hardware elements.
Good evening developer fellow! Love your game, keep up the good work!
I have spent some evenings troubleshooting the spikes of low performance and crashes too. Kinda tried everything that was suggested on this forum in the past weeks (and undid them to prevent the solution-ideas from interfering).
Crashlogs always seem to point to "PhysX3_x64.dll". Here is the most recent one with 0 / 0 ragdolls on low quality and cloth physics turned off:
(fresh win10 install, all drivers are updated)
I have tried various recent (and some very old) Nvidia drivers with and without their PhysX component installed. Awalys did clean installs with DDU. It didn't help.
The "-useallavailablecores" launch parameter fixed all my performance issues regardless of visual settings quality, but it still crashes every 10-20 minutes.
Setting bDisablePhysXHardwareSupport= to False in BaseEngine.ini allowed me to turn on ragdolling and cloth physics without noticeable performance impact, so I could enjoy all the lovely dismemberment. Doing so didn't seem to affect crash frequency.
(I didn't use these options to produce the above log, but the error at the end looks exactly the same when I do)
Got some more ideas what to try?
I added -useallavailablecores to my launch options and I haven't had any lag since then. Please try that :)
I added -useallavailablecores to my launch options and I haven't had any lag since then. Please try that :)
I struggled with troubleshooting the stuttering and crashes for a week. I tried every bloody thing anyone could ever think of. This one didn't just eliminate my crashes, but my performance skyrocketed!
Five finished matches and counting, zero issues!
I could barely finish a game before!
And crashed on the 6th game. Stability seems to be improved, but still not flawless.
The eight most recent crashlogs are stored in %localappdata% - \Mordhau\Saved\Crashes.
There are a few things you could check:
Many complain about ragdolling and other physics calculations. Setting ragdoll count + stay time to 0, and disabling cloth phisics may improve the situation (but won't fully fix the issue in my experience).
Some reported audio-issues causing the very same. Set all sounds to 0 to rule it out. You may wanna fiddle with audio drivers, disable every unused devices if it turns out to be your problem.
Others crash for mere performance issues. Does it also happen if you play with potato-graphics?
I'm no expert, but I have a slight suspicion that PhysX being disabled in the ingame config files has something to do with the issue. See for yourself in SteamLibrary\steamapps\common\Mordhau\Engine\Config\BaseEngine.cfg
You'll find the line:
As an NVIDIA user, setting that to False improved my performance noticeably. Let me know if it does the same for you - or if it causes any issues for you - there must be some reason it was off in the first place.
I was doing an extensive troubleshooting of this very issue for four days. I summarized my efforts in this post.
That's day 5 for me, and I have run out of ideas besides replacing random hardware - that I can't really afford right now - or waiting for a relevant patch. That reminds me, do you happen to have a Geforce 10 series GPU without a high-end CPU?
I contacted some players with this issue, and they all had GTX 1050-60-70-80. I contacted some players with such GPUs and no issues, and they all had i7 processors.
My theory is that as Mordhau doesn't support PhysX, all ragdolling, cloth and falling items has to be calculated by the CPU, and that is quite demanding. Manually enabling PhysX in the config files isn't the best idea - the game's binaries only seem to contain a PhysX3 SDK from 2015. Though googling says that modern CUDA-cores should support that version. Dunno.
Sadly, my efforts could only eliminate the visual glitches, but not the crashing. The crashlogs are still full of warnings about skeletal meshes and illegal transformations By the way - you said you don't see your logs as you don't get to the reporter. You can still find them in %localappdata% \Mordhau\Saved\Crashes.
At this point, I decided to only play duel and team-dm before I can afford some hardware to rule out my suspicions with.
You said you updated your driver, but your logs say it's 430.39.
The newest is 430.64.
It doesn't matter if I play with the lowest settings, everything turned off, or on Ultra. I get crashes regardless.
CPU and memory utilization shows no issues, no sudden spikes or drops happen before the crashes. Nothing ever goes above 50% on potato settings.
Neither the GPU shows abnormal activity before the crashes. Here's a sensor log, it happens at 15:23:05. Nothing unusual before, and a quite usual wind-down as the process freezes and the crash reporter comes up.
(best to download it, as it's very wide and google wraps it in a silly way)
And the log from the reporter:
System and game is on SSD. Fresh Windows install for troubleshooting. Newest shiny drivers (430.64 again - after I tried a few old ones to see if it fixes the issue. Yes, I used DDU and safe mode to shuffle them around). Steam, Discord overlays are off, never installed Gefoce Experience. Ruled out sound issues by disabling all sound-hardware, their drivers, and ingame sounds. Tested some UT4 engine friendly Nvidia Control Panel settings I found on some Fortnite-forum. Tested RAM and VRAM. Stress-tested the system for hours in 3D Mark (no crash there).
I smell PhysX.
When I started, I had these visual artifacts:
I did the same as Mr Brzęczyszczykiewicz above - disabled ragdolling and cloth. It fixed the glitches, but not the crashes.
Later I found that PhysiX hardware support is disabled in the config files, so I turned it on instead. It didn't fix the crashes, but now I could turn back the glorious ragdolling and cloth!
In case some NVIDIA(!!!) users want to experiment with it, it's in BaseEngine.ini in SteamLibrary\steamapps\common\Mordhau\Engine\Config. bDisablePhysXHardwareSupport should equal False.
I still can't complain! A crash takes 10-30 minutes to happen, so it's the most fun troubleshooting-process I ever had!
I'm troubleshooting the same issue for days. I'm no rookie at this, but I feel I ruled out everything I could think of. I suspect the GPU - many of those who wrote about mid-game crashes (and could be bothered to specify) seems to be using GTX 10 series cards - mine is a 1060 6gb.
Today is the day when I'll approach the great wise monks who live on the nvidia forum. Wish me luck.
I'm posting my finding is this thread (as it already has a lot of good troubleshooting ideas I have ruled out):
In case I find anything that is.
I'm troubleshooting for a different matter (random irregular crashes midgame), and found something that will probably help you:
PhysX is disabled in the game's configuration files. I enabled it yesterday. (GTX 1060 6gb user here) It didn't fix my crashing issue, but it fixed some ragdolling-glitches I could only circumvent previously by turning it off ingame. Now I have working cloth physics too.
If you decide to do the same, keep in mind that there may be a good reason the devs turned it off.
DO THIS AT YOUR OWN RISK! If you experience -any- kind of issues after enabling it, undo it! I didn't.
Locate the BaseEngine.ini file in your game's install directory, at some location like c:\SteamLibrary\steamapps\common\Mordhau\Engine\Config. Find the line "bDisablePhysXHardwareSupport=True", change True to False. Save, start the game, tell us if it works for you too!
3D Mark didn't help. I tortured my comp with hours of the most complex stress-testing, I didn't manage to force out a crash from it.
Yes, I have seen your earlier comment, but that doesn't help me either - my PC don't have a factory default option, but I did make a system restore point after all Windows-components, drivers, Steam, Dirext-X and the vcredists that Mordhau needs was installed (and nothing else). I'm still having crashes at that point.
I believe you had some irrelevant software related issue that restore fixed. Or I'm deeply mistaken.
But I browsed trough dozens of crash-related threads on this forum. Those who get random infrequent ingame crashes - also often graphical artifacts that BOHWulfhelm described (and could bother to tell us their specs) seem to be having Geforce 10 series cards (GTX 1050-60-70-80). I sense a pattern here.
Maybe I should try my luck at the Nvidia forum. The geek feels strong in there.
Another GTX 1060 6 GB user here, having crashes. I'm troubleshooting for a while, as one has to play a lot of Mordhau in the process.
I started (the second day of troubleshooting) with a clean W10 install, with only the bare minimum to run Mordhau. Updates, drivers, Steam, direct-x, the game, the only vcredists it needs. When I mention Nvidia drivers later, I always mean clean installs, after removal of the previous with DDU in safe mode. Only the driver, no GeForce Experience or other additions (except of course when troubleshooting the HD audio driver and PhysX).
So far I have ruled out:
Performance issues Game runs fine on max, random crashes also happen on the most potato ingame settings too.
Sound-related issues. Game runs fine with all audio-devices disabled (and all drivers meticulously removed, ingame sounds muted), random crashes still happen.
PhysX related issues. Game runs fine without PhysX installed (and PhysX + CUDA calculations sent to the cpu by nvidia control panel). Turning off ragdolling, cloth animations, and every slightly relevant settings didn't help, random crashes still happen.
Nvidia driver issues I tried various older drivers, starting from the days gtx1060 6gb was released, and from every quarter-year after that. No improvement (or visible performance decrease) with 'em.
The GPU doing something visibly fishy I used TechPowerUp GPU-Z to monitor and log many readouts while playing. All values look normal, well within the expectable range. No spike or drop happens the second before the crash and the drop following it is also normal.
I'm running out of ideas where to look. My prime suspect is still the GPU, but which tiny little aspect of it? My next idea is digging into the the depths of 3D Mark, trying to reproduce the issue in the most sterile and monitored environment I can think of.
I'll post if I find something.
Welcome the newest member of the community: Quetra
37 users were active in the last 30 minutes:
Paravox SkyCaptain Pankila BreadSticks KILLORBEKILLED5 Donald Trump Magiktako gloup Quetra hehhh ToLazy4Name CurrentlySeizing Rusmus urm Ser_Thank_You MrGuarnere Atlas-D Bexton Makozer Cence CatR lox228333 DuckSauce TheDankestMeme Gambit PinkerStinklage das Deadmode DrGert Beautiful Brexit Boy LuxCandidus Treusturm smug Fürst von Butz Cynath Romul smellycathawk