Results 1 to 11 of 11

Thread: LW 2015.3 Layout & Modeler random freezes (OGL related?)

  1. #1
    Registered User WaveRider's Avatar
    Join Date
    Dec 2014
    Location
    origin
    Posts
    17

    Question LW 2015.3 Layout & Modeler random freezes (OGL related?)

    Hi,

    I don't know why but somethings I have random freezes in both LW 2015.3 Layout and Modeler.
    Sometimes happening while transforming, rotating or scaling objects in the viewports, sometimes while mouse-dragging to change values in input fields or tools(modeler).
    After some time it just shows the application error window.

    Click image for larger version. 

Name:	02.png 
Views:	33 
Size:	23.6 KB 
ID:	148366

    Is this OGL related? I have an RTX 2070 running the latest drivers.

    Thanks for your attention

  2. #2
    Founding member raymondtrace's Avatar
    Join Date
    May 2003
    Location
    Ohio
    Posts
    1,166
    The fault DLL appears to be "ogl". A google search shows this as a common fault on many 3D apps...with the suggested solution being either roll back your graphic drivers or update them.

    You might also experiment with the latest LW release to see if this behaves any better. It is possible that the card and drivers are too new for LW2015.

    EDIT: One other idea... In LightWave, go to Edit -> Display Options -> Interface, and set the Input Device from Mouse to Tablet (even if you use a mouse). Restart the program and see if that improves the situation.
    Last edited by raymondtrace; 07-21-2020 at 01:55 PM.
    LW4, 7.5D, 2015, 2018, 2019, 2020 running portably on a USB drive on an Amiga 2500 running Wine.

  3. #3
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,987
    Exception 0x40000015 is STATUS_FATAL_APP_EXIT which suggests Nvidia's OGL (nvoglv64.dll) encountered some kind of unrecoverable error during operation. As suggested, for starters, either look into updated video drivers for your hardware, or if on latest/beta try rolling back to prior version (if possible).

    In order to debug further, I'd need the full content of the "problem signature" frame at minimum, actual crashdump ideally, in order to check whether the cause and location are consistent across the different freeze conditions, or if it varies between the different freezes (that could hint at multiple different errors occurring from different triggers).

    Doing a search online for '"nvoglv64.dll" "26.21.14.4587"' (the latter is the driver version), I see a bunch of issues but none with the exact same exception. However the other issues combined with your own experience probably make it worthwhile to try upgrading your video driver version, if possible, to see if that helps.
    John W.
    LW2015.3UB/2019.1.5 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  4. #4
    Registered User WaveRider's Avatar
    Join Date
    Dec 2014
    Location
    origin
    Posts
    17
    Thanks everyone,
    I'll try posting the complete crashdump once the error occurs again. I will also update those display drivers.

  5. #5
    TrueArt Support
    Join Date
    Feb 2003
    Location
    Poland
    Posts
    8,152
    Crash at exit of the app usually means that memory has been corrupted at much earlier stage. Damaged memory is just detected during freeing previously allocated chunk of the memory. e.g. overflow of an array.

  6. #6
    Registered User WaveRider's Avatar
    Join Date
    Dec 2014
    Location
    origin
    Posts
    17
    It's me again,

    full crash report

    Code:
    Problem signature:
      Problem Event Name:	APPCRASH
      Application Name:	Modeler.exe
      Application Version:	0.0.0.0
      Application Timestamp:	55c53160
      Fault Module Name:	nvoglv64.DLL
      Fault Module Version:	27.21.14.5167
      Fault Module Timestamp:	5f022397
      Exception Code:	40000015
      Exception Offset:	00000000010c053f
      OS Version:	6.1.7601.2.1.0.256.1
      Locale ID:	1031
      Additional Information 1:	ade8
      Additional Information 2:	ade8cb386c61d3d525c08a819daf7011
      Additional Information 3:	c8e9
      Additional Information 4:	c8e939903893c25260964e7a83837e5b
    https://drive.google.com/file/d/1CyT...ew?usp=sharing
    it won't let me generate minidumps of user-level threads, so this is a 300+ MB file

    Thanks for your attention

  7. #7
    Registered User WaveRider's Avatar
    Join Date
    Dec 2014
    Location
    origin
    Posts
    17
    Code:
    Problem signature:
      Problem Event Name:	APPCRASH
      Application Name:	Layout.exe
      Application Version:	0.0.0.0
      Application Timestamp:	55c531d7
      Fault Module Name:	ntdll.dll
      Fault Module Version:	6.1.7601.24520
      Fault Module Timestamp:	5d673de3
      Exception Code:	c0000264
      Exception Offset:	00000000000c8658
      OS Version:	6.1.7601.2.1.0.256.1
      Locale ID:	1031
      Additional Information 1:	8f1f
      Additional Information 2:	8f1f06ea0de616c737719cb7f5f6f804
      Additional Information 3:	9625
      Additional Information 4:	96257c8906934c434d5924e6a39011b0

  8. #8
    Electron wrangler jwiede's Avatar
    Join Date
    Aug 2007
    Location
    San Jose, CA
    Posts
    6,987
    Whatever's occurring in the above Layout crash, the crash is quite different from what occurred in the Modeler crash. What were the circumstances here?

    Sorry for the delay getting back to you. I do have the DMP downloaded, just haven't had a chance to dig into it with the debugger.
    Last edited by jwiede; 08-05-2020 at 01:17 PM.
    John W.
    LW2015.3UB/2019.1.5 on MacPro(12C/24T/10.13.6),64GB RAM, NV 980ti

  9. #9
    Registered User WaveRider's Avatar
    Join Date
    Dec 2014
    Location
    origin
    Posts
    17
    Thank you very much jwiede. There's no rush. I just want to get a vague idea where those crashes in 2015.3 come from. Most are related to surfacing(tools.dll), then the OGL freeze(nvoglv64.dll) and some are related to rendering(the one above occurred after rendering with the perspective camera, changing the camera to classic and rendering again).
    I can't upgrade to LW2020 right now because I need the classic renderer for what I'm doing. I also considered going back to an older, more stable version of LW.

  10. #10
    Registered User
    Join Date
    Jan 2005
    Location
    Colorado Springs
    Posts
    1,863
    DebugDiag might be helpful in that the TXT file generated contains the stack information rather than just the top-level exception. Often, the top-level exception is caused by bad / corrupted data provided by the caller, so the stack traceback can be very helpful in debugging the crash.

    Here's a post re: DebugDiag from last year:

    https://forums.newtek.com/showthread...=1#post1581104

    Good luck!
    mTp

  11. #11
    Registered User WaveRider's Avatar
    Join Date
    Dec 2014
    Location
    origin
    Posts
    17
    Thank you, I'll try to log any future crash with DebugDiag.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •