Error exception access violation blender

$begingroup$

I just installed Blender, but when I try to start it, the command prompt comes up with «Error: Exception_Access_Violation» and then closes (and Blender never starts of course). How do I fix this? I tried running as administrator and that doesn’t help either.

asked Aug 27, 2016 at 10:54

$endgroup$

$begingroup$

I want to answer so that anyone with my particular situation might benefit … I had this same frustrating problem with WIN 7, and a Intel HD graphics (which supports only OpenGL 2.1) … I tried some suggestions which didn’t work (though I needed the 2013 C++ library anyway, a link to this is given at the Blender site just below the Blender download links—I had only 2010) then I simply updated the graphics driver from a 2010 version to the 2012 version . and that did it. Actually I was surprised it did, but it did.

Read also that some other people had to go back to an older driver instead.

At any rate 2.77 can at least run with a Intel HD graphics, I am proof.

By the way I used an Intel utility called Intel driver update Utility to find the right driver. The screen went black after the driver was installed, and I feared the worst, but after restarting things seemed ok, the driver was installed and even Blender worked! Darkest before the dawn or something. Assuming all is well..

Oh last detail which probably doesn’t matter) I didn’t install Blender, I unzipped the zip file and ran it straight..

answered Sep 14, 2016 at 6:26

$endgroup$

$begingroup$

I googled this and found this bug report:

https://developer.blender.org/T44334

You need to delete ALL versions of blender (you will need admin privileges), then reinstall the latest version.

«I was also experiencing this bug on with version 2.76 windows 10 like Will Tice. Like Will I had followed all the instructions above to no avail. I decided to try the older 2.73 version of blender and was uninstalling 2.76 when I noticed there were left over files from version 2.69 from windows 8. After thoroughly cleaning out all blender files and reinstalling 2.76 I’m having no issues. Checking for and removing previous versions of blender may help with this issue.»

«I had the same problem but noticed I had a 32bit 2.6x version around together with the 2.76 I had just installed. Getting rid of the two of them and reinstalling just the 64bit 2.76 got rid of the problem.»

«I’m using Windows 10 and had this issue. Uninstalling both versions of blender and reinstalling blender-2.76b-windows64.msi fixed it.»

Another potential problem could be your drivers/video card, although I highly doubt it:

https://stackoverflow.com/a/32552796/6655092

answered Aug 27, 2016 at 11:18

JakeDJakeD

8,2272 gold badges28 silver badges70 bronze badges

$endgroup$

$begingroup$

Had the same issue. Tried updating graphics driver, removing all of the old blender installs, as well as reinstalling newest blender version only. None of them worked for me.

Downgraded blender from 2.79 to 2.78, and it worked again!

Maybe this helps someone out there.

answered Jan 28, 2018 at 9:09

$endgroup$

$begingroup$

Downgrading from 2.79 to 2.78 worked for me aswell, until I activated cycles render, then it crashed.

I had to upgrade my intel graphics driver, too Intel Support. The thing was, that my intel graphics were disabled (It seems that many motherboards do this automatically, when a graphic card is plugged in). So I had to activate onboard graphics in the bios first, before I could update the intel graphic driver.

Now everything is fine again.

answered Nov 24, 2018 at 8:58

$endgroup$

$begingroup$

Nothing worked but deleting this C:UsersusernameAppDataRoamingBlender FoundationBlender2.93config

answered Oct 14, 2021 at 0:45

IgnacIgnac

1171 gold badge1 silver badge12 bronze badges

$endgroup$

$begingroup$

i just downloaded opengl32.dll from this web site ftp://ftp.blender.org/sergey/softwaregl

i hope that’s well help some one because it worked for me.

answered May 5, 2018 at 15:54

$endgroup$

$begingroup$

It turns out Windows Update doesn’t do anything to update the graphics driver. Go to Intel’s support site, look for your graphics card (in my case Intel HD Graphics 620), and manually install the graphics driver. This solved the problem for me.

