Crash upon Startup #51644

New Issue

Alex Strand · 2017-05-28T08:43:51+02:00

Alex Strand commented

2017-05-28 08:43:51 +02:00

System Information
Windows 7, Nvidia 840m

Blender Version
Broken: 2.8 Build from 5-(26-28)-17 (Could not load splash screen)
Worked: Last version tested 2.78a e8299c8 (I doubt it's an issue found in any official releases though)

Short description of error
Opens command window (standard)
Displays a message that processor speed is not as expected by AL (unrelated)
next line:
Win32 Error# (3221692565) :

Not much I could find about this issue elsewhere but I did find a post on the OpenGL forums with the exact error code (seems like it might be a good place to look to for a start)

I've attempted running blender 2.8 versions built with 32 bit, 64 bit, and vc2015. but to no avail.

Exact steps for others to reproduce the error
Download the bleeding edge build of blender 2.8 project
Extract zip into Downloads folder
Open blender.exe

1 Second later CRASH-

I'm sorry I could not provide any further information on replicating this issue but I cannot get further into blender to see any more details. I feel it might just be user error, maybe I've extracted it in the wrong place (although blender is very portable) but I'm at a loss here.

Thank you.

**System Information** Windows 7, Nvidia 840m **Blender Version** Broken: 2.8 Build from 5-(26-28)-17 (Could not load splash screen) Worked: Last version tested 2.78a e8299c8 (I doubt it's an issue found in any official releases though) **Short description of error** Opens command window (standard) Displays a message that processor speed is not as expected by AL (unrelated) next line: Win32 Error# (3221692565) : <no system message> Not much I could find about this issue elsewhere but I did find a post on the OpenGL forums with the exact error code (seems like it might be a good place to look to for a start) I've attempted running blender 2.8 versions built with 32 bit, 64 bit, and vc2015. but to no avail. **Exact steps for others to reproduce the error** Download the bleeding edge build of blender 2.8 project Extract zip into Downloads folder Open blender.exe - 1 Second later CRASH- I'm sorry I could not provide any further information on replicating this issue but I cannot get further into blender to see any more details. I feel it might just be user error, maybe I've extracted it in the wrong place (although blender is very portable) but I'm at a loss here. Thank you.

Alex Strand commented

2017-05-28 08:43:51 +02:00

Changed status to: 'Open'

Alex Strand commented

2017-05-28 08:43:51 +02:00

Added subscriber: @AlexStrand

blender-admin commented

2017-05-28 08:43:51 +02:00

#52377 was marked as duplicate of this issue

Joel Godin commented

2017-05-28 12:32:11 +02:00

Added subscriber: @FloridaJo

Joel Godin commented

2017-05-28 12:32:11 +02:00

Upon crash Blender writes a file, can you upload it.
Instructions are here: https://docs.blender.org/manual/ja/dev/troubleshooting/crash.html

Upon crash Blender writes a file, can you upload it. Instructions are here: https://docs.blender.org/manual/ja/dev/troubleshooting/crash.html

Alex Strand commented

2017-05-28 19:02:23 +02:00

I looked in the C:\tmp directory but could not find any text file with the crash information. Blender doesn't just "stop responding" it creates a window with a gray screen and then "closes" silently.

(update) I've got blender to stop responding rather than closing itself by clicking on the window border. while it wasn't able to write a file I was able to collect this from the not responding window.

Problem Event Name:	AppHangB1
Application Name:	blender.exe
Application Version:	2.8.0.0
Application Timestamp:	592a249f
Hang Signature:	cb04
Hang Type:	0
OS Version:	6.1.7601.2.1.0.768.3
Locale ID:	1033
Additional Hang Signature 1:	cb04b3809e798fbc1fac417362058dbe
Additional Hang Signature 2:	1ccf
Additional Hang Signature 3:	1ccf51897c8c20d1b0c9edb8084e6637
Additional Hang Signature 4:	cb04
Additional Hang Signature 5:	cb04b3809e798fbc1fac417362058dbe
Additional Hang Signature 6:	1ccf
Additional Hang Signature 7:	1ccf51897c8c20d1b0c9edb8084e6637

I know this might not help as much considering blender focuses on multi-platform issues but I just couldn't get the crash file. perhaps it's crashing without ever getting a chance to write one.
Or maybe I just followed the troubleshooting instructions wrong but I couldn't find anything in my temp directory aside from a few renders from other blender versions.

I looked in the C:\tmp directory but could not find any text file with the crash information. Blender doesn't just "stop responding" it creates a window with a gray screen and then "closes" silently. (update) I've got blender to stop responding rather than closing itself by clicking on the window border. while it wasn't able to write a file I was able to collect this from the not responding window. ``` Problem Event Name: AppHangB1 Application Name: blender.exe Application Version: 2.8.0.0 Application Timestamp: 592a249f Hang Signature: cb04 Hang Type: 0 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Hang Signature 1: cb04b3809e798fbc1fac417362058dbe Additional Hang Signature 2: 1ccf Additional Hang Signature 3: 1ccf51897c8c20d1b0c9edb8084e6637 Additional Hang Signature 4: cb04 Additional Hang Signature 5: cb04b3809e798fbc1fac417362058dbe Additional Hang Signature 6: 1ccf Additional Hang Signature 7: 1ccf51897c8c20d1b0c9edb8084e6637 ``` I know this might not help as much considering blender focuses on multi-platform issues but I just couldn't get the crash file. perhaps it's crashing without ever getting a chance to write one. Or maybe I just followed the troubleshooting instructions wrong but I couldn't find anything in my temp directory aside from a few renders from other blender versions.

Bastien Montagne commented

2017-05-29 09:34:47 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2017-05-29 09:34:47 +02:00

Please check that you have latest official NVidia drivers installed, and give us their exact version.

Also please note that we are very picky with bug reports on 2.8 series currently, branch is in rather WIP state, and due to lack of man power we can only handle very precise and easily reproducible reports…

Please check that you have latest **official NVidia** drivers installed, and give us their exact version. Also please note that we are very picky with bug reports on 2.8 series currently, branch is in rather WIP state, and due to lack of man power we can only handle very precise and easily reproducible reports…

Stefano Orpelli commented

2017-05-30 11:52:19 +02:00

Added subscriber: @stefanoaq

Stefano Orpelli commented

2017-05-30 11:52:19 +02:00

I have the same problem. The console log says:

E:\Software\blender-2.80>blender --factory-startup --verbose 3 -d

Switching to fully guarded memory allocator.
Blender 2.80 (sub 0)
Build: Tue 05/30/2017 06:18 AM Windows Release
argv- [x] = blender
argv- [x] = --factory-startup
argv- [x] = --verbose
argv- [x] = 3
argv- [x] = -d
read file

Version 272 sub 2 date unknown hash unknown

Win32 Error# (3221692565):
Win32 Error# (3221692565):
Win32 Error# (3221684237):
Win32 Error# (3221684237):
Win32 Error# (3221684237):
Win32 Error# (3221684237):
found bundled python: E:\Software\blender-2.80\2.80\python
Error: EXCEPTION_ACCESS_VIOLATION

But.... if I add

debug-gpu
to the CLI, Blender starts and works (slowly because of the console logs)

I have Windows 8.1 64bit with Intel HD Graphics + NVIDIA Geforce 310M (NVIDIA Optimus)

Hope it helps.

I have the same problem. The console log says: E:\Software\blender-2.80>blender --factory-startup --verbose 3 -d Switching to fully guarded memory allocator. Blender 2.80 (sub 0) Build: Tue 05/30/2017 06:18 AM Windows Release argv- [x] = blender argv- [x] = --factory-startup argv- [x] = --verbose argv- [x] = 3 argv- [x] = -d read file ``` Version 272 sub 2 date unknown hash unknown ``` Win32 Error# (3221692565): <no system message> Win32 Error# (3221692565): <no system message> Win32 Error# (3221684237): <no system message> Win32 Error# (3221684237): <no system message> Win32 Error# (3221684237): <no system message> Win32 Error# (3221684237): <no system message> found bundled python: E:\Software\blender-2.80\2.80\python Error: EXCEPTION_ACCESS_VIOLATION But.... if I add - debug-gpu to the CLI, Blender starts and works (slowly because of the console logs) I have Windows 8.1 64bit with Intel HD Graphics + NVIDIA Geforce 310M (NVIDIA Optimus) Hope it helps.

Mike Erwin commented

2017-05-30 23:35:18 +02:00

Added subscriber: @MikeErwin

Mike Erwin commented

2017-05-30 23:35:18 +02:00

I'll try to reproduce this issue on a debug build which should tell us more information. I only have a few NVIDIA cards though, none of the ones reported here...

Geforce 310M supports OpenGL 3.3 and 840M supports GL 4.5 so both of these shouldwork.

I'll try to reproduce this issue on a debug build which should tell us more information. I only have a few NVIDIA cards though, none of the ones reported here... Geforce 310M supports OpenGL 3.3 and 840M supports GL 4.5 so both of these **should**work.

Stefano Orpelli commented

2017-05-31 10:40:12 +02:00

On my Geforce 310M, Blender 2.78 always worked fine.
If I start 2.80 with command line: blender.exe -d --debug-gpu it works too and I can use Eevee and so on. So the card is ok.
The question is why the --debug-gpu thing make the deal?

On my Geforce 310M, Blender 2.78 always worked fine. If I start 2.80 with command line: blender.exe -d --debug-gpu it works too and I can use Eevee and so on. So the card is ok. The question is why the --debug-gpu thing make the deal?

santiago commented

2017-06-02 01:39:55 +02:00

Added subscriber: @yagasan

santiago commented

2017-06-02 01:39:55 +02:00

https://www.gamedev.net/topic/658138-creating-an-opengl-context-on-windows-with-glew/
https://www.opengl.org/discussion_boards/archive/index.php/t-175619.html

maybe it can help

In #51644#437765, @MikeErwin wrote:
I'll try to reproduce this issue on a debug build which should tell us more information. I only have a few NVIDIA cards though, none of the ones reported here...

Geforce 310M supports OpenGL 3.3 and 840M supports GL 4.5 so both of these shouldwork.

https://www.gamedev.net/topic/658138-creating-an-opengl-context-on-windows-with-glew/ https://www.opengl.org/discussion_boards/archive/index.php/t-175619.html maybe it can help > In #51644#437765, @MikeErwin wrote: > I'll try to reproduce this issue on a debug build which should tell us more information. I only have a few NVIDIA cards though, none of the ones reported here... > > Geforce 310M supports OpenGL 3.3 and 840M supports GL 4.5 so both of these **should**work.

Joshua Leung commented

2017-06-18 14:32:01 +02:00

Added subscriber: @JoshuaLeung

Joshua Leung commented

2017-06-18 14:32:01 +02:00

I'm running into this bug as well with both the Grease Pencil branch (own build) and Buildbot (blender-2.80-f860369-win64.zip).

Specs:
Windows 8.1 64-bit, Nvidia GeForce GT 740M (with optimus stuff), Driver Version 331.82

System Info OpenGL info:
https://developer.blender.org/P501

Output of running buildbot build with --debug-gpu:
b28-debug_gpu_errors.txt / https://developer.blender.org/P502

I'm running into this bug as well with both the Grease Pencil branch (own build) and Buildbot (`blender-2.80-f860369-win64.zip`). Specs: Windows 8.1 64-bit, Nvidia GeForce GT 740M (with optimus stuff), Driver Version 331.82 System Info OpenGL info: https://developer.blender.org/P501 Output of running buildbot build with --debug-gpu: [b28-debug_gpu_errors.txt](https://archive.blender.org/developer/F634603/b28-debug_gpu_errors.txt) / https://developer.blender.org/P502

Mike Erwin commented

2017-06-18 15:26:54 +02:00

Thanks @JoshuaLeung, that debug dump has some useful info.

Major issue:
Failed shader link. The GLSL should be easy to fix.

Minor issue:
"Texture state usage warning: Waste of memory: Texture 0 has mipmaps, while its min filter is inconsistent with mipmaps."

Thanks @JoshuaLeung, that debug dump has some useful info. Major issue: Failed shader link. The GLSL should be easy to fix. Minor issue: "Texture state usage warning: Waste of memory: Texture 0 has mipmaps, while its min filter is inconsistent with mipmaps."

david mcsween commented

2017-07-05 10:31:44 +02:00

Added subscriber: @davidmcsween

david mcsween commented

2017-07-05 10:31:44 +02:00

I get a crash on start up from build bot:

blender-2.80.0-git.b090520-windows64
running on
OS Windows 7 SP1 64bit with OpenGL 4.0
Graphics Intel HD4600

Starting from command line returns:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\MCSWEEND2C> cd C:\Users\MCSWEEND2C\Documents\blender-2.80.0-git.b090520
-windows64

C:\Users\*******\Documents\blender-2.80.0-git.b090520-windows64>Blender.exe
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.
Win32 Error# (0): The operation completed successfully.

C:\Users\*******\Documents\blender-2.80.0-git.b090520-windows64>Blender.exe
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
Win32 Error# (3221692565): <no system message>
Win32 Error# (3221692565): <no system message>
Win32 Error# (3221692565): <no system message>
found bundled python: C:\Users\*******\Documents\blender-2.80.0-git.b090520-w
indows64\2.80\python
Error: EXCEPTION_ACCESS_VIOLATION

C:\Users\*******\Documents\blender-2.80.0-git.b090520-windows64>Blender.exe -
-debug-gpu
AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead
Win32 Error# (3221692565): <no system message>
Win32 Error# (3221692565): <no system message>
Win32 Error# (3221692565): <no system message>
Failed to hook OpenGL debug callback.
found bundled python: C:\Users\*******\Documents\blender-2.80.0-git.b090520-w
indows64\2.80\python
Error: EXCEPTION_ACCESS_VIOLATION

64 bit Blender builds of 2.79 from same period work fine.

I get a crash on start up from build bot: blender-2.80.0-git.b090520-windows64 running on OS Windows 7 SP1 64bit with OpenGL 4.0 Graphics Intel HD4600 Starting from command line returns: ``` Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\MCSWEEND2C> cd C:\Users\MCSWEEND2C\Documents\blender-2.80.0-git.b090520 -windows64 C:\Users\*******\Documents\blender-2.80.0-git.b090520-windows64>Blender.exe AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead Win32 Error# (0): The operation completed successfully. Win32 Error# (0): The operation completed successfully. Win32 Error# (0): The operation completed successfully. Win32 Error# (0): The operation completed successfully. Win32 Error# (0): The operation completed successfully. Win32 Error# (0): The operation completed successfully. Win32 Error# (0): The operation completed successfully. C:\Users\*******\Documents\blender-2.80.0-git.b090520-windows64>Blender.exe AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead Win32 Error# (3221692565): <no system message> Win32 Error# (3221692565): <no system message> Win32 Error# (3221692565): <no system message> found bundled python: C:\Users\*******\Documents\blender-2.80.0-git.b090520-w indows64\2.80\python Error: EXCEPTION_ACCESS_VIOLATION C:\Users\*******\Documents\blender-2.80.0-git.b090520-windows64>Blender.exe - -debug-gpu AL lib: (EE) UpdateDeviceParams: Failed to set 44100hz, got 48000hz instead Win32 Error# (3221692565): <no system message> Win32 Error# (3221692565): <no system message> Win32 Error# (3221692565): <no system message> Failed to hook OpenGL debug callback. found bundled python: C:\Users\*******\Documents\blender-2.80.0-git.b090520-w indows64\2.80\python Error: EXCEPTION_ACCESS_VIOLATION ``` 64 bit Blender builds of 2.79 from same period work fine.

Joshua Leung commented

2017-07-07 01:27:27 +02:00

Good news! I just tested the f67c331 buildbot, and it's now possible to run 2.8 and play around with it if I enable the --debug-gpu flag first. However, just running it still segfaults.

Definitely a step in the right direction... now, to figure out what's causing the crash :)

Good news! I just tested the f67c331 buildbot, and it's now possible to run 2.8 and play around with it if I enable the --debug-gpu flag first. However, just running it still segfaults. Definitely a step in the right direction... now, to figure out what's causing the crash :)

Dalai Felinto commented

2017-07-07 16:28:15 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2017-07-07 16:28:15 +02:00

@JoshuaLeung I guess b43cdc91ce was the cause for your initial issues then. That said, it's really strange that it works with --debug-gpu but not without.

@JoshuaLeung I guess b43cdc91ce was the cause for your initial issues then. That said, it's really strange that it works with --debug-gpu but not without.

Gabriel Mari Tararam commented

2017-07-20 16:54:53 +02:00

Added subscriber: @gabrielmtararam

Gabriel Mari Tararam commented

2017-07-20 16:54:53 +02:00

I got the same issue here, when i try to open the .exe file it shows Win32 Error# (3221692565):
on terminal it shows Error: EXCEPTION_ACCESS_VIOLATION blender

maybe it's something about windows 7, cause all crashes here came from a windows 7 pc... i don't know...
anyway, here are some information that may help DxDiag.txt

sorry for my terrible english....

I got the same issue here, when i try to open the .exe file it shows Win32 Error# (3221692565): <no system message> on terminal it shows Error: EXCEPTION_ACCESS_VIOLATION blender maybe it's something about windows 7, cause all crashes here came from a windows 7 pc... i don't know... anyway, here are some information that may help [DxDiag.txt](https://archive.blender.org/developer/F673198/DxDiag.txt) ![Captura de tela 2017-07-20 11.47.45.png](https://archive.blender.org/developer/F673199/Captura_de_tela_2017-07-20_11.47.45.png) ![Captura de tela 2017-07-20 11.51.34.png](https://archive.blender.org/developer/F673201/Captura_de_tela_2017-07-20_11.51.34.png) ![Captura de tela 2017-07-20 11.51.34.png](https://archive.blender.org/developer/F673202/Captura_de_tela_2017-07-20_11.51.34.png) sorry for my terrible english....

oby commented

2017-08-08 09:52:02 +02:00

Added subscriber: @xobyxmj

Brecht Van Lommel commented

2017-08-13 11:45:53 +02:00

Added subscriber: @TheMakerJonny

Stefano Orpelli commented

2017-08-14 17:11:45 +02:00

I got this log, which I didn't have before. Hope it could help:

GL API other: Program/shader state info: Assembly program 0 failed to compile at
 position 2432.  The associated error string is:  line 75, column 27:  error: in
valid operand variable

GL API other: Program/shader state info: GLSL program 148 failed to link
GPUShader: linking error:
Vertex info
-----------
0(22) : warning C7050: "finalColor.w" might be used before being initialized
Internal error: assembly compile error for vertex shader at offset 2432:
-- error message --
line 75, column 27:  error: invalid operand variable
-- internal assembly text --
!!NVvp4.1
OPTION NV_parameter_buffer_object2;
- cgc version 3.1.0001, build date Aug 29 2013
- command line args:
- vendor NVIDIA Corporation
- version 3.1.0.1
- profile gp4_1vp
- program main
- semantic ModelViewProjectionMatrix
- semantic ViewProjectionMatrix
- semantic ModelViewMatrix
- semantic ProjectionMatrix
- semantic screen_space
- semantic draw_size
- semantic color
- semantic ramp
- var float4 gl_Position : $vout.POSITION : HPOS : -1 : 1
- var float4x4 ModelViewProjectionMatrix :  : c[0], 4 : -1 : 1
- var float4x4 ViewProjectionMatrix :  : , 4 : -1 : 0
- var float4x4 ModelViewMatrix :  : c[4], 4 : -1 : 1
- var float4x4 ProjectionMatrix :  : c[8], 4 : -1 : 1
- var int screen_space :  : c[12] : -1 : 1
- var float draw_size :  : c[13] : -1 : 1
- var float3 color :  :  : -1 : 0
- var sampler1D ramp :  :  : -1 : 0
- var float3 pos : $vin.ATTR0 : ATTR0 : -1 : 1
- var float4 rot : $vin.ATTR1 : ATTR1 : -1 : 1
- var float val :  :  : -1 : 0
- var float3 inst_pos : $vin.ATTR2 : ATTR2 : -1 : 1
- var int axis : $vin.ATTR3 : ATTR3 : -1 : 1
#var float4 finalColor : $vout.ATTR0_FLAT : ATTR0 : -1 : 1
PARAM c[14] = { program.local[0..13] };
ATTRIB vertex_attrib[] = { vertex.attrib[0..3] };
OUTPUT result_attrib[] = { result.attrib[0..0] };
TEMP R0, R1, R2;
TEMP RC, HC;
SEQ.S R0.x, c[12], {1, 0, 0, 0};
MOV.U.CC RC.x, -R0;
IF    NE.x;
MUL.F R0, vertex.attrib[0].y, c[5];
MAD.F R0, vertex.attrib[0].x, c[4], R0;
MAD.F R0, vertex.attrib[0].z, c[6], R0;
ADD.F R1, R0, c[7];
MOV.F R0.w, {0, 0, 0, 0}.x;
MUL.F R0.xyz, vertex.attrib[2], c[13].x;
ADD.F R0, R1, R0;
MUL.F R1, R0.y, c[9];
MAD.F R1, R0.x, c[8], R1;
MAD.F R1, R0.z, c[10], R1;
MAD.F result.position, R0.w, c[11], R1;
ELSE;
SGT.S R0.y, vertex.attrib[3].x, {-1, 0, 0, 0}.x;
MOV.U.CC RC.x, -R0.y;
MOV.F R0.x, c[13];
IF    NE.x;
MUL.F R0.x, c[13], {2, 0, 0, 0};
ENDIF;
MUL.F R0.xyz, vertex.attrib[2], R0.x;
MUL.F R1.xyz, vertex.attrib[1].wyzw, R0.yzxw;
MAD.F R1.xyz, vertex.attrib[1].zwyw, R0.zxyw, -R1;
MAD.F R1.xyz, vertex.attrib[1].x, R0, R1;
MUL.F R2.xyz, vertex.attrib[1].wyzw, R1.yzxw;
MAD.F R1.xyz, vertex.attrib[1].zwyw, R1.zxyw, -R2;
MAD.F R0.xyz, R1, {2, 0, 0, 0}.x, R0;
ADD.F R0.xyz, vertex.attrib[0], R0;
MUL.F R1, R0.y, c[1];
MAD.F R1, R0.x, c[0], R1;
MAD.F R0, R0.z, c[2], R1;
ADD.F result.position, R0, c[3];
ENDIF;
SEQ.S R1.xyz, vertex.attrib[3].x, {0, 1, 2, 0};
MOV.U.CC RC.x, -R1;
MOV.F result.attrib[0].xyz, {0, 0, 0, 0}.x;
MOV.U R0.xy, -R1.yzzw;
MOV.F result.attrib[0].w, result.attrib[0];
IF    NE.x;
MOV.F R0.xyz, {1, 0, 0, 0}.xyyw;
ELSE;
MOV.U.CC RC.x, R0;
IF    NE.x;
MOV.F R0.xyz, {0, 1, 0, 0}.xyxw;
ELSE;
MOV.U.CC RC.x, R0.y;
IF    NE.x;
MOV.F R0.xyz, {0, 1, 0, 0}.xxyw;
ELSE;
MOV.F R0.xyz, {0, 0, 0, 0}.x;
ENDIF;
ENDIF;
ENDIF;
MOV.F result.attrib[0].xyz, R0;
MOV.F result.attrib[0].w, {1, 0, 0, 0}.x;
END
# 56 instructions, 3 R-regs

GPUShader: linking error:
Vertex info
-----------
0(22) : warning C7050: "finalColor.w" might be used before being initialized
Internal error: assembly compile error for vertex shader at offset 2432:
-- error message --
line 75, column 27:  error: invalid operand variable
-- internal assembly text --
!!NVvp4.1
OPTION NV_parameter_buffer_object2;
- cgc version 3.1.0001, build date Aug 29 2013
- command line args:
- vendor NVIDIA Corporation
- version 3.1.0.1
- profile gp4_1vp
- program main
- semantic ModelViewProjectionMatrix
- semantic ViewProjectionMatrix
- semantic ModelViewMatrix
- semantic ProjectionMatrix
- semantic screen_space
- semantic draw_size
- semantic color
- semantic ramp
- var float4 gl_Position : $vout.POSITION : HPOS : -1 : 1
- var float4x4 ModelViewProjectionMatrix :  : c[0], 4 : -1 : 1
- var float4x4 ViewProjectionMatrix :  : , 4 : -1 : 0
- var float4x4 ModelViewMatrix :  : c[4], 4 : -1 : 1
- var float4x4 ProjectionMatrix :  : c[8], 4 : -1 : 1
- var int screen_space :  : c[12] : -1 : 1
- var float draw_size :  : c[13] : -1 : 1
- var float3 color :  :  : -1 : 0
- var sampler1D ramp :  :  : -1 : 0
- var float3 pos : $vin.ATTR0 : ATTR0 : -1 : 1
- var float4 rot : $vin.ATTR1 : ATTR1 : -1 : 1
- var float val :  :  : -1 : 0
- var float3 inst_pos : $vin.ATTR2 : ATTR2 : -1 : 1
- var int axis : $vin.ATTR3 : ATTR3 : -1 : 1
#var float4 finalColor : $vout.ATTR0_FLAT : ATTR0 : -1 : 1
PARAM c[14] = { program.local[0..13] };
ATTRIB vertex_attrib[] = { vertex.attrib[0..3] };
OUTPUT result_attrib[] = { result.attrib[0..0] };
TEMP R0, R1, R2;
TEMP RC, HC;
SEQ.S R0.x, c[12], {1, 0, 0, 0};
MOV.U.CC RC.x, -R0;
IF    NE.x;
MUL.F R0, vertex.attrib[0].y, c[5];
MAD.F R0, vertex.attrib[0].x, c[4], R0;
MAD.F R0, vertex.attrib[0].z, c[6], R0;
ADD.F R1, R0, c[7];
MOV.F R0.w, {0, 0, 0, 0}.x;
MUL.F R0.xyz, vertex.attrib[2], c[13].x;
ADD.F R0, R1, R0;
MUL.F R1, R0.y, c[9];
MAD.F R1, R0.x, c[8], R1;
MAD.F R1, R0.z, c[10], R1;
MAD.F result.position, R0.w, c[11], R1;
ELSE;
SGT.S R0.y, vertex.attrib[3].x, {-1, 0, 0, 0}.x;
MOV.U.CC RC.x, -R0.y;
MOV.F R0.x, c[13];
IF    NE.x;
MUL.F R0.x, c[13], {2, 0, 0, 0};
ENDIF;
MUL.F R0.xyz, vertex.attrib[2], R0.x;
MUL.F R1.xyz, vertex.attrib[1].wyzw, R0.yzxw;
MAD.F R1.xyz, vertex.attrib[1].zwyw, R0.zxyw, -R1;
MAD.F R1.xyz, vertex.attrib[1].x, R0, R1;
MUL.F R2.xyz, vertex.attrib[1].wyzw, R1.yzxw;
MAD.F R1.xyz, vertex.attrib[1].zwyw, R1.zxyw, -R2;
MAD.F R0.xyz, R1, {2, 0, 0, 0}.x, R0;
ADD.F R0.xyz, vertex.attrib[0], R0;
MUL.F R1, R0.y, c[1];
MAD.F R1, R0.x, c[0], R1;
MAD.F R0, R0.z, c[2], R1;
ADD.F result.position, R0, c[3];
ENDIF;
SEQ.S R1.xyz, vertex.attrib[3].x, {0, 1, 2, 0};
MOV.U.CC RC.x, -R1;
MOV.F result.attrib[0].xyz, {0, 0, 0, 0}.x;
MOV.U R0.xy, -R1.yzzw;
MOV.F result.attrib[0].w, result.attrib[0];
IF    NE.x;
MOV.F R0.xyz, {1, 0, 0, 0}.xyyw;
ELSE;
MOV.U.CC RC.x, R0;
IF    NE.x;
MOV.F R0.xyz, {0, 1, 0, 0}.xyxw;
ELSE;
MOV.U.CC RC.x, R0.y;
IF    NE.x;
MOV.F R0.xyz, {0, 1, 0, 0}.xxyw;
ELSE;
MOV.F R0.xyz, {0, 0, 0, 0}.x;
ENDIF;
ENDIF;
ENDIF;
MOV.F result.attrib[0].xyz, R0;
MOV.F result.attrib[0].w, {1, 0, 0, 0}.x;
END
# 56 instructions, 3 R-regs

GPUShader: compile error:
0(805) : error C1101: ambiguous overloaded function reference "min(mediump float
, float)"
    (0) : vec4 min(vec4, float)
    (0) : vec3 min(vec3, float)
    (0) : vec2 min(vec2, float)
    (0) : ps gp5 gp4 cp50 fp50 vp50 gp50 cpf fpf vpf gpf mediump float min(mediu
mp float, mediump float)
    (0) : float min(float, float)
