Nvidia drivers 551.23

[temis01]

Hi strange behavior since driver 551.23 just installed as usual (clean install with DDU)

• mpv version : 0.37 + mpv v3 20240128 nightly = same behavior = won't start with windows event 1000

• Windows Version 11 (22631.3085)

• Source of the mpv binary : shinchiro

• GPU model RTX 3050

• Nvidia driver 551.23

my mpv video settings : Working settings before nvidia drivers 551.23 : (previous nvidia drivers installed 546.65)

---

profile=gpu-hq vo=gpu-next hwdec=vulkan # hwdec=vulkan or vulkan-copy work with version 0.36 or later

gpu-api=vulkan # MPV default is d3d11, vulkan is the new nvidia video server gpu-context=winvk vf=format=vulkan # Optional to use vulkan api

contrast=5 brightness=-2 gamma=10 saturation=-5

glsl-shader="C:/Program Files/MPV/shaders/noise_static_luma.hook" glsl-shader="C:/Program Files/MPV/shaders/noise_static_chroma.hook"

scale=ewa_lanczossharp dscale=mitchell cscale=spline64

---

Expected behavior

start mpv and/or play video

Actual behavior

mpv fails to start or play video with windows event ID 1000

Edit : feb 1st 2024 : I finally ended up reinstalling nvidia 551.23 drivers mpv can play XviD & XviD videos without problem ! Still no go for AVC or HEVC

Workaround (not really a workaround : MPV falls back to software decoding) I had to comment out the following settings to get mpv to start again with nvidia 551.23 drivers I have tried every vulkan parameters combination : only commenting out these 2 would let mpv play a video I use mostly AVC + HEVC encoded files

• gpu-api=vulkan

• gpu-context=winvk

Log file

mpv.log

[lvqcl]

https://github.com/mpv-player/mpv/issues/11739#issuecomment-1909947448

[llyyr]

#11739 (comment)

This issue has nothing to do with vulkan hardware decoding, not sure why you'd link that.

This is an Nvidia bug so you should email(?) them

[llyyr]

mpv.log

This log file actually has no errors, you need to provide logs with --no-config where mpv does actually fail

[temis01]

#11739 (comment)

This issue has nothing to do with vulkan hardware decoding, not sure why you'd link that.

This is an Nvidia bug so you should email(?) them

I am not linking anything to anything I just tried to find a workaround to the problem I ran into after installing 551,23 drivers. I didn’t find the other thread cause I searched 551.23 instead of 550 driver.

If it’s a known bug, good for us, nvidia will fix it.

[temis01]

mpv.log

This log file actually has no errors, you need to provide logs with --no-config where mpv does actually fail

Since the 550 new drivers are the culprit providing a —no-config log is now irrelevant !

[netExtra]

This does not seem to be an mpv or Nvidia issue.

On Windows 10 with my own mpv build running Nvidia 551.23 driver and:

hwdec=vulkan gpu-api=vulkan gpu-context=winvk

I am able to play mkv & mp4 files with no errors reported on the mpv console log or debug.

[netExtra]

[netExtra]

my own mpv build

Which ffmpeg is your build using?

Good question. I'm not using the main branch ffmpeg. Instead I am using https://github.com/mitzsch/FFmpeg/tree/master-3 which is a little behind the latest ffmpeg build and has its own set of commits.

[Raza-0007]

@temis01, was your issue resolved? I upgraded to Nvidia driver 551.23 last night, and I don't have an issues playing any file with gpu-api=vulkan

~Raza

[temis01]

@temis01, was your issue resolved? I upgraded to Nvidia driver 551.23 last night, and I don't have an issues playing any file with gpu-api=vulkan

~Raza

no changes yet ! I am on shinshiro 0.37 or nightly latest.

what version of mpv are you using ?

[Raza-0007]

I am also on mpv 0.37, the January 24th release, from Zhongfly as Shinchiro's was not available on that day, but they are essentially the same. And since there has not been a lot of changes in mpv since then, so I doubt the latest release would make any difference.

Try reinstalling the Nvidia driver, this time instead of using DDU just choose the "clean installation" option from within the driver exe.

~Raza

[temis01]

