Dual channel is a hardware design concept to increase the speed of memory.
I would recommend removing the 2Gb memory and trying again.
I would recommend removing the 2Gb memory and trying again.
-
-
My ancient desktop with Gigabyte motherboard can accept different-sized RAM sticks, even on a single channel. However, they recommended that for best performance both sticks on a channel should be the same size and timing. The slowest one will set the speed for the channel. So, when I first built it, I had 2 newly-bought 2GB sticks on one channel, and 2 older, slower 1GB sticks on the other. It worked OK, since I rarely did anything that pushed memory usage over 4GB (still rarely happens). Later replaced the 1GB with matched-spec 2GB on the second channel so now I have 8GB total all the same size & speed. That last is the ideal, but check your system documentation - things might more flexible if you're willing to compromise performance a bit.
EDIT: I just looked at those log files, and there's no way OR could be causing the crash absent something wrong with the hardware. It's only using (I think, looking near the end), 8-10 MEGABYTES (not GB) of RAM - even if all those usages are supposed to be added up for total used, it's only about double that. Also, even though it worked for me to have different-sized sticks, it's very motherboard-dependent; I'd pull the 2GB stick out and try again - most likely, you'll get all of the bigger one showing up. If that happens:
- get a stick that matches the first one for size and timing, and install that.
- make sure virtual memory is turned on and that Windows is managing it.
Then try again.
EDIT2: those disks are still too full. Virtual memory needs some disk space to work with. Address the disk space issue - buy another disk for C: and keep it clean (not more than 2/3 used).Last edited by mikeebb; 03-06-2018, 15:27.Comment
-
So I tried running it with just the one 8gb RAM stick and it still crashed. Once I get some extra money, I'll invest in some new RAM that match one another. OR ran fine with the 2/3 full disk space up until recently but I'll invest in a new SSD when I get some extra cash as well.RyanComment
-
So I got new RAM and installed it with the other, but then my system just started beeping and wouldn't show anything. I found that both RAM sticks were incompatible with each other despite having the same specifications. I then tried running OR with just the one new stick and it still crashed. I think I'm just going to give up on OR for the time being as it's not worth spending all this money on one thing when I do not have issues with anything else.RyanComment
-
Hi Ryan,
It's very, very unlikely that your problems are directly attributable to Open Rails! It could be because OR pushes your memory harder than your other software, and has found a weakness.
Not only must the RAM sticks be compatible with each other, they must also be compatible with your motherboard; you may need to make changes in the BIOS.
Cheers,
GedComment
-
Both RAM sticks work fine on my motherboard individually, but not together. OR has worked fine on my system up until last week when I booted it up again after about a one month hiatus and there were no updates to OR during that time so I know it's not OR. I found that it works just fine on my laptop so until I can invest in rebuilding/getting a new computer, I'll play it on that.RyanComment
-
Just a small update, I managed to get OR running without a crash on my system, but at the cost of turning off the sound. Could this also be the result of my apparent memory issues?RyanComment
-
That is a good pickup.
In the past, if the number of sounds was too high, it would crash MSTS, but I have not noticed any bugs with respect to OR.
Can I suggest that you update your sound drivers and try again.
What hardware is doing your sound?Comment
-
It looks like updating my sound card (Soundblaster X-fi Titanium BTW) solved my issue. Thanks for the help you guys.RyanComment
Comment