0(815) : error C1101: ambiguous overloaded function reference "min(mediump float
, float)"
    (0) : vec4 min(vec4, float)
    (0) : vec3 min(vec3, float)
    (0) : vec2 min(vec2, float)
    (0) : ps gp5 gp4 cp50 fp50 vp50 gp50 cpf fpf vpf gpf mediump float min(mediu
mp float, mediump float)
    (0) : float min(float, float)

Error: EXCEPTION_ACCESS_VIOLATION

I got this log, which I didn't have before. Hope it could help: ----------------------------- ``` GL API other: Program/shader state info: Assembly program 0 failed to compile at position 2432. The associated error string is: line 75, column 27: error: in valid operand variable GL API other: Program/shader state info: GLSL program 148 failed to link GPUShader: linking error: Vertex info ----------- 0(22) : warning C7050: "finalColor.w" might be used before being initialized Internal error: assembly compile error for vertex shader at offset 2432: -- error message -- line 75, column 27: error: invalid operand variable -- internal assembly text -- !!NVvp4.1 OPTION NV_parameter_buffer_object2; - cgc version 3.1.0001, build date Aug 29 2013 - command line args: - vendor NVIDIA Corporation - version 3.1.0.1 - profile gp4_1vp - program main - semantic ModelViewProjectionMatrix - semantic ViewProjectionMatrix - semantic ModelViewMatrix - semantic ProjectionMatrix - semantic screen_space - semantic draw_size - semantic color - semantic ramp - var float4 gl_Position : $vout.POSITION : HPOS : -1 : 1 - var float4x4 ModelViewProjectionMatrix : : c[0], 4 : -1 : 1 - var float4x4 ViewProjectionMatrix : : , 4 : -1 : 0 - var float4x4 ModelViewMatrix : : c[4], 4 : -1 : 1 - var float4x4 ProjectionMatrix : : c[8], 4 : -1 : 1 - var int screen_space : : c[12] : -1 : 1 - var float draw_size : : c[13] : -1 : 1 - var float3 color : : : -1 : 0 - var sampler1D ramp : : : -1 : 0 - var float3 pos : $vin.ATTR0 : ATTR0 : -1 : 1 - var float4 rot : $vin.ATTR1 : ATTR1 : -1 : 1 - var float val : : : -1 : 0 - var float3 inst_pos : $vin.ATTR2 : ATTR2 : -1 : 1 - var int axis : $vin.ATTR3 : ATTR3 : -1 : 1 #var float4 finalColor : $vout.ATTR0_FLAT : ATTR0 : -1 : 1 PARAM c[14] = { program.local[0..13] }; ATTRIB vertex_attrib[] = { vertex.attrib[0..3] }; OUTPUT result_attrib[] = { result.attrib[0..0] }; TEMP R0, R1, R2; TEMP RC, HC; SEQ.S R0.x, c[12], {1, 0, 0, 0}; MOV.U.CC RC.x, -R0; IF NE.x; MUL.F R0, vertex.attrib[0].y, c[5]; MAD.F R0, vertex.attrib[0].x, c[4], R0; MAD.F R0, vertex.attrib[0].z, c[6], R0; ADD.F R1, R0, c[7]; MOV.F R0.w, {0, 0, 0, 0}.x; MUL.F R0.xyz, vertex.attrib[2], c[13].x; ADD.F R0, R1, R0; MUL.F R1, R0.y, c[9]; MAD.F R1, R0.x, c[8], R1; MAD.F R1, R0.z, c[10], R1; MAD.F result.position, R0.w, c[11], R1; ELSE; SGT.S R0.y, vertex.attrib[3].x, {-1, 0, 0, 0}.x; MOV.U.CC RC.x, -R0.y; MOV.F R0.x, c[13]; IF NE.x; MUL.F R0.x, c[13], {2, 0, 0, 0}; ENDIF; MUL.F R0.xyz, vertex.attrib[2], R0.x; MUL.F R1.xyz, vertex.attrib[1].wyzw, R0.yzxw; MAD.F R1.xyz, vertex.attrib[1].zwyw, R0.zxyw, -R1; MAD.F R1.xyz, vertex.attrib[1].x, R0, R1; MUL.F R2.xyz, vertex.attrib[1].wyzw, R1.yzxw; MAD.F R1.xyz, vertex.attrib[1].zwyw, R1.zxyw, -R2; MAD.F R0.xyz, R1, {2, 0, 0, 0}.x, R0; ADD.F R0.xyz, vertex.attrib[0], R0; MUL.F R1, R0.y, c[1]; MAD.F R1, R0.x, c[0], R1; MAD.F R0, R0.z, c[2], R1; ADD.F result.position, R0, c[3]; ENDIF; SEQ.S R1.xyz, vertex.attrib[3].x, {0, 1, 2, 0}; MOV.U.CC RC.x, -R1; MOV.F result.attrib[0].xyz, {0, 0, 0, 0}.x; MOV.U R0.xy, -R1.yzzw; MOV.F result.attrib[0].w, result.attrib[0]; IF NE.x; MOV.F R0.xyz, {1, 0, 0, 0}.xyyw; ELSE; MOV.U.CC RC.x, R0; IF NE.x; MOV.F R0.xyz, {0, 1, 0, 0}.xyxw; ELSE; MOV.U.CC RC.x, R0.y; IF NE.x; MOV.F R0.xyz, {0, 1, 0, 0}.xxyw; ELSE; MOV.F R0.xyz, {0, 0, 0, 0}.x; ENDIF; ENDIF; ENDIF; MOV.F result.attrib[0].xyz, R0; MOV.F result.attrib[0].w, {1, 0, 0, 0}.x; END # 56 instructions, 3 R-regs GPUShader: linking error: Vertex info ----------- 0(22) : warning C7050: "finalColor.w" might be used before being initialized Internal error: assembly compile error for vertex shader at offset 2432: -- error message -- line 75, column 27: error: invalid operand variable -- internal assembly text -- !!NVvp4.1 OPTION NV_parameter_buffer_object2; - cgc version 3.1.0001, build date Aug 29 2013 - command line args: - vendor NVIDIA Corporation - version 3.1.0.1 - profile gp4_1vp - program main - semantic ModelViewProjectionMatrix - semantic ViewProjectionMatrix - semantic ModelViewMatrix - semantic ProjectionMatrix - semantic screen_space - semantic draw_size - semantic color - semantic ramp - var float4 gl_Position : $vout.POSITION : HPOS : -1 : 1 - var float4x4 ModelViewProjectionMatrix : : c[0], 4 : -1 : 1 - var float4x4 ViewProjectionMatrix : : , 4 : -1 : 0 - var float4x4 ModelViewMatrix : : c[4], 4 : -1 : 1 - var float4x4 ProjectionMatrix : : c[8], 4 : -1 : 1 - var int screen_space : : c[12] : -1 : 1 - var float draw_size : : c[13] : -1 : 1 - var float3 color : : : -1 : 0 - var sampler1D ramp : : : -1 : 0 - var float3 pos : $vin.ATTR0 : ATTR0 : -1 : 1 - var float4 rot : $vin.ATTR1 : ATTR1 : -1 : 1 - var float val : : : -1 : 0 - var float3 inst_pos : $vin.ATTR2 : ATTR2 : -1 : 1 - var int axis : $vin.ATTR3 : ATTR3 : -1 : 1 #var float4 finalColor : $vout.ATTR0_FLAT : ATTR0 : -1 : 1 PARAM c[14] = { program.local[0..13] }; ATTRIB vertex_attrib[] = { vertex.attrib[0..3] }; OUTPUT result_attrib[] = { result.attrib[0..0] }; TEMP R0, R1, R2; TEMP RC, HC; SEQ.S R0.x, c[12], {1, 0, 0, 0}; MOV.U.CC RC.x, -R0; IF NE.x; MUL.F R0, vertex.attrib[0].y, c[5]; MAD.F R0, vertex.attrib[0].x, c[4], R0; MAD.F R0, vertex.attrib[0].z, c[6], R0; ADD.F R1, R0, c[7]; MOV.F R0.w, {0, 0, 0, 0}.x; MUL.F R0.xyz, vertex.attrib[2], c[13].x; ADD.F R0, R1, R0; MUL.F R1, R0.y, c[9]; MAD.F R1, R0.x, c[8], R1; MAD.F R1, R0.z, c[10], R1; MAD.F result.position, R0.w, c[11], R1; ELSE; SGT.S R0.y, vertex.attrib[3].x, {-1, 0, 0, 0}.x; MOV.U.CC RC.x, -R0.y; MOV.F R0.x, c[13]; IF NE.x; MUL.F R0.x, c[13], {2, 0, 0, 0}; ENDIF; MUL.F R0.xyz, vertex.attrib[2], R0.x; MUL.F R1.xyz, vertex.attrib[1].wyzw, R0.yzxw; MAD.F R1.xyz, vertex.attrib[1].zwyw, R0.zxyw, -R1; MAD.F R1.xyz, vertex.attrib[1].x, R0, R1; MUL.F R2.xyz, vertex.attrib[1].wyzw, R1.yzxw; MAD.F R1.xyz, vertex.attrib[1].zwyw, R1.zxyw, -R2; MAD.F R0.xyz, R1, {2, 0, 0, 0}.x, R0; ADD.F R0.xyz, vertex.attrib[0], R0; MUL.F R1, R0.y, c[1]; MAD.F R1, R0.x, c[0], R1; MAD.F R0, R0.z, c[2], R1; ADD.F result.position, R0, c[3]; ENDIF; SEQ.S R1.xyz, vertex.attrib[3].x, {0, 1, 2, 0}; MOV.U.CC RC.x, -R1; MOV.F result.attrib[0].xyz, {0, 0, 0, 0}.x; MOV.U R0.xy, -R1.yzzw; MOV.F result.attrib[0].w, result.attrib[0]; IF NE.x; MOV.F R0.xyz, {1, 0, 0, 0}.xyyw; ELSE; MOV.U.CC RC.x, R0; IF NE.x; MOV.F R0.xyz, {0, 1, 0, 0}.xyxw; ELSE; MOV.U.CC RC.x, R0.y; IF NE.x; MOV.F R0.xyz, {0, 1, 0, 0}.xxyw; ELSE; MOV.F R0.xyz, {0, 0, 0, 0}.x; ENDIF; ENDIF; ENDIF; MOV.F result.attrib[0].xyz, R0; MOV.F result.attrib[0].w, {1, 0, 0, 0}.x; END # 56 instructions, 3 R-regs GPUShader: compile error: 0(805) : error C1101: ambiguous overloaded function reference "min(mediump float , float)" (0) : vec4 min(vec4, float) (0) : vec3 min(vec3, float) (0) : vec2 min(vec2, float) (0) : ps gp5 gp4 cp50 fp50 vp50 gp50 cpf fpf vpf gpf mediump float min(mediu mp float, mediump float) (0) : float min(float, float) 0(815) : error C1101: ambiguous overloaded function reference "min(mediump float , float)" (0) : vec4 min(vec4, float) (0) : vec3 min(vec3, float) (0) : vec2 min(vec2, float) (0) : ps gp5 gp4 cp50 fp50 vp50 gp50 cpf fpf vpf gpf mediump float min(mediu mp float, mediump float) (0) : float min(float, float) Error: EXCEPTION_ACCESS_VIOLATION ```

