Blender 2.92 Crash - Exception_Access_Violation #86521

New Issue

Andrej Pisarcik · 2021-03-12T10:49:50+01:00

Andrej Pisarcik commented

2021-03-12 10:49:50 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72

Blender Version
Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: 02948a2cab
Worked: (newest version of Blender that worked as expected)

Short description of error
Crash that occurs at random time, no matter if Im working in edit mode, or just on idle while Im using other programs.

Exact steps for others to reproduce the error
Got a new PC setup so Blender got clean installation. Maybe it is crashing when it does autosave, because almost every time I check autosave after crash, the autosave was made only few seconds ago.

In log I found this:

Exception Record:
ExceptionCode : EXCEPTION_ACCESS_VIOLATION
Exception Address : 0x00007FFD23CAB14D
Exception Module : nvoglv64.dll
Exception Flags : 0x00000000
Exception Parameters : 0x2
Parameters- [x] : 0x0000000000000000
Parameters- [x] : 0x0000000000000030

Stack trace:
nvoglv64.dll :0x00007FFD23A89470 DrvPresentBuffers
nvoglv64.dll :0x00007FFD2395F2A8 Symbols not available

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72 **Blender Version** Broken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, hash: `02948a2cab` Worked: (newest version of Blender that worked as expected) **Short description of error** Crash that occurs at random time, no matter if Im working in edit mode, or just on idle while Im using other programs. **Exact steps for others to reproduce the error** Got a new PC setup so Blender got clean installation. Maybe it is crashing when it does autosave, because almost every time I check autosave after crash, the autosave was made only few seconds ago. In log I found this: Exception Record: ExceptionCode : EXCEPTION_ACCESS_VIOLATION Exception Address : 0x00007FFD23CAB14D Exception Module : nvoglv64.dll Exception Flags : 0x00000000 Exception Parameters : 0x2 Parameters- [x] : 0x0000000000000000 Parameters- [x] : 0x0000000000000030 Stack trace: nvoglv64.dll :0x00007FFD23A89470 DrvPresentBuffers nvoglv64.dll :0x00007FFD2395F2A8 Symbols not available

Andrej Pisarcik commented

2021-03-12 10:49:50 +01:00

Added subscriber: @DarkkAndre

Andrej Pisarcik self-assigned this 2021-03-12 19:58:05 +01:00

Andrej Pisarcik commented

2021-03-12 19:58:05 +01:00

I realised it does not crash when I do manual saves all the time and disabled autosave. If it crash I will immediately post it here.

Germano Cavalcante commented

2021-03-15 16:29:22 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-03-15 16:29:22 +01:00

If I'm not mistaken, nvoglv64.dll is basically the Nvidia OpenGL driver.
So this seems like a graphic driver issue.
Please double-check if the drivers are up to date.
To upgrade to the latest driver, see here for more information: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html

If I'm not mistaken, `nvoglv64.dll` is basically the Nvidia OpenGL driver. So this seems like a graphic driver issue. Please double-check if the drivers are up to date. To upgrade to the latest driver, see here for more information: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html

obrad commented

2021-03-17 13:02:21 +01:00

Added subscriber: @obradk

obrad commented

2021-03-17 13:02:21 +01:00

I've been having this same issue after moving from 2.9, had it happen on windows build 1909, now on 20H2. Tried studio drivers, regular drivers, and it happens on mouse click - that's the only thing I can see.
The click can be anywhere, as long as it's in Blender. The driver before last caused Blender to crash without managing to write the crash log. The last one crashes with the same log as above:

nvoglv64.dll :0x00007FFF36AC9620 DrvPresentBuffers
nvoglv64.dll :0x00007FFF369AFA1C Symbols not available

An interesting thing I noticed with the older driver - one of my files would cause a crash instantly (no crash log), but if I started Blender in debug mode it would just open and work as usual. After updating the driver to the latest I can open the file without debug mode.

I've been having this same issue after moving from 2.9, had it happen on windows build 1909, now on 20H2. Tried studio drivers, regular drivers, and it happens on mouse click - that's the only thing I can see. The click can be anywhere, as long as it's in Blender. The driver before last caused Blender to crash without managing to write the crash log. The last one crashes with the same log as above: nvoglv64.dll :0x00007FFF36AC9620 DrvPresentBuffers nvoglv64.dll :0x00007FFF369AFA1C Symbols not available An interesting thing I noticed with the older driver - one of my files would cause a crash instantly (no crash log), but if I started Blender in debug mode it would just open and work as usual. After updating the driver to the latest I can open the file without debug mode.

Andrej Pisarcik commented

2021-03-17 13:10:48 +01:00

I do not understand why, because that nvoglv64.dll file is the Nvidia OpenGL driver and it crashed on mouse click like obrad said, but since I posted that problem here, Blender did not crash. I updated nvidia driver one day ago and It works correctly so it is strange what was the real problem.

I do not understand why, because that `nvoglv64.dll` file is the Nvidia OpenGL driver and it crashed on mouse click like obrad said, but since I posted that problem here, Blender did not crash. I updated nvidia driver one day ago and It works correctly so it is strange what was the real problem.

obrad commented

2021-03-17 13:26:54 +01:00

I tried the mesh object data check script that was suggested in another thread and all my objects were clean. It never crashed while rendering or while 'doing' anything, only on clicks - even clicking on regular parts of the interface. I have a feeling this is a problem with nvidia and not Blender, but no idea how to go about it.

obrad commented

2021-03-21 23:24:47 +01:00

Could somebody with this problem try this workaround? It seems to help, but since this is such a random problem I can't be sure yet.

https://forums.x-plane.org/index.php?/forums/topic/200744-bug-report-nvoglv64dll/

Go to registry editor (start -> run -> regedit)
Navigate yourself to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/GraphicsDrivers (make sure GraphicsDrivers is highlighted).
Right click -> New -> DWORD (32-bit) value -> Name it: TdrDelay -> double click it -> Set it to A (hexadecimal) or 10 (decimal).

Could somebody with this problem try this workaround? It seems to help, but since this is such a random problem I can't be sure yet. https://forums.x-plane.org/index.php?/forums/topic/200744-bug-report-nvoglv64dll/ 1. Go to registry editor (start -> run -> regedit) 2. Navigate yourself to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/GraphicsDrivers (make sure GraphicsDrivers is highlighted). 3. Right click -> New -> DWORD (32-bit) value -> Name it: TdrDelay -> double click it -> Set it to A (hexadecimal) or 10 (decimal).

Germano Cavalcante commented

2021-04-06 19:03:46 +02:00

Closed as duplicate of #85977

Germano Cavalcante closed this issue

2021-04-06 19:03:46 +02:00

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

Blender 2.92 Crash - Exception_Access_Violation #86521