Optimising i7 970 + GTX 480 SLI

[scaryjim]

Odd that Queelis: the only thing I can think is that either: CS:S tries to lock itself to a core and picked one that was bound to the folding client, or that CS:S relies on timely communication between threads and that having 3 cores heavily loaded and one idle was somehow messing that up. I know some older games have problems with thread timing etc (the original Neverwinter Nights is almost unplayable on quad core systems without setting a start parameter that binds the affinity to a single core), but I'm surprised that you've had problem just because another program had affinity set up...

[Queelis]

Odd that Queelis: the only thing I can think is that either: CS:S tries to lock itself to a core and picked one that was bound to the folding client, or that CS:S relies on timely communication between threads and that having 3 cores heavily loaded and one idle was somehow messing that up. I know some older games have problems with thread timing etc (the original Neverwinter Nights is almost unplayable on quad core systems without setting a start parameter that binds the affinity to a single core), but I'm surprised that you've had problem just because another program had affinity set up...

If it had picked a FAH-loaded core, the folding simply would've ground to a halt, but not the game go slow - that can't be it.

Maybe I'll try that again, might be only a temporary glitch. *hope*

[Tattysnuc]

Definitely food for though gents.

How can I see what points have been submitted by which rig in HFM.NET? Any ideas?

Also, to add some other angles to the BSOD codes, here's another source that seems to support the information I've already referenced in a prior post:

(taken from http://forums.pureoverclock.com/show...9265#post69265)

CODE SOLUTION
0x101 more vcore
0x124 increase or decrease QPI/VTT first, if not increase or decrease vcore. Test to see which one it is. On i7 45nm, usually means too little VVT/QPI for the speed of Uncore. On i7 32nm SB, usually means too little vCore
0x0A unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E increase vcore
0x3B increase vcore
0x3D increase vcore
0xD1 QPI/VTT, increase or decrease as necessary, can also be unstable Ram, raise Ram voltage. Try one solution at a time to isolated the real cause.
0x9C QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 Not enough or too Much memory voltage
0x116 Low IOH (NB voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E Corrupted OS file, possibly from

[Tattysnuc]

Something else I found says this regarding BSOD and overclocking...

BSOD CODES:
Here is a list of Common BDOS Errors and what to do to get rid of them; these suggestions are from trial and error, and many BDOSes from hundreds of hours of overclocking. I have gotten many of these BDOSes and checked them out (tried to cause them) and I have modified that list, here it is.
BSOD Codes
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
"0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances"
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage

I'll compile into one doc, validate and then put together a guide I think...

[Queelis]

Update on the affinities: when I removed fahcore's affinity from Core 2 instead of Core 0, the game played very smoothly, no lags whatsoever. Maybe it's that all the idle processes are with the Core 0, so when a game loads on it it's laggy? God knows, but it's a great solution for gaming. You only lose one core of folding (i.e. the PPD stays at 3/4ths of normal).

Thanks again Tatty

Edit: tried on CS:S (which is very undemanding) and on Assassin's Creed II (which is fairly recent). Both work fine with the affinity unselected from Core 2.