Crash on startup with 2.82 and Intel HD + Windows #72098

New Issue

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 #69594.

Exact steps for others to reproduce the error

Download 2.81.
Launch 'blender.exe'

blender_system_info.txt

blender_debug_output.txt

**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 #69594. **Exact steps for others to reproduce the error** 1. Download 2.81. 2. Launch 'blender.exe' [blender_system_info.txt](https://archive.blender.org/developer/F8183966/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8183967/blender_debug_output.txt)

Added subscriber: @George-Ellenburg

#88611 was marked as duplicate of this issue

#85949 was marked as duplicate of this issue

#87089 was marked as duplicate of this issue

#85507 was marked as duplicate of this issue

#85386 was marked as duplicate of this issue

#83417 was marked as duplicate of this issue

#82778 was marked as duplicate of this issue

#82554 was marked as duplicate of this issue

#82320 was marked as duplicate of this issue

#81586 was marked as duplicate of this issue

#80808 was marked as duplicate of this issue

#80989 was marked as duplicate of this issue

#79513 was marked as duplicate of this issue

#78838 was marked as duplicate of this issue

#78799 was marked as duplicate of this issue

#78016 was marked as duplicate of this issue

#77921 was marked as duplicate of this issue

#77852 was marked as duplicate of this issue

#77360 was marked as duplicate of this issue

#76781 was marked as duplicate of this issue

#76499 was marked as duplicate of this issue

#76441 was marked as duplicate of this issue

#76288 was marked as duplicate of this issue

#76042 was marked as duplicate of this issue

#75248 was marked as duplicate of this issue

#75320 was marked as duplicate of this issue

#75230 was marked as duplicate of this issue

#75067 was marked as duplicate of this issue

Added subscriber: @rjg

Changed status from 'Open' to: 'Archived'

