• 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.

Something wrong with p1475_tet1_03_1?

M

magnusvir

[H]ard|Gawd
Joined
Sep 7, 2004
Messages
1,165
Hey guys,
Take a look at my log for this protein. Not sure what happened. I think I will have to wait on the next protein to see if this is an overclocking problem. My A64 2800+ is running at 1850 mhz btw.

[23:14:41] *------------------------------*
[23:14:41] Folding@Home Gromacs Core
[23:14:41] Version 1.70 (October 24, 2004)
[23:14:41]
[23:14:41] Preparing to commence simulation
[23:14:41] - Looking at optimizations...
[23:14:41] - Files status OK
[23:15:01] - Expanded 3635576 -> 18750153 (decompressed 515.7 percent)
[23:15:02]
[23:15:02] Project: 1475 (Run 29, Clone 6, Gen 1)
[23:15:02]
[23:15:02] Assembly optimizations on if available.
[23:15:02] Entering M.D.
[23:15:24] (Starting from checkpoint)
[23:15:24] Protein: p1475_tet1_03_1
[23:15:24]
[23:15:24] Writing local files
[23:15:24] Completed 26864 out of 125000 steps (21)
[23:15:31] Extra SSE boost OK.
[23:23:22] Writing local files
[23:23:23] Completed 27500 out of 125000 steps (22)
[23:38:44] Writing local files
[23:38:44] Completed 28750 out of 125000 steps (23)
[23:54:05] Writing local files
[23:54:06] Completed 30000 out of 125000 steps (24)
[00:09:27] Writing local files
[00:09:27] Completed 31250 out of 125000 steps (25)
[00:25:01] Writing local files
[00:25:02] Completed 32500 out of 125000 steps (26)
[00:40:40] Writing local files
[00:40:40] Completed 33750 out of 125000 steps (27)
[00:56:13] Writing local files
[00:56:13] Completed 35000 out of 125000 steps (28)
[01:11:36] Writing local files
[01:11:36] Completed 36250 out of 125000 steps (29)
[01:26:57] Writing local files
[01:26:57] Completed 37500 out of 125000 steps (30)
[01:43:01] Writing local files
[01:43:02] Completed 38750 out of 125000 steps (31)
[01:58:34] Writing local files
[01:58:34] Completed 40000 out of 125000 steps (32)
[02:14:06] Writing local files
[02:14:07] Completed 41250 out of 125000 steps (33)
[02:29:39] Writing local files
[02:29:39] Completed 42500 out of 125000 steps (34)
[02:45:13] Writing local files
[02:45:13] Completed 43750 out of 125000 steps (35)
[03:00:46] Writing local files
[03:00:47] Completed 45000 out of 125000 steps (36)
[03:16:20] Writing local files
[03:16:21] Completed 46250 out of 125000 steps (37)
[03:31:54] Writing local files
[03:31:55] Completed 47500 out of 125000 steps (38)
[03:47:55] Writing local files
[03:47:55] Completed 48750 out of 125000 steps (39)
[04:04:13] Writing local files
[04:04:13] Completed 50000 out of 125000 steps (40)
[04:19:34] Writing local files
[04:19:35] Completed 51250 out of 125000 steps (41)
[04:20:14] Quit 101 - Fatal error: NaN detected: (ener[13])
[04:20:14]
[04:20:14] Simulation instability has been encountered. The run has entered a
[04:20:14] state from which no further progress can be made.
[04:20:14] This may be the correct result of the simulation, however if you
[04:20:14] often see other project units terminating early like this
[04:20:14] too, you may wish to check the stability of your computer (issues
[04:20:14] such as high temperature, overclocking, etc.).
[04:20:14] Going to send back what have done.
[04:20:14] logfile size: 42793
[04:20:14] - Writing 43356 bytes of core data to disk...
[04:20:15] Done: 42844 -> 5114 (compressed to 11.9 percent)
[04:20:15] ... Done.
[04:20:15]
[04:20:15] Folding@home Core Shutdown: EARLY_UNIT_END
[04:20:17] CoreStatus = 72 (114)
[04:20:17] Sending work to server