Brecht Van Lommel commented

2017-08-15 18:56:36 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2017-08-15 18:56:36 +02:00

I couldn't repro these GLSL errors myself, but I committed a potential fix for these issues in b68b26c265. Tomorrow's daily build should have it.

I couldn't repro these GLSL errors myself, but I committed a potential fix for these issues in b68b26c265. Tomorrow's daily build should have it.

Dalai Felinto commented

2017-08-16 11:38:24 +02:00

Changed status from 'Open' to: 'Resolved'

Dalai Felinto closed this issue

2017-08-16 11:38:24 +02:00

Dalai Felinto self-assigned this 2017-08-16 11:38:24 +02:00

Dalai Felinto commented

2017-08-16 11:38:24 +02:00

Reported as fixed in the related #52404, closing now. Write back if the problem persists.

Stefano Orpelli commented

2017-08-16 12:55:23 +02:00

Thank you Brecht. The fix allowed me to start blender with the --debug-gpu parameter and play with Eevee.
Without the parameter, Blender won't start with usual: "Error: EXCEPTION_ACCESS_VIOLATION" output.

Thank you Brecht. The fix allowed me to start blender with the --debug-gpu parameter and play with Eevee. Without the parameter, Blender won't start with usual: "Error: EXCEPTION_ACCESS_VIOLATION" output.

