Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
4 
Report this post
So, based on that that some part of the engine isn't working properly, it would be a very specific part of it (as you can still load and play the game for a very limited time).
If a part of the game is causing the crash, then the most obvious thing would be to check the integrity of the game files. But I suspect you've already tried that too...
Is there any strange behavior within the game right before it crashes? (e.g. map view tries to reload 2-3 times, like the video driver is starting over again or something else)
Personally, I haven't been confronted with something like that in MudRunner before (except overheating of some hardware components, then the game also closes abruptly). Therefore it would be very helpful, if you could list, what you exactly already tried... (To exclude some possibilities and not to start over from the beginning.)
Right now I'm out of ideas, if you really tried everything...
Nope, not really no. It just plays like it normally does, but as soon as i press the start engine it crashes. All other buttons (brake, diff lock, and all of the button works, except the start engine button). I tried verifying game integrity today but it still verifies like no files corrupted (all normal).
I have tried
The weirdest thing is, i tried to backup the game from this computer and restore it on my other computer Steam, it just works normally... (the one having problem was using Intel 12th gen i5-1240p with Iris Xe) and the other computer (which works normally) is an Intel 2nd gen i5-2320 with GeForce GTX 560.
Yes! Same.. I used to play MudRunner on Epic Games for hours and hours long until there's some problem on the crossplay then i bought it again on Steam. It works normally at that time. But not sure why i can't play it now... Is it possible that my current Windows version and build doesn't support something from the games?
Mods would have been the next thing I would have considered. You already mentioned you disabled (not only unsubscribed) all of them - so, there were also mods that didn't come from the Steam Workshop or third-party tools have been used? They could already have modified game files, even if deleted afterwards. This would actually indicate a solution via integrity check of the game files (or that files were replaced with their original state during the check that has been carried out already).
Testing on a second computer also always is a good approach, but in this case not all changes have been applied (and restored), like on the problematic system. This means that the same basis hasn't been created on the 2nd computer and is therefore only of limited relevance. But it's certainly a good method for ruling out some things and indeed could lead to the solution.
So, you already played the Steam version of the game 27 hours or does it refer to the Epic Games Store version? And does the Epic Games Store version still work on the computer where the problem with the Steam version occurs or does it also crash?
Yes! The Vehicle Engine hahaha. I'm sorry if i wasn't so clear about "engine". I meant that everytime i press the start vehicle engine button it crashed.. I can hear the engine starting but when the engine started it instantly crashed. But weirdly when it crashed i can still hear all of the other sounds normally, just i can't continue playing it.
I don’t have any 3rd party mods and never used 3rd party tools. Also, i did a full reinstall of MudRunner several times, so i think i can safely assume it’s not regarding the game files integrity corruption or something.
Nope, the Epic Games’s version also crashes like the Steam version does.
But the weird thing is, the Epic’s version crashes without the “Sorry MudRunner crashed. Please relaunch the game” error. It just force closes.
Also, i tried downloading the cracked version and it also crashed (exactly at the same thing).
Now, when I tried the normal Steam version, it didn't generate any dumpfiles. Just the log.txt (because of pressing shift and play button). But the MudRunner beta version from Steam, the normal version on Epic and the cracked version of MudRunner at least generates some dumpfiles unlike the normal Steam’s version.
When i opened the dumpfiles with Visual Studio 2022, the dump summary contains some info such as:
When i see this i thought, maybe it was Windows Security's memory integrity core isolation protection thing that caused this, so i tried disabling it and restart, turns out it was still doing it. Also tried Windows Memory Diagnostic (to test if it was my RAM that's faulty) and found there are no errors.
Because the logs.txt didn’t give any meaningful info for me, I’m starting to look at the Windows Event Viewer. I don't know if it's connected with the MudRunner crash or not but I see entries about “APPCRASH” everytime MudRunner crashes. This is the event viewer log when it crashes:
and these:
So because i thought that EpicGamesLauncher was causing the error, I uninstalled EpicGamesLauncher. Now whenever it crashes, it just doesn't generate any logs on event viewer🤦♂️
Starting to believe maybe MudRunner isn’t compatible with something in this computer, i suspect the Iris Xe Graphics or the 12th gen Intel Core i5.
Currently my solution is just… not installing MudRunner on this computer and installing it on my other working computer, then use Steam Remote Play to play from it. At least now i can play it though haha😁
If anybody needs my full specs: here:
Does the Windows username contain any non-latin letters?
Or does the path where the files Config.xml and ShaderCache.sdc are needed (C:\Users\[your Windows username]\AppData\Roaming\SpinTires MudRunner for the Steam version / C:\Users\sh1N3br5veK84sun\AppData\Roaming\MudRunner for the Epic Games Store version) have any kind of write protection?
Yes! That's what i'm suspecting too.. I guess there's something about my build of Windows that just didn't play nicely with MudRunner. I searched about "Intel 12th gen MudRunner crash" on Google, Bing and Copilot and I didn't find any meaningful result. So it's not the CPU compatibility maybe(?) and more of a "Windows" incompatibility. I'm currently using Windows 11 Home Insider Dev build 26120.1542 ge_release (It's the newest build as of today).
Nope, I logged in to Windows using my Microsoft email so it used my name as the username "darre".
If what you meant was file permission then sure, it does have the appropriate permission. I'm logged in as Administrator and i checked the permission, i have Full Control(Read, Write, Modify, Execute permission) so i guess it's not that.
I don't think it's Windows itself, but you are right - we don't know and therefore can't rule it out. If the two computer systems you have also differ in their Windows version, it might be worth trying to back up the current version with a system image and test an older Windows version. Maybe save an OS image and do a fresh Windows + MudRunner installation comparing both computer configurations? Or if strange things or a crash occur even with a fresh installation (with as little additional software as possible, only the most necessary things), you could, in my opinion, narrow it down to that software or actually to the hardware.
Personally, I don't know how it works with the Windows login creating a user profile, but if the paths are all fine with latin letters only, we can rule out this approach.
Generally, software should work properly without forcing the user to login as admin (in any case, you should only allow isolated directories or write permissions under certain circumstances). But even for this attempted solution, we now know that it wasn't the right approach.
Previously, I've tried to update the drivers through Intel Driver & Support Assistant but it couldn't find a new one, and I tried not to download the drivers manually from the Intel website since I'm using a Laptop (and laptop driver tends to have some OEM customization), I checked my laptop manufacturer website, and the last update is still on 31.0.101.5081_36862, then I decided to just try download the newest driver manually from the Intel website.
(This is the Intel drivers website for Iris Xe and Arc Graphics)
https://www.intel.com/content/www/us/en/download/785597/intel-arc-iris-xe-graphics-windows.html
(This is for the OEM customization on laptop article)
https://www.intel.com/content/www/us/en/support/articles/000096252/graphics.html
Turns out, you can update the drivers manually and not lose custom-OEM software if you not clean-install the driver. I tried to use the normal one, and now my drivers is up to date. Now MudRunner launches and plays normally. Hope it helps you guys.
So, have fun in the mud!
If all the other solutions and approaches mentioned in the discussions are also not working I'm out of ideas, sorry.
Hi, im wondering if you know whats the solution to my problem. so I've downloaded mudrunner a few weeks ago and played fine, but today my game started to show weird glitching effects. i tried to record my gameplay when glitching, but the glitching doesnt appear in the video. i thought it was my GPU dying, but when i tried other games it works like a charm. i wonder if you have any solution to this as I dont have the time to fully factory reset windows 11 and update driver from ground up
Regarding your request... that's indeed a strange behavior. Personally, I've never experienced anything similar. Maybe somebody else has already faced or was confronted with the same problem. But I doubt it's widespread as I've never come across something similar in Steam discussions and on other platforms, as far as I can remember. And you've tried all the things mentioned in the technical support (overview) already? What makes me a little suspicious is the fact that the unwanted effects were not recorded. You can try screenshots instead or just take a picture of the whole display, if you want to share that thing.
So, maybe you should consider whether it might be wiser to set up your machine after all... With an OS image you can just work around such troubles in the future. It's time-consuming at first, but saves a lot of time later on. Strange things happen to a computer system from time to time, which you often no longer have to solve if you have a working system backup.
However, if you want to discuss your problem, please create a new topic (or use an existing one, if there's already something on this), as we are already off topic and spamming the others.