Hi Takashi, I can't reproduce this. B19238 64-bit.

Hi @xiaomengatsafe, thanks for testing this.

I upgraded FME version to build 19246, but the symptom still appears. I'm wondering if it's my machine environment specific problem. For what it's worth, the specs are:

• FME 2019.0.0.1 build 19246
• Windows 10 Pro version 1803 64 bit
• Intel Core i7-7700 CPU 3.6GHz
• RAM 32.0 GB

Hi @takashi, I did come across another user that experienced crash on Windows 10 1803. I don't know if it's just a coincidence though. Would you be able to update your windows, and see if that get rid of the crash?

I have updated Windows to the latest state, but the crash still appears.

Windows 10 Pro version 1803 64 bit, OS build 17134.706

Hi @takashi,

Is there a Windows Event logged in the Event Viewer for the application crash when you go to the full screen mode?

Also have you tried FME 2019.1 - does it have the same behaviour when you go into full screen?

Hi @andreaatsafe, thanks for your response.

I upgraded FME version to 2019.0.1 build 19253, and the crash still appears. This is the Windows error event log.

?????:         Application
???:           Application Error
??:            2019/05/16 13:16:46
???? ID:       1000
????????:      (100)
???:           ???
?????:         ?????
????:          N/A
???????:       PSS-IIJIMA-01
??:
??????????????????: fmeworkbench.exe??????: 2019.7.36.19253???? ????: 0x5cd0fbad
???????????????: ig9icd64.dll??????: 23.20.16.4849???? ????: 0x59f375c0
?????: 0xc000041d
???????: 0x000000000060fc1d
????????????? ID: 0x3e44
??????????????????????: 0x01d50b9e25500b2f
????????????????? ??: C:\Program Files\FME 2019.0\fmeworkbench.exe
?????????????? ??: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_b99c0edf4a599f95\ig9icd64.dll
???? ID: 122467aa-ff96-44ab-be53-9941511cdc4d
????????????????????: 
??????????????????????????? ID: 
???? XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-05-16T04:16:46.160746200Z" />
    <EventRecordID>66806</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PSS-IIJIMA-01</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fmeworkbench.exe</Data>
    <Data>2019.7.36.19253</Data>
    <Data>5cd0fbad</Data>
    <Data>ig9icd64.dll</Data>
    <Data>23.20.16.4849</Data>
    <Data>59f375c0</Data>
    <Data>c000041d</Data>
    <Data>000000000060fc1d</Data>
    <Data>3e44</Data>
    <Data>01d50b9e25500b2f</Data>
    <Data>C:\Program Files\FME 2019.0\fmeworkbench.exe</Data>
    <Data>C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_b99c0edf4a599f95\ig9icd64.dll</Data>
    <Data>122467aa-ff96-44ab-be53-9941511cdc4d</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

It's very similar to this issue: FME 2019.0.1 Data Inspector won't handle 3D geometries?

Those crushes don't occur with FME(R) 2019.1.0.0 (20190507 - Build 19565 - WIN64).

?????:         Application
???:           Application Error
??:            2019/05/16 13:16:46
???? ID:       1000
????????:      (100)
???:           ???
?????:         ?????
????:          N/A
???????:       PSS-IIJIMA-01
??:
??????????????????: fmeworkbench.exe??????: 2019.7.36.19253???? ????: 0x5cd0fbad
???????????????: ig9icd64.dll??????: 23.20.16.4849???? ????: 0x59f375c0
?????: 0xc000041d
???????: 0x000000000060fc1d
????????????? ID: 0x3e44
??????????????????????: 0x01d50b9e25500b2f
????????????????? ??: C:\Program Files\FME 2019.0\fmeworkbench.exe
?????????????? ??: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_b99c0edf4a599f95\ig9icd64.dll
???? ID: 122467aa-ff96-44ab-be53-9941511cdc4d
????????????????????: 
??????????????????????????? ID: 
???? XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-05-16T04:16:46.160746200Z" />
    <EventRecordID>66806</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PSS-IIJIMA-01</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fmeworkbench.exe</Data>
    <Data>2019.7.36.19253</Data>
    <Data>5cd0fbad</Data>
    <Data>ig9icd64.dll</Data>
    <Data>23.20.16.4849</Data>
    <Data>59f375c0</Data>
    <Data>c000041d</Data>
    <Data>000000000060fc1d</Data>
    <Data>3e44</Data>
    <Data>01d50b9e25500b2f</Data>
    <Data>C:\Program Files\FME 2019.0\fmeworkbench.exe</Data>
    <Data>C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_b99c0edf4a599f95\ig9icd64.dll</Data>
    <Data>122467aa-ff96-44ab-be53-9941511cdc4d</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Hi @takashi,

I would say the 2 posts are related as they are both crashing based on the same faulting module - ig9icd64.dll - which is related to a known issue with QT and certain GPUs. Could you try updating the graphics driver, it looks like your current version is 23.20.16.4849?

We had a customer who recently experienced this issue found installing the following driver worked:

Version: 25.20.100.6472 ,A12 Older versions      
Release Date: 07 Feb 2019
 
File Name: Intel-HD-Graphics-500-P500-600-P600-series-Driver_0JV50_WIN_25.20.100.6472_A12.EXE
File size: 350.67 MB

I believe this is the driver here: https://www.dell.com/support/home/ca/en/cabsdt1/drivers/driversdetails?driverid=0jv50

--

Another thing to check is in the Windows Registry Editor "regedit":

• Navigate to: HKEY_CURRENT_USER\Software\Safe Software Inc.\FME Workbench\Settings

• Find the key: "Enable OpenGL For Webview"

• If this registry key exists and the value is “true”, modify the value to “false”

Let me know how this goes.

-Andrea

Hi @andreaatsafe, thanks for your suggestion. I updated the graphics driver to the latest version, then the problems both have been resolved!

This Intel site was helpful: Downloads for Graphics Drivers