- Jun 30, 2004
- 16,530
- 1,973
- 126
I could post this in the "Games" forum of "Software."
Here's the history of it -- I've been doing web-searches and all I find are people who complain about the game's occasional behavior with no resolution or identification of the problem. Forum posts usually end with "When is Codemasters going to issue an update revision?"
The "game" is both game and simulator. An example of a simulator is a flight-simulator that doesn't let you bomb any buildings or dog-fight AI fighters. A game allows you to compete against other AI race-car drivers, but your video-perspective is "outside" the car. The game is both game and simulator if you can put yourself into the driver's seat -- as with Assetto Corsa or by pressing the "T" key on GRID2.
And the problem game is GRID2. The game occasionally shows a momentary freeze -- stuck video and audio -- which resumes but causes the user to lose control of his vehicle. "REcoveries" are possible, but best to be speeding down a straight highway.
I've been monitoring this with AfterBurner monitor.
The card is OC'd so that with VSYNC "On" and other settings appropriate to the game (with help of NVidia GeForce Experience game-optimization), the core frequency will sustain itself at 2,038 Mhz, occasionally reaching 2,063 or 2,050. The VRAM OC is +452 or -- as DDR -- 8,904 Mhz.
Looking at the monitor, at the time these freezes happen, the core clock drops momentarily to 1,531 Mhz and voltage to somewhere just north of 0.800V. But operating the game at 2,038 Mhz, you'd see the voltage bounce around in the vicinity of 1.093V as a maximum.
So I tried setting the card to default -- base clock of 1,531 Mhz and memory of 4,005 Mhz or DDR 8,010.
Since the boost clock at default will take the core just north of 1,900 Mhz, I might see the clock on the monitor-history as rock-solid ~1,938, and the same -- DAMN THING -- happens. Again, this is occasional, and for the most part the game / simulator is an adrenalin rush.
But I cannot figure out what the game is doing with power states to make this happen. You could say "well, maybe it's throttling!" The power level never exceeds the 112% setting of the AfterBurner profile, and the default is of course 100% which it also never exceeds, showing the mid 90's %.
Maybe it's just the GRID2 and a bug. On the other hand, I posted in this forum to see if there were insights from graphics-savvy folks.
Here's the history of it -- I've been doing web-searches and all I find are people who complain about the game's occasional behavior with no resolution or identification of the problem. Forum posts usually end with "When is Codemasters going to issue an update revision?"
The "game" is both game and simulator. An example of a simulator is a flight-simulator that doesn't let you bomb any buildings or dog-fight AI fighters. A game allows you to compete against other AI race-car drivers, but your video-perspective is "outside" the car. The game is both game and simulator if you can put yourself into the driver's seat -- as with Assetto Corsa or by pressing the "T" key on GRID2.
And the problem game is GRID2. The game occasionally shows a momentary freeze -- stuck video and audio -- which resumes but causes the user to lose control of his vehicle. "REcoveries" are possible, but best to be speeding down a straight highway.
I've been monitoring this with AfterBurner monitor.
The card is OC'd so that with VSYNC "On" and other settings appropriate to the game (with help of NVidia GeForce Experience game-optimization), the core frequency will sustain itself at 2,038 Mhz, occasionally reaching 2,063 or 2,050. The VRAM OC is +452 or -- as DDR -- 8,904 Mhz.
Looking at the monitor, at the time these freezes happen, the core clock drops momentarily to 1,531 Mhz and voltage to somewhere just north of 0.800V. But operating the game at 2,038 Mhz, you'd see the voltage bounce around in the vicinity of 1.093V as a maximum.
So I tried setting the card to default -- base clock of 1,531 Mhz and memory of 4,005 Mhz or DDR 8,010.
Since the boost clock at default will take the core just north of 1,900 Mhz, I might see the clock on the monitor-history as rock-solid ~1,938, and the same -- DAMN THING -- happens. Again, this is occasional, and for the most part the game / simulator is an adrenalin rush.
But I cannot figure out what the game is doing with power states to make this happen. You could say "well, maybe it's throttling!" The power level never exceeds the 112% setting of the AfterBurner profile, and the default is of course 100% which it also never exceeds, showing the mid 90's %.
Maybe it's just the GRID2 and a bug. On the other hand, I posted in this forum to see if there were insights from graphics-savvy folks.
Facebook
Twitter