- What operating system are you using?
OS X 10.7.4
- Did you upgrade your operating system from a previous version?
No. Fresh install of 10.7. Unless you count 10.7 to 10.7.4
CORRECTION: The computer did originally come with 10.6.8. I installed a new HD and did a fresh install so I figured it didn't matter. But upgrading the NVIDIA driver it only lists the driver under 10.6.8. So I figured I should mention it.
- What is the model of your CPU?
2.66 GHz Intel Core i7
- What is the model of your GPU?
NVIDIA GeForce GT 330M 512 MB
and
Intel HD Graphics (Don't use this with AE of course)
- What is the version number of your graphics driver?
2.1 NVIDIA-7.18.18 270.05.25f01
- If you have an Nvidia card, what is the version of your CUDA driver?
4.2.7
I get the same error when quiting After effects
After Effects Alert
Last log message was: <140735189834080>
<ae.blitpipe> <2> HardwareBlitpipe Disengaged
.
Generating crash log, which may take a few minutes.
Everytime ... so even without using / activating the raytrace engine.
I am also getting "After Effects error: Ray-traced 3D: Initial shader compile failed (5070::0)"
| Fast Draft: | Available |
| Texture Memory: | 4560.00 MB |
| Ray-tracing: | GPU |
OpenGL
| Vendor: | NVIDIA Corporation | |
| Device: | Quadro 6000/PCIe/SSE2 | |
| Version: | 3.0.0 | |
| Total Memory: | 5.94 GB | |
| Shader Model: | 4.0 or later |
CUDA
| Driver Version: | 4.2 |
| Devices: | 2 (Tesla C2075, Quadro 6000) |
| Current Usable Memory: | 5.18 GB (at application launch) |
| Maximum Usable Memory: | 5.25 GB |
Windows 7 Ultimate Version 6.1.7601 Service Pack 1 Build 7601
HPZ820
| Processor | Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, 2901 Mhz, 8 Core(s), 16 Logical Processor(s) |
| Processor | Intel(R) Xeon(R) CPU E5-2690 0 @ 2.90GHz, 2901 Mhz, 8 Core(s), 16 Logical Processor(s) |
| BIOS Version/Date | Hewlett-Packard J63 v01.02, 3/9/2012 |
| Name | NVIDIA Quadro 6000 |
| Driver Version | 8.17.12.9670 |
| Name | NVIDIA Tesla C2075 |
| Driver Version | 8.17.12.9670 |
I more than meet the recommended specs, and still have the problem. I'm quite certain looking thru all of this, that it is an issue of 10.7.4.
I'm uninstalled and re-installed AE, updated to all the latest drivers, done everything i can short of re-intalling the OS, which quite frankly is a huge pain in the ***.
I wonder if Adobe has been able to reproduce the error in-house yet.
> I wonder if Adobe has been able to reproduce the error in-house yet.
So far, the only cases that we've seen in-house or among our pre-release testers have been due to an out-of-date CUDA driver, as described by cltcutters above. It appears that something in the CPU-based renderer is trying to make use of something in the CUDA driver, which shouldn't happen. We're still trying to get to the bottom of this.
In the meantime, I recommend that everyone try the proposed solution mentioned by cltcutters.
I installed the driver and otherwise didn't do anything. Ray-traced renderer now works and I'm no longer getting an error when I quit After Effects.
Again, this is on a 2.2 GHz Macbook Pro with 8 GB of RAM, 6750M Radeon, upgraded from 10.6.8 to 10.7.4.
I can confirm that solution mentioned by cltcutters works for me too. Just did it and it works just fine. Finally, some sort of solution. iMac here, mid 2011, AMD 6750m. So, it remains strange that CUDA driver did something and not having nvidia card installed. But, it is solution until Adobe clarifies things.
Someofmywork, that is interesting. All of my Mac systems show 4.2.7 as the latest CUDA version. Do you know where the 4.2.9 driver came from? Are there any games installed on this system from Steam, Blizzard, etc.?
I'm curious, how many of the failing systems have graphics intense games installed?
Good catch, i hadn't noticed that before.
I found it here:
http://developer.nvidia.com/cuda-downloads
i am downloading now...
The update is behind. The real current version is 4.2.9 as per the link at nvidia
devdriver_4.2.9_macos.dmg
which we didn't update to until AE started complaining about the driver being old.
MacBook Pro. Mac OS X 10.7.3
I am having the same problem at work. I hope they find the solution.
Fast Draft: | Available |
| Texture Memory: | 204.00 MB |
| Ray-tracing: | CPU |
(GPU not available - incompatible device or CUDA driver)
OpenGL
| Vendor: | NVIDIA Corporation | |
| Device: | NVIDIA GeForce GT 330M OpenGL Engine | |
| Version: | 2.1 NVIDIA-7.18.11 | |
| Total Memory: | 512.00 MB | |
| Shader Model: | - |
CUDA
| Driver Version: | - |
| Devices: | - |
| Current Usable Memory: | - |
| Maximum Usable Memory: | - |
I'm having the same trouble as well. Tried installing new Cuda drivers (4.2.9) and re-installing CS6 and that didn't help.
| Model Name: | iMac |
| Model Identifier: | iMac12,2 |
| Processor Name: | Intel Core i7 |
| Processor Speed: | 3.4 GHz |
| Number of Processors: | 1 |
| Total Number of Cores: | 4 |
| L2 Cache (per Core): | 256 KB |
| L3 Cache: | 8 MB |
| Memory: | 12 GB |
No problem. We are trying to get a system to reproduce the bug and gaming is one potential area that we have not tested against. So far on systems physically matching those reported here we are getting good results. Testing included updating the OS, trying different CUDA drivers, etc.. The 4.2.7 driver is working fine on the six systems I looked at, so that does not appear to be the issue.
If you can file a bug report and include the complete system information file from a failing system that would be great. Another is to understand how one is testing by providing exact steps including comp size, layer type, ray tracer setting, fast preview mode, etc.. On the windows side, update to the newest NVIDIA driver for the NVIDIA card. If that fails, again, include the system information file in a bug report.
One thing to check on the Mac is to be sure the EFI firmware is up to date. Another thing to try is deleting the Nvidia computer cache. On the Mac this is located in your user folder->Library->Application Support->NVIDIA->Computer Cache. Delete the Computer Cache folder. It will get rebuilt on launch of AE CS6.
Fail. My system runs a gt120 for its display card then a gtx 265 for its Cuda card. I have tried taking them in and out and reordering them and making a clean user. I really find it hard to believe this isn't replicable in the lab when its so prevalent in the wild. There are no settings to give. ON LAUNCH GPU FAILS with error about driver version.
> I really find it hard to believe this isn't replicable in the lab when its so prevalent in the wild.
It is not prevalent. There are very few people hitting this. We understand that it's annoying to you, since you're one of the people that it's hitting... and that's why Will (and others here) are trying so hard to find the exact set of circumstances that cause the problem. The more information you can give Will, the more likely he is to be able to help you.
North America
Europe, Middle East and Africa
Asia Pacific