answered Sep 11, 2018 at 13:07

MicrobobMicrobob

2293 silver badges8 bronze badges

$endgroup$

$begingroup$

Had the same error on Win7 laptop. All the drivers were up to date, but still wouldn’t run — the only thing that helped was downloading a portable (.zip) 2.78 Blender.

answered Jan 24, 2021 at 22:40

MarkMark

1011 bronze badge

$endgroup$

Источник

Содержание

Error exception access violation blender
Blender
Error exception access violation blender
Event Timeline
How do I fix Exception Access Violation error on startup?
8 Answers 8
Error exception access violation blender
Error exception access violation blender
Event Timeline

Blender

А где ты видишь это «exception access violation»? Во всплывающем окне? А ты пробовал запустить через cmd («Коммандная строка») и посмотреть что там пишет? Там подчас побольше инфы чем просто «exception access violation».

через cmd пишет:
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000
Module :
Thread : 00000ee4
Writing: C:UsersdmhitAppDataLocalTempblender.crash.txt

Драйвера видеоадаптеров обновил, micrasoft visual c++ начиная с 2005 по актуальный скачал,microsoft net framework обновил.
blender-2.49b-windows эта версия программы запускается
версии 2.5 и до 2.7 (+-2.7) выдает такую ошибку:
выходит окно с надписью:Microsoft Visual C++ Runtime Library
Runtime Error!
Program: C:.
This application has requested the Runtime to terminate it in an unusual way.
please contact the application’s support team for more information.
Когда запускаю через консоль , пишет:
found bundled python: C:UsersdmhitDesktopBLENDE

1.55-2.55python
Fatal Python error: Py_Initialize: can’t initialize sys standard streams
LookupError: unknown encoding: cp65001found bundled python: C:UsersdmhitDesktopBLENDE

1.55-2.55python
Fatal Python error: Py_Initialize: can’t initialize sys standard streams
LookupError: unknown encoding: cp65001
Версии начиная где то с 2.7 выдают только эту ошибку т.е.EXCEPTION_ACCESS_VIOLATION

Очень странно. Ну и разумеется другие программы и игры работают как надо и без проблем?

Что-т не знаю, 4 машины под руками, одна Linux, одна Windows 7, две Windows 10 64 bit; видео есть как AMD, так и nVidia и Intel — Blender работает везде, любой. Они его конечно «ломают» порою как-то усиленно с их новым подходом к разработке, но ты говоришь что у тебя и 2.79 не пашет.

Источник

Error exception access violation blender

Blender 2.91
error :EXCEPTION_ACCESS_VIOLATION
address : 0x000000006787A345
Module: atio6axx.dll thread: 00004b4

Broken: (example: 2.91, the software won’t start, 2020-11-27,)
Worked: no
when I open the software won’t start

Event Timeline

Does this occur when you try to access Blender or when you are using it?

Yes sir it occurs when I try to access Blender 2.91

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x0000000000000000
Module :
Thread : 00003a28
Writing: C:UsersLEONAppDataLocalTempblender.crash.txt

Did you try with latest Radeon driver updation?
I had also the same issue, but after I updated lastest version the it worked.
Try

Thanks, Toooooooooo much Mr.Prigith Joseph (Prigirh) It worked after I update the Radeon driver

Solved here for Nvidia Display adapters:

I’m using two monitors.

One connected to Nvidia 1070 Display adapter (with Nvidia Studio Driver 457.30 ).
Other one connected to second Display adapter HD Intel graphics 530.

If my main monitor (set in windows display settings) is connected to the Intel Display adapter. Blender does not launch.

But if my main monitor is set to the Nvidia 1070, Blender starts just good.

Источник

How do I fix Exception Access Violation error on startup?

8 Answers 8

