EDIT *** Going back to Cat 12.6 fixed the issue. Thanks to Thilan for providing the information for me.
Just wanted to share an issue I came accross. As most know here, I am not partial to any GPU vendor. I decided to grab a 7970 Ghz edition. Great card, no problems with the exception of a title I picked up during the steam sale.
Lord of the Rings - War in the North. First of all, the game is awesome. It is a shame that it gets such a low rating. With the lack of true co-op games out there, this seemed like it would score higher and would be more popular. Me and my son love it.
Second, once I hit Carn Dum (near the end of the game) I encountered a few consistent crashes. At first I just figured it was a glitch, maybe some dust in the fan, maybe my clocks are too high... So, I cleaned it out, rebooted. Same thing. About every 10 seconds on the level or so, I get the AMD Display Driver stopped responding, screen goes blank for 5 seconds and comes back and the game runs fine for another 10 seconds, rinse repeat. However, it will eventually crash... Addtionally, when this happens any network client is kicked out of the game.
So, I updated to the latest drivers, turned down all the settings. Underclocked graphics card and CPU, still the problem did not get any better. Frustrated, I eventually made it past the section of the game that causes this (there are other sections, but it seems random and non repeatable) and was able to beat the game with no more problems.
So, I decided to look this up and found that basically a ton of people (mainly with AMD/ATI) have this issue and it appears to be only AMD/ATI based graphics cards. Many frustrated users such as myself experience this game-breaking bug. Some even RMA'd their graphics cards only to receive a new one and have the same issue.
So, Snowblind said it the issue with AMD and forwarded the issue to their driver team, but a forum user posted that they contacted AMD and said nothing was in the works and they were not aware of any issues. So Snowblind (dev) points the finger and AMD and AMD states they don't even know there is an issue with it.
TLDR - If you have an AMD card, better look elsewhere, this game won't play well for you. I am thinking about putting my 480 GTX back in my rig until I have finished playing this game. Which may be a while. And I wouldn't expect a fix, both Snowblind and AMD were made aware of this issue back in 2011... and the official response by Snowblind is this is an AMD issue and that was statement was made in March of 2012. Bummer. My 7970 is flawless in every other game I play.
Although I don't write drivers, it is my opinion that the issue is with AMD, and not the gave dev. 'AMD Driver Stopped Responding' seems to be point to AMD, IMO.
-Carm Dum = 5 minute section (ends up being 20 minutes with all the suttering) you may never get past because if the display driver stops responding, you have (on my system) a 10% chance to crash the game itself, where it will set you back to your first waypoint, thus... You might not ever get past Carn Dum.
-This will also happen randomly through other areas of the game, but it is not generally repeatable and pretty rare.
** Taking bets on who will be the first person to say "I have play this game hundreds of hours on my AMD 7970Ghz with no issues, must be your computer" **
- Google War In the North Suttering AMD or ATI and find the wealth of information regarding the topic....
Just wanted to share an issue I came accross. As most know here, I am not partial to any GPU vendor. I decided to grab a 7970 Ghz edition. Great card, no problems with the exception of a title I picked up during the steam sale.
Lord of the Rings - War in the North. First of all, the game is awesome. It is a shame that it gets such a low rating. With the lack of true co-op games out there, this seemed like it would score higher and would be more popular. Me and my son love it.
Second, once I hit Carn Dum (near the end of the game) I encountered a few consistent crashes. At first I just figured it was a glitch, maybe some dust in the fan, maybe my clocks are too high... So, I cleaned it out, rebooted. Same thing. About every 10 seconds on the level or so, I get the AMD Display Driver stopped responding, screen goes blank for 5 seconds and comes back and the game runs fine for another 10 seconds, rinse repeat. However, it will eventually crash... Addtionally, when this happens any network client is kicked out of the game.
So, I updated to the latest drivers, turned down all the settings. Underclocked graphics card and CPU, still the problem did not get any better. Frustrated, I eventually made it past the section of the game that causes this (there are other sections, but it seems random and non repeatable) and was able to beat the game with no more problems.
So, I decided to look this up and found that basically a ton of people (mainly with AMD/ATI) have this issue and it appears to be only AMD/ATI based graphics cards. Many frustrated users such as myself experience this game-breaking bug. Some even RMA'd their graphics cards only to receive a new one and have the same issue.
So, Snowblind said it the issue with AMD and forwarded the issue to their driver team, but a forum user posted that they contacted AMD and said nothing was in the works and they were not aware of any issues. So Snowblind (dev) points the finger and AMD and AMD states they don't even know there is an issue with it.
TLDR - If you have an AMD card, better look elsewhere, this game won't play well for you. I am thinking about putting my 480 GTX back in my rig until I have finished playing this game. Which may be a while. And I wouldn't expect a fix, both Snowblind and AMD were made aware of this issue back in 2011... and the official response by Snowblind is this is an AMD issue and that was statement was made in March of 2012. Bummer. My 7970 is flawless in every other game I play.
Although I don't write drivers, it is my opinion that the issue is with AMD, and not the gave dev. 'AMD Driver Stopped Responding' seems to be point to AMD, IMO.
-Carm Dum = 5 minute section (ends up being 20 minutes with all the suttering) you may never get past because if the display driver stops responding, you have (on my system) a 10% chance to crash the game itself, where it will set you back to your first waypoint, thus... You might not ever get past Carn Dum.
-This will also happen randomly through other areas of the game, but it is not generally repeatable and pretty rare.
** Taking bets on who will be the first person to say "I have play this game hundreds of hours on my AMD 7970Ghz with no issues, must be your computer" **
- Google War In the North Suttering AMD or ATI and find the wealth of information regarding the topic....
Last edited:
Facebook
Twitter