TPU's WCG/BOINC Team

[Mydog]

Good to see so many dedicated people her
I tried to get the it-dep at my work to install WCG but everything is outsourced to HP and they say NO
Got 8 more cores coming online today but the last rig with the 3960X will not be on before Monday, it's LN2 time for it this weekend

Still need some code help to get Boinc to run in Ubuntu(Linux) so if anyone have the time and knowledge it will be much appreciated.

[Paulieg]

OK. After several weeks of crunching just my wifes office 1055T; my 2500k, FX-6100, and 555BE (unlocked to quad) will be back online this weekend. Time to get those numbers back up.

[Chicken Patty]

Great news!

[Radical_Edward]

It looks like my Workstation has started turning in packets.

[Chicken Patty]

Chicka Chicka yeahhhh!!!

[Paulieg]

Originally Posted by Paulieg

OK. After several weeks of crunching just my wifes office 1055T, my 2500k, FX-6100, and 555BE (unlocked to quad) will be back online this weekend. Time to get those numbers back up.

Originally Posted by Chicken Patty

Great news!

2500k and FX-6100 are now running 100%, along with the 1055T. I'll have the unlocked 555BE
running 4 cores by Saturday. If I could find a cheap Thuban, I'd grab it and give another WCG team member the 555be. If anyone finds one cheap, LMK.

[Radical_Edward]

I'm building the CruncherX4 now, should have it crunching tonight. If not, tomorrow.

Edit: Looks like tomorrow, forgot to bring home a DVD drive and a power cord. d'oh!

[Chicken Patty]

Thanks guys for your efforts! 3 million here we come!!!!

[Mydog]

Finally got the last 2600K running here but only on stock speed cause it crashes on all clocks above. I think it's either the mobo (P8P67-m PRO) or the CPU so I'm gonna test the CPU on another mobo tomorrow

[Chicken Patty]

I've been having lots of BSOD's lately. Trying one last thing, if that doesn't work I'm going to have to shut down WCG and start testing components. All started since I got my new RAM. So I'll start by there.

[Radical_Edward]

Originally Posted by Chicken Patty

I've been having lots of BSOD's lately. Trying one last thing, if that doesn't work I'm going to have to shut down WCG and start testing components. All started since I got my new RAM. So I'll start by there.

Memtest time.

[Chicken Patty]

Yea, that's next.

Originally Posted by Chicken Patty

I've been having lots of BSOD's lately. Trying one last thing, if that doesn't work I'm going to have to shut down WCG and start testing components. All started since I got my new RAM. So I'll start by there.

Do you use Intel Burn Test? If you set it on max and you don't BSOD, then it's not the memory or the CPU. You need to terminate any background apps so you can give it more memory. The problem with the max setting, especially if you have a lot of memory, is that it will smoke your CPU so you have to watch the temps. I've noticed that a single run takes a lot longer the more memory you give it access to and as a result, it tends to push temps to their absolute max.

[Chicken Patty]

Originally Posted by twilyth

Do you use Intel Burn Test? If you set it on max and you don't BSOD, then it's not the memory or the CPU. You need to terminate any background apps so you can give it more memory. The problem with the max setting, especially if you have a lot of memory, is that it will smoke your CPU so you have to watch the temps. I've noticed that a single run takes a lot longer the more memory you give it access to and as a result, it tends to push temps to their absolute max.

No, I haven't tried IBT on it yet. I did a standard run for the Gflops thread on here, but that wasn't long enough I'm sure. It BSOD's like every two days. I just dropped the clock because I think that since I'm running more RAM now the CPU might need a little bit more vcore to be stable. So dropping the clock should fix the issue if that was the case.

[KieX]

Originally Posted by Chicken Patty

I've been having lots of BSOD's lately. Trying one last thing, if that doesn't work I'm going to have to shut down WCG and start testing components. All started since I got my new RAM. So I'll start by there.

Is that the P67? And what BSOD code?

Just because if it's 124, you should read this: http://www.overclock.net/t/1120291/s...-read-op-first

[Chicken Patty]

Originally Posted by KieX

Is that the P67? And what BSOD code?

Just because if it's 124, you should read this: http://www.overclock.net/t/1120291/s...-read-op-first

Awesome thread, going to read it right now and give the 4.5 GHz another go.


...and yes this is the combo I got from you Dan.