I want to answer so that anyone with my particular situation might benefit . I had this same frustrating problem with WIN 7, and a Intel HD graphics (which supports only OpenGL 2.1) . I tried some suggestions which didn’t work (though I needed the 2013 C++ library anyway, a link to this is given at the Blender site just below the Blender download links—I had only 2010) then I simply updated the graphics driver from a 2010 version to the 2012 version . and that did it. Actually I was surprised it did, but it did.

Read also that some other people had to go back to an older driver instead.

At any rate 2.77 can at least run with a Intel HD graphics, I am proof.

Oh last detail which probably doesn’t matter) I didn’t install Blender, I unzipped the zip file and ran it straight..

Источник

Error exception access violation blender

System Information

Windows 10 V1703 build 15063.483
GPU NVidia 660Ti tested with drivers : 382.33 382.53 384.76

Blender Version

Blender 64bits, tested versions (fresh download and install zip version, also cleaned the user profile between each):

Official 2.78c (same one I was using without issue since the release)
blender-2.78-c9817c6-win64
blender-2.80-2a48927-win64-vc14

Short description of error
I have used the same system for year without issues.
Since a few days when I try to start blender it just crash with:
Error: EXCEPTION_ACCESS_VIOLATION
If fresh install and nothing in the user profile, it does start, but accessing the user preference, doing anything related to cycle or rendering cause the crash.
If there is anything in the user profile, it does not even start, just crash immediately.
As there was no change to blender itself and it’s consistant with the 3 last GPU drivers (including the one that was working for sure) it could be related to one of the recent Windows update.

Exact steps for others to reproduce the error

Try to start Blender. crash

OS and drivers are fully up-to-date. Cleaned and reinstalled GPU drivers each time.
Antivirus do not change anything.
File location do not change anything.
No other Python installed.
Tested (when it accept to start) with old, recent and new .blend file with the same result.
There is test.crash.txt or crash file generated in the tmp folder

Running with factory setting does not even popup the windows, it crash.
Running with -d report the two attached file depending if there is anything in the user roaming profile or not.

Источник

Error exception access violation blender

System Information
Windows 7 64 bit — AMD Phenom II x6 1100T — Ati HD 6870

Buildbot 2.74.5 #dc95ca9

I wanted to check out Ati / OpenCL gpu cycles render (heard there was a commit), when I try to render with F12 or switch to rendered view, press Render tab in properties or go to preferences/system tab blender crashes (directly to OS no warning).

Anything related to rendering just crashes and closes blender. Doesn’t happen on 2.74 or the previous builds from build bot until this #dc95ca9 build.

If I run blender with » blender.exe -d > errors.txt » I get nothing but EXCEPTION_ACCESS_VIOLATION

Event Timeline

@Sergey Sharybin (sergey) correct me if I am wrong, but I think we only support GCN GPUs (HD 7000 series and above). If that is the case, we might want to blacklist all older GPUs to prevent crashes.

This sounds like a driver bug which crashes at OpenCL device enumeration. Things to try:

Make sure latest drivers are installed
From the command line run: clinfo.exe. It should give list of available OpenCL platforms if there’s no bug in the drivers
Run blender from the command line: blender.exe —factory-startup —debug-cycles

@Thomas Dinges (dingto) , Think VLIW is also supported with latest drivers, maybe not on optimal speed tho. In any case you can’t blacklist anything because crash seems to happen on the device enumeration.

When using blender if I use latest drivers blender freezes my computer. At least it use to, I searched around and found a compatible driver which tolerates and recovers TDR’s (Time out Detection and Recovery). And if blender fails at least my system recovers. This is a blender specific situation, I have no problems with other software (Photoshop 3D & 2D Opengl, Zbrush, Unity, OpenGL games they work fine). I guess due to OpenGL 1.1 viewport draw. So unless the viewport supports later versions I don’t want to change my current driver and mess my TDR recoverable blender.

Clinfo.exe just crashes , windows error «Program has stopped responding».

