2665 (Run 2, Clone 84, Gen 44) nan eue 36% twice in a row.

Moderators: Site Moderators, FAHC Science Team

Post Reply
mikeb12
Posts: 28
Joined: Tue Feb 12, 2008 11:51 am
Location: South Carolina USA

2665 (Run 2, Clone 84, Gen 44) nan eue 36% twice in a row.

Post by mikeb12 »

Vista 64
6.22R3

Nan eue at 36% twice in a row.... deleted wu and grabbed a new one...

Code: Select all

[18:24:16] Folding@home Core Shutdown: FINISHED_UNIT
[18:24:20] CoreStatus = 64 (100)
[18:24:20] Sending work to server
[18:24:20] Project: 2665 (Run 2, Clone 691, Gen 44)


[18:24:21] + Attempting to send results [August 26 18:24:21 UTC]
[18:33:12] + Results successfully sent
[18:33:12] Thank you for your contribution to Folding@Home.
[18:33:12] + Number of Units Completed: 5

[18:33:13] Using generic mpiexec calls
[18:35:17] - Preparing to get new work unit...
[18:35:17] + Attempting to get work packet
[18:35:17] - Connecting to assignment server
[18:35:17] - Successful: assigned to (171.64.65.64).
[18:35:17] + News From Folding@Home: Welcome to Folding@Home
[18:35:17] Loaded queue successfully.
[18:35:31] + Closed connections
[18:35:31] 
[18:35:31] + Processing work unit
[18:35:31] Work type a1 not eligible for variable processors
[18:35:31] Core required: FahCore_a1.exe
[18:35:31] Core found.
[18:35:31] Using generic mpiexec calls
[18:35:31] Working on queue slot 06 [August 26 18:35:31 UTC]
[18:35:31] + Working ...
[18:35:31] 
[18:35:31] *------------------------------*
[18:35:31] Folding@Home Gromacs SMP Core
[18:35:31] Version 1.74 (March 10, 2007)
[18:35:31] 
[18:35:31] Preparing to commence simulation
[18:35:31] - Ensuring status. Please wait.
[18:35:36] - Starting from initial work packet
[18:35:36] 
[18:35:36] Project: 2665 (Run 2, Clone 84, Gen 44)
[18:35:36] 
[18:35:37] Assembly optimizations on if available.
[18:35:37] Entering M.D.
[18:35:56] ial work packet
[18:35:56] 
[18:35:56] Project: 2665 (Run 2, Clone 84, Gen 44)
[18:35:56] 
[18:35:57] Entering M.D.
[18:35:57] one 84, Gen 44)
[18:35:57] 
[18:35:57] Entering M.D.
[18:36:05] Rejecting checkpoint
[18:36:08] 
[18:36:08] osylations
[18:36:08] Writing local files
[18:36:09] 
[18:36:09] Writing local files
[18:36:17] Extra SSE boost OK.
[18:36:18] Writing local files
[18:36:18] Completed 0 out of 250000 steps  (0 percent)
[18:55:21] Writing local files
[18:55:21] Completed 2500 out of 250000 steps  (1 percent)
[19:12:08] Writing local files
[19:12:08] Completed 5000 out of 250000 steps  (2 percent)
[19:28:40] Writing local files
[19:28:40] Completed 7500 out of 250000 steps  (3 percent)
[19:45:10] Writing local files
[19:45:10] Completed 10000 out of 250000 steps  (4 percent)
[20:03:45] Writing local files
[20:03:45] Completed 12500 out of 250000 steps  (5 percent)
[20:20:35] Writing local files
[20:20:35] Completed 15000 out of 250000 steps  (6 percent)
[20:37:13] Writing local files
[20:37:14] Completed 17500 out of 250000 steps  (7 percent)
[20:53:41] Writing local files
[20:53:41] Completed 20000 out of 250000 steps  (8 percent)
[21:10:24] Writing local files
[21:10:24] Completed 22500 out of 250000 steps  (9 percent)
[21:27:03] Writing local files
[21:27:03] Completed 25000 out of 250000 steps  (10 percent)
[21:44:02] Writing local files
[21:44:02] Completed 27500 out of 250000 steps  (11 percent)
[22:00:57] Writing local files
[22:00:57] Completed 30000 out of 250000 steps  (12 percent)
[22:17:43] Writing local files
[22:17:43] Completed 32500 out of 250000 steps  (13 percent)
[22:34:45] Writing local files
[22:34:45] Completed 35000 out of 250000 steps  (14 percent)
[22:51:59] Writing local files
[22:51:59] Completed 37500 out of 250000 steps  (15 percent)
[23:09:42] Writing local files
[23:09:42] Completed 40000 out of 250000 steps  (16 percent)
[23:26:25] Writing local files
[23:26:25] Completed 42500 out of 250000 steps  (17 percent)
[23:43:03] Writing local files
[23:43:03] Completed 45000 out of 250000 steps  (18 percent)
[23:59:39] Writing local files
[23:59:39] Completed 47500 out of 250000 steps  (19 percent)
[00:16:36] Writing local files
[00:16:36] Completed 50000 out of 250000 steps  (20 percent)
[00:33:18] Writing local files
[00:33:19] Completed 52500 out of 250000 steps  (21 percent)
[00:50:00] Writing local files
[00:50:00] Completed 55000 out of 250000 steps  (22 percent)
[01:06:44] Writing local files
[01:06:44] Completed 57500 out of 250000 steps  (23 percent)
[01:23:25] Writing local files
[01:23:25] Completed 60000 out of 250000 steps  (24 percent)
[01:40:16] Writing local files
[01:40:16] Completed 62500 out of 250000 steps  (25 percent)
[01:56:59] Writing local files
[01:56:59] Completed 65000 out of 250000 steps  (26 percent)
[02:13:57] Writing local files
[02:13:58] Completed 67500 out of 250000 steps  (27 percent)
[02:30:46] Writing local files
[02:30:46] Completed 70000 out of 250000 steps  (28 percent)
[02:47:38] Writing local files
[02:47:38] Completed 72500 out of 250000 steps  (29 percent)
[03:04:25] Writing local files
[03:04:25] Completed 75000 out of 250000 steps  (30 percent)
[03:21:17] Writing local files
[03:21:17] Completed 77500 out of 250000 steps  (31 percent)
[03:38:09] Writing local files
[03:38:10] Completed 80000 out of 250000 steps  (32 percent)
[03:55:01] Writing local files
[03:55:01] Completed 82500 out of 250000 steps  (33 percent)
[04:11:42] Writing local files
[04:11:42] Completed 85000 out of 250000 steps  (34 percent)
[04:28:18] Writing local files
[04:28:18] Completed 87500 out of 250000 steps  (35 percent)
[04:45:18] Writing local files
[04:45:18] Completed 90000 out of 250000 steps  (36 percent)
[04:56:54] Warning:  long 1-4 interactions
[04:56:54] Quit 101 - NaN detected: (ener[20])
[04:56:54] 
[04:56:54] Simulation instability has been encountered. The run has entered a
[04:56:54]   state from which no further progress can be made.
[04:56:54] This may be the correct result of the simulation, however if you
[04:56:54]   often see other project units terminating early like this
[04:56:54]   too, you may wish to check the stability of your computer (issues
[04:56:54]   such as high temperature, overclocking, etc.).
[04:56:54] Going to send back what have done.
[04:56:54] logfile size: 76419
[04:56:54] - Writing 76969 bytes of core data to disk...
[04:56:54]   ... Done.
[04:58:54] 
[04:58:54] Folding@home Core Shutdown: EARLY_UNIT_END
[04:58:54] 
[04:58:54] Folding@home Core Shutdown: EARLY_UNIT_END
[04:58:57] CoreStatus = 7B (123)
[04:58:57] Client-core communications error: ERROR 0x7b
[04:58:57] Deleting current work unit & continuing...
[04:58:57] Using generic mpiexec calls
[05:01:01] - Preparing to get new work unit...
[05:01:01] + Attempting to get work packet
[05:01:01] - Connecting to assignment server
[05:01:02] - Successful: assigned to (171.64.65.64).
[05:01:02] + News From Folding@Home: Welcome to Folding@Home
[05:01:02] Loaded queue successfully.
[05:01:19] + Closed connections
[05:01:24] 
[05:01:24] + Processing work unit
[05:01:24] Work type a1 not eligible for variable processors
[05:01:24] Core required: FahCore_a1.exe
[05:01:24] Core found.
[05:01:24] Using generic mpiexec calls
[05:01:24] Working on queue slot 07 [August 27 05:01:24 UTC]
[05:01:24] + Working ...
[05:01:24] 
[05:01:24] *------------------------------*
[05:01:24] Folding@Home Gromacs SMP Core
[05:01:24] Version 1.74 (March 10, 2007)
[05:01:24] 
[05:01:24] Preparing to commence simulation
[05:01:24] - Ensuring status. Please wait.
[05:01:29] - Starting from initial work packet
[05:01:29] 
[05:01:29] Project: 2665 (Run 2, Clone 84, Gen 44)
[05:01:29] 
[05:01:29] Assembly optimizations on if available.
[05:01:29] Entering M.D.
[05:01:49] 3 percent)
[05:01:49] - Starting from initial work packet
[05:01:49] 
[05:01:49] Project: 2665 (Run 2, Clone 84, Gen 44)
[05:01:49] 
[05:01:50] Entering M.D.
[05:01:58] Rejecting checkpoint
[05:01:59] Protein: HGG with glycosylations
[05:01:59] Writing local files
[05:02:08] Extra SSE boost OK.
[05:02:09] Writing local files
[05:02:09] Completed 0 out of 250000 steps  (0 percent)
[05:19:30] Writing local files
[05:19:30] Completed 2500 out of 250000 steps  (1 percent)
[05:36:31] Writing local files
[05:36:31] Completed 5000 out of 250000 steps  (2 percent)
[05:53:18] Writing local files
[05:53:18] Completed 7500 out of 250000 steps  (3 percent)
[06:10:24] Writing local files
[06:10:24] Completed 10000 out of 250000 steps  (4 percent)
[06:27:31] Writing local files
[06:27:31] Completed 12500 out of 250000 steps  (5 percent)
[06:44:20] Writing local files
[06:44:20] Completed 15000 out of 250000 steps  (6 percent)
[07:01:08] Writing local files
[07:01:08] Completed 17500 out of 250000 steps  (7 percent)
[07:18:05] Writing local files
[07:18:05] Completed 20000 out of 250000 steps  (8 percent)
[07:35:05] Writing local files
[07:35:05] Completed 22500 out of 250000 steps  (9 percent)
[07:51:54] Writing local files
[07:51:54] Completed 25000 out of 250000 steps  (10 percent)
[08:08:43] Writing local files
[08:08:43] Completed 27500 out of 250000 steps  (11 percent)
[08:25:31] Writing local files
[08:25:31] Completed 30000 out of 250000 steps  (12 percent)
[08:42:19] Writing local files
[08:42:20] Completed 32500 out of 250000 steps  (13 percent)
[08:59:08] Writing local files
[08:59:08] Completed 35000 out of 250000 steps  (14 percent)
[09:15:56] Writing local files
[09:15:57] Completed 37500 out of 250000 steps  (15 percent)
[09:32:46] Writing local files
[09:32:46] Completed 40000 out of 250000 steps  (16 percent)
[09:49:34] Writing local files
[09:49:35] Completed 42500 out of 250000 steps  (17 percent)
[10:06:22] Writing local files
[10:06:22] Completed 45000 out of 250000 steps  (18 percent)
[10:23:12] Writing local files
[10:23:12] Completed 47500 out of 250000 steps  (19 percent)
[10:40:02] Writing local files
[10:40:02] Completed 50000 out of 250000 steps  (20 percent)
[10:56:56] Writing local files
[10:56:56] Completed 52500 out of 250000 steps  (21 percent)
[11:14:05] Writing local files
[11:14:05] Completed 55000 out of 250000 steps  (22 percent)
[11:31:09] Writing local files
[11:31:09] Completed 57500 out of 250000 steps  (23 percent)
[11:48:06] Writing local files
[11:48:06] Completed 60000 out of 250000 steps  (24 percent)
[12:04:54] Writing local files
[12:04:55] Completed 62500 out of 250000 steps  (25 percent)
[12:21:57] Writing local files
[12:21:58] Completed 65000 out of 250000 steps  (26 percent)
[12:39:17] Writing local files
[12:39:18] Completed 67500 out of 250000 steps  (27 percent)
[12:56:25] Writing local files
[12:56:26] Completed 70000 out of 250000 steps  (28 percent)
[13:13:49] Writing local files
[13:13:50] Completed 72500 out of 250000 steps  (29 percent)
[13:31:19] Writing local files
[13:31:19] Completed 75000 out of 250000 steps  (30 percent)
[13:48:46] Writing local files
[13:48:46] Completed 77500 out of 250000 steps  (31 percent)
[14:06:20] Writing local files
[14:06:21] Completed 80000 out of 250000 steps  (32 percent)
[14:24:10] Writing local files
[14:24:11] Completed 82500 out of 250000 steps  (33 percent)
[14:41:32] Writing local files
[14:41:32] Completed 85000 out of 250000 steps  (34 percent)
[14:58:52] Writing local files
[14:58:52] Completed 87500 out of 250000 steps  (35 percent)
[15:16:14] Writing local files
[15:16:14] Completed 90000 out of 250000 steps  (36 percent)
[15:28:00] Warning:  long 1-4 interactions
[15:28:00] Quit 101 - NaN detected: (ener[20])
[15:28:00] 
[15:28:00] Simulation instability has been encountered. The run has entered a
[15:28:00]   state from which no further progress can be made.
[15:28:00] This may be the correct result of the simulation, however if you
[15:28:00]   often see other project units terminating early like this
[15:28:00]   too, you may wish to check the stability of your computer (issues
[15:28:00]   such as high temperature, overclocking, etc.).
[15:28:00] Going to send back what have done.
[15:28:00] logfile size: 67366
[15:28:00] - Writing 67916 bytes of core data to disk...
[15:28:00]   ... Done.
[15:28:00] - Failed to delete work/wudata_07.arc
[15:28:00] Warning:  check for stray files
[15:30:00] 
[15:30:00] Folding@home Core Shutdown: EARLY_UNIT_END
[15:30:00] 
[15:30:00] Folding@home Core Shutdown: EARLY_UNIT_END
[15:30:03] CoreStatus = 7B (123)
[15:30:03] Client-core communications error: ERROR 0x7b
[15:30:03] Deleting current work unit & continuing...
toTOW
Site Moderator
Posts: 6395
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: 2665 (Run 2, Clone 84, Gen 44) nan eue 36% twice in a row.

