Evo n610c WinDVD CPU utilization

[RickH_2]

When I launch WinDVD (SP23454) on my Evo n610c it runs well with WinDVD consuming about 40% of my CPU according to Task Manager. However after about an hour the WinDVD CPU consumption shoots up to 80+% which brings my total CPU utilization to 100%. This causes the movie to lag and flutter. What is causing this WinDVD CPU utilization spike and what can I do to fix it?

[Roger Faucher]

Rick:

You might try a free trial of a newer version from here: http://www.intervideo.com/jsp/Downloads.jsp

I would make sure my Windows Updates are all current, especially DirectX (see http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&DisplayLang=en
Keep in mind that DirectX updates cannot be uninstalled, so try creating a System Restore point before you begin.

Make a great day!

Roger

[RickH_2]

Roger,

Thanks. My company includes WinDVD as part of our base notebook image. I have gone out and downloaded two more current versions of WinDVD running on XP from our internal software site with the latest being from January 2007. And the problem continues. I have had my Evo n610c for about four years and the problem has just started in the last 2 months. Any other thoughts?

[Roger Faucher]

Rick:

Are you using an internal DVD drive or external (USB, for instance)?

Try this article:
http://support.microsoft.com/kb/308012/en-us

Hope that helps.

Roger

[RickH_2]

Roger,

I reviewed the portion of the article regarding "choppy video". My controllers are set at the right DMA settings. The part that is confusing to me is that the WinDVD application runs well when launched using about 40% of the CPU according to Task Manager. But after an hour or so the WinDVD applicatin jumps up to consume over 80% of my CPU which casues my total utilization to top out at 100% and causes the movie to become choppy. Any thoughts on why the WINDVD application itself increase CPU utilization over time?

[Roger Faucher]

Rick:

The only thing that comes to mind is that perhaps a resource is running low, such as real or virtual memory. I would make sure there's plenty of free space on the hard disk drive(s), defrag the hard drive, and set the paging file to 2x real memory.

Other than that, I'm drawing a blank.

Sorry.

Make a great day!

Roger