No expert, but it does seem to me to be a result of the codingI am an expert so I'll have a bash as the balloon has apparently gone up and the natives are getting restless.
For now, SLI should be disabled if there's any sign of graphics corruption. SLI/Crossfire mode can be tricky, I've had SLI or Crossfire since Voodoo2 and while it is gorgeous there can be some (eventually solvable) problems
I'm running a 285 Warbirds and your problem looks to be drivers with only a screenshot to go on.
You should use the Driver Cleaner, Driver Sweeper whatever mate and get the latest WHQL drivers, re-install them once you have a machine free of perhaps broken drivers
Start out at absolutely minimum settings in RoF once your graphics card drivers are installed, crank up the goodness only when you have trouble-free rendering. Try running RoF in a window and fullscreen. If this problem is seen at very low graphics settings I would be surprised, this might mean a bad card or broken drivers
The pinkness means that RoF code cannot find the textures it needs. The pinkness is a standard colour, used to indicate to the programmer that textures are not found/broken. Like in Il-2 when we make a skin but get it wrong
How one program can make it seem that the problem is the program:-
Suppose you get a game that uses large amounts of memory for the textures. It uses more memory for the textures because there are more and bigger textures than you're seeing in the other games you're playing
Now suppose that there's a fault in your graphics card hardware, the top end of memory cannot be addressed properly and you see graphics problems like this. How to test this (uncommon) fault...
Substitute another graphics card, use onboard graphics etc. The substitution test. This may give clues by eliminating from suspicion things that might have been going wrong
If I swapped the current violet-textures card for another card and the problem goes away, what can I deduce? Something wrong with the card I took out obviously. Perhaps, but one still has that lingering worry about memory addressing on the suspect card.
Now I- lower RoF settings to bare minimum, I still have the problem
-run applications that stress the card to max the graphics out, still the problem, problem not seen, still the problem back in RoF
-clean out the drivers, (I) re-install the drivers, still the problem
-check that no other program is stealing either system RAM or local RAM (on the graphics card) while RoF is running
-do not run the Mission Editor at the same time as RoF as this is known to cause the 'snow terrain' or other artifacting
-now getting more desperate, (I) swap memory sticks in case one of them is faulty when it comes to be used in big-graphics applications. Memory just sits there normally if not in use: only when it comes to be used do you see a problem
-observe that this does not look like overheating, when I would expect artifacts (odd triangles or squares jittering around, or perhaps a grid-like overlay
-run CPU-ID to monitor CPU and GPU temperatures just in case
http://www.cpuid.com/hwmonitor.php-check D3D is working ok by reinstalling the latest runtime DirectX drivers
Now I re-install RoF. Sometimes the order of installing drivers and applications can affect things. Install graphics card drivers first then a game, problems. Install a game then install drivers, problems can be fixed
"I know all that I am not a tourist!"
Well why are you asking then

Ming