On exiting VS 10+, I often get herdocdll.dll signature err

[mcope1961]

I'm using the Video Edit Profile. I have very few surprise shutdowns. At least half the time or more, when I intentionally exit VS 10+, I get a signature error related back to herdocdll.dll.

I've searched the forum and I've seen one other member say they were getting the same thing on, I think, as many 95% of his exits. I didn't see a solution. Is there a secret to avoid this ungraceful shutdown?

[Terry Stetler]

That's a VideoStudio file alright, but perhaps it's corrupted. It's also possible that it's located on a bad sector of the hard drive.

First thing I'd do is a Repair installation. You'll get this option when calling up the uninstaller from Add/Remove Software in the Control Panel. You'll need the program CD.

Next run a virus check.

Finally I'd do a backup of the system disc then schedule a disc error check by right-clicking the C: drive in Explorer and selecting Properties. In the Tools tab there is an option for Error Checking. Set it to repair etc. and reboot.

[mcope1961]

So far so good with 2 successful exits after some non-trivial work. I'll report my progress as I do more work later this week.

I did lose my created folders and thumbnails in the Library Manager. I assume the repair installation wiped those out for good. I also lost at least one effect, the Album, but I reinstalled the content pack and that seems to be working again.

[mcope1961]

After following the recommendations given above, I'm still getting an error on shutdown, sometimes. One time I got an error from ulppmgr.dll and another time it was the previously reported herdocdll.dll error. Other ideas?

[susantexas1]

Hi, Fellow VS User,

I, too, was having constant appcompat.txt error signature shut downs while editing in VS10+ and on exit, etc. with the reports referencing the faulting application as video studio 10, and files like herdocdll.dll or ulppmgr.dll or ntdll.dll.

After weeks of frustrating research, trial and error fix attempts and foul language at my PC (tee hee) - all the while under a video deadline so puttering along: work awhile - crash - cry, work awhile - crash - scream, work awhile - crash - hours of MORE research....you get the picture......I may have FINALLY found the (naturally) quite simple resolution!

I found mention of the Microsoft Decoder Check Tool on this forum (thank you, guys!) so downloaded it (it's free) and found one PowerDVD entry which the tool suggested I make the Preferred Decoder for Windows Media 10, and two Ulead decoder entries. I closed the DECCHECK program, went to my Program Files and started the Cyberlink PowerDVD program, clicked on Online Update and let it run. Once completed and rebooted, I then re-ran the DECCHECK program and selected the Cyberlink decoder as the Preferred.

Today is my first day back on VS10+, and I'm now over an hour into editing and guess what! Not one crash (thus far). This one little fix has made my life bright and video editing FUN again! I'm so grateful....I feel like posting the news everywhere, something like: DOES VIDEO STUDIO CONTINUALLY CRASH ON YOU? TRY THIS!

Anyway, obviously I'll be devastated if the crashing begins again, but at least I've had this one hour so far of the pure bliss of just working along, uninterrupted, tee hee

Perhaps this will be of some help to you, too. Good luck!

[mcope1961]

Well, the ungraceful shutdowns appear to have stopped. Before I saw the previous post, I turned my paging off. I have 4GB of memory, so that seemed pretty safe. I thought that was working, but then I started to have problems again on exit, now and then. I ran the Microsoft Decoder Check Tool, found that none of my codecs were "OK" with Microsoft, even with the latest updates. I selected my CinePlayer one, anyway, as my default. Since then I have not had any problems, but I'm keeping my fingers crossed.

When I get my courage up, I'll turn the paging back on.

Thanks for the suggestion.

[mcope1961]

Just an update, the two ideas did not work. I still probably get the herdocdll.dll signature error on about 50% of my shutdowns. I guess it's something I'll have to live with.