Blender is using the integrated graphics of your CPU instead of a dedicated GPU on your system. Try to configure it through the Nvidia control panel to use one of the dedicated GPUs. You should also [update the driver for your integrated GPU ]] since it should be capable of running Blender. The current drivers for the dedicated GPUs can be [ https:*www.nvidia.com/Download/index.aspx?lang=en | downloaded from the Nvidia website .

I will be closing this bug report, since the issue seems to be caused by a problem with the graphics drivers or GPU configuration. If the problem should not be fixed by the suggested steps, please re-open the bug report.

Blender is using the integrated graphics of your CPU instead of a dedicated GPU on your system. Try to configure it through the Nvidia control panel to use one of the dedicated GPUs. You should also [update the driver for your integrated GPU ]] since it should be capable of running Blender. The current drivers for the dedicated GPUs can be [[ https:*www.nvidia.com/Download/index.aspx?lang=en | downloaded from the Nvidia website ](https:*downloadcenter.intel.com/download/29195/Intel-Graphics-Windows-10-DCH-Drivers?product=97129). I will be closing this bug report, since the issue seems to be caused by a problem with the graphics drivers or GPU configuration. If the problem should not be fixed by the suggested steps, please re-open the bug report.

I want Blender to be using the integrated graphics.

What exactly do you want me to change because I've never had a need to touch any of my Nvidia settings.

Blender 2.80 worked just fine.

Blender 2.79 worked just fine.

What changed with 2.81?

Zbrush works just fine.

Silo works just fine.

Marvelous Designer works just fine.

The Nvidia GPUs are only used for rendering. I have no displays plugged into them.

And it's not a problem with the Intel GPU because my Surface Pro has an Intel GPU that loads Blender 2.81.

So something is seriously broken in 2.81 as evidenced by the fact you now have multiple reports of this issue.

I want Blender to be using the integrated graphics. What exactly do you want me to change because I've never had a need to touch any of my Nvidia settings. Blender 2.80 worked just fine. Blender 2.79 worked just fine. What changed with 2.81? Zbrush works just fine. Silo works just fine. Marvelous Designer works just fine. The Nvidia GPUs are only used for rendering. I have no displays plugged into them. And it's not a problem with the Intel GPU because my Surface Pro has an Intel GPU that loads Blender 2.81. So something is seriously broken in 2.81 as evidenced by the fact you now have multiple reports of this issue.

Changed status from 'Archived' to: 'Open'

It's fine if you intentionally used the integrated graphics. Due to your powerful dedicated GPUs I assumed this might be unintentional. If it worked properly in Blender 2.8 it could be a bug indeed.

Please try to update your graphics drivers anyway so we can rule out any issue caused by them. Just because the problem doesn't occur with other software doesn't mean that the driver isn't at fault.

I'll re-open the issue.

It's fine if you intentionally used the integrated graphics. Due to your powerful dedicated GPUs I assumed this might be unintentional. If it worked properly in Blender 2.8 it could be a bug indeed. Please try to update your graphics drivers anyway so we can rule out any issue caused by them. Just because the problem doesn't occur with other software doesn't mean that the driver isn't at fault. I'll re-open the issue.

Added subscriber: @MaciejJutrzenka

@rjg his GPU intel one.. is supported GPU and if he want's to run it on intel he absolutly can. And it should work.

@George-Ellenburg Hi! in deed the 2.81 introduced a few GPU problems as many reports are happening.. however a lot of them is simply because of the drivers are not up to date.. plz try updateing your drivers following this page: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html it is important to use drivers directly from manufacture of GPU intel/amd/nvidia and not from PC manufacture like dell etc.. as they often have old and bugged drivers.

Added subscriber: @robert-18

@MaciejJutrzenka

Robert Guetzkow (rjg) his GPU intel one.. is supported GPU and if he want's to run it on intel he absolutly can. And it should work.

Which is exactly what I said:

[...] You should also update the driver for your integrated GPU since it should be capable of running Blender. [...]

It's fine if you intentionally used the integrated graphics. [...]

I've already linked the pages for the driver downloads (see first comment).

Please don't add unnecessary noise into the triaging process. Thank you.

@MaciejJutrzenka > Robert Guetzkow (rjg) his GPU intel one.. is supported GPU and if he want's to run it on intel he absolutly can. And it should work. Which is exactly what I said: > [...] You should also update the driver for your integrated GPU since it should be capable of running Blender. [...] > It's fine if you intentionally used the integrated graphics. [...] I've already linked the pages for the driver downloads (see first comment). Please don't add unnecessary noise into the triaging process. Thank you.

Removed subscriber: @robert-18

@George-Ellenburg Please let us know if the driver updates improved the situation.

Added subscriber: @fclem

@fclem If the driver update doesn't solve the issue, this might be something for you to look at.

In #72098#822152, @MaciejJutrzenka wrote:
@George-Ellenburg Hi! in deed the 2.81 introduced a few GPU problems as many reports are happening.. however a lot of them is simply because of the drivers are not up to date.. plz try updateing your drivers following this page: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html it is important to use drivers directly from manufacture of GPU intel/amd/nvidia and not from PC manufacture like dell etc.. as they often have old and bugged drivers.

Hi. Good morning. I did that yesterday after I received Robert's first reply. I downloaded the latest drivers from Dell (Microsoft said there were no updates). Installed. And rebooted.

Same behavior. Still crashes.

Thank you.

Here is the msinfo32 output for the display driver:

Name Intel(R) HD Graphics 630
PNP Device ID PCI\VEN_8086&DEV_5912&SUBSYS_07DB1028&REV_04\3&11583659&0&10
Adapter Type Intel(R) HD Graphics Family, Intel Corporation compatible
Adapter Description Intel(R) HD Graphics 630
Adapter RAM 1.00 GB (1,073,741,824 bytes)
Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igd12umd64.dll
Driver Version 26.20.100.6951
INF File oem3.inf (iKBLD_w10_DS section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 3840 x 1600 x 59 hertz
Bits/Pixel 32
Memory Address 0xDB000000-0xDBFFFFFF
Memory Address 0x90000000-0x9FFFFFFF
I/O Port 0x0000FEC0-0x0000FEFF
IRQ Channel IRQ 4294967275
Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\KI132869.INF_AMD64_052EB72D070DF60F\IGDKMD64.SYS (26.20.100.6951, 19.10 MB (20,024,184 bytes), 7/15/2019 3:15 AM)

> In #72098#822152, @MaciejJutrzenka wrote: > @George-Ellenburg Hi! in deed the 2.81 introduced a few GPU problems as many reports are happening.. however a lot of them is simply because of the drivers are not up to date.. plz try updateing your drivers following this page: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html it is important to use drivers directly from manufacture of GPU intel/amd/nvidia and not from PC manufacture like dell etc.. as they often have old and bugged drivers. Hi. Good morning. I did that yesterday after I received Robert's first reply. I downloaded the latest drivers from Dell (Microsoft said there were no updates). Installed. And rebooted. Same behavior. Still crashes. Thank you. Here is the msinfo32 output for the display driver: Name Intel(R) HD Graphics 630 PNP Device ID PCI\VEN_8086&DEV_5912&SUBSYS_07DB1028&REV_04\3&11583659&0&10 Adapter Type Intel(R) HD Graphics Family, Intel Corporation compatible Adapter Description Intel(R) HD Graphics 630 Adapter RAM 1.00 GB (1,073,741,824 bytes) Installed Drivers C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki132869.inf_amd64_052eb72d070df60f\igd12umd64.dll Driver Version 26.20.100.6951 INF File oem3.inf (iKBLD_w10_DS section) Color Planes Not Available Color Table Entries 4294967296 Resolution 3840 x 1600 x 59 hertz Bits/Pixel 32 Memory Address 0xDB000000-0xDBFFFFFF Memory Address 0x90000000-0x9FFFFFFF I/O Port 0x0000FEC0-0x0000FEFF IRQ Channel IRQ 4294967275 Driver C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\KI132869.INF_AMD64_052EB72D070DF60F\IGDKMD64.SYS (26.20.100.6951, 19.10 MB (20,024,184 bytes), 7/15/2019 3:15 AM)

I will download the latest driver directly from Intel per your request this afternoon. I need to leave for work now.

https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630

I will download the latest driver directly from Intel per your request this afternoon. I need to leave for work now. https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630

Just an FYI it won't let me install the driver from Intel:

Just an FYI it won't let me install the driver from Intel: ![image.png](https://archive.blender.org/developer/F8184814/image.png)

Added subscriber: @mano-wii

The crash log looks incomplete.
That common EXCEPTION_ACCESS_VIOLATION information is missing at the end of it.
It's something like this:

(...)
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000065538649
Module  : C:\Windows\system32\nvoglv64.DLL

Try to run blender_debug-gpu.cmd that is included in the download.
After Blender closes, the logs will be in a text file which can be attached here.

Also test the others like blender_debug_gpu_glitchworkaround.cmd and report here if any of them make a difference.

The crash log looks incomplete. That common `EXCEPTION_ACCESS_VIOLATION` information is missing at the end of it. It's something like this: ``` (...) Error : EXCEPTION_ACCESS_VIOLATION Address : 0x0000000065538649 Module : C:\Windows\system32\nvoglv64.DLL ``` Try to run `blender_debug-gpu.cmd` that is included in the download. After Blender closes, the logs will be in a text file which can be attached here. Also test the others like `blender_debug_gpu_glitchworkaround.cmd` and report here if any of them make a difference.

@George-Ellenburg That's unfortunate, some vendors block the installation of drivers. You may be able to install the driver manually through the device manager as described in this How-to Geek tutorial (at your own risk).

@George-Ellenburg That's unfortunate, some vendors block the installation of drivers. You may be able to install the driver manually through the device manager as described in this [How-to Geek tutorial ](https://www.howtogeek.com/343287/how-to-fix-the-driver-being-installed-is-not-validated-for-this-computer-on-intel-computers/) (at your own risk).

Unable to manually update the driver. It will not apply. Was directed to use the Intel Driver Driver & Support Assistant. Here's the result of the scan:

And here's the full scan report:

Detailed-System-Report.html

Unable to manually update the driver. It will not apply. Was directed to use the Intel Driver Driver & Support Assistant. Here's the result of the scan: ![image.png](https://archive.blender.org/developer/F8185435/image.png) And here's the full scan report: [Detailed-System-Report.html](https://archive.blender.org/developer/F8185437/Detailed-System-Report.html)

Somebody had mentioned that the debug logs did not appear to be complete.

They were generated from running the debug .cmd file.

I'll run it again for you!

blender_debug_output.txt

blender_system_info.txt

Somebody had mentioned that the debug logs did not appear to be complete. They were generated from running the debug .cmd file. I'll run it again for you! ![image.png](https://archive.blender.org/developer/F8185441/image.png) ![image.png](https://archive.blender.org/developer/F8185444/image.png) [blender_debug_output.txt](https://archive.blender.org/developer/F8185446/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8185447/blender_system_info.txt)

Oops. Pasted the wrong image. Here:

Oops. Pasted the wrong image. Here: ![image.png](https://archive.blender.org/developer/F8185448/image.png)

For kicks and grins I just tried to (download) & run Blender 2.81 portable (ZIP) and the Steam version.

Both crash on startup as well.

For kicks and grins I just tried to (download) & run Blender 2.81 portable (ZIP) and the Steam version. Both crash on startup as well.

Added subscribers: @Jeroen-Bakker, @lichtwerk

@Jeroen-Bakker, @fclem: anything to check further here?

@George-Ellenburg Can you try the 2.82 beta?

I really think this is a driver issue. Texture creation seems to fail just after the first one.

The GL_OUT_OF_MEMORY is concerning but i'm pretty sure it's a false alert.

Why is that so? Why does it work in 2.80? did someone touch the GHOST layer? @Jeroen-Bakker have you any idea?

@George-Ellenburg Can you try the 2.82 beta? I really think this is a driver issue. Texture creation seems to fail just after the first one. The GL_OUT_OF_MEMORY is concerning but i'm pretty sure it's a false alert. Why is that so? Why does it work in 2.80? did someone touch the GHOST layer? @Jeroen-Bakker have you any idea?

The last change to the GhostWGL part was done in Mai 2019 so would already be present in 2.80.
Looking at the information of the log files. There is a log where it crashes inside the NVIDIA driver, but Blender thinks it is using the Intel GPU. that could be related to the soft switch etc.
My guess would be that a different OpenGL driver is selected between the OS vs Blender. The driver doesn't know the Intel GPU and fails on all calls. But this is a big guess, we need to find proof of this. Especially as 2.80 worked.

Best way forward is to find the commit that fails on this configuration, but that needs a developer (or technical user) to proceed. @George-Ellenburg are you up to such a task?

Sometimes these configurations have the ability in the bios to select which GPU is the primary GPU...

The last change to the GhostWGL part was done in Mai 2019 so would already be present in 2.80. Looking at the information of the log files. There is a log where it crashes inside the NVIDIA driver, but Blender thinks it is using the Intel GPU. that could be related to the soft switch etc. My guess would be that a different OpenGL driver is selected between the OS vs Blender. The driver doesn't know the Intel GPU and fails on all calls. But this is a big guess, we need to find proof of this. Especially as 2.80 worked. Best way forward is to find the commit that fails on this configuration, but that needs a developer (or technical user) to proceed. @George-Ellenburg are you up to such a task? Sometimes these configurations have the ability in the bios to select which GPU is the primary GPU...

There are also other ways to run with only one gpu. Sometimes, you can just rightclick on the executable file and choose with gpu to use.

Something got changed in 2.81 compared to 2.80 that triggers low end GPU's like crazy. @fclem maybe this is some what linked to that issiue that was on mac and that merged report about multiple materials?

Added subscriber: @bry_art_by_bry

Same problems here, Blender works great with 2.80 and 2.81 worked for a day then crashes at start up.
No driver updates from Nvidia and Intel will not let me update my graphic 630.

If it helps 2.81 worked great until I updated Bpainter for 2.81 and even that worked for a couple hours?

I'm not a programmer but have invested into 2.81 and would actually like it to work without me having to code?

I'm currently back using 2.80 and there is no issue.

Same problems here, Blender works great with 2.80 and 2.81 worked for a day then crashes at start up. No driver updates from Nvidia and Intel will not let me update my graphic 630. If it helps 2.81 worked great until I updated Bpainter for 2.81 and even that worked for a couple hours? I'm not a programmer but have invested into 2.81 and would actually like it to work without me having to code? I'm currently back using 2.80 and there is no issue.

@bry_art_by_bry That's interesting, so 2.81 worked correctly at first for you. Can you start Blender 2.81 from the command line with the --factory-startup flag? It could be that the Bpainter update is a red herring though, since nothing in the error log of gellenburg suggests a crash caused by an add-on.

Could you please create a debug log of Blender 2.81 by running the blender_debug_gpu.cmd in its installation directory (by double clicking) and post the files here? Do you remember or can you check if there have been any Windows updates between the time 2.81 worked and then didn't?

@George-Ellenburg Have you been using Bpainter as well?

@bry_art_by_bry That's interesting, so 2.81 worked correctly at first for you. Can you start Blender 2.81 from the command line with the `--factory-startup` flag? It could be that the Bpainter update is a **red herring** though, since nothing in the error log of gellenburg suggests a crash caused by an add-on. Could you please create a debug log of Blender 2.81 by running the `blender_debug_gpu.cmd` in its installation directory (by double clicking) and post the files here? Do you remember or can you check if there have been any Windows updates between the time 2.81 worked and then didn't? @George-Ellenburg Have you been using Bpainter as well?

I've never used Bpainter.

I will download the 2.82 beta and give it a try.

I've never used Bpainter. I will download the 2.82 beta and give it a try.

Ok this is weird.

Just downloaded and ran:

Blender 2.82 Alpha
December 03, 15:36:19 - b81939716d
Windows 64 bit
146.75MB

When I clicked on blender.exe it crashed.

When I ran the command blender_factory_startup.cmd it crashed.

And it generated logs but I didn't save them. Sorry.

So I realized you probably want me to run blender_debug_gpu.cmd so I did.

And now this:

And here are the generated logs:

blender_debug_output.txt

blender_system_info.txt

So let me try running blender_factory_startup.cmd again.....

Yep. It crashed.

Here are those logs:

blender_debug_output.txt

blender_system_info.txt

So let me try blender_debug_gpu.cmd again......

And it works!

And here are those (new) logs again too.

blender_system_info.txt

blender_debug_output.txt

Ok this is weird. Just downloaded and ran: Blender 2.82 Alpha December 03, 15:36:19 - b81939716de8 Windows 64 bit 146.75MB When I clicked on blender.exe it crashed. When I ran the command blender_factory_startup.cmd it crashed. And it generated logs but I didn't save them. Sorry. So I realized you probably want me to run blender_debug_gpu.cmd so I did. And now this: ![image.png](https://archive.blender.org/developer/F8188016/image.png) And here are the generated logs: [blender_debug_output.txt](https://archive.blender.org/developer/F8188021/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8188022/blender_system_info.txt) So let me try running blender_factory_startup.cmd again..... Yep. It crashed. Here are those logs: [blender_debug_output.txt](https://archive.blender.org/developer/F8188024/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8188025/blender_system_info.txt) So let me try blender_debug_gpu.cmd again...... And it works! ![image.png](https://archive.blender.org/developer/F8188028/image.png) And here are those (new) logs again too. [blender_system_info.txt](https://archive.blender.org/developer/F8188032/blender_system_info.txt) [blender_debug_output.txt](https://archive.blender.org/developer/F8188033/blender_debug_output.txt)

Excellent. When running with the gpu scripts. All available workarounds for driver bugs are enabled. One of them needs to be enabled for your driver configuration.

The upcoming days we will enable them one by one to find out which one is the needed workaround.

Please hold back until we give a signal to test.

Excellent. When running with the gpu scripts. All available workarounds for driver bugs are enabled. One of them needs to be enabled for your driver configuration. The upcoming days we will enable them one by one to find out which one is the needed workaround. Please hold back until we give a signal to test.

IIRC only blender_debug_gpu_glitchworkaround activates the workarounds. gpu_debug only enable the debug opengl extension which might trigger a specific driver path.

Added subscriber: @robert-18

This comment was removed by @bry_art_by_bry

*This comment was removed by @bry_art_by_bry*

I can't respond directly so I'll post this here. to @robert-18 Guetzkow

@echo off
echo Starting blender with GPU debugging options, log files will be created
echo in your temp folder, windows explorer will open after you close blender
echo to help you find them.
echo.
echo If you report a bug on https://developer.blender.org you can attach these files
echo by dragging them into the text area of your bug report, please include both
echo blender_debug_output.txt and blender_system_info.txt in your report.
echo.
pause
mkdir "%temp%\blender\debug_logs" > NUL 2>&1
echo.
echo Starting blender and waiting for it to exit....
set PYTHONPATH=
blender --debug --debug-gpu --python-expr "import bpy; bpy.ops.wm.sysinfo(filepath=r'%temp%\blender\debug_logs\blender_system_info.txt')" > "%temp%\blender\debug_logs\blender_debug_output.txt" 2>&1 < %0
explorer "%temp%\blender\debug_logs"

I can't respond directly so I'll post this here. to @robert-18 Guetzkow @echo off echo Starting blender with GPU debugging options, log files will be created echo in your temp folder, windows explorer will open after you close blender echo to help you find them. echo. echo If you report a bug on https://developer.blender.org you can attach these files echo by dragging them into the text area of your bug report, please include both echo blender_debug_output.txt and blender_system_info.txt in your report. echo. pause mkdir "%temp%\blender\debug_logs" > NUL 2>&1 echo. echo Starting blender and waiting for it to exit.... set PYTHONPATH= blender --debug --debug-gpu --python-expr "import bpy; bpy.ops.wm.sysinfo(filepath=r'%temp%\blender\debug_logs\blender_system_info.txt')" > "%temp%\blender\debug_logs\blender_debug_output.txt" 2>&1 < %0 explorer "%temp%\blender\debug_logs"

In addition I got it to start up from the factory start up line but I'm not sure if I should operate the program regularly from this point???
It also doesn't have any addons attached (set up).
Nor has my windows 10 updated since I first downloaded 2.81

thanks

In addition I got it to start up from the factory start up line but I'm not sure if I should operate the program regularly from this point??? It also doesn't have any addons attached (set up). Nor has my windows 10 updated since I first downloaded 2.81 thanks

@bry_art_by_bry There's been a misunderstanding, you should've double clicked on the blender_debug_gpu.cmd and uploaded the two files that are opened in the Windows Explorer once you close Blender (blender_debug_output.txt and blender_system_info.txt). Files can be uploaded by clicking on the cloud with an up-arrow icon. Since starting with factory settings allows you to run Blender properly it seems you don't have the same issue. In your case it may be caused by the problematic add-on which is disabled through --factory-startup . Uninstalling the problematic add-on should solve your issue.

@bry_art_by_bry There's been a misunderstanding, you should've double clicked on the `blender_debug_gpu.cmd` and uploaded the two files that are opened in the Windows Explorer once you close Blender (`blender_debug_output.txt` and `blender_system_info.txt`). Files can be uploaded by clicking on the cloud with an up-arrow icon. **Since starting with factory settings allows you to run Blender properly it seems you *don't* have the same issue.** In your case it may be caused by the problematic add-on which is disabled through `--factory-startup` . Uninstalling the problematic add-on should solve your issue.

@fclem As a test I ran 2.81 blender_debug_gpu_glitchworkaround.cmd and here was the generated log (it crashed too):
blender_debug_output.txt

blender-2.82-fda791ab1241-windows64:

blender.exe: CRASH

blender_debug_gpu.cmd:

blender_debug_output.txt

blender_debug_gpu_glitchworkaround.cmd: no crash

blender_debug_output.txt

blender_debug_log.cmd: CRASH

blender_debug_output.txt

blender_factory_startup.cmd: CRASH

blender_debug_output.txt

Hope this helps.

@fclem As a test I ran 2.81 blender_debug_gpu_glitchworkaround.cmd and here was the generated log (it crashed too): [blender_debug_output.txt](https://archive.blender.org/developer/F8189588/blender_debug_output.txt) blender-2.82-fda791ab1241-windows64: blender.exe: CRASH blender_debug_gpu.cmd: ![image.png](https://archive.blender.org/developer/F8189593/image.png) [blender_debug_output.txt](https://archive.blender.org/developer/F8189595/blender_debug_output.txt) blender_debug_gpu_glitchworkaround.cmd: no crash [blender_debug_output.txt](https://archive.blender.org/developer/F8189596/blender_debug_output.txt) blender_debug_log.cmd: CRASH [blender_debug_output.txt](https://archive.blender.org/developer/F8189597/blender_debug_output.txt) blender_factory_startup.cmd: CRASH [blender_debug_output.txt](https://archive.blender.org/developer/F8189600/blender_debug_output.txt) Hope this helps.

In #72098#823516, @rjg wrote:
@bry_art_by_bry There's been a misunderstanding, you should've double clicked on the blender_debug_gpu.cmd and uploaded the two files that are opened in the Windows Explorer once you close Blender (blender_debug_output.txt and blender_system_info.txt). Files can be uploaded by clicking on the cloud with an up-arrow icon. Since starting with factory settings allows you to run Blender properly it seems you don't have the same issue. In your case it may be caused by the problematic add-on which is disabled through --factory-startup . Uninstalling the problematic add-on should solve your issue.

Switching to fully guarded memory allocator.
Blender 2.81 (sub 16)
Build: 2019-11-20 16:33:00 Windows Release
argv- [x] = blender
argv- [x] = --debug
argv- [x] = --debug-gpu
argv- [x] = --python-expr
argv- [x] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\bry\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt')
Read prefs: C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\config\userpref.blend
read file C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\config\startup.blend

Version 281 sub 16 date 2019-11-20 14:27 hash 26bd5ebd42e3

GPUTexture: create : TEXTURE_CUBE_MAP, RGBA16F, w : 2, h : 2, d : 0, comp : 4, size : 0.00 MiB
GPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB
GPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB
GPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB
Using OpenGL 4.3 debug facilities
GL application marker: Successfully hooked OpenGL debug callback.
found bundled python: C:\Program Files\Blender Foundation\Blender 2.81\2.81\python
Warning: class subcustomPropertiesGroup contains a property which should be an annotation!
C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\scripts\addons\FloatingWindows_V2.py:62

  assign as a type annotation: subcustomPropertiesGroup.customString

Warning: class customPropertiesGroup contains a property which should be an annotation!
C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\scripts\addons\FloatingWindows_V2.py:65

  assign as a type annotation: customPropertiesGroup.subLists

Warning: class FloatWindowsPref contains a property which should be an annotation!
C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\scripts\addons\FloatingWindows_V2.py:3109

  assign as a type annotation: FloatWindowsPref.winaero
  assign as a type annotation: FloatWindowsPref.IsPie
  assign as a type annotation: FloatWindowsPref.IsPieFat
  assign as a type annotation: FloatWindowsPref.IsPie2
  assign as a type annotation: FloatWindowsPref.IsPin
  assign as a type annotation: FloatWindowsPref.custom_01_name
  assign as a type annotation: FloatWindowsPref.custom_01_icon
  assign as a type annotation: FloatWindowsPref.custom_01_x
  assign as a type annotation: FloatWindowsPref.custom_01_y
  assign as a type annotation: FloatWindowsPref.custom_01_perc
  assign as a type annotation: FloatWindowsPref.custom_01_cursor
  assign as a type annotation: FloatWindowsPref.custom_01_loc_x
  assign as a type annotation: FloatWindowsPref.custom_01_loc_y
  assign as a type annotation: FloatWindowsPref.custom_01_show_debug
  assign as a type annotation: FloatWindowsPref.custom_01_editor
  assign as a type annotation: FloatWindowsPref.custom_01_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_01_hide_header
  assign as a type annotation: FloatWindowsPref.custom_01_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_01_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_01_xray
  assign as a type annotation: FloatWindowsPref.custom_01_wire
  assign as a type annotation: FloatWindowsPref.custom_01_local
  assign as a type annotation: FloatWindowsPref.custom_01_ortho
  assign as a type annotation: FloatWindowsPref.custom_01_move
  assign as a type annotation: FloatWindowsPref.custom_01_view
  assign as a type annotation: FloatWindowsPref.custom_01_render
  assign as a type annotation: FloatWindowsPref.custom_01_mode
  assign as a type annotation: FloatWindowsPref.custom_01_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_01_home
  assign as a type annotation: FloatWindowsPref.custom_01_focus
  assign as a type annotation: FloatWindowsPref.custom_02_name
  assign as a type annotation: FloatWindowsPref.custom_02_icon
  assign as a type annotation: FloatWindowsPref.custom_02_x
  assign as a type annotation: FloatWindowsPref.custom_02_y
  assign as a type annotation: FloatWindowsPref.custom_02_perc
  assign as a type annotation: FloatWindowsPref.custom_02_cursor
  assign as a type annotation: FloatWindowsPref.custom_02_loc_x
  assign as a type annotation: FloatWindowsPref.custom_02_loc_y
  assign as a type annotation: FloatWindowsPref.custom_02_show_debug
  assign as a type annotation: FloatWindowsPref.custom_02_editor
  assign as a type annotation: FloatWindowsPref.custom_02_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_02_hide_header
  assign as a type annotation: FloatWindowsPref.custom_02_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_02_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_02_xray
  assign as a type annotation: FloatWindowsPref.custom_02_wire
  assign as a type annotation: FloatWindowsPref.custom_02_local
  assign as a type annotation: FloatWindowsPref.custom_02_ortho
  assign as a type annotation: FloatWindowsPref.custom_02_move
  assign as a type annotation: FloatWindowsPref.custom_02_view
  assign as a type annotation: FloatWindowsPref.custom_02_render
  assign as a type annotation: FloatWindowsPref.custom_02_mode
  assign as a type annotation: FloatWindowsPref.custom_02_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_02_home
  assign as a type annotation: FloatWindowsPref.custom_02_focus
  assign as a type annotation: FloatWindowsPref.custom_03_name
  assign as a type annotation: FloatWindowsPref.custom_03_icon
  assign as a type annotation: FloatWindowsPref.custom_03_x
  assign as a type annotation: FloatWindowsPref.custom_03_y
  assign as a type annotation: FloatWindowsPref.custom_03_perc
  assign as a type annotation: FloatWindowsPref.custom_03_cursor
  assign as a type annotation: FloatWindowsPref.custom_03_loc_x
  assign as a type annotation: FloatWindowsPref.custom_03_loc_y
  assign as a type annotation: FloatWindowsPref.custom_03_show_debug
  assign as a type annotation: FloatWindowsPref.custom_03_editor
  assign as a type annotation: FloatWindowsPref.custom_03_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_03_hide_header
  assign as a type annotation: FloatWindowsPref.custom_03_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_03_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_03_xray
  assign as a type annotation: FloatWindowsPref.custom_03_wire
  assign as a type annotation: FloatWindowsPref.custom_03_local
  assign as a type annotation: FloatWindowsPref.custom_03_ortho
  assign as a type annotation: FloatWindowsPref.custom_03_move
  assign as a type annotation: FloatWindowsPref.custom_03_view
  assign as a type annotation: FloatWindowsPref.custom_03_render
  assign as a type annotation: FloatWindowsPref.custom_03_mode
  assign as a type annotation: FloatWindowsPref.custom_03_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_03_home
  assign as a type annotation: FloatWindowsPref.custom_03_focus
  assign as a type annotation: FloatWindowsPref.custom_04_name
  assign as a type annotation: FloatWindowsPref.custom_04_icon
  assign as a type annotation: FloatWindowsPref.custom_04_x
  assign as a type annotation: FloatWindowsPref.custom_04_y
  assign as a type annotation: FloatWindowsPref.custom_04_perc
  assign as a type annotation: FloatWindowsPref.custom_04_cursor
  assign as a type annotation: FloatWindowsPref.custom_04_loc_x
  assign as a type annotation: FloatWindowsPref.custom_04_loc_y
  assign as a type annotation: FloatWindowsPref.custom_04_show_debug
  assign as a type annotation: FloatWindowsPref.custom_04_editor
  assign as a type annotation: FloatWindowsPref.custom_04_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_04_hide_header
  assign as a type annotation: FloatWindowsPref.custom_04_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_04_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_04_xray
  assign as a type annotation: FloatWindowsPref.custom_04_wire
  assign as a type annotation: FloatWindowsPref.custom_04_local
  assign as a type annotation: FloatWindowsPref.custom_04_ortho
  assign as a type annotation: FloatWindowsPref.custom_04_move
  assign as a type annotation: FloatWindowsPref.custom_04_view
  assign as a type annotation: FloatWindowsPref.custom_04_render
  assign as a type annotation: FloatWindowsPref.custom_04_mode
  assign as a type annotation: FloatWindowsPref.custom_04_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_04_home
  assign as a type annotation: FloatWindowsPref.custom_04_focus
  assign as a type annotation: FloatWindowsPref.custom_05_name
  assign as a type annotation: FloatWindowsPref.custom_05_icon
  assign as a type annotation: FloatWindowsPref.custom_05_x
  assign as a type annotation: FloatWindowsPref.custom_05_y
  assign as a type annotation: FloatWindowsPref.custom_05_perc
  assign as a type annotation: FloatWindowsPref.custom_05_cursor
  assign as a type annotation: FloatWindowsPref.custom_05_loc_x
  assign as a type annotation: FloatWindowsPref.custom_05_loc_y
  assign as a type annotation: FloatWindowsPref.custom_05_show_debug
  assign as a type annotation: FloatWindowsPref.custom_05_editor
  assign as a type annotation: FloatWindowsPref.custom_05_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_05_hide_header
  assign as a type annotation: FloatWindowsPref.custom_05_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_05_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_05_xray
  assign as a type annotation: FloatWindowsPref.custom_05_wire
  assign as a type annotation: FloatWindowsPref.custom_05_local
  assign as a type annotation: FloatWindowsPref.custom_05_ortho
  assign as a type annotation: FloatWindowsPref.custom_05_move
  assign as a type annotation: FloatWindowsPref.custom_05_view
  assign as a type annotation: FloatWindowsPref.custom_05_render
  assign as a type annotation: FloatWindowsPref.custom_05_mode
  assign as a type annotation: FloatWindowsPref.custom_05_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_05_home
  assign as a type annotation: FloatWindowsPref.custom_05_focus
  assign as a type annotation: FloatWindowsPref.custom_06_name
  assign as a type annotation: FloatWindowsPref.custom_06_icon
  assign as a type annotation: FloatWindowsPref.custom_06_x
  assign as a type annotation: FloatWindowsPref.custom_06_y
  assign as a type annotation: FloatWindowsPref.custom_06_perc
  assign as a type annotation: FloatWindowsPref.custom_06_cursor
  assign as a type annotation: FloatWindowsPref.custom_06_loc_x
  assign as a type annotation: FloatWindowsPref.custom_06_loc_y
  assign as a type annotation: FloatWindowsPref.custom_06_show_debug
  assign as a type annotation: FloatWindowsPref.custom_06_editor
  assign as a type annotation: FloatWindowsPref.custom_06_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_06_hide_header
  assign as a type annotation: FloatWindowsPref.custom_06_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_06_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_06_xray
  assign as a type annotation: FloatWindowsPref.custom_06_wire
  assign as a type annotation: FloatWindowsPref.custom_06_local
  assign as a type annotation: FloatWindowsPref.custom_06_ortho
  assign as a type annotation: FloatWindowsPref.custom_06_move
  assign as a type annotation: FloatWindowsPref.custom_06_view
  assign as a type annotation: FloatWindowsPref.custom_06_render
  assign as a type annotation: FloatWindowsPref.custom_06_mode
  assign as a type annotation: FloatWindowsPref.custom_06_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_06_home
  assign as a type annotation: FloatWindowsPref.custom_06_focus
  assign as a type annotation: FloatWindowsPref.custom_07_name
  assign as a type annotation: FloatWindowsPref.custom_07_icon
  assign as a type annotation: FloatWindowsPref.custom_07_x
  assign as a type annotation: FloatWindowsPref.custom_07_y
  assign as a type annotation: FloatWindowsPref.custom_07_perc
  assign as a type annotation: FloatWindowsPref.custom_07_cursor
  assign as a type annotation: FloatWindowsPref.custom_07_loc_x
  assign as a type annotation: FloatWindowsPref.custom_07_loc_y
  assign as a type annotation: FloatWindowsPref.custom_07_show_debug
  assign as a type annotation: FloatWindowsPref.custom_07_editor
  assign as a type annotation: FloatWindowsPref.custom_07_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_07_hide_header
  assign as a type annotation: FloatWindowsPref.custom_07_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_07_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_07_xray
  assign as a type annotation: FloatWindowsPref.custom_07_wire
  assign as a type annotation: FloatWindowsPref.custom_07_local
  assign as a type annotation: FloatWindowsPref.custom_07_ortho
  assign as a type annotation: FloatWindowsPref.custom_07_move
  assign as a type annotation: FloatWindowsPref.custom_07_view
  assign as a type annotation: FloatWindowsPref.custom_07_render
  assign as a type annotation: FloatWindowsPref.custom_07_mode
  assign as a type annotation: FloatWindowsPref.custom_07_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_07_home
  assign as a type annotation: FloatWindowsPref.custom_07_focus
  assign as a type annotation: FloatWindowsPref.custom_08_name
  assign as a type annotation: FloatWindowsPref.custom_08_icon
  assign as a type annotation: FloatWindowsPref.custom_08_x
  assign as a type annotation: FloatWindowsPref.custom_08_y
  assign as a type annotation: FloatWindowsPref.custom_08_perc
  assign as a type annotation: FloatWindowsPref.custom_08_cursor
  assign as a type annotation: FloatWindowsPref.custom_08_loc_x
  assign as a type annotation: FloatWindowsPref.custom_08_loc_y
  assign as a type annotation: FloatWindowsPref.custom_08_show_debug
  assign as a type annotation: FloatWindowsPref.custom_08_editor
  assign as a type annotation: FloatWindowsPref.custom_08_hide_tn
  assign as a type annotation: FloatWindowsPref.custom_08_hide_header
  assign as a type annotation: FloatWindowsPref.custom_08_hide_overlay
  assign as a type annotation: FloatWindowsPref.custom_08_hide_gizmo
  assign as a type annotation: FloatWindowsPref.custom_08_xray
  assign as a type annotation: FloatWindowsPref.custom_08_wire
  assign as a type annotation: FloatWindowsPref.custom_08_local
  assign as a type annotation: FloatWindowsPref.custom_08_ortho
  assign as a type annotation: FloatWindowsPref.custom_08_move
  assign as a type annotation: FloatWindowsPref.custom_08_view
  assign as a type annotation: FloatWindowsPref.custom_08_render
  assign as a type annotation: FloatWindowsPref.custom_08_mode
  assign as a type annotation: FloatWindowsPref.custom_08_3dwalk
  assign as a type annotation: FloatWindowsPref.custom_08_home
  assign as a type annotation: FloatWindowsPref.custom_08_focus
  assign as a type annotation: FloatWindowsPref.cam_lock
  assign as a type annotation: FloatWindowsPref.cam_header
  assign as a type annotation: FloatWindowsPref.cam_overlay
  assign as a type annotation: FloatWindowsPref.cam_render
  assign as a type annotation: FloatWindowsPref.cam_recenter
  assign as a type annotation: FloatWindowsPref.cam_auto_size
  assign as a type annotation: FloatWindowsPref.cam_local
  assign as a type annotation: FloatWindowsPref.show_debug
  assign as a type annotation: FloatWindowsPref.show_debug1
  assign as a type annotation: FloatWindowsPref.show_debug2
  assign as a type annotation: FloatWindowsPref.show_debug3
  assign as a type annotation: FloatWindowsPref.show_debug4

read file

Version 280 sub 57 date unknown hash unknown

read file

Version 280 sub 20 date 2018-07-14 11:44 hash 27ba739fb79

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF71F44E928
Module : C:\Program Files\Blender Foundation\Blender 2.81\blender.exe

> In #72098#823516, @rjg wrote: > @bry_art_by_bry There's been a misunderstanding, you should've double clicked on the `blender_debug_gpu.cmd` and uploaded the two files that are opened in the Windows Explorer once you close Blender (`blender_debug_output.txt` and `blender_system_info.txt`). Files can be uploaded by clicking on the cloud with an up-arrow icon. **Since starting with factory settings allows you to run Blender properly it seems you *don't* have the same issue.** In your case it may be caused by the problematic add-on which is disabled through `--factory-startup` . Uninstalling the problematic add-on should solve your issue. Switching to fully guarded memory allocator. Blender 2.81 (sub 16) Build: 2019-11-20 16:33:00 Windows Release argv- [x] = blender argv- [x] = --debug argv- [x] = --debug-gpu argv- [x] = --python-expr argv- [x] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Users\bry\AppData\Local\Temp\blender\debug_logs\blender_system_info.txt') Read prefs: C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\config\userpref.blend read file C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\config\startup.blend ``` Version 281 sub 16 date 2019-11-20 14:27 hash 26bd5ebd42e3 ``` GPUTexture: create : TEXTURE_CUBE_MAP, RGBA16F, w : 2, h : 2, d : 0, comp : 4, size : 0.00 MiB GPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB GPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB GPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB Using OpenGL 4.3 debug facilities GL application marker: Successfully hooked OpenGL debug callback. found bundled python: C:\Program Files\Blender Foundation\Blender 2.81\2.81\python Warning: class subcustomPropertiesGroup contains a property which should be an annotation! C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\scripts\addons\FloatingWindows_V2.py:62 ``` assign as a type annotation: subcustomPropertiesGroup.customString ``` Warning: class customPropertiesGroup contains a property which should be an annotation! C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\scripts\addons\FloatingWindows_V2.py:65 ``` assign as a type annotation: customPropertiesGroup.subLists ``` Warning: class FloatWindowsPref contains a property which should be an annotation! C:\Users\bry\AppData\Roaming\Blender Foundation\Blender\2.81\scripts\addons\FloatingWindows_V2.py:3109 ``` assign as a type annotation: FloatWindowsPref.winaero assign as a type annotation: FloatWindowsPref.IsPie assign as a type annotation: FloatWindowsPref.IsPieFat assign as a type annotation: FloatWindowsPref.IsPie2 assign as a type annotation: FloatWindowsPref.IsPin assign as a type annotation: FloatWindowsPref.custom_01_name assign as a type annotation: FloatWindowsPref.custom_01_icon assign as a type annotation: FloatWindowsPref.custom_01_x assign as a type annotation: FloatWindowsPref.custom_01_y assign as a type annotation: FloatWindowsPref.custom_01_perc assign as a type annotation: FloatWindowsPref.custom_01_cursor assign as a type annotation: FloatWindowsPref.custom_01_loc_x assign as a type annotation: FloatWindowsPref.custom_01_loc_y assign as a type annotation: FloatWindowsPref.custom_01_show_debug assign as a type annotation: FloatWindowsPref.custom_01_editor assign as a type annotation: FloatWindowsPref.custom_01_hide_tn assign as a type annotation: FloatWindowsPref.custom_01_hide_header assign as a type annotation: FloatWindowsPref.custom_01_hide_overlay assign as a type annotation: FloatWindowsPref.custom_01_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_01_xray assign as a type annotation: FloatWindowsPref.custom_01_wire assign as a type annotation: FloatWindowsPref.custom_01_local assign as a type annotation: FloatWindowsPref.custom_01_ortho assign as a type annotation: FloatWindowsPref.custom_01_move assign as a type annotation: FloatWindowsPref.custom_01_view assign as a type annotation: FloatWindowsPref.custom_01_render assign as a type annotation: FloatWindowsPref.custom_01_mode assign as a type annotation: FloatWindowsPref.custom_01_3dwalk assign as a type annotation: FloatWindowsPref.custom_01_home assign as a type annotation: FloatWindowsPref.custom_01_focus assign as a type annotation: FloatWindowsPref.custom_02_name assign as a type annotation: FloatWindowsPref.custom_02_icon assign as a type annotation: FloatWindowsPref.custom_02_x assign as a type annotation: FloatWindowsPref.custom_02_y assign as a type annotation: FloatWindowsPref.custom_02_perc assign as a type annotation: FloatWindowsPref.custom_02_cursor assign as a type annotation: FloatWindowsPref.custom_02_loc_x assign as a type annotation: FloatWindowsPref.custom_02_loc_y assign as a type annotation: FloatWindowsPref.custom_02_show_debug assign as a type annotation: FloatWindowsPref.custom_02_editor assign as a type annotation: FloatWindowsPref.custom_02_hide_tn assign as a type annotation: FloatWindowsPref.custom_02_hide_header assign as a type annotation: FloatWindowsPref.custom_02_hide_overlay assign as a type annotation: FloatWindowsPref.custom_02_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_02_xray assign as a type annotation: FloatWindowsPref.custom_02_wire assign as a type annotation: FloatWindowsPref.custom_02_local assign as a type annotation: FloatWindowsPref.custom_02_ortho assign as a type annotation: FloatWindowsPref.custom_02_move assign as a type annotation: FloatWindowsPref.custom_02_view assign as a type annotation: FloatWindowsPref.custom_02_render assign as a type annotation: FloatWindowsPref.custom_02_mode assign as a type annotation: FloatWindowsPref.custom_02_3dwalk assign as a type annotation: FloatWindowsPref.custom_02_home assign as a type annotation: FloatWindowsPref.custom_02_focus assign as a type annotation: FloatWindowsPref.custom_03_name assign as a type annotation: FloatWindowsPref.custom_03_icon assign as a type annotation: FloatWindowsPref.custom_03_x assign as a type annotation: FloatWindowsPref.custom_03_y assign as a type annotation: FloatWindowsPref.custom_03_perc assign as a type annotation: FloatWindowsPref.custom_03_cursor assign as a type annotation: FloatWindowsPref.custom_03_loc_x assign as a type annotation: FloatWindowsPref.custom_03_loc_y assign as a type annotation: FloatWindowsPref.custom_03_show_debug assign as a type annotation: FloatWindowsPref.custom_03_editor assign as a type annotation: FloatWindowsPref.custom_03_hide_tn assign as a type annotation: FloatWindowsPref.custom_03_hide_header assign as a type annotation: FloatWindowsPref.custom_03_hide_overlay assign as a type annotation: FloatWindowsPref.custom_03_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_03_xray assign as a type annotation: FloatWindowsPref.custom_03_wire assign as a type annotation: FloatWindowsPref.custom_03_local assign as a type annotation: FloatWindowsPref.custom_03_ortho assign as a type annotation: FloatWindowsPref.custom_03_move assign as a type annotation: FloatWindowsPref.custom_03_view assign as a type annotation: FloatWindowsPref.custom_03_render assign as a type annotation: FloatWindowsPref.custom_03_mode assign as a type annotation: FloatWindowsPref.custom_03_3dwalk assign as a type annotation: FloatWindowsPref.custom_03_home assign as a type annotation: FloatWindowsPref.custom_03_focus assign as a type annotation: FloatWindowsPref.custom_04_name assign as a type annotation: FloatWindowsPref.custom_04_icon assign as a type annotation: FloatWindowsPref.custom_04_x assign as a type annotation: FloatWindowsPref.custom_04_y assign as a type annotation: FloatWindowsPref.custom_04_perc assign as a type annotation: FloatWindowsPref.custom_04_cursor assign as a type annotation: FloatWindowsPref.custom_04_loc_x assign as a type annotation: FloatWindowsPref.custom_04_loc_y assign as a type annotation: FloatWindowsPref.custom_04_show_debug assign as a type annotation: FloatWindowsPref.custom_04_editor assign as a type annotation: FloatWindowsPref.custom_04_hide_tn assign as a type annotation: FloatWindowsPref.custom_04_hide_header assign as a type annotation: FloatWindowsPref.custom_04_hide_overlay assign as a type annotation: FloatWindowsPref.custom_04_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_04_xray assign as a type annotation: FloatWindowsPref.custom_04_wire assign as a type annotation: FloatWindowsPref.custom_04_local assign as a type annotation: FloatWindowsPref.custom_04_ortho assign as a type annotation: FloatWindowsPref.custom_04_move assign as a type annotation: FloatWindowsPref.custom_04_view assign as a type annotation: FloatWindowsPref.custom_04_render assign as a type annotation: FloatWindowsPref.custom_04_mode assign as a type annotation: FloatWindowsPref.custom_04_3dwalk assign as a type annotation: FloatWindowsPref.custom_04_home assign as a type annotation: FloatWindowsPref.custom_04_focus assign as a type annotation: FloatWindowsPref.custom_05_name assign as a type annotation: FloatWindowsPref.custom_05_icon assign as a type annotation: FloatWindowsPref.custom_05_x assign as a type annotation: FloatWindowsPref.custom_05_y assign as a type annotation: FloatWindowsPref.custom_05_perc assign as a type annotation: FloatWindowsPref.custom_05_cursor assign as a type annotation: FloatWindowsPref.custom_05_loc_x assign as a type annotation: FloatWindowsPref.custom_05_loc_y assign as a type annotation: FloatWindowsPref.custom_05_show_debug assign as a type annotation: FloatWindowsPref.custom_05_editor assign as a type annotation: FloatWindowsPref.custom_05_hide_tn assign as a type annotation: FloatWindowsPref.custom_05_hide_header assign as a type annotation: FloatWindowsPref.custom_05_hide_overlay assign as a type annotation: FloatWindowsPref.custom_05_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_05_xray assign as a type annotation: FloatWindowsPref.custom_05_wire assign as a type annotation: FloatWindowsPref.custom_05_local assign as a type annotation: FloatWindowsPref.custom_05_ortho assign as a type annotation: FloatWindowsPref.custom_05_move assign as a type annotation: FloatWindowsPref.custom_05_view assign as a type annotation: FloatWindowsPref.custom_05_render assign as a type annotation: FloatWindowsPref.custom_05_mode assign as a type annotation: FloatWindowsPref.custom_05_3dwalk assign as a type annotation: FloatWindowsPref.custom_05_home assign as a type annotation: FloatWindowsPref.custom_05_focus assign as a type annotation: FloatWindowsPref.custom_06_name assign as a type annotation: FloatWindowsPref.custom_06_icon assign as a type annotation: FloatWindowsPref.custom_06_x assign as a type annotation: FloatWindowsPref.custom_06_y assign as a type annotation: FloatWindowsPref.custom_06_perc assign as a type annotation: FloatWindowsPref.custom_06_cursor assign as a type annotation: FloatWindowsPref.custom_06_loc_x assign as a type annotation: FloatWindowsPref.custom_06_loc_y assign as a type annotation: FloatWindowsPref.custom_06_show_debug assign as a type annotation: FloatWindowsPref.custom_06_editor assign as a type annotation: FloatWindowsPref.custom_06_hide_tn assign as a type annotation: FloatWindowsPref.custom_06_hide_header assign as a type annotation: FloatWindowsPref.custom_06_hide_overlay assign as a type annotation: FloatWindowsPref.custom_06_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_06_xray assign as a type annotation: FloatWindowsPref.custom_06_wire assign as a type annotation: FloatWindowsPref.custom_06_local assign as a type annotation: FloatWindowsPref.custom_06_ortho assign as a type annotation: FloatWindowsPref.custom_06_move assign as a type annotation: FloatWindowsPref.custom_06_view assign as a type annotation: FloatWindowsPref.custom_06_render assign as a type annotation: FloatWindowsPref.custom_06_mode assign as a type annotation: FloatWindowsPref.custom_06_3dwalk assign as a type annotation: FloatWindowsPref.custom_06_home assign as a type annotation: FloatWindowsPref.custom_06_focus assign as a type annotation: FloatWindowsPref.custom_07_name assign as a type annotation: FloatWindowsPref.custom_07_icon assign as a type annotation: FloatWindowsPref.custom_07_x assign as a type annotation: FloatWindowsPref.custom_07_y assign as a type annotation: FloatWindowsPref.custom_07_perc assign as a type annotation: FloatWindowsPref.custom_07_cursor assign as a type annotation: FloatWindowsPref.custom_07_loc_x assign as a type annotation: FloatWindowsPref.custom_07_loc_y assign as a type annotation: FloatWindowsPref.custom_07_show_debug assign as a type annotation: FloatWindowsPref.custom_07_editor assign as a type annotation: FloatWindowsPref.custom_07_hide_tn assign as a type annotation: FloatWindowsPref.custom_07_hide_header assign as a type annotation: FloatWindowsPref.custom_07_hide_overlay assign as a type annotation: FloatWindowsPref.custom_07_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_07_xray assign as a type annotation: FloatWindowsPref.custom_07_wire assign as a type annotation: FloatWindowsPref.custom_07_local assign as a type annotation: FloatWindowsPref.custom_07_ortho assign as a type annotation: FloatWindowsPref.custom_07_move assign as a type annotation: FloatWindowsPref.custom_07_view assign as a type annotation: FloatWindowsPref.custom_07_render assign as a type annotation: FloatWindowsPref.custom_07_mode assign as a type annotation: FloatWindowsPref.custom_07_3dwalk assign as a type annotation: FloatWindowsPref.custom_07_home assign as a type annotation: FloatWindowsPref.custom_07_focus assign as a type annotation: FloatWindowsPref.custom_08_name assign as a type annotation: FloatWindowsPref.custom_08_icon assign as a type annotation: FloatWindowsPref.custom_08_x assign as a type annotation: FloatWindowsPref.custom_08_y assign as a type annotation: FloatWindowsPref.custom_08_perc assign as a type annotation: FloatWindowsPref.custom_08_cursor assign as a type annotation: FloatWindowsPref.custom_08_loc_x assign as a type annotation: FloatWindowsPref.custom_08_loc_y assign as a type annotation: FloatWindowsPref.custom_08_show_debug assign as a type annotation: FloatWindowsPref.custom_08_editor assign as a type annotation: FloatWindowsPref.custom_08_hide_tn assign as a type annotation: FloatWindowsPref.custom_08_hide_header assign as a type annotation: FloatWindowsPref.custom_08_hide_overlay assign as a type annotation: FloatWindowsPref.custom_08_hide_gizmo assign as a type annotation: FloatWindowsPref.custom_08_xray assign as a type annotation: FloatWindowsPref.custom_08_wire assign as a type annotation: FloatWindowsPref.custom_08_local assign as a type annotation: FloatWindowsPref.custom_08_ortho assign as a type annotation: FloatWindowsPref.custom_08_move assign as a type annotation: FloatWindowsPref.custom_08_view assign as a type annotation: FloatWindowsPref.custom_08_render assign as a type annotation: FloatWindowsPref.custom_08_mode assign as a type annotation: FloatWindowsPref.custom_08_3dwalk assign as a type annotation: FloatWindowsPref.custom_08_home assign as a type annotation: FloatWindowsPref.custom_08_focus assign as a type annotation: FloatWindowsPref.cam_lock assign as a type annotation: FloatWindowsPref.cam_header assign as a type annotation: FloatWindowsPref.cam_overlay assign as a type annotation: FloatWindowsPref.cam_render assign as a type annotation: FloatWindowsPref.cam_recenter assign as a type annotation: FloatWindowsPref.cam_auto_size assign as a type annotation: FloatWindowsPref.cam_local assign as a type annotation: FloatWindowsPref.show_debug assign as a type annotation: FloatWindowsPref.show_debug1 assign as a type annotation: FloatWindowsPref.show_debug2 assign as a type annotation: FloatWindowsPref.show_debug3 assign as a type annotation: FloatWindowsPref.show_debug4 ``` read file ``` Version 280 sub 57 date unknown hash unknown ``` read file ``` Version 280 sub 20 date 2018-07-14 11:44 hash 27ba739fb79 ``` Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF71F44E928 Module : C:\Program Files\Blender Foundation\Blender 2.81\blender.exe

This comment was removed by @bry_art_by_bry

*This comment was removed by @bry_art_by_bry*

In #72098#823516, @rjg wrote:
@bry_art_by_bry There's been a misunderstanding,

Sorry one more thing, I opened 2.81 and uploaded the files you suggested (cloud arrow key??)

I then went into 2.80 and deleted 'floating windows' addon and couldn't find Bpainter anywhere in the registry.

I then went into 2.81 'start up file' and now that is crashing.

> In #72098#823516, @rjg wrote: > @bry_art_by_bry There's been a misunderstanding, Sorry one more thing, I opened 2.81 and uploaded the files you suggested (cloud arrow key??) I then went into 2.80 and deleted 'floating windows' addon and couldn't find Bpainter anywhere in the registry. I then went into 2.81 'start up file' and now that is crashing.

@bry_art_by_bry Please remove the wall of text comments and upload the files.

@bry_art_by_bry Please remove the wall of text comments and *upload the files*. ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png)

In #72098#823845, @rjg wrote:
@bry_art_by_bry Please remove the wall of text comments and upload the files.

Sorry about that, not actually sure how to upload the files required. Perhaps a better report a bug system can be developed by blender for us non programmers. Many other programs report bugs automatically.

> In #72098#823845, @rjg wrote: > @bry_art_by_bry Please remove the wall of text comments and *upload the files*. ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png) Sorry about that, not actually sure how to upload the files required. Perhaps a better report a bug system can be developed by blender for us non programmers. Many other programs report bugs automatically.

@bry_art_by_bry There is a screenshot in my previous reply which marks the upload button with a red rectangle. This button is can be found in the area where you leave a comment on this page. You have to click on in order to upload the files. I've added another screenshot below.

We currently don't have an automated crash reporting, because we value privacy and automated telemetry is not a good idea in that regard. The developers have been discussing solution that could improve the reporting, e.g. users could manually approve error/crash log uploads. Such as solution may be available in the future.

@bry_art_by_bry There is a screenshot in my previous reply which marks the upload button with a red rectangle. This button is can be found in the area where you leave a comment on this page. You have to click on in order to upload the files. I've added another screenshot below. ![2019_12_05_upload_button.png](https://archive.blender.org/developer/F8191479/2019_12_05_upload_button.png) We currently don't have an automated crash reporting, because we value privacy and automated telemetry is not a good idea in that regard. The developers have been discussing solution that could improve the reporting, e.g. users could manually approve error/crash log uploads. Such as solution may be available in the future.

Added subscriber: @iss

Added subscriber: @Blendify

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Is this an issue still with Blender 2.82?

Still an issue I'm afraid.

I downloaded 2.82 over the weekend and it crashed at launch just like 2.81 did.

Still an issue I'm afraid. I downloaded 2.82 over the weekend and it crashed at launch just like 2.81 did.

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Added subscriber: @jounij

{F8387657}Hello,

I am also suffering from this problem i.e. Blender 2.82 occasionally works, but more often than not fails to start. The issued error messages are in the attachment.

Kind regards,

Jouni

{[F8387657](https://archive.blender.org/developer/F8387657/Blender2.82StartUpFailure.txt)}Hello, I am also suffering from this problem i.e. Blender 2.82 occasionally works, but more often than not fails to start. The issued error messages are in the attachment. Kind regards, Jouni

The original system-info.txt uses a Dell Driver from september 2019. We recommend to de-install this driver and use the latest driver found on the intel web site. You will only be able to install this driver after removing the dell driver. Please test with the latest driver from intel.

Added subscriber: @brecht

@Jeroen-Bakker, @fclem, we seem to have a lot of reports about Blender crashing startup with Intel cards. Can you guys get look through the reports and get the bottom of this, see what the pattern is?

We show a popup for old Intel drivers which we know have issues, but I don't know that there are issues resolved by upgrading e.g. 2019 drivers to the very latest. Given the limit driver support, often recent drivers are just the same old ones with maybe some security fixes.

Maybe some of the workarounds we have stopped working, and should be tested again (not necessarily on the actual Intel hardware, just whatever GPU you have)?

Maybe we are not detecting correctly when to apply workarounds? For example we have this, is the HD 630 in the same family?

    if (strstr(renderer, "UHD Graphics") ||
        /* Not UHD but affected by the same bugs. */
        strstr(renderer, "HD Graphics 530") || strstr(renderer, "Kaby Lake GT2") ||
        strstr(renderer, "Whiskey Lake")) {
      GPG.device |= GPU_DEVICE_INTEL_UHD;
    }

If we know that the glitch workarounds options work, figure out which one exactly?

Marking this as high priority, I really think we should look at this for 2.83.

@Jeroen-Bakker, @fclem, we seem to have a lot of reports about Blender crashing startup with Intel cards. Can you guys get look through the reports and get the bottom of this, see what the pattern is? We show a popup for old Intel drivers which we know have issues, but I don't know that there are issues resolved by upgrading e.g. 2019 drivers to the very latest. Given the limit driver support, often recent drivers are just the same old ones with maybe some security fixes. Maybe some of the workarounds we have stopped working, and should be tested again (not necessarily on the actual Intel hardware, just whatever GPU you have)? Maybe we are not detecting correctly when to apply workarounds? For example we have this, is the HD 630 in the same family? ``` if (strstr(renderer, "UHD Graphics") || /* Not UHD but affected by the same bugs. */ strstr(renderer, "HD Graphics 530") || strstr(renderer, "Kaby Lake GT2") || strstr(renderer, "Whiskey Lake")) { GPG.device |= GPU_DEVICE_INTEL_UHD; } ``` If we know that the glitch workarounds options work, figure out which one exactly? Marking this as high priority, I really think we should look at this for 2.83.

Added subscribers: @CarriEstabrook, @ankitm

Added subscriber: @XDloco

Last time i debuged this whole thing.. on intel HD4000.. the problem is around EEVEE.
maybe this is some help..

https://developer.blender.org/T72221

Last time i debuged this whole thing.. on intel HD4000.. the problem is around EEVEE. maybe this is some help.. https://developer.blender.org/T72221

Added subscriber: @iMineLink

Added subscribers: @Orandy, @JaisonAlexandreMartins

Hi!
Can someone explain to me why I get the same file when running any of these files? blender_debug_gpu.cmd, blender_debug_gpu_glitchworkaround.cmd, blender_debug_log.cmd
blender_debug_output.txt
blender_debug_output.txt

I also tried installing Blender 2.80 and 2.81, but that also didn't work.
What am I doing wrong?

Hi! Can someone explain to me why I get the same file when running any of these files? blender_debug_gpu.cmd, blender_debug_gpu_glitchworkaround.cmd, blender_debug_log.cmd blender_debug_output.txt [blender_debug_output.txt](https://archive.blender.org/developer/F8454861/blender_debug_output.txt) I also tried installing Blender 2.80 and 2.81, but that also didn't work. What am I doing wrong?

Hi everybody,

about the problem above, I tried many things to solve the problem (PS: I'm not a developer) and, following a tip from a friend of mine, at least for me, it worked and I was able to run Blender 2.81 and 2.82a:

click on Blender icon with right button;
click in properties;
choose compatibilities;
execute this program in mode of compatibility
apply

I believe that Blender run for you too.
(PS.2: sorry my english, I'm brazilian guy and not very good yet!).

Hi everybody, about the problem above, I tried many things to solve the problem (PS: I'm not a developer) and, following a tip from a friend of mine, at least for me, it worked and I was able to run Blender 2.81 and 2.82a: - click on Blender icon with right button; - click in properties; - choose compatibilities; - execute this program in mode of compatibility - apply I believe that Blender run for you too. (PS.2: sorry my english, I'm brazilian guy and not very good yet!).

execute this program in mode of compatibility

Just wanted to note that this workaround has helped 4-5 reports of blender crashing in support chat channel this week itself.
That makes it a good candidate for addition to troubleshooting docs, if people don't know it already.

> execute this program in mode of compatibility Just wanted to note that this workaround has helped 4-5 reports of blender crashing in support chat channel this week itself. That makes it a good candidate for addition to troubleshooting docs, if people don't know it already.

Added subscriber: @dark999

I can confirm what @ankitm wrote, in last week 6 users had solved crash problem with @JaisonAlexandreMartins workaround. Something in Window have broke trust of Blender executable, this make Blender crashing at startup or when user switch Viewport Shading. This report is related on Intel GPU but yhis workaround is nicely working on Amd GPU too (Radeon RX 580)

Added subscriber: @veronicadmello

Added subscriber: @weic1253

Added subscriber: @QT-Max

Added subscriber: @System9

Added subscriber: @linosia

MacBook Air 2017 user here :)
Have dual-core I5 and intel HD 6000

The only BUT -- I have Windows 10 1909 as Bootcamp -- with drivers from Apple

Everything works fine with 2.82a and 2.90 alpha
Was able to start app without problem and open some file (I usually use Mac OS, so tested file only for 5 min)

MacBook Air 2017 user here :) Have dual-core I5 and intel HD 6000 The only BUT -- I have Windows 10 1909 as Bootcamp -- with drivers from Apple Everything works fine with 2.82a and 2.90 alpha Was able to start app without problem and open some file (I usually use Mac OS, so tested file only for 5 min)

Added subscribers: @lauren_muller, @Alaska

Added subscriber: @EmmanuelManago

Since 13125e0948 was committed, can anyone test if the very latest Blender 2.83 build works better?
https://builder.blender.org/download/

Since 13125e0948 was committed, can anyone test if the very latest Blender 2.83 build works better? https://builder.blender.org/download/

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.

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

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

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

Removed subscriber: @weic1253

debug_logs_JJ_2020-05-23.zip Here you are. Thanks for looking into this!

[debug_logs_JJ_2020-05-23.zip](https://archive.blender.org/developer/F8549417/debug_logs_JJ_2020-05-23.zip) Here you are. Thanks for looking into this!

@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.

Added subscriber: @JulianEisel

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 {nav right-click > Run 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.

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 {nav right-click > Run with graphics processor}). I had to use [Windows Graphics settings ](https:*www.addictivetips.com/windows-tips/manage-graphics-performance-per-app-windows-10/) 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- [x] = C:\Program Files\Blender Foundation\blender-2.83-windows64\blender
argv- [x] = --debug
argv- [x] = --debug-gpu
argv- [x] = --python-expr
argv- [x] = 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

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- [x] = C:\Program Files\Blender Foundation\blender-2.83-windows64\\blender argv- [x] = --debug argv- [x] = --debug-gpu argv- [x] = --python-expr argv- [x] = 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

Removed subscriber: @Blendify

@jounij and with the blender_debug_gpu_glitchworkaround.cmd ?

Hi @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 @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).

@jounij can you try what @JulianEisel suggested?

Hi @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.

Removed subscriber: @linosia

Added subscribers: @mathieuhevey, @amy_aimei

@jounij @JulianEisel 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.

@jounij @JulianEisel 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,

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.

Hello @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.

@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:

Open Windows settings and change the setting for Blender back to "System Default".
Open Blender to see if it crashes. If it does, then continue.
Open the Nvidia control panel.
Select the "Manage 3D settings" section on the left of the control panel.
Select the "Program settings" panel in the center of the screen.
Add/browse for Blender.
Change the "Preferred graphics processor" option to the Intel GPU (Integrated graphics).
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.

@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.

Removed subscriber: @lauren_muller

Added subscriber: @lauren_muller

Removed subscriber: @lauren_muller

Added subscribers: @buggySoftware, @EAW

Added subscriber: @Dini

Hello @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.

Hello @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.

Added subscriber: @luciovr

Removed subscriber: @Gilberto.R

Added subscriber: @Yaruni

Added subscriber: @Matthew999

Added subscriber: @Gravijaton

Added subscriber: @romit_khurd

Added subscriber: @makeavoy

Added subscriber: @Ryukis

Added subscriber: @Oliver4Vood

Removed subscriber: @Oliver4Vood

Added subscriber: @Oliver4Vood

Added subscriber: @Arash

Added subscribers: @yaboijenkins, @Harley

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.

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.

@yaboijenkins this sounds more like bug #62651. I am not sure if this applies to all merged reports here though.

Added subscriber: @kelsabean

Removed subscriber: @Oliver4Vood

Added subscribers: @luxuryilusions, @Raimund58

Added subscriber: @bd986

Just wanted to add my experience to this:
Blender version: 2.91
Windows 10 Pro 20H2
Dell Precision 5520 Laptop
GPU 1: Intel HD 630 (Driver 27.20.100.9168, 2021-01-08)
GPU 2: NVIDIA Quadro M1200 (Driver 27.21.14.6140, 2021-01-22)

"OpenGL 3.3 or higher" error message displayed when opening Blender.

Within Device Manager, if I disable the Intel 630 display adapter, Blender opens without any problem. If I reenable the Intel 630 and disable the NVIDIA M1200, Blender opens without any problem.

With both display adapters enabled, the workaround mentioned above using Graphics settings to force Blender to use the Intel 630 also works (it does not work using the NVIDIA M1200).

Just wanted to add my experience to this: Blender version: 2.91 Windows 10 Pro 20H2 Dell Precision 5520 Laptop GPU 1: Intel HD 630 (Driver 27.20.100.9168, 2021-01-08) GPU 2: NVIDIA Quadro M1200 (Driver 27.21.14.6140, 2021-01-22) "OpenGL 3.3 or higher" error message displayed when opening Blender. Within Device Manager, if I disable the Intel 630 display adapter, Blender opens without any problem. If I reenable the Intel 630 and disable the NVIDIA M1200, Blender opens without any problem. With both display adapters enabled, the workaround mentioned above using Graphics settings to force Blender to use the Intel 630 also works (it does not work using the NVIDIA M1200).

Added subscriber: @Lordkranius

Added subscribers: @jrm6, @filedescriptor

Added subscriber: @LahkLeKey

Added subscribers: @anonymous, @EitanSomething

Added subscriber: @brianhuggins98

Added subscriber: @fixthewc

In #72098#1052222, @yaboijenkins wrote:
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.

WELL. THIS SAVED MY LIFE FOR 2 DAYS I WAS TRYING TO FIX THE ISSUE .. THNX A LOT!!!

> In #72098#1052222, @yaboijenkins wrote: > 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. WELL. THIS SAVED MY LIFE FOR 2 DAYS I WAS TRYING TO FIX THE ISSUE .. THNX A LOT!!!

Added subscriber: @christian-clavet

Hi, Just checked the informations and while it's better to use a dedicated video card instead of the integrated one, this should also work, but the problem is that the video memory assignment is too low on the integrated video.

You could open your BIOS settings and allocate much more memory to the intel integrated and it should start. Still I would recommend to connect all displays to the video card and disable the integrated video.

Hi, Just checked the informations and while it's better to use a dedicated video card instead of the integrated one, this should also work, but the problem is that **the video memory assignment is too low** on the integrated video. You could open your BIOS settings and allocate much more memory to the intel integrated and it should start. Still I would recommend to **connect all displays to the video card** and disable the integrated video.

The amount of reports decreased from 10s per year to a single one. We are not able to reproduce on the hardware that we have access to. This included Windows 10 + HD620
It could be that it is fixed by unrelated changes, or by third parties, but we cannot confirm this.

Note that exception access violation can also be triggered by bugs inside the video driver.

The issue reported can't be reproduced so far, and has been moved to the BF Blender: Unconfirmed project.
If 2 other people aren't able to redo the bug after 2 weeks, it will be closed.

We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them.
If there is anything you can provide to help others to reproduce the problem, be sure to include it.

The amount of reports decreased from 10s per year to a single one. We are not able to reproduce on the hardware that we have access to. This included Windows 10 + HD620 It could be that it is fixed by unrelated changes, or by third parties, but we cannot confirm this. Note that exception access violation can also be triggered by bugs inside the video driver. The issue reported can't be reproduced so far, and has been moved to the *BF Blender: Unconfirmed* project. If 2 other people aren't able to redo the bug after 2 weeks, it will be closed. We appreciate the effort that goes into making bug reports, but to be able to fix bugs we have to be able to redo them. If there is anything you can provide to help others to reproduce the problem, be sure to include it.

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash on startup with 2.82 and Intel HD + Windows #72098