Skyroof 1.39 crashing in Windows

[W3WTW]

G'day.

I just installed 1.39 and after maybe 10 mins of running it crashes with these errors. What can I do to assist troubleshooting?

Application: SkyRoof.exe
CoreCLR Version: 10.0.726.21808
.NET Version: 10.0.7
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00000171305E052C

and....

Faulting application name: SkyRoof.exe, version: 1.39.0.0, time stamp: 0x6a0e0000
Faulting module name: igxelpgicd64.dll, version: 32.0.101.6452, time stamp: 0x67814e2c
Exception code: 0xc0000005
Fault offset: 0x0000000000b5052c
Faulting process id: 0x2B10
Faulting application start time: 0x1DD12C6AFEB509D
Faulting application path: C:\Program Files\Afreet\SkyRoof\SkyRoof.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_1bcd0490883eafba\igxelpgicd64.dll
Report Id: ca095e22-4550-46e8-aeab-448b3a1b52cb
Faulting package full name:
Faulting package-relative application ID: 

[Alex VE3NEA]

Hi W3WTW,

The error report that you provided shows an exception in the Intel graphics driver, igxelpgicd64.dll. The most likely cause is a buggy or mismatched Intel driver. Version 32.0.101.6452 shown in the report is one of the Intel drivers that have a history of OpenGL crashes. What you can do:

• Update — or roll back — the Intel graphics driver. Get the latest from Intel directly (not Windows Update). If you are already on the latest, roll back to a known-good older branch. 
• If this does not work, force SkyRoof onto the discrete GPU if the machine has one: Windows Settings → System → Display → Graphics → add SkyRoof.exe → set to "High performance." That routes rendering to the NVIDIA/AMD driver instead of the crashing Intel one.
• The last resort is to fall back to software OpenGL using the Mesa workaround as described in the FAQ section of User's Guide: drop the Mesa opengl32.dll into the SkyRoof folder. CPU-heavy, but it bypasses the Intel driver entirely and will confirm the diagnosis: if it stops crashing with Mesa, the Intel driver is definitively the culprit.