I did reinstall drivers 551.23 using clean install (which I always use) = same problem. I tried using Zhongfly 20240124 + 20240131 nightlies = same problem

I removed drivers 551.23 then reinstalled previous drivers 546.65.

==>> any and every version of mpv work just fine with all vulkan settings ON ! (shinshiro + Zhongfly : official or nightlies)

[temis01]

Edit : feb 1st 2024 : I finally ended up reinstalling nvidia 551.23 drivers mpv can play XviD & XviD videos without problem ! Still no go for mkv or mp4

[netExtra]

Edit : feb 1st 2024 : I finally ended up reinstalling nvidia 551.23 drivers mpv can play XviD & XviD videos without problem ! Still no go for mkv or mp4

Have you have installed any external codec packs or lav filters?

[temis01]

Edit : feb 1st 2024 : I finally ended up reinstalling nvidia 551.23 drivers mpv can play XviD & XviD videos without problem ! Still no go for mkv or mp4

Have you have installed any external codec packs or lav filters?

None ! I mean no codec pack installed as such.

I have VLC, potplayer, MPC-BE also installed. Maybe one or more of them installed some specific codecs. I am not sure.

About lav filters I noticed that a explorer addon named QuickLook installed version .72

[netExtra]

Have you have installed any external codec packs or lav filters?

None ! I mean no codec pack installed as such.

I have VLC, potplayer, MPC-BE also installed. Maybe one or more of them installed some specific codecs. I am not sure.

About lav filters I noticed that a explorer addon named QuickLook installed version .72

All those players are pretty self contained and I use a couple of them myself and I don't have the Vulkan issue. I've never heard of QuickLook but after Googling, it might be worth you uninstalling it and rebooting to see if that helps.

[Raza-0007]

I did reinstall drivers 551.23 using clean install (which I always use) = same problem. I tried using Zhongfly 20240124 + 20240131 nightlies = same problem

Unfortunately, I cannot reproduce this issue on my system with 551.23 (Win 11, GTX 1070). All files are playing fine here. There must be something on your system other than mpv or Nvidia driver that is causing the issue.

I am not an expert at deciphering mpv logs, but the log you posted does not seem to be using gpu-api=vulkan. It is using Direct3D11. Here are a few lines from your log

[ 0.050][v][vo/gpu-next] Probing for best GPU context. [ 0.050][v][vo/gpu-next/d3d11] Initializing GPU context 'd3d11' [ 0.168][v][vo/gpu-next/d3d11] Using Direct3D 11 feature level 12_1 [ 0.168][v][vo/gpu-next/d3d11] Device Name: NVIDIA GeForce RTX 3050

Either you accidentally grabbed a different log or your custom config is being ignored.

~Raza

[netExtra]

The backtrace does suggest an issue with ffmpeg as suggested before. Looking at your ffmpeg library versions I see that your ffmpeg version is later than the mpv upstream version. My build and Shinchiro are almost identical. You have a later libavutil library.

[temis01]

Have you have installed any external codec packs or lav filters?

None ! I mean no codec pack installed as such. I have VLC, potplayer, MPC-BE also installed. Maybe one or more of them installed some specific codecs. I am not sure. About lav filters I noticed that a explorer addon named QuickLook installed version .72

All those players are pretty self contained and I use a couple of them myself and I don't have the Vulkan issue. I've never heard of QuickLook but after Googling, it might be worth you uninstalling it and rebooting to see if that helps.

Uninstalled QuickLook then check that lav filters were gone + reboot = no changes

[temis01]

The backtrace does suggest an issue with ffmpeg as suggested before. Looking at your ffmpeg library versions I see that your ffmpeg version is later than the mpv upstream version. My build and Shinchiro are almost identical. You have a later libavutil library. The builds are shown below.

Your mpv build: [ 0.004][v][cplayer] built on Feb 1 2024 07:37:02 [ 0.004][v][cplayer] libplacebo version: v6.338.0-70-gc320f61-dirty [ 0.004][v][cplayer] FFmpeg version: N-113493-ga678566ab [ 0.004][v][cplayer] FFmpeg library versions: [ 0.004][v][cplayer] libavutil 58.37.101 [ 0.004][v][cplayer] libavcodec 60.38.100 [ 0.004][v][cplayer] libavformat 60.20.100 [ 0.004][v][cplayer] libswscale 7.6.100 [ 0.004][v][cplayer] libavfilter 9.17.100 [ 0.004][v][cplayer] libswresample 4.13.100