[04:20:17] + Attempting to send results
[04:20:18] + Results successfully sent
[04:20:18] Thank you for your contribution to Folding@Home.
[04:20:22] - Preparing to get new work unit...
[04:20:22] + Attempting to get work packet
[04:20:22] - Connecting to assignment server
[04:20:22] - Successful: assigned to (171.65.103.156).
[04:20:22] + News From Folding@Home: Welcome to Folding@Home
[04:20:22] Loaded queue successfully.
[04:20:35] + Closed connections


Anyone have a problem with this protein? Let me know and I will have to push my overclock to stock :(
 
magnusvir said:
Hey guys,
Take a look at my log for this protein. Not sure what happened. I think I will have to wait on the next protein to see if this is an overclocking problem. My A64 2800+ is running at 1850 mhz btw.

...

Anyone have a problem with this protein? Let me know and I will have to push my overclock to stock :(
Click to expand...
I think that's indicative of an instability... is your machine prime-stable? 1.8 to 1.85 doesn't seem worthwhile, so if it's hurting your stability it's not too bad if you have to drop to stock. What ram do you have? MEMTESTed recently?

I haven't had any of those WUs, but I haven't hit instability in any of the 600 pointers. George just lucky, guess.
 
unhappy_mage said:
I think that's indicative of an instability... is your machine prime-stable? 1.8 to 1.85 doesn't seem worthwhile, so if it's hurting your stability it's not too bad if you have to drop to stock. What ram do you have? MEMTESTed recently?

I haven't had any of those WUs, but I haven't hit instability in any of the 600 pointers. George just lucky, guess.
Click to expand...

I have had this happen, but only every great while though.

 
looks like it could be the fact that this is a beta protein. I had 3 600 poniters on this which did fine. Right now I have another 600 pointer and dropped back to stock. Hey it was a good 30 seconds while it lasted. :D
 
It's hard to imagine a 50 MHz overclock causing a problem. Maybe RAM or PSU problems? Although, I would probably just wait and see if anyone else is having trouble with them. One thing is for sure though, these BIG work units work our systems harder than anything we have had before. That being the case, anything that may be a problem will likely show up while running one.
 
Killer[MoB] said:
One thing is for sure though, these BIG work units work our systems harder than anything we have had before.
Click to expand...
lol I'm running 3 900mHz machines on these... 2:20ish per frame, total around 8 days each WU. They make deadlines with plenty of headroom, believe it or not.
 
A lot of people are really pushing these new 64bit CPU’s hard. The fact remains however if you’re not Prime 95 stable your going to waste a ton of cycles on early terminations of proteins.

Prime 95 and MemTest are your best friends.

This has come up a lot in the AMD forum on this site. For some reason people think Prime 95 is flaky instead of their computer. It just doesn’t work that way.

Check your over clocks carefully, use those cycles wisely. ;)
 
I've had that happen every so often. Don't worry about it unless it happens ALL the time. Otherwise it's probably due to the beta software or whatnot.
 
yup protein fault. I just got credited roughly half the points. Hope they stabilise the protein cause it takes me 26 hours to finish those and is worth over 350 points.
 
Try 11:35 for a frame and 19.5 hours for the whole protien.
Times two as both my Opterons have now got one each.
Thats close to 900 points per day from this one box.

My XP @ 2.0 Ghz takes 31:38 per frame.

Luck.......... :D
u=Tigerbiten.gif
 
Tigerbiten said:
Try 11:35 for a frame and 19.5 hours for the whole protien.
Times two as both my Opterons have now got one each.
Thats close to 900 points per day from this one box.

My XP @ 2.0 Ghz takes 31:38 per frame.

Luck.......... :D
Click to expand...

Are you talking about those "Black Magic" 364 pointers that they've been sending out recently?
 
You must log in or register to reply here.
Back
Top