If it can handle soma without crashing i don't think it will be an issue with overheating or drivers.
It doesn't happen with all routes, in fact only with mini rotterdam.
Could it be sp3 that does this ?
I doubt it because it doesn't happen with all routes. If this is the case, then it's definitely not drivers or hardware, although, a cooler is still a good thing to get because that will make the laptop work overall.
Can you open the mini-Rotterdam route in Surveyor and have a look around? The issue could be a faulty asset. The asset may appear fine, but could be corrupted causing the program to freeze.
I've had that before back in TS12. I had a very long route that I used often, but there was one place where the program would freeze dead and sometimes crash to the desktop. This only occurred in one particular area and if I looked in another direction, there was only a slight pause. I went back and looked at the area more than once but could never find anything. After many years, and ready to give up, TANE came along and I converted my old Speed Trees to something else in order to bring the route into TANE. During the tree conversion process, I clicked on one of mcguirel's maple trees and in order to add it to the replace assets tool, and the program crashed! Poof, gone! I sat through a lengthy DBR a few times as I attempted to replace that tree. Eventually, I got lucky and I was able to move on and the route has survived right through and into TRS19.
Sadly, finding the asset that's causing this issue is a lengthy routine called process of elimination.
You need to hide all non-built-in assets in Content Manager
Load the route.
Does it crash?
Nope...
Unhide about 100 of the hidden assets.
Load the route.
Does it crash?
Nope...
Unhide another 100 of the assets.
Load the route.
Repeat.
Yes...!!!
Go back to Content Manager and disable one asset at a time from the last batch and test until things stop crashing.
The last asset you hid again is the faulty one.
To confirm this, keep this last asset hidden and unhide the others from the last batch. If things still don't crash, you found the culprit.
While doing this, I highly recommend defragmenting your hard disk because there will be lots of disk writing that will fragment your hard drive. You can disregard this if you have the data on an SSD.