Help with Multi GPU folding

[GTSRguy]

Problem resolved

just had to mess around w/ it a bit

thank you for your support, the response was overwhelming, i didnt get to read all the posts but thank you all

--------EDIT

This guide has got it working for me...so far

Multi GPU guide

If you follow that guide, make sure you do not check the box in client config that says "do NOT lock cores..."

 

[FaaR]

I don't think ~2 hours passing with no replies to your topic QUITE qualifies you for that level of acerbic sarcasm, buddy.

If you want people to help and advice you in the future, don't insult them alright? Not even in this underhanded fashion, it's simply poor sport.

 

[GTSRguy]

*sigh*

 

[GLeeM]

Glad you got it working

Eventually I am going to get another GPU for my rig ... I am thinking I'll need help too

 

[waffleironhead]

What was the problem and the solution? Might help future F@H users.

 

[GLeeM]

Did you have to Configure the second instance to a different MachineID?

 

[GTSRguy]

Thanks for the info Gleem, i had them the same, but just now changed them. Aparently changing them does this (quote from OC.net)

... I remember I kept getting the same projects on both cards at the same time. This stopped after I changed the machine ID numbers. "

 

[GTSRguy]

Some may notice ive been editing my messages 10 times a minute, thats becasue the situaiton keeps chaning...

right now, i uninstalled and deleted everything pertaining to F@h, and started again from scratch....right now everything seems to be working fine. Well see.

 

[GLeeM]

Just didn't want you crunching the same WU twice and only getting credit once!

 

[GTSRguy]

Right now im getting hit with NANs and UNSTABLE_MACHINE on both cards. I already deleted the work/que/WU folders and re-started the client, and it maybe folds 1 WU but then both cards end up doing the same thing. Cant even fold right now...uhhhggg


[18:33:10] + Working ...
[18:33:10] - Calling '.\FahCore_11.exe -dir work/ -suffix 03 -nocpulock -checkpoint 15 -verbose -lifeline 4728 -version 623'

[18:33:10]
[18:33:10] *------------------------------*
[18:33:10] Folding@Home GPU Core - Beta
[18:33:10] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
[18:33:10]
[18:33:10] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[18:33:10] Build host: amoeba
[18:33:10] Board Type: Nvidia
[18:33:10] Core :
[18:33:10] Preparing to commence simulation
[18:33:10] - Looking at optimizations...
[18:33:10] - Created dyn
[18:33:10] - Files status OK
[18:33:10] - Expanded 46646 -> 252912 (decompressed 542.1 percent)
[18:33:10] Called DecompressByteArray: compressed_data_size=46646 data_size=252912, decompressed_data_size=252912 diff=0
[18:33:10] - Digital signature verified
[18:33:10]
[18:33:10] Project: 5768 (Run 7, Clone 198, Gen 316)
[18:33:10]
[18:33:10] Assembly optimizations on if available.
[18:33:10] Entering M.D.
[18:33:16] Working on Protein
[18:33:17] Client config found, loading data.
[18:33:17] mdrun_gpu returned
[18:33:17] NANs detected on GPU
[18:33:17]
[18:33:17] Folding@home Core Shutdown: UNSTABLE_MACHINE
[18:33:20] CoreStatus = 7A (122)
[18:33:20] Sending work to server
[18:33:20] Project: 5768 (Run 7, Clone 198, Gen 316)
[18:33:20] - Read packet limit of 540015616... Set to 524286976.
[18:33:20] - Error: Could not get length of results file work/wuresults_03.dat
[18:33:20] - Error: Could not read unit 03 file. Removing from queue.
[18:33:20] EUE limit exceeded. Pausing 24 hours.


does that on every WU on each card^

 

[dajeepster]

reboot?
i'm pretty sure you've already done this though

 

[GTSRguy]

actually no, ill try that

 

[GLeeM]

Originally posted by: GTSRguy
Right now im getting hit with NANs and UNSTABLE_MACHINE on both cards.

What are your GPU temps?

Is it overclocked?

 

[GTSRguy]

no their not overclocked, and they are running at about 73C tops when folding

i restarted and ran F@H and im getting the same errors on both cards.

----

EDIT I followed the guide in post 1 exactly.... i checked "do not lock cores to specific GPU" i also checked the "allow something larger than 10MB"...im going to uncheck them and see if thats makes a difference...

 

[GLeeM]

I remember something about having to turn off SLI in order to get two clients working, at least with older drivers.

I think I read recently that with newest drivers SLI does not have to be turned off and two monitors are not needed.

Also, I seem to recall something about a switch or command to be added when starting the client.
Not sure exactly, something like: "-forcegpu " ? Not even sure what it does, but it might be a place to start looking.
Looks like it could be added into the "Additional Client Parameters" box on the Advanced tab of the Configure... dialog.

Sorry I can't help you more.

 

[GTSRguy]

i unchecked the box "do not lock cores to speicifc CPU" in the configure menu for the client.... ive been folding for sevral hours now and no problems. Ill check back tommaro and see if it continues to work.

This multi GPU stuff is hard, there are a million things that could be wrong, thanks for the tips

EDIT: Been folding for 24 hours with no problems on either card, the problem was i checked that stupid box in config

 

[Golgatha]

Originally posted by: GLeeM
I remember something about having to turn off SLI in order to get two clients working, at least with older drivers.

I think I read recently that with newest drivers SLI does not have to be turned off and two monitors are not needed.

Also, I seem to recall something about a switch or command to be added when starting the client.
Not sure exactly, something like: "-forcegpu " ? Not even sure what it does, but it might be a place to start looking.
Looks like it could be added into the "Additional Client Parameters" box on the Advanced tab of the Configure... dialog.

Sorry I can't help you more.

http://forums.anandtech.com/me...=2338818&enterthread=y

-gpu 0 -forcegpu nvidia_g80

-gpu 1 -forcegpu nvidia_g80


The -gpu 0 and 1 are for the cards in the primary and secondary slots. Also, you are right that SLI does not have to be disabled in the nVidia drivers.