My mpv build: built on Jan 28 2024 13:09:49 libplacebo version: v6.338.0-64-g34e019b-dirty FFmpeg version: git-2024-01-26-4f8838eaf FFmpeg library versions: libavutil 58.36.101 libavcodec 60.38.100 libavformat 60.20.100 libswscale 7.6.100 libavfilter 9.17.100 libswresample 4.13.100

Shinchiro v3 mpv build: built on Jan 28 2024 00:11:42 libplacebo version: v6.338.0-64-g34e019b-dirty FFmpeg version: N-113434-g0c517fcbe FFmpeg library versions: libavutil 58.36.101 libavcodec 60.38.100 libavformat 60.20.100 libswscale 7.6.100 libavfilter 9.17.100 libswresample 4.13.100

Shinchiro gcc mpv build: mpv v0.37.0-234-g57d68262 Copyright © 2000-2024 mpv/MPlayer/mplayer2 projects built on Feb 1 2024 00:36:20 libplacebo version: v6.338.0-70-gc320f61-dirty FFmpeg version: N-113492-gfa469545b FFmpeg library versions: libavutil 58.36.101 libavcodec 60.38.100 libavformat 60.20.100 libswscale 7.6.100 libavfilter 9.17.100 libswresample 4.13.100

I don't think these line come from my mpv.log : the latest version of libavutil I get tracing mpv is 58.36.101 not 58.37.101

Your mpv build: ===>>> NO NOT MINE ! [ 0.004][v][cplayer] built on Feb 1 2024 07:37:02 [ 0.004][v][cplayer] libplacebo version: v6.338.0-70-gc320f61-dirty [ 0.004][v][cplayer] FFmpeg version: N-113493-ga678566ab [ 0.004][v][cplayer] FFmpeg library versions: [ 0.004][v][cplayer] libavutil 58.37.101 [ 0.004][v][cplayer] libavcodec 60.38.100 [ 0.004][v][cplayer] libavformat 60.20.100 [ 0.004][v][cplayer] libswscale 7.6.100 [ 0.004][v][cplayer] libavfilter 9.17.100 [ 0.004][v][cplayer] libswresample 4.13.100

I know one thing for sure it's that when I reinstall the previous nvidia drivers any and every version of mpv whether shinchiro zhongfly official build or nightlies : ALL OF THEM WORK

[temis01]

I did reinstall drivers 551.23 using clean install (which I always use) = same problem. I tried using Zhongfly 20240124 + 20240131 nightlies = same problem

Unfortunately, I cannot reproduce this issue on my system with 551.23 (Win 11, GTX 1070). All files are playing fine here. There must be something on your system other than mpv or Nvidia driver that is causing the issue.

I am not an expert at deciphering mpv logs, but the log you posted does not seem to be using gpu-api=vulkan. It is using Direct3D11. Here are a few lines from your log

[ 0.050][v][vo/gpu-next] Probing for best GPU context. [ 0.050][v][vo/gpu-next/d3d11] Initializing GPU context 'd3d11' [ 0.168][v][vo/gpu-next/d3d11] Using Direct3D 11 feature level 12_1 [ 0.168][v][vo/gpu-next/d3d11] Device Name: NVIDIA GeForce RTX 3050

Either you accidentally grabbed a different log or your custom config is being ignored.

~Raza

You are absolutely right, mpv must have ignored vulkan from my custom config for some reason even though it is listed in the log. [ 0.000][v][cplayer] Setting option 'hwdec' = 'vulkan' (flags = 4) [ 0.000][v][cplayer] Setting option 'vf' = 'format=vulkan' (flags = 4)

[netExtra]

Apologies it is the wrong one. But did you notice the following error messages:

[ 0.215][v][vd] Opening decoder hevc [ 0.215][v][vd] Looking at hwdec hevc-vulkan... [ 0.215][v][vo/gpu-next] Loading hwdec drivers for format: 'vulkan' [ 0.215][v][vo/gpu-next] Loading hwdec driver 'vulkan' [ 0.215][e][vo/gpu-next/vulkan] This is not a libplacebo vulkan gpu api context. [ 0.215][v][vd] Could not create device. [ 0.215][v][vd] Using software decoding.

[ 0.267][v][vo/gpu-next] Loading hwdec drivers for format: 'vulkan' [ 0.267][i][hwupload] no support for this hw format [ 0.267][i][hwupload] hardware format not supported

[temis01]

Just wondering ...

I had to activate RESIZABLE BAR in the BIOS to be able to use mpv with nvidia VSR activated in nvidia control panel (even though I know that mpv does not use nvidia VSR ... yet) but that was advised somewhere here on github and it worked for me.

I like to use nvidia VSR with MPC-BE + MPC video renderer it is quite amazing, as good as MADVR, but ... NO crazy settings !

Could this be related ?

[netExtra]

Just wondering ...

I had to activate RESIZABLE BAR in the BIOS to be able to use mpv with nvidia VSR activated in nvidia control panel (even though I know that mpv does not use nvidia VSR ... yet) but that was advised somewhere here on github and it worked for me.

I like to use nvidia VSR with MPC-BE + MPC video renderer it is quite amazing, as good as MADVR, but ... NO crazy settings !

Could this be related ?

Very unlikely.

I used madVR for years and it is good but mpv is better which is why I switched. Did you look at the Vulkan errors I saw in your logs?

[temis01]

Just wondering ... I had to activate RESIZABLE BAR in the BIOS to be able to use mpv with nvidia VSR activated in nvidia control panel (even though I know that mpv does not use nvidia VSR ... yet) but that was advised somewhere here on github and it worked for me. I like to use nvidia VSR with MPC-BE + MPC video renderer it is quite amazing, as good as MADVR, but ... NO crazy settings ! Could this be related ?

I used madVR for years and it is good but mpv is better which is why I switched. Did you look at the Vulkan errors I saw in your logs?

Ok, but the point was more about RE-BAR

[netExtra]

Just wondering ... I had to activate RESIZABLE BAR in the BIOS to be able to use mpv with nvidia VSR activated in nvidia control panel (even though I know that mpv does not use nvidia VSR ... yet) but that was advised somewhere here on github and it worked for me. I like to use nvidia VSR with MPC-BE + MPC video renderer it is quite amazing, as good as MADVR, but ... NO crazy settings ! Could this be related ?

I used madVR for years and it is good but mpv is better which is why I switched. Did you look at the Vulkan errors I saw in your logs?

Ok, but the point was more about RE-BAR

Yes and as I said, "very unlikely" :)

[temis01]

Just wondering ... I had to activate RESIZABLE BAR in the BIOS to be able to use mpv with nvidia VSR activated in nvidia control panel (even though I know that mpv does not use nvidia VSR ... yet) but that was advised somewhere here on github and it worked for me. I like to use nvidia VSR with MPC-BE + MPC video renderer it is quite amazing, as good as MADVR, but ... NO crazy settings ! Could this be related ?

I used madVR for years and it is good but mpv is better which is why I switched. Did you look at the Vulkan errors I saw in your logs?

Ok, but the point was more about RE-BAR

Yes and as I said, "very unlikely" :)

how do you get mpv to beat madvr ? shaders ? anything else ? send me some config plz

I am testing to see if I still get this same error

EDIT : This very error does not appear any more in the logs

[netExtra]

how do you get mpv to beat madvr ? shaders ? anything else ? send me some config plz

Unless you are using a projector then madvr hasn't been updated since 2018. Newer doesn't always equal better, but I mostly watch high quality blu-rays on a large virtual screen and mpv is not only more flexible but the picture engine always had the edge. YMMV. I spent years trying out various shaders and configurations found on the Internet but after all that, my current config is nothing special. I use high-quality mode with gpu-next, temporal ordered dither and catmull_rom downscale. For low quality stuff, I use an ffmepg denoiser which isn't always strictly necessary and the adaptive-sharpen shader on the luma channel works surprisingly well. For anything 1080p and below I upscale with FSRCNNX_x2_16-0-4-1 which is mostly overkill but there are times when it is useful :)

