Why this error??

Moderators: Site Moderators, FAHC Science Team

Post Reply
RobbyB
Posts: 7
Joined: Tue Aug 27, 2024 1:09 am
Hardware configuration: Hardware configuration:Homebuilt Windows 10, 64-Bit Operating System
Main Board: GigaByte GA-B85M-D3H
Processor: Intel Core i7-4770 ~ 2014 or 2015
Memory: 32 GB RAM (up from 8 GB in 2018)
GPS: GigaByte GEFORCE GTX 1660 GPU ~ March 2020
Location: Alabama USA

Why this error??

Post by RobbyB »

Hello,

Can anyone explain what is going on? I'm folding on a plugged in DESKTOP, not a laptop (however it is plugged into an APC UPS). Am on Windows 10, with similar issues as described in my earlier serious report.

By the way, I am folding using 8.4.5

Thanks,
Robby

Code: Select all

16:34:13:I1:WU61:Completed 925000 out of 2500000 steps (37%)
16:35:21:W :WU61:Detected clock skew (16 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:36:45:I1:WU61:Completed 950000 out of 2500000 steps (38%)
16:37:31:I1:WU61:Checkpoint completed at step 950000
16:38:20:W :WU61:Detected clock skew (21 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:38:33:W :WU56:Detected clock skew (22 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:40:32:I1:WU61:Completed 975000 out of 2500000 steps (39%)
16:40:57:W :WU56:Detected clock skew (19 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:41:03:W :WU61:Detected clock skew (18 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:42:12:W :WU56:Detected clock skew (23 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:43:17:W :WU61:Detected clock skew (20 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:43:26:I1:WU61:Completed 1000000 out of 2500000 steps (40%)
16:43:26:W :WU56:Detected clock skew (29 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:43:58:I1:WU61:Checkpoint completed at step 1000000
16:46:51:W :WU61:Detected clock skew (16 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:47:03:I1:WU61:Completed 1025000 out of 2500000 steps (41%)
16:47:29:W :WU56:Detected clock skew (19 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
16:49:21:I1:WU61:Completed 1050000 out of 2500000 steps (42%)
16:49:22:I1:WU61:Checkpoint completed at step 1050000
16:51:46:I1:WU61:Completed 1075000 out of 2500000 steps (43%)
16:54:12:I1:WU61:Completed 1100000 out of 2500000 steps (44%)
16:54:13:I1:WU61:Checkpoint completed at step 1100000
16:56:34:I1:WU56:Completed 130000 out of 250000 steps (52%)
16:56:39:I1:WU61:Completed 1125000 out of 2500000 steps (45%)
Image
Main Board: GigaByte GA-B85M-D3H, Processor: I7-4770
Memory: 32Gig RAM, GPU: GeForce GTX 1660 MB
Joe_H
Site Admin
Posts: 7937
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: Why this error??

Post by Joe_H »

Besides the common cause of a laptop sleeping and this message appearing when processing resumed, I have seen this on desktop systems under a few conditions. One was from excessive interrupts causing the CPU to stop processing while handling them. One time it was failing hard drive, another time it was a damaged drive cable causing many retries on I/Os. Another issue resulting in the clock skew message was on a system with not quite enough RAM to process the WU after a memory leak in another process. There was a lot of paging and swapping occurring.

Something I have not seen personally, but was reported here, was this error eventually being traced to a dead or dying clock battery on a logic board. Not sure why that would cause the problem, but would guess there may have been frequent resets of the time.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
RobbyB
Posts: 7
Joined: Tue Aug 27, 2024 1:09 am
Hardware configuration: Hardware configuration:Homebuilt Windows 10, 64-Bit Operating System
Main Board: GigaByte GA-B85M-D3H
Processor: Intel Core i7-4770 ~ 2014 or 2015
Memory: 32 GB RAM (up from 8 GB in 2018)
GPS: GigaByte GEFORCE GTX 1660 GPU ~ March 2020
Location: Alabama USA

Re: Why this error??

Post by RobbyB »

Thanks for providing those suggestions Joe.

This system is pushing 10 years old (the motherboard). The easiest solution would be the battery. I'll check it out in a day or so and report back if changing it made a difference. I'll also re-seat the memory and other peripherals.

Cheers!!
Robby
Image
Main Board: GigaByte GA-B85M-D3H, Processor: I7-4770
Memory: 32Gig RAM, GPU: GeForce GTX 1660 MB
RobbyB
Posts: 7
Joined: Tue Aug 27, 2024 1:09 am
Hardware configuration: Hardware configuration:Homebuilt Windows 10, 64-Bit Operating System
Main Board: GigaByte GA-B85M-D3H
Processor: Intel Core i7-4770 ~ 2014 or 2015
Memory: 32 GB RAM (up from 8 GB in 2018)
GPS: GigaByte GEFORCE GTX 1660 GPU ~ March 2020
Location: Alabama USA

Re: Why this error??

Post by RobbyB »

Sorry for the delay in responding.

I've replaced the battery. That unfortunately did not fix the problem.

The hard drive running this system was affected by a Windows "update" in the late spring, which essentially bricked this computer. It was not the same one that Crowdstrike's debacle that crashed many Windows 10 systems a month or so later. I managed to restore operations, but it is very slow (like 7-10 minutes) from a simple restart to a usable state. The PC takes a long time just to open a fresh program that was not opened in its state after a reboot. It is also more unstable, and will lock up after 2-3 days (it used to go for weeks between reboots) while running FAH and other processes without issue. My newer solid state hard drive is still not working after a similar "update" for windows; why I'm on my older Seagate drive. A funny thing, if I am using the computer or have other processes going, the below quoted error does not occur like after the bottom 20:20 time.
Detected clock skew (21 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates

Code: Select all

18:41:57:I1:WU134:        PID: 7984
18:41:57:I1:WU134:        CWD: C:\ProgramData\FAHClient\work
18:41:57:I1:WU134:********************************************************************************
18:41:57:I1:WU134:Project: 18490 (Run 23, Clone 19, Gen 138)
18:41:57:I1:WU134:Unit: 0x00000000000000000000000000000000
18:41:57:I1:WU134:Reading tar file core.xml
18:41:57:I1:WU134:Reading tar file frame138.tpr
18:41:57:I1:WU134:Digital signatures verified
18:41:57:I1:WU134:Calling: mdrun -c frame138.gro -s frame138.tpr -x frame138.xtc -cpt 5 -nt 4 -ntmpi 1
18:41:57:I1:WU134:Steps: first=690000000 total=695000000
18:41:59:I1:WU134:Completed 1 out of 5000000 steps (0%)
18:42:10:I1:WU133:There are 4 platforms available.
18:42:10:I1:WU133:Platform 0: Reference
18:42:10:I1:WU133:Platform 1: CPU
18:42:10:I1:WU133:Platform 2: OpenCL
18:42:10:I1:WU133:  opencl-device 0 specified
18:42:10:I1:WU133:Platform 3: CUDA
18:42:10:I1:WU133:  cuda-device 0 specified
18:42:49:I1:WU133:Attempting to create CUDA context:
18:42:49:I1:WU133:  Configuring platform CUDA
18:43:45:I1:WU133:  Using CUDA on CUDA Platform and gpu 0
18:43:45:I1:WU133:  GPU info: Platform: CUDA
18:43:45:I1:WU133:  GPU info: PlatformIndex: 0
18:43:45:I1:WU133:  GPU info: Device: NVIDIA GeForce GTX 1660 SUPER
18:43:45:I1:WU133:  GPU info: DeviceIndex: 0
18:43:45:I1:WU133:  GPU info: Vendor: 0x10de
18:43:45:I1:WU133:  GPU info: PCI: 04:00:00
18:43:45:I1:WU133:  GPU info: Compute: 7.5
18:43:45:I1:WU133:  GPU info: Driver: 12.6
18:43:45:I1:WU133:  GPU info: GPU: true
18:43:45:I1:WU133:Completed 0 out of 2500000 steps (0%)
18:43:46:I1:WU133:Checkpoint completed at step 0
18:46:59:I1:WU133:Completed 25000 out of 2500000 steps (1%)
18:49:31:W :WU134:Detected clock skew (19 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
18:49:31:W :WU133:Detected clock skew (18 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
18:50:11:I1:WU133:Completed 50000 out of 2500000 steps (2%)
18:50:12:I1:WU133:Checkpoint completed at step 50000
18:53:26:I1:WU133:Completed 75000 out of 2500000 steps (3%)
18:56:22:I1:WU134:Completed 50000 out of 5000000 steps (1%)
18:56:40:I1:WU133:Completed 100000 out of 2500000 steps (4%)
18:56:42:I1:WU133:Checkpoint completed at step 100000
19:00:57:W :WU134:Detected clock skew (2 mins 12 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:00:58:I1:Account websocket closed: PROTOCOL msg=
19:00:58:W :WU133:Detected clock skew (2 mins 12 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:00:58:I1:OUT11:> GET https://api.foldingathome.org/machine/MOmAM7j2ku1LApLBrhORh5qafheGOxCsFPXV2NocF00 HTTP/1.1
19:00:58:I1:OUT11:< HTTP/1.1 200 HTTP_OK
19:01:15:W :WU133:Detected clock skew (17 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:01:15:W :WU134:Detected clock skew (17 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:01:15:I1:OUT8:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
19:01:15:I1:OUT8:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
19:01:15:I1:Logging into node account
19:01:36:I1:WU133:Completed 125000 out of 2500000 steps (5%)
19:04:50:I1:WU133:Completed 150000 out of 2500000 steps (6%)
19:04:52:I1:WU133:Checkpoint completed at step 150000
19:08:06:I1:WU133:Completed 175000 out of 2500000 steps (7%)
19:11:24:I1:WU133:Completed 200000 out of 2500000 steps (8%)
19:11:25:I1:WU133:Checkpoint completed at step 200000
19:12:28:W :WU134:Detected clock skew (50 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:12:28:W :WU133:Detected clock skew (49 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:13:26:I1:WU134:Completed 100000 out of 5000000 steps (2%)
19:14:41:I1:WU133:Completed 225000 out of 2500000 steps (9%)
19:15:27:W :WU134:Detected clock skew (22 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:15:28:W :WU133:Detected clock skew (22 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:18:04:I1:WU133:Completed 250000 out of 2500000 steps (10%)
19:18:06:I1:WU133:Checkpoint completed at step 250000
19:21:21:I1:WU133:Completed 275000 out of 2500000 steps (11%)
19:24:38:I1:WU133:Completed 300000 out of 2500000 steps (12%)
19:24:39:I1:WU133:Checkpoint completed at step 300000
19:27:56:I1:WU133:Completed 325000 out of 2500000 steps (13%)
19:28:14:I1:WU134:Completed 150000 out of 5000000 steps (3%)
19:28:58:W :WU133:Detected clock skew (17 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:29:48:W :WU134:Detected clock skew (17 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
19:31:25:I1:WU133:Completed 350000 out of 2500000 steps (14%)
19:31:40:I1:WU133:Checkpoint completed at step 350000
19:35:14:I1:WU133:Completed 375000 out of 2500000 steps (15%)
19:38:48:I1:WU133:Completed 400000 out of 2500000 steps (16%)
19:39:04:I1:WU133:Checkpoint completed at step 400000
19:42:32:I1:WU133:Completed 425000 out of 2500000 steps (17%)
19:44:43:I1:WU134:Completed 200000 out of 5000000 steps (4%)
19:46:17:I1:WU133:Completed 450000 out of 2500000 steps (18%)
19:46:34:I1:WU133:Checkpoint completed at step 450000
19:50:03:I1:WU133:Completed 475000 out of 2500000 steps (19%)
19:53:45:I1:WU133:Completed 500000 out of 2500000 steps (20%)
19:54:13:I1:WU133:Checkpoint completed at step 500000
19:57:55:I1:WU133:Completed 525000 out of 2500000 steps (21%)
19:58:33:W :WU133:Detected clock skew (16 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:01:02:I1:WU134:Completed 250000 out of 5000000 steps (5%)
20:01:29:I1:WU133:Completed 550000 out of 2500000 steps (22%)
20:01:32:W :WU134:Detected clock skew (16 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:01:32:W :WU133:Detected clock skew (20 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:01:57:I1:WU133:Checkpoint completed at step 550000
20:02:21:W :WU134:Detected clock skew (21 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:02:52:W :WU133:Detected clock skew (16 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:05:35:I1:WU133:Completed 575000 out of 2500000 steps (23%)
20:06:21:W :WU133:Detected clock skew (27 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:09:15:I1:WU133:Completed 600000 out of 2500000 steps (24%)
20:09:47:I1:WU133:Checkpoint completed at step 600000
20:12:43:W :WU134:Detected clock skew (16 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:13:00:W :WU133:Detected clock skew (16 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:13:22:I1:WU133:Completed 625000 out of 2500000 steps (25%)
20:14:14:W :WU134:Detected clock skew (17 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:17:18:I1:WU133:Completed 650000 out of 2500000 steps (26%)
20:17:48:I1:WU133:Checkpoint completed at step 650000
20:20:12:I1:WU134:Completed 300000 out of 5000000 steps (6%)
20:20:18:W :WU134:Detected clock skew (18 secs), I/O delay, laptop hibernation, other slowdown or clock change noted, adjusting time estimates
20:21:28:I1:WU133:Completed 675000 out of 2500000 steps (27%)
20:24:52:I1:WU133:Completed 700000 out of 2500000 steps (28%)
20:24:53:I1:WU133:Checkpoint completed at step 700000
20:28:10:I1:WU133:Completed 725000 out of 2500000 steps (29%)
20:31:28:I1:WU133:Completed 750000 out of 2500000 steps (30%)
20:31:30:I1:WU133:Checkpoint completed at step 750000
20:34:30:I1:WU134:Completed 350000 out of 5000000 steps (7%)
20:34:48:I1:WU133:Completed 775000 out of 2500000 steps (31%)
20:38:08:I1:WU133:Completed 800000 out of 2500000 steps (32%)
20:38:11:I1:WU133:Checkpoint completed at step 800000
20:41:29:I1:WU133:Completed 825000 out of 2500000 steps (33%)
20:44:50:I1:WU133:Completed 850000 out of 2500000 steps (34%)
20:44:51:I1:WU133:Checkpoint completed at step 850000
If you or anyone has suggestions, let me know. I'm probably going to do a complete install of Windows and hope for the best afterward. My budget does not allow for a wished for update to a faster system - for another year or so. I may go to the Mac or Linux route in a future update...

Cheers,
Robby
Image
Main Board: GigaByte GA-B85M-D3H, Processor: I7-4770
Memory: 32Gig RAM, GPU: GeForce GTX 1660 MB
Post Reply