# 617.14 driver symbols missing from symbol server

**URL:** <https://forums.developer.nvidia.com/t/617-14-driver-symbols-missing-from-symbol-server/384235>\
**Category:** OpenGL\
**Created:** [September 24, 2026, 5:17pm UTC](https://forums.developer.nvidia.com/t/617-14-driver-symbols-missing-from-symbol-server/384235 "2026-09-24T17:17:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![krizdjali](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/krizdjali/32/541493_2.png) [@krizdjali](https://forums.developer.nvidia.com/u/krizdjali)\
**Post date:** [September 24, 2026, 5:17pm UTC](https://forums.developer.nvidia.com/t/617-14-driver-symbols-missing-from-symbol-server/384235/1 "2026-09-24T17:17:17Z")

</div>

When debugging a user crash dump, the debugger attempts to load [https://driver-symbols.nvidia.com/nvoglv64.dll/6AAC6FFC2eab000/nvoglv64.dll](https://driver-symbols.nvidia.com/nvoglv64.dll/6AAC6FFC2eab000/nvoglv64.dll), but that gives an access denied error. If I manually download the 617.14 driver and extract its installer with 7zip, the debugger is happy to use the `nvolgv64.dll` it contains. Inspecting the DLL with `dumpbin nvolgv64.dll /headers` reveals that its timestamp is `6AAC6FFC time date stamp Thu Sep 17 23:55:56 2026` and its size is `2EAB000 size of image`, so the `6AAC6FFC2eab000` ID the debugger uses appears to be correct.

As there are some historical posts suggesting a timezone issue, I tried adjusting the timestamp part of the URL in one hour (`0xE10`) increments for several hours earlier and later, but none of these URLs yielded a DLL, either.