[Mydog]

I hope you're using SB mem Patty cause I just discovered that my mATX doesn't like any old 1366/1156 mem, crashed in IBT with three different sets so I put in some G.Skill quad channel and it runs fine. Passing IBT max mem at 4,6GHz CPU and 2133mhz mem.

[Chicken Patty]

Originally Posted by Mydog

I hope you're using SB mem Patty cause I just discovered that my mATX doesn't like any old 1366/1156 mem, crashed in IBT with three different sets so I put in some G.Skill quad channel and it runs fine. Passing IBT max mem at 4,6GHz CPU and 2133mhz mem.

Yeah, my RAM Kit is designed for SB.

[Chicken Patty]

Do you guys have Spread Spectrum enabled or disabled?

[KieX]

Originally Posted by Chicken Patty

Do you guys have Spread Spectrum enabled or disabled?

http://img.techpowerup.org/120120/Capture064.jpg

Spread spectrum disabled. Best thing is to go into BIOS and select the Load Optimized defaults. Then with that OCN guide should be able to reach a stable clock without 124. I had that combo on Auto OC, which is 4.4GHz.

I'm gonna find out what the Asus cover is, just in case you wanna RMA it for a new one.

[Chicken Patty]

Originally Posted by KieX

Spread spectrum disabled. Best thing is to go into BIOS and select the Load Optimized defaults. Then with that OCN guide should be able to reach a stable clock without 124. I had that combo on Auto OC, which is 4.4GHz.

I'm gonna find out what the Asus cover is, just in case you wanna RMA it for a new one.

Thanks but I don't think that'll be necessary.

Ever since I got it from you I had it running at 4.5 GHz without an issue. But I had made some tweaks once I got my new RAM trying to push the RAM and I don't think I saved my settings. But I went ahead and made a few changes after reading the guide over at OCN so we'll see how it behaves now. Running at this for now.

[KieX]

Originally Posted by Chicken Patty

Thanks but I don't think that'll be necessary.

Ever since I got it from you I had it running at 4.5 GHz without an issue. But I had made some tweaks once I got my new RAM trying to push the RAM and I don't think I saved my settings. But I went ahead and made a few changes after reading the guide over at OCN so we'll see how it behaves now. Running at this for now.

http://img.techpowerup.org/120120/Capture065012.jpg

Cool you know how to find me if need be.

If it's with RAM settings, try raising the VCCIO a step or two as it could help. BSOD 124 is a pain with SB. The 2600K I had at work ran fine for 6 months before I got a 124 in the middle of a (*&%$!) presentation!

[Chicken Patty]

Originally Posted by KieX

Cool you know how to find me if need be.

If it's with RAM settings, try raising the VCCIO a step or two as it could help. BSOD 124 is a pain with SB. The 2600K I had at work ran fine for 6 months before I got a 124 in the middle of a (*&%$!) presentation!

After reading the guide and the thread over at OCN that was one of the few changes I made this last boot. Raised VCCIO to 1.150v I believe it was.

[F150_Raptor]

Originally Posted by Chicken Patty

No, I haven't tried IBT on it yet. I did a standard run for the Gflops thread on here, but that wasn't long enough I'm sure. It BSOD's like every two days. I just dropped the clock because I think that since I'm running more RAM now the CPU might need a little bit more vcore to be stable. So dropping the clock should fix the issue if that was the case.

If your running more ram than before when it was stable, you need up the cpu vtt. If your not comfortable with upping it any more or you have it maxed out at 1.45, raising the qpi pll will allow you to run a lower cpu vtt. For most of my rigs, I set the vtt at 1.375 and raise the qpi pll until it stablizes itself. IBT is good for checking stability and temps, but you always have to tweak some voltages here and there after running wcg or F@H. They put the real stress on it.

[Chicken Patty]

Originally Posted by F150_Raptor

If your running more ram than before when it was stable, you need up the cpu vtt. If your not comfortable with upping it any more or you have it maxed out at 1.45, raising the qpi pll will allow you to run a lower cpu vtt. For most of my rigs, I set the vtt at 1.375 and raise the qpi pll until it stablizes itself. IBT is good for checking stability and temps, but you always have to tweak some voltages here and there after running wcg or F@H. They put the real stress on it.

Will definitely keep that in mind if I get another BSOD. Keeping my fingers crossed.