Post by toTOW »

No data for this WU ...

You can try qfix to submit partial results ...
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
7im
Posts: 10179
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: 2665 (Run 2, Clone 84, Gen 44) nan eue 36% twice in a row.

Post by 7im »

Lot's of NaNs indicate a hardware or overclock problem. An occasional one is just a bad WU.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
mikeb12
Posts: 28
Joined: Tue Feb 12, 2008 11:51 am
Location: South Carolina USA

Re: 2665 (Run 2, Clone 84, Gen 44) nan eue 36% twice in a row.

Post by mikeb12 »

It was a random one. ever since I sorted out my issues posted in the 6.22r3 thread, all my clients have been fine... this was the first eue in about a week. these seem to run in cycles with me. 7 smp clients going 24/7 and they'll fold uninterrupted for an extended period, then as soon as one gets grumpy, it's contagious. I had 2 others, same eue on different machines, same day.

I just deleted the wu a couple times and picked up a new one.. When these random ones happen on machines that have been turning in back to back wu's, I usually try to catch it and kill the wu before it tries 3 times in ro but sometimes I don't get to it til it's on it's 2nd or 3rd try.

It would be nice if we could get that 3 try standard reduced to 2. that 3rd ones a pita and a useless effort IMO..
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: 2665 (Run 2, Clone 84, Gen 44) nan eue 36% twice in a row.

Post by bruce »

mikeb12 wrote:It would be nice if we could get that 3 try standard reduced to 2. that 3rd ones a pita and a useless effort IMO..
I'd like to see it even better. An EUE gives partial credit and move on after one try. A series of EUEs (whatever it takes to indicate a hardware problem rather than a bad WU or two) gives UNSTABLE MACHINE and the client stops until you fix your hardware.

. . . but then I'm a dreamer.
Post Reply