Yes. For one minute. If you don't experience the problem you're trying to address during that time, there won't be anything in the log about it.
Here's your recording session in the log:
17:05:48.749: ==== Recording Start ===============================================
17:05:48.749: [ffmpeg muxer: 'adv_file_output'] Writing file 'C:/Users/riotr/OneDrive/Desktop/Videos/2018-02-27 17-05-48.mp4'...
17:06:47.598: [ffmpeg muxer: 'adv_file_output'] Output of file 'C:/Users/riotr/OneDrive/Desktop/Videos/2018-02-27 17-05-48.mp4' stopped
17:06:47.598: Output 'adv_file_output': stopping
17:06:47.598: Output 'adv_file_output': Total frames output: 3517
17:06:47.598: Output 'adv_file_output': Total drawn frames: 3531
17:06:47.598: ==== Recording Stop ================================================
You dropped some frames, but it doesn't say why. It seems likely that whatever interval OBS is monitoring what is going on, it's not catching the reason while it's happening.
That said, the usual advice there is to either lower captured framesize or framerate, or use a faster CPU preset. Adjust those three values until you can capture smoothly at the quality you want.