Cool VL Viewer forum

View unanswered posts | View active topics It is currently 2025-09-23 15:17:54



Reply to topic  [ 2 posts ] 
Crash from nvogl, invalid memory read 
Author Message

Joined: 2011-10-07 10:39:20
Posts: 216
Reply with quote
Hello Henri,

probably not too useful. Got a crash from the NVidia OpenGL driver running 1.32.4.5 on Windows 10.
Did nothing really extraordinary, just some shopping at Smooching Serpents and trying some furniture.

NVidia Driver Version is 576.88.

Crashdump and Log attached.


Code:
............................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr
(c48.885c): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007fff`63a8f344 c3              ret
0:056> !analyze -v
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

...............................................................
............................................
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 656

    Key  : Analysis.Elapsed.mSec
    Value: 28086

    Key  : Analysis.IO.Other.Mb
    Value: 1

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 38

    Key  : Analysis.Init.CPU.mSec
    Value: 484

    Key  : Analysis.Init.Elapsed.mSec
    Value: 103830

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 150

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    Key  : Failure.Bucket
    Value: INVALID_POINTER_READ_c0000005_nvoglv64.dll!Unknown

    Key  : Failure.Exception.Code
    Value: 0xc0000005

    Key  : Failure.Exception.IP.Address
    Value: 0x7fff1a9b0030

    Key  : Failure.Exception.IP.Module
    Value: nvoglv64

    Key  : Failure.Exception.IP.Offset
    Value: 0xb60030

    Key  : Failure.Hash
    Value: {a08f2bd3-6036-8f62-b5d9-fb156f5f1e59}

    Key  : Failure.ProblemClass.Primary
    Value: INVALID_POINTER_READ

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 933237

    Key  : Timeline.Process.Start.DeltaSec
    Value: 10362

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.Process.Version
    Value: 1.32.4.5


FILE_IN_CAB:  CoolVLViewer.dmp

CONTEXT:  (.ecxr)
rax=0000026c0df62fe0 rbx=00000269db0a8840 rcx=00000269db0a9020
rdx=00000269db0a8840 rsi=0000000000000000 rdi=0000026c0df62800
rip=00007fff1a9b0030 rsp=00000085f0ffe778 rbp=0000000000000800
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=0000000000000004 r12=0000000000000000 r13=0000000000000400
r14=00000000000000f8 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nvoglv64!DrvPresentBuffers+0x1389e0:
00007fff`1a9b0030 0f1041e0        movups  xmm0,xmmword ptr [rcx-20h] ds:00000269`db0a9000=????????????????????????????????
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007fff1a9b0030 (nvoglv64!DrvPresentBuffers+0x00000000001389e0)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000269db0a9000
Attempt to read from address 00000269db0a9000

PROCESS_NAME:  CoolVLViewer.exe

READ_ADDRESS:  00000269db0a9000

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000269db0a9000

STACK_TEXT: 
00000085`f0ffe778 00007fff`1a9afc5e     : 00000000`00000000 00000269`9fe26340 00000000`00000010 00007fff`1a9ba939 : nvoglv64!DrvPresentBuffers+0x1389e0
00000085`f0ffe780 00007fff`1a8c15b5     : 0000026a`23661580 00000000`00000302 00000000`00001000 00000085`f0ffeb20 : nvoglv64!DrvPresentBuffers+0x13860e
00000085`f0ffe7d0 00007fff`1a8c0b8e     : 0000026c`86f0b400 00000000`00000001 0000026b`00000000 00000000`00000000 : nvoglv64!DrvPresentBuffers+0x49f65
00000085`f0ffeaa0 00007fff`1a8c0ee5     : 00000269`9fe26340 00000269`dafa8040 0000026b`864aa508 00007fff`1a9b74e8 : nvoglv64!DrvPresentBuffers+0x4953e
00000085`f0ffec80 00007fff`1a8c114f     : 00000000`00000001 00000269`9fe20000 00000000`00000000 00000000`00000000 : nvoglv64!DrvPresentBuffers+0x49895
00000085`f0ffefd0 00007fff`1a8daaed     : 0000026b`864aa6d0 00000269`dafa8040 0000026c`cbe2e5f0 00000269`9fe26340 : nvoglv64!DrvPresentBuffers+0x49aff
00000085`f0fff080 00007fff`1a8dac82     : 0000026c`cbe2e5f0 00000269`dafa8040 00000000`00000001 00000000`00000000 : nvoglv64!DrvPresentBuffers+0x6349d
00000085`f0fff0f0 00007fff`1a989334     : 03040400`03040400 0000026b`00040004 00000000`00000000 00000269`00000000 : nvoglv64!DrvPresentBuffers+0x63632
00000085`f0fff520 00007fff`1a989688     : 00000269`00000000 00000269`9fe26340 0000026c`00000000 00007fff`00000000 : nvoglv64!DrvPresentBuffers+0x111ce4
00000085`f0fff5c0 00007fff`1a4719eb     : 00000269`9e360000 00007fff`00000000 00000085`00000001 00000000`00000000 : nvoglv64!DrvPresentBuffers+0x112038
00000085`f0fff680 00007fff`1a5a5056     : 00000000`00000001 00000000`00000001 0000026b`864aa340 0000026c`cbe2e5f0 : nvoglv64+0x6219eb
00000085`f0fff700 00007fff`1a5a9910     : 0000026b`864aa300 00000000`00000000 00000269`9e360000 00000269`00000400 : nvoglv64+0x755056
00000085`f0fffaa0 00007fff`1a5aa7da     : 0000026c`daff3800 00000000`00000400 00000000`00000000 00007fff`00000de1 : nvoglv64+0x759910
00000085`f0fffb80 00007fff`1a5b6e12     : 00000000`00000000 0000026b`864aa340 00000000`00000000 00000000`00000de1 : nvoglv64+0x75a7da
00000085`f0fffc80 00007fff`1a40bec3     : 0000026c`a10cfde4 00000000`00000400 00000269`a56edf48 00000269`a56edf48 : nvoglv64+0x766e12
00000085`f0fffd10 00007fff`1a5d378a     : 00000269`a4dcd080 00000269`a56ee2e4 00000269`a56edf48 00000269`a56ee2e4 : nvoglv64+0x5bbec3
00000085`f0fffd80 00007fff`1a5d334e     : 00000269`00000064 00000269`a56ee2e4 00000000`0000885c 00000269`a56ee400 : nvoglv64+0x78378a
00000085`f0fffde0 00007fff`1a854f98     : 00000269`a56ee400 00000000`00000000 00000000`00000000 00000000`00000000 : nvoglv64+0x78334e
00000085`f0fffe10 00007fff`62aa7374     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvoglv64!DrvValidateVersion+0xdf88
00000085`f0fffe40 00007fff`63a3cc91     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
00000085`f0fffe70 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


