Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
clhelper.exe Fails Microsoft Driver Verification Tests
nullack [Avatar]
Member Joined: Dec 29, 2010 04:09 Messages: 139 Offline
[Post New]
In my quest to troubleshoot the problems Im having with BSOD's when attempting 3D bluray disc playback (whatever happened to buying commercial software and having it just work??!!), I decided to configure my HTPC in the MS driver verification mode, using the default check conditions, on all drivers. Upon rebooting, when I entered into the Cyberlink GUI and attempted to playback my 3D bluray disc, the driver verifier threw a driver verifier detection violation stop code

When I rebooted and did an analyse -v in the windows debugger to get the microsoft SDK to analyse the crash dump, it blames the process clhelper.exe which is a cyberlink powerdvd component

Why are you releasing software to production that doesnt even pass basic Microsoft testing tools?

The main problem is that NVIDIAs drivers are BSOD'ing when I try to run 3D mode processes in full screen and I had assumed it would be NVIDIAs drivers that would show up as at fault when in the device driver verification mode. However, it turns out its your software that Microsofts debuggers are saying is making illegal calls in kernel mode processes
stevek
Senior Contributor Location: Houston, Texas USA Joined: Jan 25, 2011 12:18 Messages: 4663 Offline
[Post New]
You have been around for awhile so you know that we (users) do not have (your) software. We just use it.



!) Di your have your antivirus active during the install. Sometimes they do block the proper registration of .dll.

2) Did/Do you use a registry cleaner and not look at what it was deleting?

3) Did you try older drivers?

4) Have you tried using VLC tp play the video? Dod you get a BSOD?

5) Did you try reinstalling the program?

6) Did you try using somethign like REVO Uninstaller Pro to remove all traces of the program, reboot, turn off your antivirus, instell the program and then reboot?



Sometimes we looki at details without looking at the big picture. You said you have had BSOD so I know that you are doing detailed troubleshooting and running into issues. Sometimes we don't see the forest for the trees.

If there were a BUG in the program, there would be a lot more conplaints the same as yours about the program. Since there ar not, it appears that there is somethign in your set up - either computer or installation.

And of course, did you contact Cyberlink Tech support to help you. .
.
BoilerPlate: To posters who ask for help -- it is nice to thank the volunteers who try to answer your questions !
Anything I post unless stated with a reference is my personal opinion.
nullack [Avatar]
Member Joined: Dec 29, 2010 04:09 Messages: 139 Offline
[Post New]
Steve I respect that in the past youve been helpful to other topics on the Cyberlink forum. I'm sorry but in this case, your clearly not across what the issues are, and the questions your asking are nonsense. For a proper discussion, you need to be across stuff like


  • X86 and X64 CPU architecture, specifically ring 0 kernel mode and ring 3 user modes, how the modes are different from each other

  • MS Windows architecture, how they have implemented CPU modes in their operating system etcetc

  • What debugging tools like driver verifier from MS does, how it is used, what it means


Ignorance and superstition about irrelevant stuff with registry cleaners and antivirus etcetc wont make any effective contribution to this specific problem. The fact of the situation which your not understanding is that, in the special driver verification mode that checks ring 0 kernel mode processes for valid operation, the clhelper.exe cyberlink process is in fact making illegal calls and its due to programming errors from Cyberlink. The only fix is for Cyberlink to fix their code, and compile a new version, and test it properly before releasing it to production. Its got nothing to do with registry, with antivirus, reinstall the software or whatever else a layman might imagine up as the cause like you have. If your interested, theres nothing stopping you from learning about these things and trying it for yourself - its not elusive knowledge its just fundamentals of computer science and the x86/x64 Windows platform.

As to your claim about why others arent complaining about bugs in the software. There is a significant portion of the HTPC community who avoid PowerDVD because they consider it "bloated and buggy". And on 3D Bluray disc specifically, many fellow enthusiasts on HTPC community sites have suggested to forget about using PowerDVD for 3D playback because its going to be a big hassle and consume allot of time in troubleshooting to get it to work, theyve suggested using a cheap standard alone player which is about the cost of the PowerDVD15 software. Personally I've bought every version of PowerDVD since 10 and I'm a bit of a fan, even thought I really shouldnt be and probably should have cut my losses a long time ago given the lack of quality and ongoing bugs in their software. Anyway the reality is that PowerDVD remains the only real x86/x64 software that does bluray menu playback and thats why Ive stuck with it. To say that people arent annoyed with bugs in Powerdvd is simply untrue when you consider the content on HTPC enthusiast forums and blogs etcetc.
Powered by JForum 2.1.8 © JForum Team