@SteveZee I saw a big problem in my cooling system, because four fans were not working. I have fixed this today and ran the game until it crashed again. Now, we can conclude that this is not a cooling issue, but something else. For further investigation look at my findings and try to find another way to explain the cause of this bug:
Time of crash: 19:49
GPU temperature: 63℃
CPU temperature: 59℃
Information among time of crash:
Informatie 22/05/2018 19:50:17 Security-SPP 16384 None
Informatie 22/05/2018 19:49:47 Windows Error Reporting 1001 None
Informatie 22/05/2018 19:49:47 Security-SPP 1003 None
Informatie 22/05/2018 19:49:47 Security-SPP 1003 None
Informatie 22/05/2018 19:49:47 Security-SPP 1033 None
Informatie 22/05/2018 19:49:46 Security-SPP 16394 None
Informatie 22/05/2018 19:49:43 ESENT 916 ⚽
Informatie 22/05/2018 19:49:34 Windows Error Reporting 1001 None
Informatie 22/05/2018 19:49:33 Desktop Window Manager 9027 None
Information when starting up Star Wars Battlefront II:
Informatie 22/05/2018 19:39:30 ESENT 916 ⚽
Informatie 22/05/2018 19:39:16 ESENT 916 ⚽
Informatie 22/05/2018 19:37:37 Security-SPP 16384 None
Informatie 22/05/2018 19:37:06 Security-SPP 16394 None
Informatie 22/05/2018 19:36:44 ESENT 916 ⚽
Informatie 22/05/2018 19:29:52 User Profile Service 1530 None
Informatie 22/05/2018 19:29:52 User Profile Service 1530 None
Informatie 22/05/2018 19:29:52 ESENT 916 ⚽
Informatie 22/05/2018 19:29:52 Winlogon 6000 None
Informatie 22/05/2018 19:29:51 Winsrv 10001 None
Informatie 22/05/2018 19:29:51 Winsrv 10001 None
Informatie 22/05/2018 19:29:51 Desktop Window Manager 9027 None
Informatie 22/05/2018 19:29:47 ESENT 916 ⚽
All error, warning and information reports from the time I start up my PC:
Fout 22/05/2018 19:51:55 DistributedCOM 10016 None
Waarschuwing 22/05/2018 19:49:33 Display 4101 None
Waarschuwing 22/05/2018 19:49:30 Display 4101 None
Fout 22/05/2018 19:37:52 DistributedCOM 10016 None
Informatie 22/05/2018 19:37:33 BROWSER 8033 None
Informatie 22/05/2018 19:37:31 BROWSER 8033 None
Fout 22/05/2018 19:37:05 DistributedCOM 10016 None
Informatie 22/05/2018 19:36:43 Winlogon 7001 (1101)
Informatie 22/05/2018 19:36:34 e1iexpress 32 None
Informatie 22/05/2018 19:36:33 Power-Troubleshooter 1 None
Informatie 22/05/2018 19:36:31 Kernel-Boot 27 (33)
Informatie 22/05/2018 19:36:31 Kernel-Boot 25 (32)
Informatie 22/05/2018 19:36:31 Kernel-Boot 32 (58)
Informatie 22/05/2018 19:36:31 Kernel-Boot 18 (57)
Informatie 22/05/2018 19:36:31 Kernel-Boot 30 (21)
Informatie 22/05/2018 19:36:30 EnhancedStorage-EhStorTcgDrv 100 Driver
Informatie 22/05/2018 19:36:30 Kernel-General 1 (5)
Informatie 22/05/2018 19:29:53 Kernel-Power 107 (102)
Informatie 22/05/2018 19:29:53 EnhancedStorage-EhStorTcgDrv 100 Driver
Informatie 22/05/2018 19:29:53 Kernel-Power 42 (64)
Informatie 22/05/2018 19:29:52 Winlogon 7002 (1102)
Informatie 22/05/2018 19:25:51 BROWSER 8033 None
Informatie 22/05/2018 19:25:49 BROWSER 8033 None
Fout 22/05/2018 19:25:24 DistributedCOM 10016 None
Informatie 22/05/2018 19:25:03 Winlogon 7001 (1101)
Informatie 22/05/2018 19:24:52 e1iexpress 32 None
Informatie 22/05/2018 19:24:51 Power-Troubleshooter 1 None
Informatie 22/05/2018 19:24:49 Kernel-Boot 27 (33)
Informatie 22/05/2018 19:24:49 Kernel-Boot 25 (32)
Informatie 22/05/2018 19:24:49 Kernel-Boot 32 (58)
Informatie 22/05/2018 19:24:49 Kernel-Boot 18 (57)
Informatie 22/05/2018 19:24:49 Kernel-Boot 30 (21)
Informatie 22/05/2018 19:24:48 EnhancedStorage-EhStorTcgDrv 100 Driver
Informatie 22/05/2018 19:24:48 Kernel-General 1 (5)
In any event, the crashes themselves are a result of the graphics subsystem. The windows error reporting is what's reporting the actual crash itself.
The next step is to figure out what is faulting and why.
The graphics driver may be at fault here. But you'd have to perform a system stress test to rule out hardware failures.
What you can possible do, if you have to time, is to figure out if the windows error reporting is producing a system memory dump, and then try to upload that from its location. I dont remember where it is, but if i find its location, ill let you know. But stress testing, and driver reversion is a good next step if you haven't tried it all ready.
