EEVEE: Crash Intel iGPU UHD620 (Lookdev world shader + probe remap) #120919

New Issue

Jeroen Bakker · 2024-04-22T11:16:27+02:00

Jeroen Bakker commented

2024-04-22 11:16:27 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: Intel(R) UHD Graphics 620 Intel 4.6.0 - Build 27.20.100.9365

Blender Version
Broken: version: 4.2.0 Alpha, branch: main, commit date: 2024-04-21 15:39, hash: 1d9d0f0056f3
Worked: (newest version of Blender that worked as expected)

Short description of error
Crash when using EEVEE Next on UHD 620/Windows.
Linux works fine.

Exact steps for others to reproduce the error

Start Blender
Switch to EEVEE Next
Switch to rendered shading mode.
The shader is always being compiled/used as it is part of the reflection probes

WARN (gpu.shader): eevee_reflection_probe_remap ComputeShader:
      |
   21 | #define int2 ivec2
      |                                                                                                              ^
      | Warning: '' : barrier call inside control flow
      |
      | #define int2 ivec2
      |                                                                                                                    ^
      | Warning: '' : barrier call inside control flow

Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFB6082C425
Module  : igc64.dll
Thread  : 00002404
Writing: C:\Users\Jeroen\AppData\Local\Temp\blender.crash.txt

By spec any barrier inside a control flow isn't supported, but many driver have some sort of freedom. Seems like this driver is very pesky about it.

note "eevee_reflection_probe_remap" doesn't compile and results in a null handle

Adem 1

ERROR (gpu.shader): WOLookdev Linking:
      | The ♦ shader uses varying _I;draw_resource_id_iface;resource_index, but previous shader does not write to it.
      | Out of resource error.

Exception Parameters  : 0x2
	Parameters[0] : 0x0000000000000000
	Parameters[1] : 0x0000000000000008


