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'

**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)

George Ellenburg commented

Added subscriber: @George-Ellenburg

blender-admin commented

#88611 was marked as duplicate of this issue

blender-admin commented

#85949 was marked as duplicate of this issue

blender-admin commented

#87089 was marked as duplicate of this issue

blender-admin commented

#85507 was marked as duplicate of this issue

blender-admin commented

#85386 was marked as duplicate of this issue

blender-admin commented

#83417 was marked as duplicate of this issue

blender-admin commented

#82778 was marked as duplicate of this issue

blender-admin commented

#82554 was marked as duplicate of this issue

blender-admin commented

#82320 was marked as duplicate of this issue

blender-admin commented

#81586 was marked as duplicate of this issue

blender-admin commented

#80808 was marked as duplicate of this issue

blender-admin commented

#80989 was marked as duplicate of this issue

blender-admin commented

#79513 was marked as duplicate of this issue

blender-admin commented

#78838 was marked as duplicate of this issue

blender-admin commented

#78799 was marked as duplicate of this issue

blender-admin commented

#78016 was marked as duplicate of this issue

blender-admin commented

#77921 was marked as duplicate of this issue

blender-admin commented

#77852 was marked as duplicate of this issue

blender-admin commented

#77360 was marked as duplicate of this issue

blender-admin commented

#76781 was marked as duplicate of this issue

blender-admin commented

#76499 was marked as duplicate of this issue

blender-admin commented

#76441 was marked as duplicate of this issue

blender-admin commented

#76288 was marked as duplicate of this issue

blender-admin commented

#76042 was marked as duplicate of this issue

blender-admin commented

#75248 was marked as duplicate of this issue

blender-admin commented

#75320 was marked as duplicate of this issue

blender-admin commented

#75230 was marked as duplicate of this issue

blender-admin commented

#75067 was marked as duplicate of this issue

Robert Guetzkow commented

Added subscriber: @rjg

Robert Guetzkow commented

Changed status from 'Open' to: 'Archived'

Robert Guetzkow closed this issue

Robert Guetzkow self-assigned this 2019-12-01 23:07:18 +01:00

Robert Guetzkow commented

2019-12-02 00:18:05 +01:00

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.

George Ellenburg commented

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.

Robert Guetzkow commented

2019-12-02 00:35:37 +01:00

Changed status from 'Archived' to: 'Open'

Robert Guetzkow reopened this issue

2019-12-02 00:35:37 +01:00

Robert Guetzkow commented

2019-12-02 00:35:37 +01:00

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.

Maciej Jutrzenka commented

2019-12-02 01:20:01 +01:00

Added subscriber: @MaciejJutrzenka

Maciej Jutrzenka commented

2019-12-02 01:20:01 +01:00

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

Maciej Jutrzenka commented

2019-12-02 01:23:20 +01:00

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

Maciej Jutrzenka changed title from ~~Blender 2.81 crash on start~~ to Blender 2.81 crash on start INTEL GPU

2019-12-02 01:24:38 +01:00

Maciej Jutrzenka changed title from ~~Blender 2.81 crash on start INTEL GPU~~ to [START_CRASH] Blender 2.81 Intel

2019-12-02 01:53:23 +01:00

Robert Guetzkow commented

2019-12-02 09:32:42 +01:00

Added subscriber: @robert-18

Robert Guetzkow commented

2019-12-02 09:32:42 +01:00

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

Robert Guetzkow removed their assignment 2019-12-02 09:33:58 +01:00

Robert Guetzkow commented

2019-12-02 09:34:49 +01:00

Removed subscriber: @robert-18

Robert Guetzkow commented

2019-12-02 09:51:16 +01:00

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

Robert Guetzkow commented

2019-12-02 09:59:35 +01:00

Added subscriber: @fclem

Robert Guetzkow commented

2019-12-02 09:59:35 +01:00

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

George Ellenburg commented

2019-12-02 11:09:35 +01:00

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)

George Ellenburg commented

2019-12-02 11:11:56 +01:00

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

George Ellenburg commented

2019-12-02 11:22:21 +01:00

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)

Germano Cavalcante commented

2019-12-02 14:38:51 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-12-02 14:38:51 +01:00

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.

Robert Guetzkow commented

2019-12-02 14:39:23 +01:00

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

George Ellenburg commented

2019-12-02 21:17:26 +01:00

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)

George Ellenburg commented

2019-12-02 21:20:13 +01:00

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!

2019-12-02 21:20:51 +01:00

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)

George Ellenburg commented

Oops. Pasted the wrong image. Here:

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

George Ellenburg commented

2019-12-02 22:01:34 +01:00

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.

Philipp Oeser commented

2019-12-03 11:41:19 +01:00

Added subscribers: @Jeroen-Bakker, @lichtwerk

Philipp Oeser commented

2019-12-03 11:41:19 +01:00

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

Clément Foucault commented

2019-12-03 13:22:46 +01:00

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

Jeroen Bakker commented

2019-12-03 13:55:31 +01:00

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

Clément Foucault commented

2019-12-03 14:07:11 +01:00

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.

Maciej Jutrzenka commented

2019-12-03 14:17:42 +01:00

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?

Bryan F commented

2019-12-03 17:07:51 +01:00

Added subscriber: @bry_art_by_bry

Bryan F commented

2019-12-03 17:07:51 +01:00

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.

Robert Guetzkow commented

2019-12-03 17:17:09 +01:00

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

George Ellenburg commented

2019-12-03 21:40:16 +01:00

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.

George Ellenburg commented

2019-12-03 21:50:22 +01:00

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:

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

Yep. It crashed.

Here are those logs:

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

And it works!

And here are those (new) logs again too.

2019-12-03 23:36:49 +01:00

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)

Jeroen Bakker self-assigned this 2019-12-03 23:36:49 +01:00

Jeroen Bakker commented

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.

Clément Foucault commented

2019-12-04 01:05:38 +01:00

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

Bryan F commented

2019-12-04 05:21:02 +01:00

Added subscriber: @robert-18

Bryan F commented

2019-12-04 05:21:02 +01:00

This comment was removed by @bry_art_by_bry

*This comment was removed by @bry_art_by_bry*

Bryan F commented

2019-12-04 05:23:13 +01:00

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"

Bryan F commented

2019-12-04 05:30:22 +01:00

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

Jeroen Bakker removed their assignment 2019-12-04 07:56:40 +01:00

Robert Guetzkow commented

2019-12-04 13:06:51 +01:00

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

George Ellenburg commented

2019-12-04 17:27:51 +01:00

@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_gpu_glitchworkaround.cmd: no crash

blender_debug_log.cmd: CRASH

blender_factory_startup.cmd: CRASH