SYMBOL_NAME:  nvoglv64+1389e0

MODULE_NAME: nvoglv64

IMAGE_NAME:  nvoglv64.dll

STACK_COMMAND: ~56s; .ecxr ; kb

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_nvoglv64.dll!Unknown

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  32.0.15.7688

FAILURE_ID_HASH:  {a08f2bd3-6036-8f62-b5d9-fb156f5f1e59}

Followup:     MachineOwner
---------


Attachments:
CoolVLViewer_3144.zip [48.22 KiB]
Downloaded 2 times
CoolVLViewer.zip [35.5 KiB]
Downloaded 3 times
2025-09-21 17:50:51
Profile

Joined: 2009-03-17 18:42:51
Posts: 6055
Reply with quote
Well, that's a first for NVIDIA drivers, though, lately, those became quite shitty. Even under Linux, their newest drivers are catastrophic (I am stuck with 575, because 580 is unstable: it does not crash but causes Xid errors and render mess with meshes).

Apparently, the crash happened in one of the shared GL context threads, inside the NVIDIA DLL itself.

To avoid more such crashes, my advice would therefore be to either try an older driver version, or to disable the GL worker threads in the Graphics preferences of the viewer (they cause VRAM memory leaks anyway)...

Here's all what I got with the crash dump from VS debugger:
Attachment:
trace.png [314.53 KiB]
Not downloaded yet


2025-09-21 18:50:23
Profile WWW
Display posts from previous:  Sort by  
Reply to topic   [ 2 posts ] 

Who is online

Users browsing this forum: No registered users and 26 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.