Stack trace:
blender.exe         :0x00007FF6EA50EF20  GPU_pass_shader_get C:\blender-git\blender\source\blender\gpu\intern\gpu_codegen.cc:913
blender.exe         :0x00007FF6E810FD10  blender::draw::detail::PassBase<blender::draw::command::DrawCommandBuf>::material_set C:\blender-git\blender\source\blender\draw\intern\draw_pass.hh:934
blender.exe         :0x00007FF6E82627B0  blender::eevee::BackgroundPipeline::sync C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_pipeline.cc:41
blender.exe         :0x00007FF6E8131BF0  blender::eevee::World::sync C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_world.cc:138
blender.exe         :0x00007FF6E8134030  blender::eevee::Instance::begin_sync C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_instance.cc:196
blender.exe         :0x00007FF6E80073B0  eevee_cache_init C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_engine.cc:120
blender.exe         :0x00007FF6E7EF82B0  drw_engines_cache_init C:\blender-git\blender\source\blender\draw\intern\draw_manager_c.cc:1050
blender.exe         :0x00007FF6E7EF0C80  DRW_draw_render_loop_ex C:\blender-git\blender\source\blender\draw\intern\draw_manager_c.cc:1700
blender.exe         :0x00007FF6E7EF3180  DRW_draw_view C:\blender-git\blender\source\blender\draw\intern\draw_manager_c.cc:1626
blender.exe         :0x00007FF6EA160DA0  view3d_draw_view C:\blender-git\blender\source\blender\editors\space_view3d\view3d_draw.cc:1572
blender.exe         :0x00007FF6EA161720  view3d_main_region_draw C:\blender-git\blender\source\blender\editors\space_view3d\view3d_draw.cc:1608
blender.exe         :0x00007FF6E7B9FF90  ED_region_do_draw C:\blender-git\blender\source\blender\editors\screen\area.cc:533
blender.exe         :0x00007FF6E6DB87D0  wm_draw_window_offscreen C:\blender-git\blender\source\blender\windowmanager\intern\wm_draw.cc:1007
blender.exe         :0x00007FF6E6DB8430  wm_draw_window C:\blender-git\blender\source\blender\windowmanager\intern\wm_draw.cc:1176
blender.exe         :0x00007FF6E6DB7D80  wm_draw_update C:\blender-git\blender\source\blender\windowmanager\intern\wm_draw.cc:1577
blender.exe         :0x00007FF6E6D25A10  WM_main C:\blender-git\blender\source\blender\windowmanager\intern\wm.cc:642
blender.exe         :0x00007FF6E6BC2580  main C:\blender-git\blender\source\creator\creator.cc:589
blender.exe         :0x00007FF6EAA4C200  invoke_main D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:79
blender.exe         :0x00007FF6EAA4BFB0  __scrt_common_main_seh D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288
blender.exe         :0x00007FF6EAA4BF90  __scrt_common_main D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:331
blender.exe         :0x00007FF6EAA4C2C0  mainCRTStartup D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_main.cpp:17
KERNEL32.DLL        :0x00007FFAA9C87330  BaseThreadInitThunk
ntdll.dll           :0x00007FFAAB502690  RtlUserThreadStart

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: Intel(R) UHD Graphics 620 Intel 4.6.0 - Build 27.20.100.9365 **Blender Version** Broken: version: 4.2.0 Alpha, branch: main, commit date: 2024-04-21 15:39, hash: `1d9d0f0056f3` Worked: (newest version of Blender that worked as expected) **Short description of error** Crash when using EEVEE Next on UHD 620/Windows. Linux works fine. **Exact steps for others to reproduce the error** * Start Blender * Switch to EEVEE Next * Switch to rendered shading mode. * The shader is always being compiled/used as it is part of the reflection probes ``` WARN (gpu.shader): eevee_reflection_probe_remap ComputeShader: | 21 | #define int2 ivec2 | ^ | Warning: '' : barrier call inside control flow | | #define int2 ivec2 | ^ | Warning: '' : barrier call inside control flow Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FFB6082C425 Module : igc64.dll Thread : 00002404 Writing: C:\Users\Jeroen\AppData\Local\Temp\blender.crash.txt ``` By spec any barrier inside a control flow isn't supported, but many driver have some sort of freedom. Seems like this driver is very pesky about it. note "eevee_reflection_probe_remap" doesn't compile and results in a null handle # Adem 1 ``` ERROR (gpu.shader): WOLookdev Linking: | The ♦ shader uses varying _I;draw_resource_id_iface;resource_index, but previous shader does not write to it. | Out of resource error. ``` ``` Exception Parameters : 0x2 Parameters[0] : 0x0000000000000000 Parameters[1] : 0x0000000000000008 Stack trace: blender.exe :0x00007FF6EA50EF20 GPU_pass_shader_get C:\blender-git\blender\source\blender\gpu\intern\gpu_codegen.cc:913 blender.exe :0x00007FF6E810FD10 blender::draw::detail::PassBase<blender::draw::command::DrawCommandBuf>::material_set C:\blender-git\blender\source\blender\draw\intern\draw_pass.hh:934 blender.exe :0x00007FF6E82627B0 blender::eevee::BackgroundPipeline::sync C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_pipeline.cc:41 blender.exe :0x00007FF6E8131BF0 blender::eevee::World::sync C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_world.cc:138 blender.exe :0x00007FF6E8134030 blender::eevee::Instance::begin_sync C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_instance.cc:196 blender.exe :0x00007FF6E80073B0 eevee_cache_init C:\blender-git\blender\source\blender\draw\engines\eevee_next\eevee_engine.cc:120 blender.exe :0x00007FF6E7EF82B0 drw_engines_cache_init C:\blender-git\blender\source\blender\draw\intern\draw_manager_c.cc:1050 blender.exe :0x00007FF6E7EF0C80 DRW_draw_render_loop_ex C:\blender-git\blender\source\blender\draw\intern\draw_manager_c.cc:1700 blender.exe :0x00007FF6E7EF3180 DRW_draw_view C:\blender-git\blender\source\blender\draw\intern\draw_manager_c.cc:1626 blender.exe :0x00007FF6EA160DA0 view3d_draw_view C:\blender-git\blender\source\blender\editors\space_view3d\view3d_draw.cc:1572 blender.exe :0x00007FF6EA161720 view3d_main_region_draw C:\blender-git\blender\source\blender\editors\space_view3d\view3d_draw.cc:1608 blender.exe :0x00007FF6E7B9FF90 ED_region_do_draw C:\blender-git\blender\source\blender\editors\screen\area.cc:533 blender.exe :0x00007FF6E6DB87D0 wm_draw_window_offscreen C:\blender-git\blender\source\blender\windowmanager\intern\wm_draw.cc:1007 blender.exe :0x00007FF6E6DB8430 wm_draw_window C:\blender-git\blender\source\blender\windowmanager\intern\wm_draw.cc:1176 blender.exe :0x00007FF6E6DB7D80 wm_draw_update C:\blender-git\blender\source\blender\windowmanager\intern\wm_draw.cc:1577 blender.exe :0x00007FF6E6D25A10 WM_main C:\blender-git\blender\source\blender\windowmanager\intern\wm.cc:642 blender.exe :0x00007FF6E6BC2580 main C:\blender-git\blender\source\creator\creator.cc:589 blender.exe :0x00007FF6EAA4C200 invoke_main D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:79 blender.exe :0x00007FF6EAA4BFB0 __scrt_common_main_seh D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288 blender.exe :0x00007FF6EAA4BF90 __scrt_common_main D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:331 blender.exe :0x00007FF6EAA4C2C0 mainCRTStartup D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_main.cpp:17 KERNEL32.DLL :0x00007FFAA9C87330 BaseThreadInitThunk ntdll.dll :0x00007FFAAB502690 RtlUserThreadStart ```

