Windows SMP Client, general troubleshooting

[ThunderRd]

That's why I run the backup routine I posted in another thread. Then I can rollback and start again. Has worked nearly all the time.

[Strongwolf]

I'm using an AMD 4200x2 @ 2.57 (by now). I think I'm going to use Toro's recommendation a leave it as a shortcut. Wolf1 (AMD 4000) and Wolf2 run 24/7 unless I'm messing with the hardware (which is not rare).

[Strongwolf]

So far this SMP thing is looking good. It's start OK every time I double click the shortcut. So,... I was not suppose to OC from the start?? Well, to late for that now. @2.64 and planning on push it up until...Let's hope it don't happens.

[Strongwolf]

Although I use Ctrl + C to close SMP when I restart it it says that there has been "8 inappropriate terminations". Suppose I'm doing something wrong; what is it?

[ThunderRd]

After it tells you that, does the client start up and show the correct percentage? If so, ignore it. It's just the beta client being fussy.

If the cores don't start properly, post again and let me know.

[Strongwolf]

Yes, it start in the same percentage and keep working from that point up. I'll just ignore it.

[SteveI]

Careful with overclocks. The memory & CPU are both very highly stressed while folding, and the SMP core is very sensitive. If the WU has a lot of progress, let it go until it completes... Last thing you need is to have the core dump the WU @ 99% due to an overclock problem.

[Samuknow]

I put this up on the F@H front page. This is some good info here.

Front Page

[Strongwolf]

Maybe I'm dancing with the devil but I keep OCing this thing with SMP and all. Don't have much choice. Necorum is breathing down my neck. So far no problems. If worse case scenario happens I will cry aloud and post it here for your amusement. Now @2.73

[Strongwolf]

@2.80

[Strongwolf]

Well...it's happens. Lost a WU (62%) @ 2.8. Whaaaaaa,Whaaaaa, Whaaaaa.
That's it. Needless to say I would do it again. Maybe a little more power to the CPU.

[smiffy]

What voltage are u using Strongwolf?Also what motherboard?
Also try slackening Max Async Latency and Read Preamble Time under memory timings
Smiffy

[Strongwolf]

Using an Asus A8n-SLI Deluxe; V core 1.392 actually @ 2.58 using 2Gb of pc3200 generic ram and a 4200+x2 AMD cpu.

What do you mean by "slackening Max Async Latency and Read Preamble Time"? Lowering them? I usually don't mess much with memory (not much knowledge about them). Only change from 2.5T or 2.0 to 1T or vice versa. Willing to learn and I always do my home work.

[Strongwolf]

These are my options under DRAM Config for the Asus:


Name========= Actual Value

CAS# Latency (tcl).......................................[3]

Min Ras# active time (tras).............................[7t]

RAS# to CAS# delay (trcd).............................[3t]

Row Precharge Time (trp)...............................[3t]

Row Cycle Time (trc).....................................[16t]

Row Refresh Cyc Time (trec)...........................[18t]

Read to Write Time (trwt)...............................[4t]

Write Recovery Time (twr)..............................[3t]

1t/2t Memoty Timing......................................[2t]

S/W DRAM Over 4G Remapping.........................[enabled]

H/W DRAM Over 4G Remapping.........................[enabled]

[Necorum]

wolf you go smp i go smp on my rigs then

[Necorum]

3 rigs smp client now

tomorrows agenda list overclock

[Necorum]

smp rigs - they use smp til needed for other things then run the regular f@h single core client

[Strongwolf]

Do you know how to use it???

[Necorum]

yes its done

[smiffy]

Originally Posted by Strongwolf

Using an Asus A8n-SLI Deluxe; V core 1.392 actually @ 2.58 using 2Gb of pc3200 generic ram and a 4200+x2 AMD cpu.

What do you mean by "slackening Max Async Latency and Read Preamble Time"? Lowering them? I usually don't mess much with memory (not much knowledge about them). Only change from 2.5T or 2.0 to 1T or vice versa. Willing to learn and I always do my home work.

Hi Strongwolf
download AMD64 info
http://avala.yubc.net/~lukija/A64Info-beta.exe
and see what the max Async Latency and read preamble are
Slackening is raising the time eg moving MAL from 8ns to 10ns.
Smiffy