My Video Application Crashed at nvd3dum!QueryOglResource

Hi there,

 I am developing a video surveillance client which uses NVIDIA NVS 510 and the driver version is 430.86 which is running on Windows 10 operating system.

 The application is using D3D9 for decoding video(DXVA2) via FFMPEG and video processing/rendering (DXVA-HD). 
 The application runs fine where in i am able to connect two monitors to the graphics card and display a total of 20 videos with 10 each per monitor. The application is capable of dividing each monitor in to different tiles and display video on each tile, also it is capable of switching between different video source on each tile.
 After around 48 hours of run-time there is a crash and the call stack is as follows:

EXCEPTION_RECORD: ffffffff – (.exr 0xffffffffffffffff)
ExceptionAddress: 62685de2 (nvd3dum!QueryOglResource+0x000fbff2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: a8a67fa8
Attempt to read from address a8a67fa8

Call Stack is as follows:
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
777ceebc 62685cca 00000001 000000a0 777cef1c nvd3dum!QueryOglResource+0xfbff2
777cefdc 6268507f 80070057 00000001 777cf178 nvd3dum!QueryOglResource+0xfbeda
777cf004 6267caba 80070057 0ee77440 627eec70 nvd3dum!QueryOglResource+0xfb28f
777cf1dc 6258b73c 7219cedc a3643924 7219cedc nvd3dum!QueryOglResource+0xf2cca
777cf1f0 624f5a65 a35b3800 7219cedc 00000000 nvd3dum!QueryOglResource+0x194c
777cff34 6250f6f7 a8f152e8 6250f6c0 777cff80 nvd3dum+0x815a65
777cff44 627be453 42ef60c0 705510d5 627be3fb nvd3dum+0x82f6f7
777cff80 77c08484 a8f152e8 77c08460 66350c60 nvd3dum!QueryOglResource+0x234663
777cff94 77e241c8 a8f152e8 6612af06 00000000 kernel32!BaseThreadInitThunk+0x24
777cffdc 77e24198 ffffffff 77e3f32a 00000000 ntdll!__RtlUserThreadStart+0x2f
777cffec 00000000 627be3fb a8f152e8 00000000 ntdll!_RtlUserThreadStart+0x1b

   Can we get the symbols for nvd3dum.dll or can some one analyse this callstack and inform us what went wrong here? As of now i have a feeling that this thread is not spawn by my application.

   Hope i get a quick reply, thanks for your reply in advance.
  • Satheesh M
1 Like