Crash Trace - VLC or Nvidia Issue?

Microsoft Windows specific usage questions
Forum rules
Please post only Windows specific questions in this forum category. If you don't know where to post, please read the different forums' rules. Thanks.
aitte
Cone that earned his stripes
Cone that earned his stripes
Posts: 310
Joined: 28 Feb 2012 00:26

Crash Trace - VLC or Nvidia Issue?

Postby aitte » 17 May 2019 04:56

I'm trying to solve [url=https://trac.videolan.org/vlc/ticket/20483]this bug[/url] (so I'm on Windows 64-bit, with a GTX 1060, etc.)

I finally got the debug version of VLC built and ran it with gdb attached. I'm seeing this stack trace (I've included the gdb logs as well):

Code: Select all

warning: direct3d9 vout display debug: Direct3D9 scene released successfully warning: direct3d9 vout display error: SetThumbNailClip failed: 0x800706f4 warning: direct3d9 vout display debug: Win32 Vout EventThread terminating warning: direct3d9 vout display debug: Win32VoutCloseWindow warning: direct3d9 vout display debug: WinProc WM_DESTROY [Thread 7256.0x10b4 exited with code 0] warning: main filter debug: removing module "chain" warning: main filter debug: removing module "d3d9_filters" [New Thread 7256.0x1048] warning: main filter debug: Filter 00000000074cee90 removed from chain warning: main filter debug: removing module "sharpen" warning: main filter debug: Filter 00000000074cf200 removed from chain warning: main video output debug: Filter 00000000074ceb20 removed from chain warning: main filter debug: removing module "d3d9_filters" warning: main generic debug: removing module "i420_nv12" warning: wasapi generic debug: buffer size : 96000 frames Thread 95 received signal SIGSEGV, Segmentation fault. [Switching to Thread 7256.0x2a3c] 0x000007fedf883381 in d3d9!Direct3DCreate9Ex () from /cygdrive/c/Windows/system32/D3D9.DLL (gdb) where #0 0x000007fedf883381 in d3d9!Direct3DCreate9Ex () from /cygdrive/c/Windows/system32/D3D9.DLL #1 0x000007fe98a86c89 in QueryOglResource () from /cygdrive/c/Windows/system32/nvd3dumx.dll #2 0x000007fe989f18f9 in ?? () from /cygdrive/c/Windows/system32/nvd3dumx.dll #3 0x000007fe98ccb8b4 in QueryOglResource () from /cygdrive/c/Windows/system32/nvd3dumx.dll #4 0x000000007713556d in KERNEL32!BaseThreadInitThunk () from /cygdrive/c/Windows/system32/kernel32.dll #5 0x000000007729385d in ntdll!RtlUserThreadStart () from /cygdrive/c/Windows/SYSTEM32/ntdll.dll #6 0x0000000000000000 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb)
I recently updated the Nvidia drivers from versions that were about a year old to the newest, and got the same crash. I know you're going to claim it's an Nvidia driver problem, but how do we know it's not a bad call to the api? I.e., bad memory address, or passing buffers or objects that have been corrupted by something in vlc?

I don't see any code from VLC in the stack. How is the code above getting called by VLC? Does the nvidia driver run some sort of a queue thread where you can submit rendering requests and they're run in the background?

I'm having zero other problems with 3D games and other video players. The only crash is from VLC.

Return to “VLC media player for Windows Troubleshooting”

Who is online

Users browsing this forum: No registered users and 20 guests