Windows 10 - video player hangs and/or crashes (Page 3 of 3)

It seems only 64 bit SVP crash on my system. Tried 32 bit, no crash at all.

WORKS

Will give it a try.

Has this been resolved or still up in the air for the fix ?

I also had an annoying instant crash on startup with MPC-HC and SVP4 on win10. Turns out it was because of F-Secure SAFE's DeepGuard so I turned that off and the crashing stopped.

I'm not sure if it was really related to SVP at all, but it first started after I updated something with the SVP utility. I suppose someone else could have the same problem so there it is.

I'm on windows 10 64 bit with latest drivers for nvidia gtx 980. I'm using the latest Stereoscopic player 3d with the NVIDIA StereoPlayer.cst file replaced.
Unfortunately svp crashes every 5-10 minutes.  I can't purchase a license if it crashes like this. For those 5-10 minutes it works beautifully.

I tried turning off GPU acceleration so it just uses my i7-2600k, but it still crashes.  I tried doing the performance test and it still crashes.

It's always the same problem:

22:33:14.970 I]: Playback [280102]: full screen mode activated
22:38:23.407 I]: FFDShow: remove instance [280102]
22:38:23.407 I]: Playback [280102]: disabled while video is playing
22:38:23.808 I]: Playback [280102]: deleted

22:22:34.852 I]: Playback [8b03aa]: full screen mode activated
22:29:06.904 I]: FFDShow: remove instance [8b03aa]
22:29:06.904 I]: Playback [8b03aa]: disabled while video is playing
22:29:07.307 I]: Playback [8b03aa]: deleted

(EDIT)
OKAY, I think I figured it out.

I re-installed the latest version of ffdshow here: https://sourceforge.net/projects/ffdsho … p_redirect

Stereoscopic 3d player has not crashed yet, this is good.

Hi,
Today, I did the update for the last madvr codec through svp4 pro and since then when watching a video with mpc-hc, my gpu fans start ramping up to full speed and the only way I can stop them is to turn down my computer. The first time it happened was while watching a video and at about the tenth minute it started doing that. I reloaded the video and about the same time mpc-hc crashed. I was using the nvidia drivers geforce 390.65 nvidia drivers and went back to the 388.71 (I'm still on them) using ddu as always to see if this was the issue but it is not. I don't have this problem watching anything without svp running. So it is the svp update who created this issue. I tried the online downloader version and the offline version too. Same problem. I also downloaded madvr from their own website (the lastest and the second to last version of madvr) with no success. I also downloaded the last known ffdshow standalone version, no success either. I'm running W10-Pro 64bits (I reinstalled everything everytime I tried the solutions above to fix the issue).

I know, I oc'ed my gc a year ago using afterburner and didn't have any problem with it. It didn't ramp up like this before the svp update I made yesterday. I didn't change anything on my sytem except doing this update. The override with the last afterburner don't change a thing. I cleaned my pc today to see if it was dirt but the card wasn't even dirty and it does the same thing as before the cleaning. I thought my psu had died but it's working well still. I'm looking it up with hwinfo64 and all voltages seems to be ok. I don't know what's happening.

I finally found the problem. It was madvr all along. Things have changed in the last version of it which made my gpu go nuts. I tried resetting madvr settings to default and it worked. No problem since then I will need to rework some new settings that don't r*pe the gpu in the near future. Hope that helps someone.

Sorry for necroing this thread but I am commenting to confirm that Nvidia CUVID still is unusable on Windows 10 at the time of my reply (15-10-2019 Australian date).  If I have Nvidia CUVID set in the LAV internal Decoder I get a black screen and sound when the video plays followed by a full crash of Media Player Classic (Both the HC and BE variants), in both 23bit and 64bit iterations.   The only way to go on Windows 10 is to have DXVA2 (Copy-back) set and to point it to the GPU for GPU acceleration.  Since this has clearly been an issue since Windows 10's incep[tion in 2015 I doubt this will ever get rectified as Microsoft either doesn't care about addressing it or having the CUVID decoder not working somehow fits Microsoft's agenda somehow.