and running blender.exe with » —factory-startup —debug-cycles » outputs «unknown argument» for both.

By the way I agree with Thomas, I understand Ati decided to support only their latest gpu’s for opencl, like i said ın the original post I want to test it. Didn’t expect to cause a multiple source- bad crash — like this. I guess its easier to blacklist the gpu’s since the culprit is AMD / Ati. I just like to prevent this problem in upcoming 2.75 release. > Working blender without opencl.

When clinfo crashes, it’s a driver problem, and not a Blender problem. We can only support latest and official AMD drivers.

I downloaded the 15.x beta drivers and blender stopped crashing , the clinfo.exe also works. So If the report was valid then thats the conclusion —

However I do like to point out some things.

The previous TDR tolerant driver I was using is official Ati driver 13.1 which is the default driver for the card. And I only reverted to it stop blender from hanging up my system (Its a Blender specific problem).

Like I explained the hanging up problem is related to OpenGL version of Blender. The problem specially occurs on GLSL view. This doesn’t occur on Nvidia (they support older 1.1 OpenGL on their drivers ). So if ATI supported older openGL versions it would solve a lot of conflicts in Blender.
.
Technically AMD / ATI is at fault here, but Blender is also making it worse. Currently I’m worried that I’m going to get into an impossible situation. If blender freezes the computer with 15.x driver then I have revert to official 13.1. If I revert to 13.1 then that means the current master will crash everytime I touch a button related to rendering.

So I think there is a conflict, viewport needs older compatible drivers while cycles needs the latest drivers. Maybe a BlackList is better at solving these issues.

Anyway, I do wish blender gets a decent viewport which supports recent cards with OpenGL 2.1 or 3.3. Because openGL 1.1 kind of chokes the current development. Thanks for your time.

Источник

I’ve just downloaded Blender 2.75a, and all it does is bring up a console window that says «Error: EXCEPTION_ACCESS_VIOLATION»

The console window will not close, will not exit with task manager, and when I try to end its process it says Access is Denied. So I have a permanent broken blender on my desktop until I restart.

How do I make blender run?

asked Aug 19, 2015 at 18:07

On my computer this error was caused by the video card driver, in particular the Intel GMA 4500 graphics driver that Windows 8.1 will automatically (re-)install with Windows update. This video card is often found in older laptops with Core 2 Duo processors.

In previous tests I found out that the driver version that Microsoft provides through Windows update does include the required OpenGL version for some games and graphics applications.

I solved this problem by downloading and modifying (according to this tutorial) Intel GMA 4500 driver version 15.17.19.64.2869 (file name Win7Vista_64_151719.exe) so that I can install it on Windows 8.1. But keep in mind that this can cause some graphical artifacts and glitches that you would normally not see.

answered Sep 13, 2015 at 17:58

chrkichrki

6,0646 gold badges35 silver badges54 bronze badges

Источник

Hey ConnorB123,

Do you mean that this workaround is not preventing crashes for you?

— Ryan

Yes, that workaround does not work for me. Sometimes my renders will not crash, but most times they do.

Hey ConnorB123,

Thanks for reporting this! This is actually the first report of the workaround not solving render crashes so I would like to get some more information so this can be solved for you and anyone else who may be experiencing the issue. I have a few questions that would help me learn more about this:

What is your system information?
- Operating System
- Blender System Information (attach file: Blender > Help > Save System Info)
- Addon Version
- CPU Model
- GPU Model
Are you using an official release version of Blender? Or an alternative build such as a nightly build or custom branch?
Are you using the the denoising feature? — The denoising feature can be unstable and cause EXCEPTION_ACCESS_VIOLATION errors with certain setting configurations.
Do you notice any patterns that relate to the frequency of crashes? Examples:
- Increase when rendering whitewater
- Decrease after a system restart
- GPU rendering vs CPU rendering
- High resolution vs low resolution simulations
- Low samples vs high samples
Do the crashes occur at the same stage of rendering?
- During render initialization (right before rendering)?
- During rendering?
- After rendering completes?
Do the crashes occur when rendering from the command line? Command line rendering seems to be the most stable method of rendering

