GP SoftwareTwitter
Opus FAQsManualCommandsObjects

Opus 12.13 crashing, apparently due to PlayClawHook64.dll

#1

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.

any ideas what might be causing this ?

Mike.

New Version (12.13) Crashes upon Start, even after reinstall
#2

It's most likely this issue which we're investigating at the moment:

Installers for 12.12 and 12.12.1 (which don't cause the problem for people who were seeing it) are here:

We should have a fix soon, and a new test version sooner if you'd like to try it. They'll be posted in that thread.

#3

yes please, I'll keep my eye open.

#4

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

New Version (12.13) Crashes upon Start, even after reinstall
#5

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?

#6

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.

#7

So you're not even seeing the UpdateString would have... lines that you got before, while still using the test version?

Could you generate a process dump when Opus is in that state and send it to us? (Instructions here: Crash dumps for bug reports )

#8

yes sorry, I do get

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:\"

but as I said nothing else mentioning dopus

#9

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
Capture
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

not much use for this problem I know.

#10

[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's because this option has been turned on:

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.

#11

found it.

Line 1: 00000001	0.00000000	[15052] [9140] dopus: UpdateString would have previously invalided PIDL for "O:\" 	
	Line 2: 00000002	0.00377260	[15052] [9140] dopus: UpdateString would have previously invalided PIDL for "P:\" 	
	Line 3: 00000003	2.08280110	[15052] [12776] dopus: ShellChange: 000001DEDFB47A00, 3	
	Line 4: 00000004	2.08284235	[15052] [12776] dopus: ShellChange: dwEvent = 20000	
	Line 5: 00000005	2.08294892	[15052] [12776] dopus: ShellChange: rename disk U:\	
	Line 6: 00000006	2.08322525	[15052] [12776] dopus: ShellChange: 000001DEDFB478E0, 3	
	Line 7: 00000007	2.08325958	[15052] [12776] dopus: ShellChange: dwEvent = 20000	
	Line 8: 00000008	2.08329248	[15052] [12776] dopus: ShellChange: rename disk W:\	
	Line 9: 00000009	2.08339715	[15052] [12776] dopus: ShellChange: 000001DEDFB47BE0, 3	
	Line 10: 00000010	2.08342957	[15052] [12776] dopus: ShellChange: dwEvent = 20000	
	Line 11: 00000011	2.08350229	[15052] [12776] dopus: ShellChange: rename disk X:\	
	Line 12: 00000012	2.08358288	[15052] [12776] dopus: ShellChange: 000001DEDFB474C0, 3	
	Line 13: 00000013	2.08360815	[15052] [12776] dopus: ShellChange: dwEvent = 20000	
	Line 14: 00000014	2.08364987	[15052] [12776] dopus: ShellChange: rename disk Y:\	
	Line 15: 00000015	2.08435273	[15052] [12776] dopus: ShellChange: 000001DEDFB47940, 3	
	Line 16: 00000016	2.08437800	[15052] [12776] dopus: ShellChange: dwEvent = 20000	
	Line 17: 00000017	2.08443666	[15052] [12776] dopus: ShellChange: rename disk Z:\	
	Line 683: 00000683	221.08822632	[15052] [12776] dopus: ShellChange: 000001DEDE995280, 3	
	Line 684: 00000684	221.08830261	[15052] [12776] dopus: ShellChange: dwEvent = 40000	
	Line 744: 00000744	356.88552856	[3004] [10728] dopus: UpdateString would have previously invalided PIDL for "O:\" 	
	Line 745: 00000745	356.88989258	[3004] [10728] dopus: UpdateString would have previously invalided PIDL for "P:\" 	
	Line 746: 00000746	359.10949707	[3004] [15284] dopus: ShellChange: 000001A140BB8920, 3	
	Line 747: 00000747	359.10958862	[3004] [15284] dopus: ShellChange: dwEvent = 20000	
	Line 748: 00000748	359.10980225	[3004] [15284] dopus: ShellChange: rename disk U:\	
	Line 749: 00000749	359.11032104	[3004] [15284] dopus: ShellChange: 000001A140BB8B90, 3	
	Line 750: 00000750	359.11038208	[3004] [15284] dopus: ShellChange: dwEvent = 20000	
	Line 751: 00000751	359.11041260	[3004] [15284] dopus: ShellChange: rename disk Y:\	
	Line 752: 00000752	359.11056519	[3004] [15284] dopus: ShellChange: 000001A13F42E400, 3	
	Line 753: 00000753	359.11059570	[3004] [15284] dopus: ShellChange: dwEvent = 20000	
	Line 754: 00000754	359.11062622	[3004] [15284] dopus: ShellChange: rename disk W:\	
	Line 755: 00000755	359.11087036	[3004] [15284] dopus: ShellChange: 000001A13F42DB30, 3	
	Line 756: 00000756	359.11090088	[3004] [15284] dopus: ShellChange: dwEvent = 20000	
	Line 757: 00000757	359.11093140	[3004] [15284] dopus: ShellChange: rename disk X:\	
	Line 758: 00000758	359.11114502	[3004] [15284] dopus: ShellChange: 000001A13F42E670, 3	
	Line 759: 00000759	359.11120605	[3004] [15284] dopus: ShellChange: dwEvent = 20000	
	Line 760: 00000760	359.11120605	[3004] [15284] dopus: ShellChange: rename disk Z:\	
	Line 761: 00000761	374.60687256	[3376] [9020] dopus: UpdateString would have previously invalided PIDL for "O:\" 	
	Line 762: 00000762	374.61035156	[3376] [9020] dopus: UpdateString would have previously invalided PIDL for "P:\" 	
	Line 763: 00000763	376.60949707	[3376] [9064] dopus: ShellChange: 000001A0C89E7B90, 3	
	Line 764: 00000764	376.60952759	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 765: 00000765	376.60961914	[3376] [9064] dopus: ShellChange: rename disk U:\	
	Line 766: 00000766	376.60983276	[3376] [9064] dopus: ShellChange: 000001A0C89E7860, 3	
	Line 767: 00000767	376.60989380	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 768: 00000768	376.60992432	[3376] [9064] dopus: ShellChange: rename disk W:\	
	Line 769: 00000769	376.61010742	[3376] [9064] dopus: ShellChange: 000001A0C89E7B60, 3	
	Line 770: 00000770	376.61013794	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 771: 00000771	376.61019897	[3376] [9064] dopus: ShellChange: rename disk X:\	
	Line 772: 00000772	376.61044312	[3376] [9064] dopus: ShellChange: 000001A0C89E79B0, 3	
	Line 773: 00000773	376.61053467	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 774: 00000774	376.61056519	[3376] [9064] dopus: ShellChange: rename disk Y:\	
	Line 775: 00000775	376.61077881	[3376] [9064] dopus: ShellChange: 000001A0C89E7890, 3	
	Line 776: 00000776	376.61080933	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 777: 00000777	376.61087036	[3376] [9064] dopus: ShellChange: rename disk Z:\	
	Line 978: 00000978	1121.25109863	[3376] [9064] dopus: ShellChange: 000001A0C8892D40, 3	
	Line 979: 00000979	1121.25109863	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 1159: 00001159	1718.48193359	[3376] [9064] dopus: ShellChange: 000001A0C8892B00, 3	
	Line 1160: 00001160	1718.48193359	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 1766: 00001766	2021.24304199	[3376] [9064] dopus: ShellChange: 000001A0C8A16E40, 3	
	Line 1767: 00001767	2021.24304199	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 1943: 00001943	3537.72949219	[3376] [9064] dopus: ShellChange: 000001A0C8A16E10, 3	
	Line 1947: 00001947	3552.81884766	[3376] [9064] dopus: ShellChange: 000001A0C77A8350, 3	
	Line 1948: 00001948	3553.38037109	[3376] [9064] dopus: ShellChange: 000001A0C77A7FC0, 3	
	Line 2272: 00002272	3620.27246094	[3376] [9064] dopus: ShellChange: 000001A0C77A7C60, 3	
	Line 2273: 00002273	3620.27246094	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 2793: 00002793	3630.64941406	[3376] [9064] dopus: ShellChange: 000001A0C77A8380, 3	
	Line 2818: 00002818	3750.45654297	[3376] [14052] dopus: UpdateString would have previously invalided PIDL for "O:\" 	
	Line 2819: 00002819	3750.46069336	[3376] [14052] dopus: UpdateString would have previously invalided PIDL for "P:\" 	
	Line 2824: 00002824	3821.22485352	[3376] [9064] dopus: ShellChange: 000001A0C8855810, 3	
	Line 2825: 00002825	3821.22485352	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 3723: 00003723	4723.25195313	[3376] [9064] dopus: ShellChange: 000001A0C8C7B700, 3	
	Line 3724: 00003724	4723.25195313	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 3937: 00003937	5621.29101563	[3376] [9064] dopus: ShellChange: 000001A0C8C7B880, 3	
	Line 3938: 00003938	5621.29101563	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 4101: 00004101	6916.26953125	[3376] [9064] dopus: ShellChange: 000001A0C77A7FC0, 3	
	Line 4106: 00004106	6931.41113281	[3376] [9064] dopus: ShellChange: 000001A0C77A8200, 3	
	Line 4107: 00004107	6931.97021484	[3376] [9064] dopus: ShellChange: 000001A0C77A7E10, 3	
	Line 4445: 00004445	13594.83496094	[3376] [9064] dopus: ShellChange: 000001A0C880D290, 3	
	Line 4446: 00004446	13594.85937500	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 5835: 00005835	13605.87109375	[3376] [9064] dopus: ShellChange: 000001A0C880DAD0, 3	
	Line 5910: 00005910	13721.14746094	[3376] [9064] dopus: ShellChange: 000001A0C880D5C0, 3	
	Line 5911: 00005911	13721.14746094	[3376] [9064] dopus: ShellChange: dwEvent = 40000	
	Line 5912: 00005912	13734.03417969	[3376] [9064] dopus: ShellChange: 000001A0C880D920, 3	
	Line 5913: 00005913	13734.03417969	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 5914: 00005914	13734.03710938	[3376] [9064] dopus: ShellChange: rename disk U:\	
	Line 5915: 00005915	13734.03808594	[3376] [9064] dopus: ShellChange: 000001A0C880D9E0, 3	
	Line 5916: 00005916	13734.03906250	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 5917: 00005917	13734.04003906	[3376] [9064] dopus: ShellChange: rename disk W:\	
	Line 5918: 00005918	13734.04003906	[3376] [9064] dopus: ShellChange: 000001A0C880D6B0, 3	
	Line 5919: 00005919	13734.04199219	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 5920: 00005920	13734.04296875	[3376] [9064] dopus: ShellChange: rename disk X:\	
	Line 5921: 00005921	13734.04296875	[3376] [9064] dopus: ShellChange: 000001A0C880D260, 3	
	Line 5922: 00005922	13734.04492188	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 5923: 00005923	13734.04492188	[3376] [9064] dopus: ShellChange: rename disk Y:\	
	Line 5924: 00005924	13734.04589844	[3376] [9064] dopus: ShellChange: 000001A0C880D2F0, 3	
	Line 5925: 00005925	13734.04687500	[3376] [9064] dopus: ShellChange: dwEvent = 20000	
	Line 5926: 00005926	13734.04785156	[3376] [9064] dopus: ShellChange: rename disk Z:\	

now it wont open any listers again.
I just left it alone for a couple of hours.

#12

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.

#13

here is the one from today, one from yesterday and three from the 13th
DOpus.Minidumps.zip (116.2 KB)

#14

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.]

#15

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.

#16

Yes, that was the same component.

#17

thanks for the confirmation, I've emailed them with their logs to see if they can fix it.

#18

they have replied

Just add its process in the playclaw black list.

changed it as advised in playclaw6 settings.
I'll give it a go and see what happens.

#19

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. :slight_smile: But we have no control over what they do, other than potentially showing a warning if we detect their DLL in our process.

#20

thanks for the help sorting it out :smiley:

1 Like