PC1:
Intel Core 2 Duo @ 1.86ghz
Radeon HD 5450
4gb ddr2 (2gb allocated for client)
java 8 update 101
forge-1.10-12.18.0.2016 with FTB 1.10.2 modpack Unstable 4.2.4
PC2:
i5-3570k @ 3.4ghz
GTX 660Ti
16gb ddr3 (2gb allocated for client)
java 8 update 101
forge-1.10-12.18.0.2016 with FTB 1.10.2 modpack Unstable 4.2.4
This exact same thing happened on both PCs. Pictures are made around 60 seconds apart from eachother. You can see it stopped responding at the 4th picture this time.
Different forge versions and different modpacks make no difference.
1.10 had no issues.
I have managed to get in-game twice, but both times the load time was abysmal and my OS became slow and unusable from lack of RAM. But the game performance itself did not seem any different from 1.10.
There are no issues with a small amount of mods. We tried adding only around 20 mods, and Forge loaded mostly at the same speed as before. But it's kind of stupid to be limited to 20 mods when during a previous version there were no issues with 150.
So the issue appears only during Forge startup, while being allocated around 2gb memory. The issue seems to occur around the same time as shown on the pictures, regardless of the amount of mods. So I'm guessing Forge is trying to load some data all at once and it causes it to usually just die down from lack of memory.
You said it loaded up for you in 15 seconds, did you try running a large modpack? I'm honestly clueless as to what may be wrong other than Forge so any ideas are appreciated. Upgrading isn't a possibility and the idea of being unable to use newer Forge versions sucks too.