• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

New nVidia core.

T

Tigerbiten

[H]ard|DCer of the Month - February 2007/January 2
Joined
Sep 24, 2002
Messages
5,028
From the FF ............

No showstoppers were found during the beta testing of v1.18, but we do not want to force a core upgrade at this time.
If you are having problems with v1.15, please try replacing it with this newer version.
It can be downloaded from http://www.stanford.edu/~friedrim/FahCore_11.exe.
Thanks.

So if you've been having trouble with v1.15, you can try a new core.

Luck ........... :D <-You need it .... :p

 
Duh, forgot to post that when I first saw this.

As Mark Friedrich said, the closed beta testing is too small to have a valid sampling to see if it works better or not. So if you have a gpu client which always EUE, try this and report here to see if it solve your problem or not.

 
Thanks for the "heads up" Tigerbiten.

Folding and WCGing for a CURE

 
Thanks for the info. I will wait to see what others think of this new core.

 
Thanks for letting us know, but it does not seem to help. I am still getting sent these 5801 WUs and they will not run for me:

[23:10:57] Folding@Home GPU Core - Beta
[23:10:57] Version 1.18 (Thu Oct 23 10:15:05 PDT 2008)
[23:10:57]
[23:10:57] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[23:10:57] Build host: amoeba
[23:10:57] Board Type: Nvidia
[23:10:57] Core :
[23:10:57] Preparing to commence simulation
[23:10:57] - Looking at optimizations...
[23:10:57] - Created dyn
[23:10:57] - Files status OK
[23:10:57] - Expanded 42847 -> 246265 (decompressed 574.7 percent)
[23:10:57] Called DecompressByteArray: compressed_data_size=42847 data_size=246265, decompressed_data_size=246265 diff=0
[23:10:57] - Digital signature verified
[23:10:57]
[23:10:57] Project: 5801 (Run 9, Clone 210, Gen 0)
[23:10:57]
[23:10:57] Assembly optimizations on if available.
[23:10:57] Entering M.D.
[23:11:04] Working on p5801_supervillin_e1
[23:11:04] Client config found, loading data.
[23:11:04] Starting GUI Server
[23:11:24] mdrun_gpu returned
[23:11:24] NANs detected on GPU
[23:11:24]
[23:11:24] Folding@home Core Shutdown: UNSTABLE_MACHINE
[23:11:27] CoreStatus = 7A (122)
[23:11:27] Sending work to server
[23:11:27] Project: 5801 (Run 9, Clone 210, Gen 0)
[23:11:27] - Error: Could not get length of results file work/wuresults_08.dat
[23:11:27] - Error: Could not read unit 08 file. Removing from queue.
[23:11:27] EUE limit exceeded. Pausing 24 hours.
 
+1 The new core does not help in getting the 5801 WUs to actually run without EUE. My kingdom for a stable core and good WU. So many GPU sitting around idle. :(

 
The 5801 units and 1.18 testing is 2 different things. I think mixing both of them doesn't work at all so Vijay pulled the 5801 units off circulation until they can find out what's wrong.

 
Xilikon said:
The 5801 units and 1.18 testing is 2 different things. I think mixing both of them doesn't work at all so Vijay pulled the 5801 units off circulation until they can find out what's wrong.

Click to expand...

When did he pull them? Cause mine has been getting them (5801s) for the last two hours. Getting tired of restarting my clients.


 
ok cool.. hopefully they pulled it when they told you they did.. cuz last update at 4:58 PM PST i received another 5801.. had to restart so it gave me another 5800..
 
I'll wait to install 1.18 until somebody tells me it fixes the rampant issues.
 
Thanks for the heads up. I'm starting up the client that was having trouble with 1.15 with 1.18 now.

@Xilikon: I swear I read Mark Fidrych in your first post. :D


2.png
 
Still no go on my second card with v1.18, no difference. For my own sanity, I'm running a couple work units from ps3grid just to see if its a hardware issue.


2.png
 
Xilikon said:
The 5801 units and 1.18 testing is 2 different things. I think mixing both of them doesn't work at all so Vijay pulled the 5801 units off circulation until they can find out what's wrong.
Click to expand...
Yes, I believe they are two separate issues as well. The P5801s crash instantly which seems to simply be a case of an unstable WU, whereas the v1.15 core with all other WUs will more likely complete than crash even if it increases the failure rate to around 20% compared to the v1.13 core.

Razor_FX_II said:
FahCore_11 1.18 runs about 200 ppd less from my normal ppd with FahCore_11 1.15
Click to expand...
I guess one of the things Stanford did was revert to an intermediary performance core between v1.15's level of performance and its predecessor, v1.13's performance level. Slowing it down a notch or two probably helps with stability at the cost of some speed. I'd welcome that if it will guarantee 100% EUE-free operation.

Switching back to 1.15 since I wasn't having problems with it.
Click to expand...
I'm not switching unless I have absolute definitive and authoritative information it is worth it. Regrettably, I was an early adopter of the v1.15 core. :rolleyes:

 
FahCore_11 1.18 runs about 200 ppd less from my normal ppd with FahCore_11 1.15
Switching back to 1.15 since I wasn't having problems with it.
 
Running a couple ps3grid work units gave my GPUs no problem, so I'm pretty certain that whatever the issue is, its not on my end. So I'm voting v1.18 changed nothing.


2.png
 
You must log in or register to reply here.
Back
Top