- Ambient Wars Creator
Join Date: Oct 2009
I experienced that and it was because I had my system to close to the edge. I removed all OC across the system and it became stable then I bumped them to reasonable levels and it remained so.
What you are describing is the last command executed by AW. It complete its tick events and therefore complete all commands associated with it but died before it ticked again. That's not AW, or very likely not. Worth a shot.
To be more specific, GTA-4 is one of the most system grinding games ever. Those types of games can certainly uncover hardware on the edge. Take that and add on even more stress with multiple AW work threads interacting with the core game through functions in large bursts in the span of milliseconds repeatedly. If the system is on the edge this will push it over. I had my i7-975EE 4@4 on the edge as well as my QSLI 2x295's. AW pushed it over that edge. But relaxing the OC a bit on all 4 GPU and the FSB made everything perfectly stable again. So what I suggested above is from direct personal experience and it's why it is in the troubleshooting file that has been in the AW 2010 package since v126.96.36.199 (initial release)
Since I'm back out of state again continuing my contract I'm on a slower (but nice) portable which is not on the edge in any way so I see zero of these issues. It's just slower overall but that's what settings are for
Last edited by Ironhide; 08-22-2010 at 06:54 PM..
|Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)|