View Stats:
Miasmata > General Discussions > Topic Details
Kai Nov 26, 2017 @ 9:24am
game crashes computer
Twice the game has crashed my computer and forced it to restart. (I'm using windows 10).
< >
Showing 1-5 of 5 comments
pawzisme Nov 26, 2017 @ 11:04am 
DarkStarSword may be able to help you on this
DarkStarSword Nov 26, 2017 @ 7:53pm 
Not sure how much I can actually help - I'm not one of the developers and have never experienced any crashes in this game myself so I can't exactly investigate what causes them.

Try "verify integrity of game files" in Steam or searching the forums for solutions that may have helped others.

Someone did report that installing the community patch (see the sticky) made the game more stable, which was not one of its goals, but is possible since it does fix some bugs (those bugs didn't cause crashes for me, but it it concievable they might have for others).

We would also need to know more details of your system to have any chance of reproducing this (Go into Steam's Help menu -> System Information -> Right Click -> Copy all text to clipboard -> paste it here).
Last edited by DarkStarSword; Nov 26, 2017 @ 7:54pm
Kai Nov 26, 2017 @ 8:11pm 
Hi, here's my system info.
also, I tried downloading the patch, but when I try to install it it says "main.rs5" isn't found. (I can see the file in the miasmata folder though)
thank you for helping.

Computer Information:
Manufacturer: Gigabyte Technology Co., Ltd.
Model: Z170X-UD3
Form Factor: Desktop
Touch Input Detected

Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
CPU Family: 0x6
CPU Model: 0x5e
CPU Stepping: 0x3
CPU Type: 0x0
Speed: 3504 Mhz
4 logical processors
4 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Supported

Operating System Version:
Windows 10 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0

Video Card:
Driver: NVIDIA GeForce GTX 1070
DirectX Driver Name: nvldumd.dll
Driver Version:
DirectX Driver Version:
Driver Date: 10 27 2017
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: NVIDIA GeForce GTX 1070
VendorID: 0x10de
DeviceID: 0x1b81
Revision: 0xa1
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 23.62" x 13.39" (27.13" diag)
60.0cm x 34.0cm (68.9cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 8191 MB
Supported MSAA Modes: 2x 4x 8x

Sound card:
Audio device: LG Ultra HD-8 (NVIDIA High Defi

RAM: 8141 Mb

UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 113045 Mb
Largest Free Hard Disk Block: 34446 Mb
OS Install Date: Dec 31 1969
Game Controller: None detected
VR Headset: None detected

DarkStarSword Nov 26, 2017 @ 11:02pm 
Originally posted by Kai:
also, I tried downloading the patch, but when I try to install it it says "main.rs5" isn't found. (I can see the file in the miasmata folder though)
The patcher gets the path from the Windows registry, so that error might suggest the game isn't installed properly. You should still be able to click browse and manually tell it where Miasmata is installed.

Video Card:
Driver: NVIDIA GeForce GTX 1070
I think I saw someone else mention they were having a problem with running Miasmata on a 1070 recently, so maybe there's something to this. I'm not sure why that would be - the game only needs DX9 and this card is more than capable of that (assuming that there are no hardware faults of course, but if there are you are likely to experience crashes in a range of games).

FWIW I'm currently on 2x GTX 980 in SLI, but haven't run Miasmata much on this computer - I was mostly using my laptop when I was playing Miasmata, which has a single GTX 680m in it, and never experienced any of these crashes then.

Driver Version:
DirectX Driver Version:
I think that's 388.13 in NVIDIA terms, which is the same one I'm currently running - but I'm only running it because of Windows 10 forced an update on me again.

I did take the liberty of skimming the 388.13 feedback thread looking for reports of crashes (there were a fair few, but that is not unusual). One suggestion that jumped out at me since I know it's helped with some with other Windows 10 issues as well:
Go into Windows 10 settings, under Gaming, turn off Game Bar and turn off Game Mode.

Another suggestion I spotted was to downgrade to 385 (385.69?), which someone reported more stable in Wolfenstein 2.

I also saw someone quote 384.76 as being the last stable driver for The Division.

Someone also suggested blacklisting any crashing games from using gsync (I'm not actually sure if DX9 games can use gsync - I don't have a gsync monitor, so can't test).

The feedback thread for this driver version is here - I only skimmed this, I could have missed some other suggestions: https://forums.geforce.com/default/topic/1027519/geforce-drivers/official-388-13-game-ready-whql-display-driver-feedback-thread-released-10-30-17-/

I do a lot of 3D Vision modding, and I can tell you that recent drivers are quite often full of bugs, and the forced driver updates that Windows 10 introduced are a major headache for this (we often have to tell people to use specific driver versions, and very often when someone says one of our mods stopped working it is because Windows forced a driver update on them) - it is always best to use DDU to completely uninstall the NVIDIA driver and install a known working version from geforce.com, and if something goes wrong check the version number to see if Windows forced another update.

I haven't been gaming much lately and can't personally vouch for any of the recent drivers - when I was last active 373.06 was the last known working driver for ABZU with 3D Vision + SLI, and only exactly version 384.76 had decent performance in WATCH_DOGS2 with 3D Vision + SLI.

Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
That is a fairly high resolution, and it is possible the game might be struggling because of that. It might be worth trying the game on 1920x1080 for a while to see if it improves stability. I think I recall seeing someone else experiencing crashes note that they had to have their desktop resolution and the game resolution matching, so worth trying that as well.

Sound card:
Audio device: LG Ultra HD-8 (NVIDIA High Defi
Interesting - you're running audio over HDMI? That is usually ok, but I have on occasion had stability problems with that configuration (I suspect it was driver bugs, but I'm not aware of any current ones), so if you have another option it might be worth trying just to rule that out as a possibility - I doubt it will make a difference, but you never know.

RAM: 8141 Mb
That's pretty small for Windows 10 - I don't know if it would do anything for your current problem but I would suggest looking into a RAM upgrade at some point, at least doubling that to 16GB or go all the way to 32GB if you can afford it (My Windows 10 system is currently consuming 10GB of RAM while just idle running Steam, Firefox and a handful of background apps - with only 8GB that would force it to use the page file, and Microsoft seems to have some pretty severe regressions in their paging code in Windows 10, that in some cases can lead to crashes or hangs). I was getting out of memory errors with only 16GB RAM on Windows 10, despite the fact that Windows had allocated a 50GB page file and should have been able to cope (but I was compiling UE4 at the time - 16GB is probably sufficient for most normal use).
Last edited by DarkStarSword; Nov 26, 2017 @ 11:09pm
Kai Dec 1, 2017 @ 1:12pm 
Hi thanks a lot for all the information/suggestions. after posting this I ran into the same issue with a few other games, so i'll need to look into it a bit more.
< >
Showing 1-5 of 5 comments
Per page: 15 30 50

Miasmata > General Discussions > Topic Details