Joshua Leung commented

2017-09-19 09:04:18 +02:00

I'm currently still having to run blender via --debug-gpu, which makes things really slow. So, I decided to do a little more digging today (after setting up a dedicated copy of the 2.8/gp branches to avoid having to worry about so many leftover build files when changing branches).

It turns out that for me, it's currently bugging out on the following check:

  GHOST_ContextWGL.cpp  ->  GHOST_ContextWGL::initializeDrawingContext()  ->  !WIN32_CHK(m_hGLRC != NULL)       (line 882, gp branch)

Adding a few more prints, to each of the cases leading up to this, I get the following startup sequence:

profile mask = 1
major version = 4
minor version = 5
m_hGLRC = wglCreateContextAttribsARB => 0000000000000000
C:\blenderdev\dev\blender\intern\ghost\intern\GHOST_ContextWGL.cpp(890):[m_hGLRC != NULL] -> Win32 Error# (3221692565): <no system message>
profile mask = 1
major version = 4
minor version = 4
m_hGLRC = wglCreateContextAttribsARB => 0000000000030000
profile mask = 1
major version = 4
minor version = 4
m_hGLRC = wglCreateContextAttribsARB => 0000000000050000
found bundled python: C:\blenderdev\dev\install\2.80\python
addon not found: 'cycles'
Error: EXCEPTION_ACCESS_VIOLATION

