Welcome to Folding@Home!
[I am just a folder like you, reading your log and making comments. I am not an authority, I have just been folding 13 years, so I have read logs before]
03:15:07: CPU: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
The U at the end of the CPU name means it is low wattage, so I start to suspect this is a laptop.
03:15:07: Memory: 3.81GiB
The odd amount of memory also makes me suspect it is a laptop
03:15:07: GPU 0: Bus:1 Slot:0 Func:0 AMD:5 Mars [Radeon R7 M260/M265/M270]
03:15:07: GPU 1: Bus:0 Slot:2 Func:0 INTEL:1 KBL GT2 [HD Graphics 620]
Having two GPUs is also a hint this is a laptop, many Laptops run their low wattage Intel GPU until some program need more power then switches to a more powerful GPU.
https://www.techpowerup.com/gpu-specs/r ... m265.c2484
Your 'more powerful' M265, however, cannot run Folding@Home. One needs two hardware items: a OpenCL 1.2 interface, (which it has) and the ability to do 64 bit (Double Precision) Floating Point Math. (which it lacks)
You can do CPU folding, however. (If the GPUs slow down the CPU folding, we can deal with that later with pause-on-start = true)
03:15:14:WU02:FS00:0xa7: CPUs: 4
F@H sees 4 threads of CPU, but there is/was a longtime 'feature' that folds the first Work Unit with 1 thread and only uses all 4 after that.
03:15:14:WU02:FS00:0xa7:Calling: mdrun -s frame733.tpr -o frame733.trr -x frame733.xtc -cpi state.cpt -cpt 15 -nt 1
-nt 1 or -np 1 indicate 1 thread, we hope that automatically goes to 4 after the first WU. If not, we can optimize.
The -cpt 15 states that we save a Check Point every 15 minutes, so if we stop folding, we may lose up to 15 minutes of work.
Now I just make stuff up:
03:47:55:WU02:FS00:0xa7:Completed 13750 out of 125000 steps (11%)
03:57:36:FS00:Shutting core down
03:57:37:WU02:FS00:0xa7:WARNING:Console control signal 1 on PID 7548
03:57:37:WU02:FS00:0xa7:Exiting, please wait. . .
03:57:50:WU02:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
Your laptop thinks about F@H for 15 minutes and then is interrupted. I suspect your screensaver comes on then it goes to sleep.
If you go to the Power and Sleep Setting in the Control Panel, (I click the gear icon in the Windows menu then type Power in the search box at the top of the screen)
Set Sleep 'when plugged in, PC goes to sleep after' to Never. You want it to sleep on battery, F@H won't run on battery anyway.
This may stop the interrupted messages every 15 minutes. That may be all your issues, if not, show us a new log and more experts may chime in.