I think it started from v12.12.2 beta ? now using v12.13
after turning on the machine dopus runs fine and opens on double click the desktop.
take to day, after using it for may be 20 mins I closed the open lister and went for lunch, returning around an hour later dopus will not open a lister either by double clicking on the desktop, by using the start menu icon and nothing happens when I either right or left click on the quick launch icon.
task manager shows both dopus and the dopus helper running.
the only way of getting dopus back is to restart my computer.
here I only get [15968] [15492] dopus: UpdateString would have previously invalided PIDL for "O:\" [15968] [15492] dopus: UpdateString would have previously invalided PIDL for "P:\"
after playing anno 1800 beta it doesn't work again but there is nothing else from dopus in debug view
Does 12.12.1 work OK for you, and the problem only start in 12.12.2?
Was the new test version working OK at first and only stopped after running Anno 1880? Could you describe how it goes wrong so we can be sure it's the same issue?
this time I started at system boot, killed dopus ran debug and used the .exe dopus ran as it should with no sightings in debug.
I just left the computer alone at 1.22pm and did other stuff all day, came back to the computer at 8.50pm.
Same as before happened, there's nothing showing in debug about dopus but I cannot use it.
According to task manager directory opus and directory opus helper application are running but I cannot get dopus to show its self.
I have tried opening dopus by using the start menu icon, double clicking on the desktop, double clicking the icon in the quick start menu, single click the quick launch icon and selecting open new lister but nothing happens and right click the desktop and select new lister.
The strange thing is I have it on another machine and it works as expected and not showing any problems like this one.
That one is using v12.12.4 beta I've not updated that one yet.
00000001 0.00000000 [15968] [15492] dopus: UpdateString would have previously invalided PIDL for "O:\"
00000002 0.00432380 [15968] [15492] dopus: UpdateString would have previously invalided PIDL for "P:\"
I've just had a different one ?
I just downloaded the latest adrenalin software from amd.com and tried to right click it to run as admin and got a requester open up
after clicking ok it saved it as win10-64bit-radeon-software-adrenalin-2019-edition-19.4.1-apr3.exe.txt on my desktop.
There is only one extra line in debug and I had that before I ran dopus.
00000001 0.00000000 [8740] [10592] dopus: UpdateString would have previously invalided PIDL for "O:\"
00000002 0.00405790 [8740] [10592] dopus: UpdateString would have previously invalided PIDL for "P:\"
00000003 32.41399384 [14616] Suspending
[I've move things back into this thread to make the two threads a bit easier to follow & come back to, although they may both turn out to be about the same issue. Not sure yet.]
That should only be on if you're trying to diagnose issues with incorrect or blank icons in context menus.
Could you try a creating a manually generated process dump when things are going wrong? That will help us see if it's the same type of problem as in the other thread, or something else, and may help us solve what's going wrong.
Is there something.on your system that would be frequently renaming disks or changing their icons? Or are those removable drives or network drives which are changing state?
Please make the dump file I mentioned earlier. That could point to where the problem is without having to guess.
All 6 of those crashes appear to be caused by this component:
G:\Programs\Video\PlayClaw 6\playclawhook64.dll
That looks like it's part of a screen recording tool.
Try uninstalling that and see if the problem goes away. If it does, it was most likely the cause and you'll probably need to contact the authors of it. If you still have the problem with it uninstalled, please send any new dumps and we can analyze them.
[I've updated the thread title to help anyone else with the same problem.]
the oldest minidump I have is dated the 8th april, see attached, is it playclaw6 making it crash in that one ?dopus.20190408.115620.zip (19.8 KB)
the latest playclaw6 update I have is dated the 9th april, I'm trying work out which version it is crashing it.
It'd be good if they actually fixed it rather than make people manually add processes they crash to a blacklist after spending a week working out what the cause is. But we have no control over what they do, other than potentially showing a warning if we detect their DLL in our process.
But we have no control over what they do, other than potentially showing a warning if we detect their DLL in our process.