Thank youI've just underclocked my CPU to be the same as yours, and turned down my GPU speed so that it is also similar to yours, and this was the result @ 1366x768 60Hz using Ultra settings but with environment quality set to low...
Your laptop can play F1 2015 at your desired resolution and fps but only when lowering the VRAM usage - If I raised the environment quality to ultra then VRAM usage was around 3Gb, so you'll need to lower the environment quality (which I guess just means texture quality) to reduce VRAM usage to be at or lower than your available 2Gb..
That's because the limitation is software based, as in unoptimised coding, and not hardware based. If you use hardware monitoring application you can see that sometimes the game doesn't reach the target fps but also doesn't have any hardware bottleneck - like my recent race in Australia in the wet where my fps went from 60 fps (my target) down to 45 to 50 fps, while the component that was working the hardest, my GTX 780, was only running at 75%.Also OC the GPU, do not change the fps!!
Had this problem every wet race since day one.@ Jonathan: Some displays don't work well @ 60Hz so nVidia (maybe also AMD) provide a 59Hz option (which actually operates either at or very near to 60 fps, not 59 - so it's perhaps actually 59.94 fps) just to match display cycles and provide a smoother output. I think this applies to TVs more than monitors.
As for v-sync - I've just run a few performance tests and it turns out that Codemasters' internal v-sync option not only seems to hold back GPU performance from hitting it's true potential and stopping the game from hitting the v-sync limit of fps, but it's also the reason why replays and certain cinematic scenes are capped to 30 fps. Disabling the internal v-sync obviously allows full GPU use at the cost of screen tearing, but if you force v-sync within your GPUs control panel to either On or Adaptive then it'll still perform better than before (and replays / cinematics fps will also be unlocked from the 30 fps cap).
That said, there's still some strange optimisation issues present either way - my stormy Australia run still had performance issues such as 30-35 fps on the starting grid while the GPU was running only at ~50% even though I was nVidia v-synced to 60 fps. However after a couple of race restarts the performance fluctuated between 50 and 60 fps with the GPU then running nearer 70-80%, so whatever the problem is, there are inconsistencies present.