I'm currently still having to run blender via --debug-gpu, which makes things really slow. So, I decided to do a little more digging today (after setting up a dedicated copy of the 2.8/gp branches to avoid having to worry about so many leftover build files when changing branches). It turns out that for me, it's currently bugging out on the following check: ``` GHOST_ContextWGL.cpp -> GHOST_ContextWGL::initializeDrawingContext() -> !WIN32_CHK(m_hGLRC != NULL) (line 882, gp branch) ``` Adding a few more prints, to each of the cases leading up to this, I get the following startup sequence: ``` profile mask = 1 major version = 4 minor version = 5 m_hGLRC = wglCreateContextAttribsARB => 0000000000000000 C:\blenderdev\dev\blender\intern\ghost\intern\GHOST_ContextWGL.cpp(890):[m_hGLRC != NULL] -> Win32 Error# (3221692565): <no system message> profile mask = 1 major version = 4 minor version = 4 m_hGLRC = wglCreateContextAttribsARB => 0000000000030000 profile mask = 1 major version = 4 minor version = 4 m_hGLRC = wglCreateContextAttribsARB => 0000000000050000 found bundled python: C:\blenderdev\dev\install\2.80\python addon not found: 'cycles' Error: EXCEPTION_ACCESS_VIOLATION ```

Aristide Lai commented

