[FFmpeg-devel] ffmpeg crashing system with GPU intalled?
John Riker
jriker1 at yahoo.com
Wed Dec 8 16:53:07 EET 2021
I have some older systems but still decent that I have been doing hevc encoding with for a long time. These are Dell Precision R5500 rack mount systems with dual X5680 Xeon CPUs. One had no GPU in it and was running Windows 10 and working fine. The second running Windows 2016 Server and has a NVidia NVS 295 GPU in it with latest drivers. The server kept crashing at random times. ffmpeg 4.4-full The Windows 10 was fine.
Tried triaging the Server issues so replaced thermal paste and set my 6 fans to 100% and the device was running cool. Still crashed but just black screens and no crash logs. So I recently installed a GPU back into the Windows 10 computer. NVidia Quadro M4000 with latest drivers. It bluescreened during encoding and received crash logs which look like it's NVidia related but my encoding is not using the GPU at all or don't think so and task manager doesn't show any activity for it.
Below is an example of the command I'm sending:
ffmpeg.exe -i "<input_filename>.mkv" -c:v libx265 -x265-params level=51:hdr10=1:hdr-opt=1:high-tier=1:repeat-headers=1:colorprim=bt2020:transfer=smpte2084:colormatrix=bt2020nc:master-display=G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1):max-cll=854,365:crf=16:chromaloc=2:no-sao=1:info=0:range=limited:vbv-maxrate=15000:vbv-bufsize=15000 -vf crop=3840:1600:0:280 -preset slower -pix_fmt yuv420p10le -sn -an "<output_filename>.hevc"
I do suspect "maybe?" at some point when RDPing into the server maybe that's related? But doesn't seem to happen for the most part, just sometimes shortly after remoting in it goes down even though it didn't the last 50 times so may be a coincidence? The review of the crash log on the Windows 10 system is:
> > 14: kd> !analyze -v
> *******************************************************************************
> * *
> * Bugcheck Analysis *
> * *
> *******************************************************************************
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a
> pageable (or completely invalid) address at an interrupt request level
> (IRQL) that is too high. This is usually caused by drivers using
> improper addresses. If kernel debugger is available get stack
> backtrace. Arguments: Arg1: 00000000000035a4, memory referenced Arg2:
> 000000000000000c, IRQL Arg3: 0000000000000000, value 0 = read
> operation, 1 = write operation Arg4: fffff80035712f86, address which
> referenced memory
>
> Debugging Details:
> ------------------
>
>
> KEY_VALUES_STRING: 1
>
> Key : Analysis.CPU.mSec
> Value: 6233
>
> Key : Analysis.DebugAnalysisManager
> Value: Create
>
> Key : Analysis.Elapsed.mSec
> Value: 8351
>
> Key : Analysis.Init.CPU.mSec
> Value: 1639
>
> Key : Analysis.Init.Elapsed.mSec
> Value: 45867
>
> Key : Analysis.Memory.CommitPeak.Mb
> Value: 87
>
> Key : WER.OS.Branch
> Value: vb_release
>
> Key : WER.OS.Timestamp
> Value: 2019-12-06T14:06:00Z
>
> Key : WER.OS.Version
> Value: 10.0.19041.1
>
>
> FILE_IN_CAB: MEMORY.DMP
>
> BUGCHECK_CODE: d1
>
> BUGCHECK_P1: 35a4
>
> BUGCHECK_P2: c
>
> BUGCHECK_P3: 0
>
> BUGCHECK_P4: fffff80035712f86
>
> READ_ADDRESS: 00000000000035a4
>
> BLACKBOXBSD: 1 (!blackboxbsd)
>
>
> BLACKBOXNTFS: 1 (!blackboxntfs)
>
>
> BLACKBOXPNP: 1 (!blackboxpnp)
>
>
> BLACKBOXWINLOGON: 1
>
> PROCESS_NAME: ffmpeg.exe
>
> TRAP_FRAME: ffffbc80b81f2160 -- (.trap 0xffffbc80b81f2160) NOTE: The
> trap frame does not contain all registers. Some register values may be
> zeroed or incorrect. rax=ffffcd8387447d00 rbx=0000000000000000
> rcx=0000000000002700 rdx=ffffcd8389a22000 rsi=0000000000000000
> rdi=0000000000000000 rip=fffff80035712f86 rsp=ffffbc80b81f22f8
> rbp=0000000000000001 r8=0000000000000000 r9=0000000000000000
> r10=ffffcd838a91f7a0 r11=ffffcd838a91f460 r12=0000000000000000
> r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0
> nv up ei ng nz ac pe nc nvlddmkm+0xa2f86: fffff800`35712f86
> 8b81a40e0000 mov eax,dword ptr [rcx+0EA4h]
> ds:00000000`000035a4=???????? Resetting default scope
>
> STACK_TEXT: ffffbc80`b81f2018 fffff800`2d809069 :
> 00000000`0000000a 00000000`000035a4 00000000`0000000c
> 00000000`00000000 : nt!KeBugCheckEx ffffbc80`b81f2020
> fffff800`2d805369 : 00000000`00025106 00000000`00989680
> 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
> ffffbc80`b81f2160 fffff800`35712f86 : ffffcd83`89b64000
> 00000000`00000000 00000000`00000000 00000000`00000000 :
> nt!KiPageFault+0x469 ffffbc80`b81f22f8 fffff800`35713896 :
> ffffbc80`b81f2490 00000000`00000000 00000000`00000000
> 00000000`00000000 : nvlddmkm+0xa2f86 ffffbc80`b81f2328
> ffffcd83`89aea000 : ffffcd83`89aea000 ffffbc80`b81f2490
> ffffbc80`b81f23a9 ffffbc80`b81f2778 : nvlddmkm+0xa3896
> ffffbc80`b81f2358 ffffcd83`89aea000 : ffffbc80`b81f2490
> ffffbc80`b81f23a9 ffffbc80`b81f2778 ffffcd83`89b64000 :
> 0xffffcd83`89aea000 ffffbc80`b81f2360 ffffbc80`b81f2490 :
> ffffbc80`b81f23a9 ffffbc80`b81f2778 ffffcd83`89b64000
> fffff800`35e66fe0 : 0xffffcd83`89aea000 ffffbc80`b81f2368
> ffffbc80`b81f23a9 : ffffbc80`b81f2778 ffffcd83`89b64000
> fffff800`35e66fe0 ffffcd83`89b64000 : 0xffffbc80`b81f2490
> ffffbc80`b81f2370 ffffbc80`b81f2778 : ffffcd83`89b64000
> fffff800`35e66fe0 ffffcd83`89b64000 00000000`00000000 :
> 0xffffbc80`b81f23a9 ffffbc80`b81f2378 ffffcd83`89b64000 :
> fffff800`35e66fe0 ffffcd83`89b64000 00000000`00000000
> 00000000`00000000 : 0xffffbc80`b81f2778 ffffbc80`b81f2380
> fffff800`35e66fe0 : ffffcd83`89b64000 00000000`00000000
> 00000000`00000000 00000000`00000000 : 0xffffcd83`89b64000
> ffffbc80`b81f2388 fffff800`35e3760e : ffffcd83`89b64000
> 00000000`00000000 00000000`00000000 ffffcd83`8a69b010 :
> nvlddmkm+0x7f6fe0 ffffbc80`b81f2438 00000000`00000000 :
> ffffbc80`b81d8180 00000000`00000286 00000000`0000000c
> 00000000`00fd86d5 : nvlddmkm+0x7c760e
>
>
> SYMBOL_NAME: nvlddmkm+a2f86
>
> MODULE_NAME: nvlddmkm
>
> IMAGE_NAME: nvlddmkm.sys
>
> STACK_COMMAND: .cxr; .ecxr ; kb
>
> BUCKET_ID_FUNC_OFFSET: a2f86
>
> FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
>
> OS_VERSION: 10.0.19041.1
>
> BUILDLAB_STR: vb_release
>
> OSPLATFORM_TYPE: x64
>
> OSNAME: Windows 10
>
> FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
>
> Followup: MachineOwner
> ---------
More information about the ffmpeg-devel
mailing list