Jeroen Bakker added this to the 4.2 LTS milestone 2024-04-22 11:16:28 +02:00

Jeroen Bakker added the

labels 2024-04-22 11:16:28 +02:00

Jeroen Bakker self-assigned this 2024-04-22 11:16:29 +02:00

Jeroen Bakker added this to the EEVEE & Viewport project 2024-04-22 11:16:29 +02:00

Jeroen Bakker referenced a pull request that will close this issue

2024-04-22 14:20:37 +02:00

WIP: Fix #120919: EEVEE-Next: Fix incorrect barrier control flow #120930

Clément Foucault commented

2024-04-22 23:39:41 +02:00

WARN (gpu.shader): eevee_reflection_probe_remap ComputeShader:
      |
   21 | #define int2 ivec2
      |                                                                                                              ^
      | Warning: '' : barrier call inside control flow
      |
      | #define int2 ivec2
      |                                                                                                                    ^
      | Warning: '' : barrier call inside control flow

Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FFB6082C425
Module  : igc64.dll
Thread  : 00002404
Writing: C:\Users\Jeroen\AppData\Local\Temp\blender.crash.txt

Correlation is not causation ;)

``` WARN (gpu.shader): eevee_reflection_probe_remap ComputeShader: | 21 | #define int2 ivec2 | ^ | Warning: '' : barrier call inside control flow | | #define int2 ivec2 | ^ | Warning: '' : barrier call inside control flow Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FFB6082C425 Module : igc64.dll Thread : 00002404 Writing: C:\Users\Jeroen\AppData\Local\Temp\blender.crash.txt ``` Correlation is not causation ;)

Jeroen Bakker commented

2024-04-23 06:21:54 +02:00

Just mentioning the symptoms and still investigating the root cause. Think I can continue with this on Friday.

Jeroen Bakker referenced this issue

2024-04-24 06:40:24 +02:00

Intel GPU: Shadows stop working properly when changing render pass in viewport #109269

Jeroen Bakker changed title from ~~EEVEE: Crash Intel iGPU UHD620 (barrier control flow)~~ to EEVEE: Crash Intel iGPU UHD620 (Lookdeb world shader)

2024-04-24 13:29:25 +02:00

Jeroen Bakker changed title from ~~EEVEE: Crash Intel iGPU UHD620 (Lookdeb world shader)~~ to EEVEE: Crash Intel iGPU UHD620 (Lookdev world shader)

