The log contains more system and OBS information than you can ever provide by other means. One view into the log is like looking upon your PC and being able to say: "ah, it's this kind of thing. So I recommend this and that..." By the way, you didn't post any information about your system.
Many people post painstakingly prepared screenshots of all their OBS settings they deem relevant, actually leaving out "the" relevant setting for their problem, while a simple post of the log that includes a recording attempt would be all information necessary to come to a conclusion.
I wonder why you want to record at 240fps. There isn't probably nobody besides yourself who is able to display 240fps.
It's also not reasonable to let a game render more fps the monitor is able to display. The overflow fps are lost. The frames are computed, taking up system resources, but nobody will ever notice them. They will not be displayed. If you have one of these new monitors that are able to display 144 fps, and you feed it with a fps of 2880, it would be able to display every 20th frame. 19 frames out of 20 are computed and immediately thrown away, and 1 frame is displayed.
If your game renders exactly 144 fps on a 144 fps monitor, all frames are actually used. No one missing, no one thrown away. This is the perfect setup. It's also perfect, because the frames are produced and recorded at the correct timestamp. If you pick one of 20 frames, you never know for which timestamp the frame was produced, so the taken frame may come a bit too early or a bit too late, producing micro-stutter. The resulting video looks not as smooth as it should be. If, on the other hand, the frames are exactly produced and recorded at their intended timestamp, the video looks smoother. This smoothness is as important as a reasonably high frame rate.
