Faulting module MFC80.DLL, version 8.0.50727.1833
Moderator: lata
If you're getting the reference to MFC80.DLL 8.0.50727.1833, then I guess you've installed either of Visual Studio 2008 or SQL Server 2008 on your PC. Perhaps the DLLs are by now being shipped with some other applications? My thinking is that you may not be getting the same error as I am, as I could never get to the stage of shutting the app down. The MFC assemblies are core programming libraries, so not too surprising that another issue will show up as an MFC error.
As you'll see from the various postings, this isn't something that's easy to fix. Really, the only answer is to get a fix from Corel. If they can't provide it, then I'd be asking for a refund. If you do have Visual Studio or SQL Server 2008 installed, I'd be interested to know if uninstalling them does make the error go away. The trouble with the core Windows DLLs is that various applications depend on them. If an uninstaller sees that nothing else is using the DLLs, then it should let you remove them.
As you'll see from the various postings, this isn't something that's easy to fix. Really, the only answer is to get a fix from Corel. If they can't provide it, then I'd be asking for a refund. If you do have Visual Studio or SQL Server 2008 installed, I'd be interested to know if uninstalling them does make the error go away. The trouble with the core Windows DLLs is that various applications depend on them. If an uninstaller sees that nothing else is using the DLLs, then it should let you remove them.
I have tried three times to fix the WINDVD8 problem crash with the MFC application error. I have removed WINDVDE8, downloaded it again, downloaded the Microsoft "fix" and have been told by Corel customer support that it is a Microsoft error. Microsoft states it is a Corel error.
Corel also told me that WINDVD9 would not have the same error but various threads on this forum indicate there are MFC applicaiton errors.
Has Corel updated their software to fix the MFC error? If not, how is it fixed by doing a workaround that does not upset Windows Vista Home Premium 32 bit OS?
Corel also told me that WINDVD9 would not have the same error but various threads on this forum indicate there are MFC applicaiton errors.
Has Corel updated their software to fix the MFC error? If not, how is it fixed by doing a workaround that does not upset Windows Vista Home Premium 32 bit OS?
SPWHITING
I'm reasonably sure that Corel could do a release to fix this issue, especially as I was able to come up with a workaround on both Vista 32-bit and XP. However the good news is that Microsoft have released a "hotfix" for the DLLs that cause this issue. See the Knowledge Base article at http://support.microsoft.com/kb/961894. That article contains a link to the download page at http://code.msdn.microsoft.com/KB961894 ... aseId=2067. Make sure you get the correct language (ENU for English).
After carefully reading the warnings that this is a hotfix and not fully tested
install the package. WinDVD should no longer give the MFC error.
Serendipitously, I came upon this fix a couple of days ago after trying to update my ATI video card drivers. See topic "Updated VCREDIST to solve install issues" on the ATI Catalyst forum at http://forums.amd.com/game/categories.c ... forumid=11
My experience was that I needed to install vredist_x86.exe, even though I am running Vista 64-bit. This is required because WinDVD is a 32-bit application. The 64-bit hotfix vredist_x64.exe fixed my issue with the video driver. A reboot wasn't required. My WinDVD had been working fine on my new PC, but last weekend I added SQL Server 2008 and Visual Studio 2008. That killed WinDVD.
I hope this fixes things for you too.
After carefully reading the warnings that this is a hotfix and not fully tested
install the package. WinDVD should no longer give the MFC error.Serendipitously, I came upon this fix a couple of days ago after trying to update my ATI video card drivers. See topic "Updated VCREDIST to solve install issues" on the ATI Catalyst forum at http://forums.amd.com/game/categories.c ... forumid=11
My experience was that I needed to install vredist_x86.exe, even though I am running Vista 64-bit. This is required because WinDVD is a 32-bit application. The 64-bit hotfix vredist_x64.exe fixed my issue with the video driver. A reboot wasn't required. My WinDVD had been working fine on my new PC, but last weekend I added SQL Server 2008 and Visual Studio 2008. That killed WinDVD.
I hope this fixes things for you too.
@Lancea,
Thanks for the link but it did not eliminate the MFC error - it still occurs after about three minutes of playing a DVD on WINDVD8. I did not reinstall WINDVD8 after downloading the update from your link. I'll try uninstalling WINDVD8 and reinstalling it later and let you know if there is any change. Thanks for your help anyway.
Thanks for the link but it did not eliminate the MFC error - it still occurs after about three minutes of playing a DVD on WINDVD8. I did not reinstall WINDVD8 after downloading the update from your link. I'll try uninstalling WINDVD8 and reinstalling it later and let you know if there is any change. Thanks for your help anyway.
SPWHITING
Hello spwhiting. That's a shame. Looking back through this thread, I don't think you've ever confirmed your error is exactly the same as the one I refer to in the first posting. But it's clearly not since you can actually play a DVD. Have you looked in the Application Event Log, and at the "technical details" of the Microsoft error report (assuming that option is coming up)? Hopefully there will be a reference that's useful. The more detailed the error information the more likely you'll find a matching issue by doing an internet search. Good luck!
I installed theMS 8.0.50727.42 program, removed WINDVD8, reinstalled WINDVD8 (during the WINDVDV8 installation it asked to install the MS program and it installed 8.0.58299,so both MS programs are now available), rebooted and restarted WINDVD8. The MFC APPLICATION error appears after about 60 seconds of playing the DVD. I then removed MS 8.0.58299, rebooted and restarted WINDVD8 and the error appeared after about a minute of playing the DVD.
Windows Media Center will play the DVD just fine so I'll use that since I am not savy enough to get to the Application Log you mentioned.
Again, thanks for your help.
Pete
Windows Media Center will play the DVD just fine so I'll use that since I am not savy enough to get to the Application Log you mentioned.
Again, thanks for your help.
Pete
SPWHITING
Windows Media isn't too bad at all and it's true that you may never get a fix for this. After I'd bought 2 copies I wasn't about to be beaten
If you want to look at the Event Log, on Vista you just need to type "event" (without the quotes) in the Search box. Program "Event Viewer" will most likely be at the top of the results. Run it and select the "Windows Logs" folder on the left of the Viewer. Next, select "Application" and look for the events labelled with a red exclamation at the time it last crashed. The detail that is shown should have more detail than you've seen previously.
Unfortunately it's not easy to delete specific versions of DLLs on XP or Vista. They go into a special protected area called WinSxS. On the other hand, that feature is generally a good thing since it makes it much harder to accidentally kill an application.
The other thing on Vista that can be useful is the "Reliability and Performance Monitor". Again, just start typing "reliability" in the Search box and the program link will appear. Run it and select "Reliability Monitor".
If you want to look at the Event Log, on Vista you just need to type "event" (without the quotes) in the Search box. Program "Event Viewer" will most likely be at the top of the results. Run it and select the "Windows Logs" folder on the left of the Viewer. Next, select "Application" and look for the events labelled with a red exclamation at the time it last crashed. The detail that is shown should have more detail than you've seen previously.
Unfortunately it's not easy to delete specific versions of DLLs on XP or Vista. They go into a special protected area called WinSxS. On the other hand, that feature is generally a good thing since it makes it much harder to accidentally kill an application.
The other thing on Vista that can be useful is the "Reliability and Performance Monitor". Again, just start typing "reliability" in the Search box and the program link will appear. Run it and select "Reliability Monitor".
Events showed about eight of these:
Faulting application WinDVD.exe, version 8.0.6.109, time stamp 0x45ff706f, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000005, fault offset 0x000659c3, process id 0x1e2c, application start time 0x01c9871900b79f0d.
Makes no sense to me but maybe Intervideo can use it to fix WinDVD8.
Windows Media Center will work, but it is not as useful as WINDVD8 used to be before it died. I might ask for a refund since WINDVD8 is useless.
Faulting application WinDVD.exe, version 8.0.6.109, time stamp 0x45ff706f, faulting module ntdll.dll, version 6.0.6001.18000, time stamp 0x4791a7a6, exception code 0xc0000005, fault offset 0x000659c3, process id 0x1e2c, application start time 0x01c9871900b79f0d.
Makes no sense to me but maybe Intervideo can use it to fix WinDVD8.
Windows Media Center will work, but it is not as useful as WINDVD8 used to be before it died. I might ask for a refund since WINDVD8 is useless.
SPWHITING
NTDLL.DLL is used by pretty much every application so it is probably a funadamental incompatibility of your "system" with WinDVD 8. I have exactly the same version of the DLL as you. Certainly having that extra information would be very helpful - especially if other people get the exact same error. But going from my experience with the MFC issue, you'd be unlikely to get anything from Support for an older version of WinDVD.
I've looked back through your earlier posts and see you've never tried version 9 because you saw it also had MFC issues. So far as I know the MFC issue is fixed by the patch I mentioned earlier. There may well be other MFC issues (in which case the Event Log should show something different), but this one at least is resolved by the hotfix. Therefore I'd definitely give the trial of WinDVD 9 a try. If you don't have the patch it will crash long before you can start playing a DVD. That's not to say it will never crash
Good luck.
I've looked back through your earlier posts and see you've never tried version 9 because you saw it also had MFC issues. So far as I know the MFC issue is fixed by the patch I mentioned earlier. There may well be other MFC issues (in which case the Event Log should show something different), but this one at least is resolved by the hotfix. Therefore I'd definitely give the trial of WinDVD 9 a try. If you don't have the patch it will crash long before you can start playing a DVD. That's not to say it will never crash
Good luck.