On pressing the button play, the world is displayed, but next a core dump log is generated almost immediately. Find below relevant part of the log that is generated from Minecraft Launcher 1.6.61 in the "Game Output" tab and attached the full log.

20:33:54] [Server thread/INFO]: Preparing spawn area: 56%
[20:33:55] [Server thread/INFO]: Preparing spawn area: 67%
[20:33:56] [Server thread/INFO]: Preparing spawn area: 78%
[20:33:57] [Server thread/INFO]: Preparing spawn area: 86%
[20:33:58] [Server thread/INFO]: Preparing spawn area: 95%
[20:33:59] [Server thread/INFO]: Changing view distance to 12, from 10
[20:33:59] [Server thread/INFO]: MatteoG2M[local:E:e2c5c0b0] logged in with entity id 230 at (62.5, 64.0, 210.5)
[20:33:59] [Server thread/INFO]: MatteoG2M joined the territory
[20:34:05] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 5949ms behind, skipping 118 tick(s)
#

1. A fatal error has been detected by the Java Runtime Environment:
   #
2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffea8f76b37, pid=10956, tid=8668
   #
3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)
4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)
5. Problematic frame:
6. C [ig8icd64.dll+0x16b37]
   #
7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
   #
8. An error report file with more information is saved as:
9. C:\Users\francesca\AppData\Roaming\.minecraft\hs_err_pid10956.log
   #
10. If you would like to submit a bug report, please visit:
11. http://bugreport.sun.com/bugreport/crash.jsp
12. The crash happened outside the Java Virtual Machine in native code.
13. See problematic frame for where to report the bug.
    #
    AL lib: (EE) alc_cleanup: 1 device not closed
    Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release