as soon as i updated to this version of experience, the rendering via adobe encoder stopped and the cmd windows popped up with the following on 2 occasions.
so as soon as these happened, i decided to uninstall experience totally and see if it happened again and it seems it is the reason...no idea why though
Ok, its not all down to "experince" software, as it just happened again. but this time it took a lot longer , ie several clips later
GeForce Experience 2.0.1.0 makes neatvideo crash
-
- Posts: 56
- Joined: Fri May 28, 2010 8:51 pm
-
- Posts: 56
- Joined: Fri May 28, 2010 8:51 pm
already thought of that, i updated the driver few weeks back, not a single problem up until the 6 hours after i updated experience.
i have a theory but not to sure.
every time ive rendered in adobe encoder cc with a bunch of projects, the memory and "ppreimer.exe" (not exact spelling), it stays there untill you remove the project thats ended from the que and the system memory stays on 100% until you kill the process from task manager.
ive said this to the guy thats worked on premier pro months ago but this is justa thought, and i say this because the warning messages go on about the memory on the gpu, yet the memory on the gpu ISNT 100% used up.
i have a theory but not to sure.
every time ive rendered in adobe encoder cc with a bunch of projects, the memory and "ppreimer.exe" (not exact spelling), it stays there untill you remove the project thats ended from the que and the system memory stays on 100% until you kill the process from task manager.
ive said this to the guy thats worked on premier pro months ago but this is justa thought, and i say this because the warning messages go on about the memory on the gpu, yet the memory on the gpu ISNT 100% used up.
-
- Posts: 56
- Joined: Fri May 28, 2010 8:51 pm
It says "Unknown error (999) in GPUCUDAApi::getDeviceMemory". Yes, that indicates that the error occured when Neat Video was trying to allocate some GPU memory. Why did it occur? - We don't know, since it happened inside CUDA itself and because CUDA did not provide any further details (Unknown error (999)).
CUDA is trying to do its job (which may involve general RAM, GPU RAM, etc.) and fails for some unclear reason.
Vlad
CUDA is trying to do its job (which may involve general RAM, GPU RAM, etc.) and fails for some unclear reason.
Vlad
-
- Posts: 56
- Joined: Fri May 28, 2010 8:51 pm