Command:

/path/to/blender.exe -b /path/to/blend_file.blend -a

For example, my command looks like this (using Windows CMD):

"C:Program FilesBlender FoundationBlenderblender.exe" -b "C:UsersryanlDocumentsBlendermy_blender_scene.blend" -a

Thanks for providing any additional information, and sorry for the inconvenience! Hopefully I’ll be able to gain some insight to what could be the cause of this issue.

— Ryan

This comment has been minimized.

The crashes don’t occur often when rendering via the blender GUI, but they happen every few frames when rendering using blender’s network render add on, which does the actual render via the command line. I also use the command line to start up the network master server and slave. I’m using the latest release version of blender and the add on. I am using the denoising feature, but the crashes happen when I don’t use it as well. I haven’t tried rendering at low resolution/low samples, so I don’t know if that would help. The crashes happen when I use CPU or GPU rendering. The crashes always seem to happen either just after a frame finishes rendering, or right as the next one starts, I can’t tell which.

PC used for baking/modeling:
AMD Ryzen 7 1700
32GB DDR4 3000mhz
GTX 960 4GB
Windows 10 Pro

PC used for network rendering:
AMD FX 4350
20GB DDR3 1600mhz
GTX 1080ti
Windows 10 Home

Thanks for providing this information! I’ll need to try using the Network Renderer addon to see if I can reproduce this issue. I’ll need to wait until Monday to have access to multiple systems for testing. I’ll keep you updated.

Hi,

Any update with this? If I could use the network render it would help speed up my workflow a lot.

Hello ConnorB123,

I only had a chance to test this very briefly last Monday, but was not able to reproduce this issue. I still want to test this more extensively using a higher resolution simulation. At the moment, development and bug fixes for the FLIP Fluids addon is on hold. I am currently in the process of moving homes and do not have access to my desktop system used for development. Development should resume as normal within the next few days however. Sorry for this inconvenience!

I would like to test this issue using the exact Blender builds that you are running. Would you be able to attach the Blender System Info files for both of your systems. This file can be retrieved through Blender: Blender > Help > Save System Info. This file will give me more info on your Blender setup.

— Ryan

This comment has been minimized.

rlguy

changed the title
Error: EXCEPTION_ACCESS_VIOLATION when rendering

Error: EXCEPTION_ACCESS_VIOLATION when rendering using Network Render Addon

Jan 31, 2019

I will be closing this issue due to inactivity and to clean up the issue tracker. If there are any further updates, feel free to add them here or send us an email at flip.fluids@gmail.com

Same Issue here in Blender 2.8 and Flip-Fluid from 14.02.2019. Currently, the only well working workaround is to render from console.

Issue: When trying to render as animation or as image, while initializing blender crashes. It seems to be more likely to work, when rendering a single image.

Hi PascalSchimmler,

Thanks for the report! I have a few questions that could help me understand this issue:

Are you able to render successfully without using Network Render, or does this only happen when using the Network Render addon?
Does this happen when rendering with EEVEE, or with Cycles, or both?

— Ryan

Hi,
can confirm for me Cycles is crashing upon starting a render, single frame or animation does not matter, rendering from command line seems to work.

Im not using any Network Render atm and haven`t tried it with Eevee yet

Cheers,

I’m having this issue in heavy particle animated scenes and this is my fix: if I use the command line for rendering, keep the auto-ram cleaning open and instead of getting all the frames with » -a » in cmd I use a for loop to open separate shell for each frame.
I’ve been experimenting and when you try to batch render frames in one shell it crashes. And if you have other blender instances running they very most possibly will try to occupy the same memory addresses so keep your running tasks list clean.

Источник