Lurk
Active member
I admit I'm a little stubborn, but there are a few reasons that lead me to think the second card is fine and the problem lies with the game itself and/or probably also the fact that it runs on Steam, which brings me to reason number one:
1) after thoroughly searching, I found out that there has been a problem in the past with Steam games running on FX CPU's. An undocumented fix was released quite a while ago (search "Orochi-CEG"). The problem possibly existed in a faulty code in 990 mobos bioses, was supposedly fixed in more recent ones, yet it remains unknown whether each company selling FX compatible mobos has actually released a fix or a fixed bios alltogether.
I did try the undocumented fix, but I still cannot tell if it's actually working. I'll explain why in reason 3.
2) Been running a whole bunch of games with Crossfire support, some pumped at Eyefinity resolutions with max settings (Alien: Isolation, Elite: Dangerous and The Talos Principle) without a single hitch, crash or sign of a second card malfunctioning.
3) Most importantly, I came around a method that seemingly fixes crashing in Shadow of Mordor, and the method applied leads me to think the game suffers from some kind of memory leak or similar bug (btw, a fix for SoM memory leak leading to crashes on SLI systems was recently released. It did nothing for my Crossfire setup).
The method involves using a utility by Techie007 that adds a right click option to folders so their entire content can be cached to RAM. It can also be launched with a few basic command lines through a link pointing to the folder that needs caching.
It fills up all available RAM with the content of the folder. The presence of the files cached in RAM can be easily verified with a utility such as RAMmap from sysinternals.com.
While the 40+ Gb's of the SoM folder definitely exceed my onboard 8 Gb's, using this method has so far allowed me to play through long sessions of the game without any crashes. I can't swear it fixes the problem completely in the long run, but it certainly delays it in time to a point I can finally play and exit the game when I've had enough, without my system going nuts (blue screens, freezes, etc...) i.e I haven't had a crash since, whereas before this method I couldn't play for half an hour straight.
I only wish that payed developers would take a bit of their time to solve such annoyances so that I could enjoy games I've payed for without having to tinker with game-breaking nuisances like this myself.
Hope this blabber can be useful for others.
1) after thoroughly searching, I found out that there has been a problem in the past with Steam games running on FX CPU's. An undocumented fix was released quite a while ago (search "Orochi-CEG"). The problem possibly existed in a faulty code in 990 mobos bioses, was supposedly fixed in more recent ones, yet it remains unknown whether each company selling FX compatible mobos has actually released a fix or a fixed bios alltogether.
I did try the undocumented fix, but I still cannot tell if it's actually working. I'll explain why in reason 3.
2) Been running a whole bunch of games with Crossfire support, some pumped at Eyefinity resolutions with max settings (Alien: Isolation, Elite: Dangerous and The Talos Principle) without a single hitch, crash or sign of a second card malfunctioning.
3) Most importantly, I came around a method that seemingly fixes crashing in Shadow of Mordor, and the method applied leads me to think the game suffers from some kind of memory leak or similar bug (btw, a fix for SoM memory leak leading to crashes on SLI systems was recently released. It did nothing for my Crossfire setup).
The method involves using a utility by Techie007 that adds a right click option to folders so their entire content can be cached to RAM. It can also be launched with a few basic command lines through a link pointing to the folder that needs caching.
It fills up all available RAM with the content of the folder. The presence of the files cached in RAM can be easily verified with a utility such as RAMmap from sysinternals.com.
While the 40+ Gb's of the SoM folder definitely exceed my onboard 8 Gb's, using this method has so far allowed me to play through long sessions of the game without any crashes. I can't swear it fixes the problem completely in the long run, but it certainly delays it in time to a point I can finally play and exit the game when I've had enough, without my system going nuts (blue screens, freezes, etc...) i.e I haven't had a crash since, whereas before this method I couldn't play for half an hour straight.
I only wish that payed developers would take a bit of their time to solve such annoyances so that I could enjoy games I've payed for without having to tinker with game-breaking nuisances like this myself.
Hope this blabber can be useful for others.
Last edited: