Page MenuHome

Crash on startup with 2.82 and Intel HD + Windows
Needs Developer to Reproduce, HighPublicBUG

Description

System Information
Operating system: Windows 10 Pro (1909)
Graphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951

Blender Version
Broken: 2.81, 2.82, downloaded from blender.org
Worked: 2.80 worked.

Short description of error
Blender crashes on start:

C:\Program Files\Blender Foundation\Blender 2.81>blender.exe
GPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.00 MiB.
GPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.00 MiB.
GPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.00 MiB.
found bundled python: C:\Program Files\Blender Foundation\Blender 2.81\2.81\python
GPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.34 MiB.
GPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB

This appears to be similar to T69594.

Exact steps for others to reproduce the error

  1. Download 2.81.
  2. Launch 'blender.exe'

Related Objects

Mentioned In
T83167: EXCEPTION_ACCESS_VIOLATION_ERROR
T83072: Crash after Startup
T82975: It will not open.
T82778: Can´t start Blender
T82674: EXCEPTION_ACCESS_VIOLATION
T82554: Blender Will Not Open
T82320: Blender Doesn't work anymore even after reinstall
T81586: Crash startup blender 2.8 2.9
T81446: Blender 2.90.1 and 2.83 LTS won't open
T80989: Crashing on startup
T80672: Blender won't open or run
T80099: Always crash every few minutes
T79728: Open GL issue after GPU update.
T79229: Blender crash on start-up, EXCEPTION_ACCESS_VIOLATION, OpenGL.3.3 or higher required
T78838: I can't open Blender 2.83
T78016: Blender will not open
T77921: The version of 2.83 couldn't recognize the graphic card
T77852: Unable to Open Blender.
T77651: ChromeOS: Black screen/window on startup:
D7935: Add trouble shooting steps for Intel GPUs.
T77381: Crash on startup: ChoosePixelFormat
T77360: Cannot start Blender 2.83 - Crashing on startup
rB13125e094881: GPU: Attempt to fix Crash on startup with Intel HD Graphics 620/630
T76441: Blender doesnt start
T76265: Blender won't start
T75048: Blender won't Launch 2.8x
T76042: Blender does not open 2.82a
T75248: Blender Crashes on startup
T75215: Blender crash at startup
T76007: Unstable version crashes on startup
T75882: Blender crashes when click on shading tab
T75835: Blender crashes whole PC when I want to change layout in Shading tab
T75320: Crash on startup with 2.82a, NVIDIA, Windows 10
T75230: Blender 2.82 crashes on startup
T75184: official blender 2.82a does not start on my computer
T75058: Blender using integrated GPU, not dedicated
T75067: Blender stopped working.
Mentioned Here
T62651: Dual monitor on separate graphics card driver error
rB13125e094881: GPU: Attempt to fix Crash on startup with Intel HD Graphics 620/630
T72221: [GPU] Intel HD 4000 driver does not handle multiple glcontext right. Crash.
rB26bd5ebd42e3: Update rest of submodules to correct commit for Blender 2.81 release
rBb81939716de8: Fix T70378: Grease pencil armature modifier not normalizing weights as expected.
T69594: crash start

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Operating system: Windows 10 (1909)
Graphics card: Intel(R) HD Graphics 630, version: '4.5.0 - Build 25.20.100.6576'
I used to have the latest drivers provided by my manufacturer(Acer) but they were giving me issues not only with Blender, but also with the latest Windows 10 version. So I downloaded drivers directly from Intel, and now everything works fine.

I just downloaded this 2.83Beta, but alas, no luck launching it. When I start it from the command prompt a new window frame appears briefly but will close before it is properly initialised. This is displayed in the command prompt window:

C:\Program Files\Blender Foundation\blender-2.83-windows64>blender.exe
GPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.00 MiB.
GPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.00 MiB.
GPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.00 MiB.
found bundled python: C:\Program Files\Blender Foundation\blender-2.83-windows64\2.83\python
GPUTexture: create : TEXTURE_2D, RGBA8, w : 3133, h : 45, d : 0, comp : 4, size : 0.54 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.54 MiB.
GPUTexture: create : TEXTURE_1D_ARRAY, R8, w : 16384, h : 1, d : 0, comp : 1, size : 0.02 MiB
GPUTexture: texture alloc failed. Likely not enough Video Memory.
Current texture memory usage : 0.02 MiB.
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF796680D00
Module : C:\Program Files\Blender Foundation\blender-2.83-windows64\blender.exe

@Jouni Juntunen (jounij) Can you provide your blender_system_info.txt please? see https://developer.blender.org/T72098#823516 for how to do.

Here you are. Thanks for looking into this!

@Jouni Juntunen (jounij) you are using an old driver. Please update with the one provided here https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630 and test again.

Tested with an older 2.83 and a 2.90 build, both start fine if I force using the integrated chip, Intel UHD Graphics 630.

Note for others who try to recreate this: Blender didn't want to use the Intel GPU using the conventional ways (NVidia settings or right-clickRun with graphics processor). I had to use Windows Graphics settings to force the Intel. So better double check if Blender is actually using the Intel GPU using system-info.txt when trying to recreate this.

Hello,

I installed the latest stable Intel drivers dated 5/5/2020 (win10_100.8190). After this things are worse, I think... This is what I get now:

C:\Program Files\Blender Foundation\blender-2.83-windows64>blender.exe
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000

When running blender_debug_gpu.cmd only blender_debug_output.txt is generated with the following contents (the same exception is reported with not much else):
Switching to fully guarded memory allocator.
Blender 2.83 (sub 17)
Build: 2020-05-19 21:49:19 Windows Release
argv[0] = C:\Program Files\Blender Foundation\blender-2.83-windows64\\blender
argv[1] = --debug
argv[2] = --debug-gpu
argv[3] = --python-expr
argv[4] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\jouni\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt')
read file

Version 280 sub 39 date unknown hash unknown

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000

@Jouni Juntunen (jounij) and with the blender_debug_gpu_glitchworkaround.cmd ?

Hi @Clément Foucault (fclem) , running blender_debug_gpu_glitchworkaround.cmd produced only the file blender_debug_output.txt with exactly the same content as I showed above (I checked the file date stamp and the file was newly generated i.e. is not a left-over from my previous attempt).

Hi @Clément Foucault (fclem) , yes, under Graphics settings I made sure that Classic App was selected in the drop down list, added Blender.exe and chose options for Blender. The dialog stated that Power Saving GPU is set to Intel and High Performance GPU is set to NVIDIA. By default the preference was set to "System Default". I changed this to "Power saving" to enforce selection of Intel. This did the trick! Or at least I was now able to launch Blender without the crash. Odd, but I don't mind as long as it continues to work. :)

Hi all, by forcing the "Power saving" GPU via Windows advanced graphics settings for the Blender executable I was able to run Blender v2.82 which was previously not working on the Intel UHD Graphics 630.

@Jouni Juntunen (jounij) @Julian Eisel (Severin) Both of you said changing the Windows settings to force Blender to use your Intel GPU worked in fixing this issue.

May I ask, if you change the Windows settings back to how they were and then changed the settings in something like the Nvidia Control Panel to force Blender to use the Intel GPU, does that also work?

Just asking as it may be useful in slimming down the documentation of this work around.

Note: Please make sure that changing the setting back in the Windows settings actually causes Blender to crash again. I don't want to document the control panel as a work around if it only works if you've done the Windows setting work around first.

Hello @Alaska (Alaska),

Everything was at "Default" settings before I forced them, as described above.

It may be relevant to mention that in this otherwise powerful computer I have one dedicated display card (NVIDIA) and then the onboard Intel Graphics chips and two monitors - one connected to each. The NVIDIA card - most likely to be the main culprit here - is an old GeForce GT 630. NVIDIA Control Panel constantly reminds me that the Nvidia driver is not up-to-date. Despite this, whenever I try to update it, the process fails with "your operating system is not supported". My OS is W10 Professional 64-bit with all available updates applied.

I just haven't bothered acquiring a new graphics card as I don't run any games or anything else that requires powerful graphics - apart from an occasional video editing session. So I am happy with the workaround: as long as Blender does not crash and otherwise works, I can accept the slow video processing. It's not like I'd sit and watch it happen.

@Jouni Juntunen (jounij) I was asking if doing the same process, but with the Nvidia control panel also works. This is just as a test to clarify things.

Here are some instructions:

  1. Open Windows settings and change the setting for Blender back to "System Default".
  2. Open Blender to see if it crashes. If it does, then continue.
  3. Open the Nvidia control panel.
  4. Select the "Manage 3D settings" section on the left of the control panel.
  5. Select the "Program settings" panel in the center of the screen.
  6. Add/browse for Blender.
  7. Change the "Preferred graphics processor" option to the Intel GPU (Integrated graphics).
  8. Test Blender to see if it crashes.

I'm just asking out of curiosity. Does this also work (they should do the same thing, but I'm not so sure)? Is the "Integrated graphics" option even there?

Having this information would be useful for simplifying a patch for the manual.

Once you've done the test, you can go back to using which ever method you want.

Hello @Alaska (Alaska) ,
I just navigated to Graphic Settings, changed Graphics preference setting for Blender from "Power Saving" to BOTH "Let Windows Decide" and "High Performance". After each change I was able to launch Blender successfully. I also removed the setting overwrite for Blender. I was still able to launch Blender without the crash. Odd.

Note that that I did not reboot the computer between these attempts. Because the previous crash did not occur, I did not experiment with the NVIDIA Control Panel settings.

Found a simple, but overlooked fix:
This will not work unless you have a discrete graphics card installed. Essentially, in the process of trying to figure out this issue, I came across the fact that my monitor's HDMI cord was plugged into the motherboard. This was the reason why Blender and other programs were not able to correctly use the graphics card. Instead, and I'm not sure why I hadn't has this already done in the first place, I plugged the HDMI cord into the graphics card in my PC and it ran as normal. Again, this will only work if you have a separate graphics card in your PC. Not sure why my HDMI cable was not already plugged into the graphics card, but for whatever reason, it was plugged into the wrong place on my PC.

In short: Make sure your HDMI cable from your monitor is going to your GPU in your computer, not your motherboard.

@yaboi jenkins (yaboijenkins) this sounds more like bug T62651. I am not sure if this applies to all merged reports here though.