[Raza-0007]

I am testing to see if I still get this same error

EDIT : This very error does not appear any more in the logs

@temis01, you need to post an updated log, specifically the one right after mpv crashes on you. That log will tell you which process caused mpv to terminate.

Although unlikely but try with Nvidia VSR disabled in NVCP. Because one of the things they added in 551.23 driver which was not present in earlier driver is this

Adds support for “Auto” setting for RTX Video Super Resolution

Since I see two people here having issues with vulkan and both are on the 30+ series Nvidia gpu's, where this is applicable.

Also, I recommend you start with a trimmed down config just to check if Vulkan is working: Use only these to start

profile=high-quality
vo=gpu-next
gpu-api=vulkan 
gpu-context=winvk
hwdec=vulkan 

You can add the other entries after vulkan works fine.

~Raza

[temis01]

I am testing to see if I still get this same error EDIT : This very error does not appear any more in the logs

@temis01, you need to post an updated log, specifically the one right after mpv crashes on you. That log will tell you which process caused mpv to terminate.

Although unlikely but try with Nvidia VSR disabled in NVCP. Because one of the things they added in 551.23 driver which was not present in earlier driver is this

Adds support for “Auto” setting for RTX Video Super Resolution

Since I see two people here having issues with vulkan and both are on the 30+ series Nvidia gpu's, where this is applicable.

Also, I recommend you start with a trimmed down config just to check if Vulkan is working: Use only these to start

profile=high-quality
vo=gpu-next
gpu-api=vulkan 
gpu-context=winvk
hwdec=vulkan 

You can add the other entries after vulkan works fine.

~Raza

I notices the auto setting for VSR + status + HDR new stuff I deactivated them right after the first crash just in case and set everything back to default.

I cleared mpv caches from c/users/local/mpv I am using mpv now as if from scratch with your minimal conf = no change at all still can play divx/xvid though.

I will try and debug mpv with the dedicated tools if I manage to get that to work (it's a first for me)

[temis01]

The logs are useless, you need to download the debug symbols to get backtrack. For shinchiro or zhongfly builds, download debug package for the build, copy pdb next to mpv.exe, and use windbg to get backtrace easily.

I put pdb file next to mpv.exe and installed drmingw as advised on shinchiro download page.

here is what drmingw says when clicking on a video (mkv)

does that help ? drmingw.txt

[temis01]

The logs are useless, you need to download the debug symbols to get backtrack. For shinchiro or zhongfly builds, download debug package for the build, copy pdb next to mpv.exe, and use windbg to get backtrace easily.

I put pdb file next to mpv.exe and installed drmingw as advised on shinchiro download page. here is what drmingw says when clicking on a video (mkv) does that help ? drmingw.txt

drmingw only working for gcc build, for new clang build, you need to use windbg, you can download it from the MS Store. The procedure can be found here. Note windbg for MS Store does not require install Windows SDK

does this help ? windbg.txt

by the way, no config file allows mpv to start and play any video file ;)

[temis01]

The logs are useless, you need to download the debug symbols to get backtrack. For shinchiro or zhongfly builds, download debug package for the build, copy pdb next to mpv.exe, and use windbg to get backtrace easily.

I put pdb file next to mpv.exe and installed drmingw as advised on shinchiro download page. here is what drmingw says when clicking on a video (mkv) does that help ? drmingw.txt

drmingw only working for gcc build, for new clang build, you need to use windbg, you can download it from the MS Store. The procedure can be found here. Note windbg for MS Store does not require install Windows SDK

does this help ? windbg.txt by the way, no config file allows mpv to start and play any video file ;)

It looks like the pdb doesn't match your mpv.exe, but it does seem to be the same problem I'm having.

I did it again with mpv + pdb from Zhongfly the result seems more eloquent !

windbg - zhongfly.txt

[netExtra]

The logs are useless, you need to download the debug symbols to get backtrack. For shinchiro or zhongfly builds, download debug package for the build, copy pdb next to mpv.exe, and use windbg to get backtrace easily.