2024-04-24 13:29:33 +02:00

Jeroen Bakker changed title from ~~EEVEE: Crash Intel iGPU UHD620 (Lookdev world shader)~~ to EEVEE: Crash Intel iGPU UHD620 (Lookdev world shader + probe remap)

2024-04-24 13:44:42 +02:00

YimingWu referenced this issue

2024-04-25 04:30:53 +02:00

Crash when moving default object in new general project #121052

Jeroen Bakker commented

2024-04-25 08:14:11 +02:00

I believe the crash should be fixed in more recent drivers. Will update this system and close this report if that is the case. Other users don't experience this crash.

Jeroen Bakker referenced this issue

2024-04-25 14:51:21 +02:00

Blender crashes when EEVEE Next is set to Rendered mode, even with the default cube #120669

Jeroen Bakker commented

2024-04-25 14:57:20 +02:00

Just a remark what is going on.
The driver is very bad and crashes a lot for many different reasons.
What we need do to support this driver (what we know so far)

Change the barriers of eevee_reflection_probe_remap. Although they are supported by all other platforms, they fail for this specific driver. Removing the barriers have proved that EEVEE can render the default cube correctly. A proper fix might be to manually unroll the for loop.
Patch the lookdev world vertex shader to write all the missing interface information.

I was able to get it working, but would almost recommend to blacklist this platform due to these issues as we don't know what would then be broken.
Other applications are facing similar issues
OpenGL specs is quite clear that the barriers are set correct in the shader and this is a driver bug.

Just a remark what is going on. The driver is very bad and crashes a lot for many different reasons. What we need do to support this driver (what we know so far) - Change the barriers of `eevee_reflection_probe_remap`. Although they are supported by all other platforms, they fail for this specific driver. Removing the barriers have proved that EEVEE can render the default cube correctly. A proper fix might be to manually unroll the for loop. - Patch the lookdev world vertex shader to write all the missing interface information. > I was able to get it working, but would almost recommend to blacklist this platform due to these issues as we don't know what would then be broken. > Other applications are facing similar issues > OpenGL specs is quite clear that the barriers are set correct in the shader and this is a driver bug.

Jeroen Bakker commented

2024-04-25 15:39:51 +02:00

Hi @xavierh; just want you to be included with the issues around UHD630 driver.

we have some issues with supporting UHD630 on Windows. Linux/Mesa works, but it seems that the windows opengl driver doesn't follow the specs about barriers in compute shaders among other things. Due to the time it takes to add a work-around, we might let this ticket slip.
We also faced other issues with this platform See #121062.

Hi @xavierh; just want you to be included with the issues around UHD630 driver. we have some issues with supporting UHD630 on Windows. Linux/Mesa works, but it seems that the windows opengl driver doesn't follow the specs about barriers in compute shaders among other things. Due to the time it takes to add a work-around, we might let this ticket slip. We also faced other issues with this platform See #121062.

Xavier Hallade commented

2024-04-25 15:51:57 +02:00

Hi!

The hardware is discontinued and the Windows driver for it is in maintenance mode:
https://www.intel.com/content/www/us/en/support/articles/000091662/graphics.html
That means the issues unfortunately needs to be absolutely critical to get fixed.

The latest Windows driver for UHD 630 is 101.2127: https://www.intel.com/content/www/us/en/download/776137/intel-7th-10th-gen-processor-graphics-windows.html
Can you reproduce the issue with it ?

Hi! The hardware is discontinued and the Windows driver for it is in maintenance mode: https://www.intel.com/content/www/us/en/support/articles/000091662/graphics.html That means the issues unfortunately needs to be absolutely critical to get fixed. The latest Windows driver for UHD 630 is 101.2127: https://www.intel.com/content/www/us/en/download/776137/intel-7th-10th-gen-processor-graphics-windows.html Can you reproduce the issue with it ?

Jeroen Bakker referenced a pull request that will close this issue

2024-04-26 07:14:04 +02:00

Fix: EEVEE-Next: Intel UHD support for probe remapping. #121105

Sign in to join this conversation.