Messages posted by bitman

As the title suggested something in my system brings down PD11 64 bit ultra down periodically
(say around 10 minutes after starting up PD).
PD cannot even report this as it usually does when it crashes by it's own fault.
Window application event states ==> atimpenc64.dll_unloaded
I started noticing this recently.
PD has become unworkable by this.
- sw: catalyst 13.3 beta 3 (works fine in all games, even openCL is tested and benchmarked, has a fix for openGL)
Note do not use 13.3 beta 2 as this has an issue with openGL (not openCL)

Note that crash can happen even when PD is idling (start up PD default option full edit, do nothing, then minimize on desktop)
Note: I do have IE10 and email open while PD is idling.
Note: PD does not need to be idling, as I have it also when working with it.

I will make a separate thread for the idle issue, although I believe we have the same root issue.
I had one time the same crash while the PD11 was not minimized idling.
-we both have C drive SSD and a non C: big datadrive,
-we both have ATI versions 13.x
-we both have windows 7 64 bit ultimate
-we may have other items in common

- what is not the issue (tried by me or the OP):
------------------------------------------------
- interference other video editors (OP did fresh installs)
- codex issues (same reason)
- anti virus (we have different ones)
- PD11 itself (yes, it looks to me some other program/process/services time-out or scheduled thing unloads the dll used by PD11 making PD11 crash. In fact PD11 cannot even report the issue, it is windows own reporting that gives the crash info.

- observations
--------------
- the problem goes away by using nvidea ==> points to ATi videocard, or possibly catalyst sw suite
- the problem looks to be less or gone (not sure, more test needed) if all programs are removed from startup (this includes CCC).
Unfortunately I upgraded IE9 to IE10 from MS a few days ago, this could also be causing issues, to be on the safe side, I deactivated HW acceleration in IE
I am beginning to suspect catalyst control center (and associated MOM process) itself.

I am not out of the woods yet
It still crashes on idling (when minimized) after about 10 minutes, I looking into the win7 scheduler, but I do not see anything planned for when it crashes.
I can rule out autosave I think as I disable it (unless the gui un-tick is not properly propagated to the program code).
I need to check the registry.
Any of you folks have PD11 crash in following steps?
- start PD 11 (64 bits) full edit
- do nothing with it, just minimize it with the normal windows minimalize dash (right top corner)
- wait for 10-15 minutes (start email and IE in the mean time to keep you busy )
- crash

in reply to Dafydd Bevan
Yes I am a gamer with a gamer rig I always build and configure myself, including watercooling. However I have not overclocked in years as even today's games are sometimes so taxing that overclocking is indeed very tricky for stability.
Your suggestion about the power options (2 terrabyte cash disk falling asleep) as my pd11 is installed on SSD, it did crossed my mind as well, I'll give it a go.

I may found a cure for my PD11 crash (atimpenc64.dll_unloaded) after 10 minutes, it may or not may cure your rendering crash as I was not rendering, but was just idling after startup, but here it is (you may want to try this).
I was looking for something periodically scheduled, so I tried to disable the autosave of PD11 which was set at the suspicious value of 10 minutes, but this did not help.
Next I disabled every program / utility from starting when the PC starts (I kept the services going).
This seems to have cured my problem (together with disabling autosave in PD11).
You can do this via typing msconfig from the command field in windows.
click on the tab "opstarten" (not services) I guess it would be "start-up" in English as I have a Dutch os,
and untick all programs/utitilies or the ones you suspect.
You need to reboot after that.
For my PC I (may) narrowed it down to the following culprits (you may have other programs):
- install shield update service
- plexutilities
- quicktime
- Samsung panel manager
- Skype
- Spotify
- Steam client bootstrapper
- Bluetooth stack for ..
- Plexradar

In time I will narrow it down even more by gradually re-adding (tick ) those above until the guilty one is found.

Update:
putting the autosave back on, gave me again the error, so I am not sure if it is the combination of
- removing some stuff from the PC startup (use msconfig to experiment with)
- deactivating the autosave in PD

I am still looking for other culprits as I am not sure I nailed it as there are other users having issues with the latest catalyst drivers and cyberlink PD

http://forums.guru3d.com/showthread.php?p=4567390

Now I am beginning to suspect the atimpenc64.dll_unloaded is related to yet another selectable part of the catalyst package, the accelerated "transcoding drop and drag feature for win7"...
You may want to try this:
I first unticked it in the CCC , then uninstalled that part from the package (use the regular ati catalyst install manager program to uninstall that single part-via uninstall programs, select the cat install program, and use custom to select only that item to uninstall.
Next reboot your PC.
Note that the feature can be removed as it is pretty useless unless you have external devices connected (e.g. ipod) were you want to HW assisted transcoding stuff to it ...

Summary things to do
1) removing some stuff from the PC startup (use msconfig to experiment with)
2) experiment with activating/deactivating the autosave in PD (or change the timer)
3) untick "drag en drop thingy" in CCC and uninstall that part from the catalyst suite + reboot your pc after uninstall

