Modeling (mode edit) and stack overflow into the driver NVIDIA #50126
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
13 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#50126
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I change title of old : "Modeling - Freeze - Crash Graphics Card - White screen"
System Information
Operating system : Windows 10 Famille - 64 bits - 16 Go RAM
graphics card : GTX 580 x2
Blender Version
Broken: 2.78
def365eWorked: 2.75a
c27589eShort description of error
During modeling, freeze, crash graphics card, white screen.
Require to kill the process.
Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
1 / Modeling on a cylinder
2 / Putting a Subsurf
3 / Add cuts
Bam! Freeze! White screen
Splash screen blender broken
Process back
White screen
Windows error report
Windows error report
Blender fichier
Vaisseau.blend1
Vaisseau.blend
Changed status to: 'Open'
Added subscriber: @Almisuifre
Added subscriber: @CrepeC
Added subscriber: @LazyDodo
Can't seem to repro, added some loopcuts to cylinder.000, seemed just peachy, could be a driver bug.
To check for that you can try dropping the opengl32.dll from here http://download.blender.org/ftp/sergey/softwaregl/win64/ into your blender folder and try again. (be sure to remove it when you're done testing, software opengl doesn't have the best performance)
I did this test last time. The result was a big freeze.
What I can not explain: why blender 2.75a works. Why 2.78 does not work. Same conditions of use for both versions.
Blender 2.75a:
Blender 2.78 all versions and bluidbot:
So it's not a driver bug. When this bug is when I add loop cut on an object in edit mode.
Added subscriber: @VukGardasevic
This is not a Blender Buildbot Project - removing.
Added subscriber: @JulianEisel
Removing all project tags but #bf_blender for until we now what actually causes the issue.
Please, let us handle the project tagging.
Ok
Added subscriber: @Blendify
Its highly likely that this bug is specific to your hardware/driver configuration.
These kinds of display issues are often caused by OpenGL driver bugs.
While its possible a software error in Blender,
its worth checking if this functions correctly...
blender-softwareglIf this is a driver bug, or we can't link to this to an error in Blender's code,
the report may be closed as a driver error,
so please help us determine whether this is a bug in Blender or not.
Thank you for answering
It would seem that this may come from there. But why would it work perfectly with previous versions?
I upgraded to the latest NVidia drivers.
Indeed, I have not tested on my laptop. But I do not think I'd do it until I'm sure it's OK level bug. Alas, when I see the todo bug list ...
Lost, I have no more Linux available to test.
I tested this option. Big fat lag ... impossible to run Blender. It's as if you do shoot the scene and you have time to drink your coffee and read a good Shakespire same time!
I maintain that Blender works in its previous versions. Since version 2.77, big concerns regardless of the version, not stable, stable or ongoing!
Please let me know what Blender is doing while I'm using it. This may be useful to see if it's not a "null point"
Sometimes it will fail to work on older hardware because Blender updates its code to new standards.
The 'opengl32.dll' is going to be slower because it runs the entire UI on the CPU and thus illuminating possible GPU issues.
It is critical that you wait through the lags and test. If you find that it still happens with the dll-file then we we know that it is a bug with Blender and will be willing to look more into this specific issue.
However, like what other people have said after testing leads me to believe that this is a hardware issue. If using the dll-file gives correct results then there is nothing we can do because the issue comes from your hardware.
Also you say that you are running windows 10 family but that does not exist https://en.wikipedia.org/wiki/Windows_10_editions So something seems wrong on your end.
Would this imply that the embedded version of OPEN-GL of my graphics cards is exceeded?
Is it wise to block the material yet not so old? Especially since others use versions even older than my cards?
To get back on the dll, this is far from being so obvious. What do we mean by "It's critical that you wait through the lags and test." ?
In addition, here is a view of the driver version used and up to date currently.
Changed status from 'Open' to: 'Archived'
No reply in more than a week... closing
Changed status from 'Archived' to: 'Open'
Eeeh, the author did reply, AFAICS this task is pending action from us.
Added subscribers: @MikeErwin, @mont29
This indeed smells like GPU/driver issue… Even though GTX 580 is a bit old, it should still be supported for sure, afaik.
You mention 2 GPUs though, maybe you could try running with only one and see whether it fixes the problem? Also, sometimes newer drivers with older GPUs can actually introduce new bugs instead of removing them… That’s why software OGL, as slow as it is, is a good test - if it does not crash with it, then there is 99% of probability that the issue is with your current GPU driver.
Maybe someone from OGL team having similar hardware can test? @MikeErwin?
In the mean while, you may check those additional points:
--factory-startupcommandline option) (this will ensure whether this is a userpref or addon issue or not).-doption and attach as text file here any error printed out in the console (do not paste it directly in comment).PS: as for 2.75 running OK, well, Blender also evolves and tends to use more modern features in newer versions, like more shaders etc.
Thank you for bringing me these few answers.
I do not use any add-ons. I even prefer to use the basic configuration.
However, I have 2 questions.
1 / For tests, is it imperative to use the DLL?
2 / On Windows, how to have the console?
Removed subscriber: @CrepeC
GTX 580 is a few years old but very capable GPU. It should be supported for 2.7x and even 2.8x
Try this with the latest Blender version:
Open command prompt (windows key, type "cmd").
Navigate to Blender's install location with the "cd" command. On my system it lives at
C:\Program Files\Blender Foundation\Blender>
type "blender --debug-gpu" to run it with extra OpenGL debugging.
For simplicity. I downloaded the latest version, unzipped as from the bluidbot.
I put the dll as requested and navigated with the command prompt.
Some returns now with attached files.Test-opengl_dll.blend1
Test-opengl_dll.blend
quit.blend
Test-opengl_dll2.blend
cmd-2.txt
cmd.txt
If it helps.
Added subscriber: @MichaelCalmbach
I am the author from the Ticket #50506, it works then I copy the opengl32.dll to the path from blender.exe.
But the blender is so slow that I can’t work with him, open the by pressing ctrl alt u need up to three second to open the menu.
This issue comes all from update to windows10 build 15014 from windows insider program in the fast ring.
I report that also to Microsoft other the insider program and the feedback hub
Michael
I do not have time to watch tonight. I'm trying to resume testing this weekend, probably Sunday.
Sorry to make you wait. Ok for the new test.
It's cool that there are ideas on W10 updates.
I just tried the ctrl + alt + u and nothing opened!
How did you do this operation?
Added subscriber: @GameKyuubi
I'm also getting a white screen except it's on startup. It doesn't seem to be a freeze or crash, as by clicking around in the white space I accidentally opened a link to blender.org. It seems GPU-related, as if I run with integrated graphics it works fine (if a little slow) but if I run with my 730m I get white screen. Drivers are latest.
Blender 2.78c fresh install
Windows 10 x64 insider preview
NVIDIA GeForce 730m
Good evening,
Finally a little time to do a bit of blender.
I attacked a mod, on which I place a smooth. I made a pre-rendered bam, Blender to stop working.
As usual, I have attached my report on the others.
Premier-objet.blend
Bam.txt
Bam-2.txt
I continued my investigations. I turn the SLi which can lead to lags. As a result, I always have the same error. This time, it happened during Ctrl + Z.
I would be very happy if you find out where this can come from.
History to unwind a little more. I loaded the benchs of Blender cycles. As I had first thought, it's during the modeling and more precisely when I manipulate the scene. Rotate / move object.
10 minutes of rendering without any particular problem. The ram held, the graphics cards also.
But what is that?
New error during modeling
Bam.txt
Consider:
I changed the sound quality. This seems to have resolved the message from the startup screen. But it still crashes!
A turn under dxdiag report errors on a dll. As explained at the beginning.
DxDiag.txt
I also looked at whether the Dll in question was in its proper place. Its good :
There, I can do nothing better.
There is hope that the concern is a little more isolated.
Hello,
Investigations continued.
I incriminate the audio through the DLL indicated above and in the report of errors. So I eliminated the sound in options such as:
I used the command line tool to start Blender. I discovered this:
I reinstalled the MV C ++ Redistributable (X64) and (X32) 2013 and 2013:
Let's add the file userperf.blend in relation to the following post (https:*developer.blender.org/T44127 , https:*developer.blender.org/T48027 and https://developer.blender.org/T30271):
userpref.blend
I am moving more and more towards a concern python + dll. I hope this will help the community to resolve this concern.
Good luck
These error messages are harmless:
Failed to set 48000 Hz
<!> event has invalid window
Not freed memory blocks
So they're not related to the problem you're seeing.
Okay :)
I finished my tests with the .blend that crashes, I put it at your disposal.
SF-Flight.blend
There is no step type that is planted. On the other hand, this often happens during moving 3d objects in the scene to see during the viewport manupilation.
Simple example.
Another example.
But other steps can lead to crashing.
Hello
New tests and new crashes.
This time I was in the temp folder to find what happens.
1896.blend
quit.blend
Once again. There is no order. Place a cylinder, make a copy of some faces, extrude, make a subsurf, place one or two cuts, put a subdivision and make a spin ...
Operations somes all basic.
But if it can help the team, give as much information as possible.
I did not see any error in the ms-dos window. Which means that the crash happened somewhere unprecedented.
By dint of search, I found tracks. A priori many people are full of W10. I think that one of the tracks is here.
Hello,
Despite the return to a correct operation over several days. "Blender to stop working."
The video driver is up to date.
From there, I think the problem is difficult to flush out.
Zut-1.txt
7512.blend
DieselPunk.blend
6988.blend
1/ place mesh plane
2/ edit mesh, add face, add vertex, extrude face...
3/ place modifier -> curve + array not applied
4/ move object in edit mod
5/ crash
I just got my hands on Blender's dump-crash.
blender.exe.484.dmp
blender.exe.5344.dmp
It is very simple, crashes occur during edit mode.
Would not the concern be that the ctrl + r would cause a bad name for the vertex?
When windows closed, a null point occurred.
Added subscriber: @xuekepei
windows 10 has a future is auto re-install GPU driver but not mentioned.
You can download a driver from nvidia's home page, then re-install GPU driver again manually.
This could solve a lot of situation when run blender on windows 10.
Lost, I am up to date manually level graphics card driver.
On the other hand, found very interesting system info!
Config.txt
Removed subscriber: @Blendify
Good evening,
Is it possible that Windows 10 imposes its graphics driver instead of that of NVIDIA?
If so, it would explain that the nvoglv64.DLL dll crash because it is used by the Windows 10 driver.
That is the conclusion I have drawn from it.
For now, I'm back on the driver version of windows said "generic". But I do not think it has solved the problem.
Do you confirm this possibility?
Not really, hardware companies (AMD, NV, Intel) make the OpenGL drivers on Windows.
Ok.
Can it come from the autosave?
I switched Blender to stand alone on a disk other than the system, I disabled the autosave. That seems to work. I look forward to seeing in the long run!
I still have the problem: blender has stopped working.
Certainly the autosave less, makes it happen a little later. I could work on it for several days.
On the other hand, I have a certainty. When it crashes, I'm in edit mode.
This is where we must look now.
Thanks to the team who will be able to resume the subject because it is important to know why the mode edit plant.
Other info, I have no error in the console at the time of crash.
analysis for the dump @Almisuifre posted , looks like a stack overflow in the nvidia driver...
Ok for this information and thank you for the describe.
Now you have to do what?
Do I have to report this information back to NVIDIA?
Or should I wait for a fix in a particular build?
I'm waiting to see Blender work again.
Modeling - Freeze - Crash Graphics Card - White screento Modeling (mode edit) and stack overflow into the driver NVIDIACould still be we're feeding the ogl driver bad data and it's wigging out because of that, most of the opengl got quite some rework in 2.8, try a 2.8 build and see if you can make it misbehave.
It's possible. Especially since the 2.75 works. After, the 2.76, 2.77 and 2.78 causes crashes!
If I understand. So I have to take in the buildbot? But what version could contain a fix?
In any case I am ready to help you with the resolution.
Any of the 2.8 builds for your platform would do
Ok, so go for this version:
I'll keep you informed of the results.
Thanks
Removed subscriber: @VukGardasevic
Added subscriber: @renderluz-2
I think I can confirm this bug on my machine, I have a Geforce Gtx760 and in 2.78c I'm getting random crashes like the ones described here,
Loop cut then crash, Ctrl+z then crash, delete face or vertex then crash, as the creator of this bug ticket said, all the crashes happened in edit mode.
The most frustrating thing about this problem is that I can't seem to reproduce this problem with consistency, I can be modeling for some half an hour or an hour and nothing happens, and some times I load Blender and the first vertex I move in edit mode crashes the application, tho this is rare, most of times it crashes after I been working for at least half an hour or an hour.
Im working on windows10 and my drivers are up to date, I also have a two monitor setup one is a Samsung screen and the other is a Hybrid Cintiq.
In my command window, in debug mode, all I get is an error: EXCEPTION_ACCESS_VIOLATION at the end of the line, and the thing written previous to that is literally just the last action I did in blender that caused the crash, like a loop cut, or ctr+z
I haven't experimented with 2.8 but I might as well give it a shot, I will report my findings as well.
Thank you for your report. It is identical to mine!
I've been looking for the latest buildbot, to continue testing and installed the latest NVidia drivers.
Blender hash:
9cd6b03version: 2.78 (sub 5), branch: master, commit date: 2017-06-30 13:58, hash:
9cd6b03, type: Releasebuild date: Sat 07/01/2017, 04:15 AM
platform: Windows
binary path: 'F:\blender-2.78.0-git.9cd6b03-windows64\blender.exe'
system-info.txt
System info:
Windows 10 familly 64bits
Encountered problem. Again in edit mode. During vertex translation.
Result, blue screen. Reboot Pc.
Information 1. Driver crash at the hardware error level.
Source
Windows
Résumé
Erreur matérielle
Date
01/07/2017 16:27
Statut
Rapport envoyé
Description
Un problème rencontré avec le matériel a provoqué un dysfonctionnement de Windows.
Signature du problème
Nom d’événement du problème : LiveKernelEvent
Code: 141
Paramètre 1: ffff8f08bd7d34a0
Paramètre 2: fffff8027f83c584
Paramètre 3: 0
Paramètre 4: 0
Version du système d’exploitation: 10_0_14393
Service Pack: 0_0
Produit: 768_1
Version du système: 10.0.14393.2.0.0.768.101
Identificateur de paramètres régionaux: 1036
Blue screen:
Source
Windows
Résumé
Arrêt non planifié
Date
01/07/2017 16:29
Statut
Rapport envoyé
Signature du problème
Nom d’événement du problème : BlueScreen
Code: 116
Paramètre 1: ffff8f08bd7d34a0
Paramètre 2: fffff8027f83c584
Paramètre 3: 0
Paramètre 4: d
Version du système d’exploitation: 10_0_14393
Service Pack: 0_0
Produit: 768_1
Version du système: 10.0.14393.2.0.0.768.101
Identificateur de paramètres régionaux: 1036
Informations complémentaires sur le problème
ID du récipient : 0x116_TdrBCR:D_Tdr:9_IMAGE_nvlddmkm.sys
Informations complémentaires sur le problème
ID du récipient : LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys
Informations du serveur : eb6b3796-c78b-4b34-8176-73724f474d55
Information 2. Office manager crash.
Source
Gestionnaire de fenêtres du Bureau
Résumé
Fonctionnement arrêté
Date
01/07/2017 16:27
Statut
Rapport envoyé
Description
Chemin d’accès de l’application défaillante : C:\Windows\System32\dwm.exe
Signature du problème
Nom d’événement du problème : APPCRASH
Nom de l’application: dwm.exe
Version de l’application: 10.0.14393.0
Horodatage de l’application: 578999ab
Nom du module par défaut: dwmcore.dll
Version du module par défaut: 10.0.14393.1198
Horodateur du module par défaut: 590280b3
Code de l’exception: c00001ad
Décalage de l’exception: 00000000000f5956
Version du système: 10.0.14393.2.0.0.768.101
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 1bb2
Information supplémentaire n° 2: 1bb2579c4c365f595b01ec03a4108773
Information supplémentaire n° 3: 64e2
Information supplémentaire n° 4: 64e27b6c46f1119f2eea7829f05553cd
Informations complémentaires sur le problème
ID de compartiment : 053a69c88097865ef15cdb52c7803900 (120757229146)
NVidia:
Source
NVIDIA Container
Résumé
Fonctionnement arrêté
Date
01/07/2017 11:00
Statut
Rapport envoyé
Description
Chemin d’accès de l’application défaillante : C:\Program Files\NVIDIA Corporation\Display.NvContainer\NVDisplay.Container.exe
Signature du problème
Nom d’événement du problème : BEX64
Nom de l’application: NVDisplay.Container.exe
Version de l’application: 1.2.0.0
Horodatage de l’application: 5952c3df
Nom du module par défaut: NVSVC64.DLL_unloaded
Version du module par défaut: 8.17.13.8476
Horodateur du module par défaut: 5952c113
Décalage de l’exception: 000000000007e5c3
Code de l’exception: c0000005
Données d’exception: 0000000000000008
Version du système: 10.0.14393.2.0.0.768.101
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: d41d
Information supplémentaire n° 2: d41d8cd98f00b204e9800998ecf8427e
Information supplémentaire n° 3: 7f9b
Information supplémentaire n° 4: 7f9b824bee5702d5026bdb35e17a93d8
Informations complémentaires sur le problème
ID de compartiment : 99eaa7820e76e2ac5cd114f15e6d74fd (116405097440)
I maintain that it is impossible to leave such as this problem. Blender is unusable.
For any useful purpose, here is the report crash that I just made on NVIDIA forums. Sometimes it can help as much in the driver part as in the Blender part.
geforce drivers/384-76-desktop win10 64bit international whql gtx 580 blender - bsod
This day, with the previous version of Blender + the last driver:
Add the crash dump:
blender.exe.9716.dmp
And event:
Source
Blender
Résumé
Fonctionnement arrêté
Date
02/07/2017 09:43
Statut
Rapport envoyé
Description
Chemin d’accès de l’application défaillante : F:\blender-2.78-b94a433-win64\blender-2.78.0-git.b94a433-windows64\blender.exe
Signature du problème
Nom d’événement du problème : BEX64
Nom de l’application: blender.exe
Version de l’application: 2.7.8.0
Horodatage de l’application: 5945e3c9
Nom du module par défaut: nvoglv64.DLL
Version du module par défaut: 22.21.13.8476
Horodateur du module par défaut: 5952b8c3
Décalage de l’exception: 0000000000ffd428
Code de l’exception: c0000409
Données d’exception: 0000000000000007
Version du système: 10.0.14393.2.0.0.768.101
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 6a0e
Information supplémentaire n° 2: 6a0e7d123c9ae6cdb16d6867452aab0c
Information supplémentaire n° 3: 7552
Information supplémentaire n° 4: 755238a31d77a89c4e2c31e7ef4e8aec
Informations complémentaires sur le problème
ID de compartiment : a1339df29229a8eea60b7ac707fb51dc (116406557167)
I confirm 2.75 Good job.
2.76, 2.77, 2.78 ans build bot not worked
Please stop posting crashdumps, they add nothing and just clutter op the ticket, instead post EXACT instructions on how to reproduce the problem instead.
For the steps.
Example as here in this mesh of the photo:
Module.blend
It is clear that I am in edit mode in the lower part. I could not save it before the crash!
This is identical as remarked to what says @renderluz-2 -> link here https://developer.blender.org/T50126#441900
Ok, I would not add more copies of errors. I thought it might be useful.
However, have you been able to reproduce this bug? Or are you on a inspect?
Merci
You're gonna have to do better, i still have a hard time figuring out how to make it happen
x) crash
Be EXACT ? maybe record a video showing the steps?
@Almisuifre
Please, you have to understand that there is a language barrier that sometimes makes things a bit difficult to understand.
Also you have a specific card the 580 X2 which is two 580 glued together which can have some specifics related to drivers that is not supported well anymore especially in a new Windows version i.e. the problems that other cards can have can be magnified here.
From the description of the issue seems to be GPU / GPU driver related. You have to first try to eliminate that problem.
The point of using the
opengl32.dllis not to replace the defaults, it's to test if Blender crashes. If it doesn't then it's a GPU / driver related issue.Since Blender is heavily dependent on OpenGL for all operations and CUDA/OpenCL for rendering most of the GPU hardware / driver related issues will make Blender misbehave / crash / hang or at least not render. The issues can vary from a severe lag, Cycles not being able to run on a GPU, to crashes to desktop / freezes.
If that is the case, posting Blend files is useless as the problem is not on the Blender's side or if there is a problem it is related to specific GPU/driver/OS combination that doesn't crash for the majority of the users.
Added subscriber: @VukGardasevic
Sorry for not speaking in your language!
What I want above all is to help you.
I'll stop you right now! This speech too often advanced does not progress.
However, I note that version 2.75 is working. I also find that other graphics cards are impacted with an identical driver, an identical installation and a newer OpenGL.
So we can say that the problem is not coming from there.
No more than for Cycles that works very well.
That's the right question. I was able to make a video from a webcam. Because when it crashes, I can not save the video being recorded.
All the steps are there!
https://youtu.be/C4pl5sYOm3Y
Thank you very much for your help
Removed subscriber: @LazyDodo
Good evening,
An example with version 2.75.
https://youtu.be/aldehZdaS_o
Prevent me from a build works.
Thanks
Removed subscriber: @xuekepei
Removed subscriber: @VukGardasevic
New test with openGL.dll.
Result, it works!
https://youtu.be/z5QOQ9IOZ7M
My Pc is therefore old and the GTX are to possess towards the exit
Thank you
Added subscriber: @dfelinto
Changed status from 'Open' to: 'Archived'
In this case, closing since this is a driver issue.