2017-11-27 10:29:00 +01:00

Added subscriber: @AristideLai

Aristide Lai commented

2017-11-27 10:29:00 +01:00

Here the error message on my computer... it looks coming around the format extension...

Here the error message on my computer... it looks coming around the format extension... ![Blender28Error.jpg](https://archive.blender.org/developer/F1200448/Blender28Error.jpg)

Stefano Orpelli commented

2017-12-24 18:48:49 +01:00

Why is this bug "Closed/Resolved" ? The problem is still here. Blender won't start without the --debug-gpu.

ameen vengara commented

2018-07-06 08:13:26 +02:00

Added subscriber: @ameenvengara

ameen vengara commented

2018-07-06 08:13:26 +02:00

I too have the same problem.. Only runs with

-d --debug-gpu

E:\Software\blender\blender-2.80-7a07500-win64\blender-2.80.0-git.7a07500-window
s64>blender.exe
Read prefs: C:\Users\Edit\AppData\Roaming\Blender Foundation\Blender\2.80\config
\userpref.blend
AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead
Win32 Error# (3221692565): <no system message>
Win32 Error# (3221692565): <no system message>
found bundled python: E:\Software\blender\blender-2.80-7a07500-win64\blender-2.8
0.0-git.7a07500-windows64\2.80\python
Error   : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000065538649
Module  : C:\Windows\system32\nvoglv64.DLL

Using Windows 7
Intel Core i5-4440 CPU @ 3.10GHz
Geforce GTX 750

I too have the same problem.. Only runs with ``` -d --debug-gpu ``` ``` E:\Software\blender\blender-2.80-7a07500-win64\blender-2.80.0-git.7a07500-window s64>blender.exe Read prefs: C:\Users\Edit\AppData\Roaming\Blender Foundation\Blender\2.80\config \userpref.blend AL lib: (EE) UpdateDeviceParams: Failed to set 48000hz, got 44100hz instead Win32 Error# (3221692565): <no system message> Win32 Error# (3221692565): <no system message> found bundled python: E:\Software\blender\blender-2.80-7a07500-win64\blender-2.8 0.0-git.7a07500-windows64\2.80\python Error : EXCEPTION_ACCESS_VIOLATION Address : 0x0000000065538649 Module : C:\Windows\system32\nvoglv64.DLL ``` Using Windows 7 Intel Core i5-4440 CPU @ 3.10GHz Geforce GTX 750

Robin Tomar commented

2018-08-05 16:39:14 +02:00

Added subscriber: @RobinTomar

Robin Tomar commented

2018-08-05 16:39:14 +02:00

I too had this kind of error [EXCEPTION_ACCESS_VIOLATION in nvoglv].

What I did to solve this issue:
In Nvidia Control Panel > Manage 3D settings, Added blender in Program Settings tab and tweaked the settings
and found that disabling Threaded optimization made the blender to start normally.

This worked for me

Graphics Hardware: Nvidia 9400GT with driver version 342.01 [Nov 2016]

I too had this kind of error [EXCEPTION_ACCESS_VIOLATION in nvoglv]. What I did to solve this issue: In *Nvidia Control Panel* > *Manage 3D settings*, Added blender in *Program Settings* tab and tweaked the settings and found that disabling *Threaded optimization* made the blender to start normally. ![Blender_Crash.PNG](https://archive.blender.org/developer/F4128875/Blender_Crash.PNG) This worked for me Graphics Hardware: Nvidia 9400GT with driver version 342.01 [Nov 2016]

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Crash upon Startup #51644