You may want to start with only the third thing first

Update: it is not solved yet, still working to find the issue

Not sure this is an openCL issue. My reasoning: if you disable both HW acceleration options in the preferences, do no rendering, in fact do nothing at all, let the program idle, then still the program crashes by itself after say 10 minutes or so of starting the program.
Going back to 12.1 catalyst drivers is no option for me as I also am an avid gamer.
On a side note, the developer page at AMD is indeed pointing to 12.1, but if you install from the AMD opencl developer site only the run time SDK for opencl (AMD-APP-SDK-v2.8-Windows-64.exe), you will see that the AMD APP SDK Runtime is version 10.0.1124.2 and this version is higher than the version included in CCC 13.1 (10.0.1084.4 as HDedit pointed out).
In fact if you install 13.3 beta 3 (latest beta) you will get the latest and exact same opencl drivers as on the developer page (10.0.1124.2), so you could spare the effort installing from the developer page drivers.
You can test if openCL is working fine by downloading gpu-z and CLBenchmark.
gpu-z will show a tickmark at opencl if it detects opencl capability, and with CLBenchmark you can test opencl itself and have a performance score.
CCC Version 13.3 beta 3 work fine by the way (apart from the crash in this thread).

I do have an other issue (I believe unrelated to the re-occurring crash), but related to hw acceleration and one particular effects filter called "continuous shooting". Just drop one of the default video's or jpg on the time line and the filter on top of it will always crash my PD, other filters do not have this, disabling the HW acceleration fixes this. There is a separate thread on this, as I am not the only one with this problem, even some nvidea guys have this issue with this particular filter, do you have this issue as well?

Sad to say , but I too have this re-occuring error PD11 64 bit ultra crashes every 10 to 13 minutes.
I get atimpenc64.dll_unloaded in the win7 event monitor.
In fact very easy to simulate: start PD11 all default, no projects or any work selected.
Then minimize on desktop and just wait...
Maybe this came after upgrading to the PD11 latest patch 11.0.0.2707, not sure.
I have 2x ATI 5850 in crossfire, running catalyst 13.3 beta 3
It does not matter if HW acceleration is on or off.
I do have C drive with 2XSSD in raid, and no, the 18GB swap file is not on the C-drive but on a 2 terraB disk,
memory is 6GB of ram; also all PD11 working directories are adapted to point to the terabyte disk.
OS is win 7 64 bit.

xerox : you are probably not using external videocards, but the AMD embedded graphics sollution (the architecture like e.g. video memory is used differently). So it may work for you.
For Cranston,I see you tested it on an XP PC which I doubt it be 64 bit OS , nor PD11 64 bit, and on the i7 laptop, which is definatly 64 bit (as it has 8G), but here again, I doubt it has a dedicated grahic card, most laptops have specifically designed embedded grahics solutions to save power and cost. So again it may work for you as well.

To rule out crossfire issues (the AMD equivalent for NVIDEA SLI), I disabled crossfire, but it still crashes my PD11 on that one filter.
Very easy to reproduce: start PD11 (so you are in a new/default project, make sure you are 16/9, drag the default nature.mpg from cyberlink to the timeline and drop the effect "continuous shooting" on it.
As I am Belgian, we use PAL here, but that is possibly not relevant (I hope).

I have the same problem with the "continous shooting filter".
This one crashes PD11 if I have GPU HW enabled. I suppose because this filter is using GPU HW acceleration as indicated in the pictogram of the filter.
I do not have nvidea, but ATI (now AMD) 2 x 5850 videocards in crossfire mode supporting openCL (and openGL)
I tried many videodrivers latest official 13.1 and beta 13.3
I have tried a few other GPU accelarated effects and they seem to work fine. Have not tried them all, hovever the "continous shooting filter" is probably NOK as it also always crashes my PD11 (ultra).
os: win 7 (64 bit), i7 930 processor, 6GB ram
Cyberlink should fix this.
Anyway I am glad I am not alone with this issue, as it rules out bad setup or drivers