I put pdb file next to mpv.exe and installed drmingw as advised on shinchiro download page. here is what drmingw says when clicking on a video (mkv) does that help ? drmingw.txt

drmingw only working for gcc build, for new clang build, you need to use windbg, you can download it from the MS Store. The procedure can be found here. Note windbg for MS Store does not require install Windows SDK

does this help ? windbg.txt by the way, no config file allows mpv to start and play any video file ;)

It looks like the pdb doesn't match your mpv.exe, but it does seem to be the same problem I'm having.

I did it again with mpv + pdb from Zhongfly the result seems more eloquent !

windbg - zhongfly.txt

I did a bit of searching with the previous traceback file and the results are identical to this one. The only difference is that this one clearly shows the faulting file as vulkan.c. The previous traceback file only showed the ff_vk_exec_add_dep_frame symbol and I had to search Github to find the file location.

[temis01]

The logs are useless, you need to download the debug symbols to get backtrack. For shinchiro or zhongfly builds, download debug package for the build, copy pdb next to mpv.exe, and use windbg to get backtrace easily.

I put pdb file next to mpv.exe and installed drmingw as advised on shinchiro download page. here is what drmingw says when clicking on a video (mkv) does that help ? drmingw.txt

drmingw only working for gcc build, for new clang build, you need to use windbg, you can download it from the MS Store. The procedure can be found here. Note windbg for MS Store does not require install Windows SDK

does this help ? windbg.txt by the way, no config file allows mpv to start and play any video file ;)

It looks like the pdb doesn't match your mpv.exe, but it does seem to be the same problem I'm having.

I did it again with mpv + pdb from Zhongfly the result seems more eloquent ! windbg - zhongfly.txt

I did a bit of searching with the previous traceback file and the results are identical to this one. The only difference is that this one clearly shows the faulting file as vulkan.c. The previous traceback file only showed the ff_vk_exec_add_dep_frame symbol and I had to search Github to find the file location.

nvidia has a new driver out 551.32, apparently only for RTX 3050 (which I have) = still no go !

windbg - zhongfly - new drivers 551.32.txt

[temis01]

I don't know what's going on ! Right after installing drivers 551.76 zongfly mpv dated 20240227 worked ! Now it does not any more ! same for shinchiro dated 20240310 !

[temis01]

the thing is its NOT working with most of the videos I tested ! But I just tested again with the video of the oscars ceremony I just downloaded and it DOES work with that one video only !

[temis01]

you are right I checked the 2 different logs :

[ 0.697][v][vd] Opening decoder mpeg2video [ 0.697][v][vd] Not trying to use hardware decoding: codec mpeg2video is not on whitelist. [ 0.697][v][vd] Using software decoding. [ 0.697][v][vd] Detected 12 logical cores.

[grill2010]

The logs are useless, you need to download the debug symbols to get backtrack. For shinchiro or zhongfly builds, download debug package for the build, copy pdb next to mpv.exe, and use windbg to get backtrace easily.

I put pdb file next to mpv.exe and installed drmingw as advised on shinchiro download page. here is what drmingw says when clicking on a video (mkv) does that help ? drmingw.txt

drmingw only working for gcc build, for new clang build, you need to use windbg, you can download it from the MS Store. The procedure can be found here. Note windbg for MS Store does not require install Windows SDK

does this help ? windbg.txt by the way, no config file allows mpv to start and play any video file ;)

It looks like the pdb doesn't match your mpv.exe, but it does seem to be the same problem I'm having.

I did it again with mpv + pdb from Zhongfly the result seems more eloquent ! windbg - zhongfly.txt

I did a bit of searching with the previous traceback file and the results are identical to this one. The only difference is that this one clearly shows the faulting file as vulkan.c. The previous traceback file only showed the ff_vk_exec_add_dep_frame symbol and I had to search Github to find the file location.

I think this is related

https://github.com/streetpea/chiaki4deck/issues/239#issuecomment-1931408400

I tried this patch in one of my programs and it works fine now.

[temis01]

I think this is related

streetpea/chiaki4deck#239 (comment)

I tried this patch in one of my programs and it works fine now.

It is related, AVC/HEVC with vulkan acceleration are back !