"APPCRASH" Error When Trying to Build Orthomosaic

[mr.barnadib]

Hello,

This error occurred in the middle of building orthomosaic

Log Name:      Application
Source:        Application Error
Date:          22/09/2017 13:56:23
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-AUAE39A
Description:
Faulting application name: photoscan.exe, version: 1.0.0.1, time stamp: 0x5992dd13
Faulting module name: nvoglv64.DLL, version: 22.21.13.8569, time stamp: 0x59bd55a4
Exception code: 0xc0000409
Fault offset: 0x000000000100cf88
Faulting process id: 0x2980
Faulting application start time: 0x01d3336f6d63d63b
Faulting application path: C:\Program Files\Agisoft\PhotoScan Pro\photoscan.exe
Faulting module path: C:\Windows\SYSTEM32\nvoglv64.DLL
Report Id: 9c9bdb10-ab58-4f19-90eb-f206eb1e9bd3
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-09-22T06:56:23.508854000Z" />
    <EventRecordID>6357</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-AUAE39A</Computer>
    <Security />
  </System>
  <EventData>
    <Data>photoscan.exe</Data>
    <Data>1.0.0.1</Data>
    <Data>5992dd13</Data>
    <Data>nvoglv64.DLL</Data>
    <Data>22.21.13.8569</Data>
    <Data>59bd55a4</Data>
    <Data>c0000409</Data>
    <Data>000000000100cf88</Data>
    <Data>2980</Data>
    <Data>01d3336f6d63d63b</Data>
    <Data>C:\Program Files\Agisoft\PhotoScan Pro\photoscan.exe</Data>
    <Data>C:\Windows\SYSTEM32\nvoglv64.DLL</Data>
    <Data>9c9bdb10-ab58-4f19-90eb-f206eb1e9bd3</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

PhotoScan Installed Version: 1.3.3.4827 64bit
Windows 10 Pro 64bit
Full Spec :
Core i7 6700K - with CM Seidon 240P
MSI H170 gaming M3
Gigabyte GTX 1080Ti Xtreme Edition 11G AORUS with latest nvdia driver : 385.69
Elite Team 32 gb of RAM (8 gb x 4)
Samsung NVMe SSD 960 PRO 512 mb
HDD WDC Blue 4 tb

[Alexey Pasumansky]

Hello mr.barnadib,

nvoglv64.DLL - is related to NVIDIA drivers, so I can suggest a clean install of the latest driver version.

[mr.barnadib]

Hello mr.barnadib,

nvoglv64.DLL - is related to NVIDIA drivers, so I can suggest a clean install of the latest driver version.

thanks for your fast response, Alexey bruv...

I've done what you suggested, but it still crash...

[Alexey Pasumansky]

Hello mr.barnadib,

Can you please also provide the processing log from PhotoScan (you can redirect it to file using "Write log to file" option in the Preferences window) related to the crash?

[mr.barnadib]

Hello mr.barnadib,

Can you please also provide the processing log from PhotoScan (you can redirect it to file using "Write log to file" option in the Preferences window) related to the crash?

here you go...

[Alexey Pasumansky]

Hello mr.barnadib,

I can suggest to run PhotoScan Pro using --opengl angle parameters and see if it helps:

Code: [Select]

photoscan.exe --opengl angle

[mr.barnadib]

Hello mr.barnadib,

I can suggest to run PhotoScan Pro using --opengl angle parameters and see if it helps:

Code: [Select]

photoscan.exe --opengl angle

I have done that even before you suggested, because of the other thread. It is funny because my lenovo u41 has problem with diappearing toolbar and zooming bugs. But it was solved with --opengl angle parameters.
Back to my PC, I have also rolled back to earlier nvidia driver. but nothing changes.
Using --opengl angle in shortcut, and it was a little weird. Photoscan keep running until a few percent progress, but the monitor keeps on and off several times. It was like when you set monitor to turn off after several minutes in windows control panel / power option. But I make sure it was set to high performance and never turn off the monitor. And after several minutes, the monitor turned off / the screen goes blank. It says no video input, but the CPU load still full, I knew it from the sound of the CPU fan and GPU fan ( can you imagine seidon 240 and gigabyte aorus xtreme triple fan running at 100%?).
Finally I had to hit the reset button to restart the PC. I relieved my gtx 1080ti is not dead yet.

I ran the same project with lenovo u41 laptop, it was done building orthomosaic, but sadly it took a lot of my precious time.

Weird, innit? Is it some kind of bottleneck? I am planning to change the msi h170 with aorus z270x.

[mr.barnadib]

UPDATE

I have bought new Gigabyte z270x gaming 7 - Aorus
Been reinstall windows and everything, but still crash

[Alexey Pasumansky]

Hello mr.barnadib,

Are the drivers installed from the NVIDIA web-site directly and not from some Windows services?

[mr.barnadib]

Hello mr.barnadib,

Are the drivers installed from the NVIDIA web-site directly and not from some Windows services?

Sure, yes...

And been reported to nvidia devtalk
https://devtalk.nvidia.com/default/topic/1024452/opengl/bug-report-nvoglv64-dll/

[mr.barnadib]

It solved. I just got an email from nvidia :

   
Recently you requested personal assistance from our on-line support center. Below is a summary of your request and our response. We will assume your issue has been resolved if we do not hear from you within 72 hours. Thank you for allowing us to be of service to you.
Subject
Faulting module path: C:\Windows\SYSTEM32\nvoglv64.DLL

Response By Email (Sonal) (09/26/2017 04:28 PM)
Hello,
 
Thank you for your patience.
 
As per the system file, nvlddmkm.sys crash is reported as well.
 
The issue occurs when the Timeout Detection and Recovery (TDR) feature available in Windows Vista and Windows 7, 8 and 10 OS, detects that the graphics card (GPU) has not responded within a predetermined period of time and reinitializes it with the Windows Display Driver Model (WDDM) to prevent the need to reboot.

Since the graphic card is always drawing to your screen, Windows will often report the graphics card or its drivers as the problematic device after a system error.  In most cases, the problem is caused by another device or component in your system such as the motherboard, system memory, power supply or hard drive

So there are several factors that could cause such issue like OS corruption, driver corruption, RAM Issue, power issues, outdated motherboard BIOS, application / game specific and lastly the card itself.
 
 
For the troubleshooting purpose, please create registry back up as mentioned in the link http://ccm.net/faq/28961-windows-8-make-a-backup-of-the-registry

Once it is done, reboot the PC and perform the steps as below:

1. Goto registry editor (start -> run -> regedit)
2. Navigate yourself to HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/GraphicsDrivers (make sure GraphicsDrivers is highlighted).
3. Right click -> New -> DWORD (32-bit) value -> Name it: TdrDelay -> double click it -> Set it to A (hexadecimal) or 10 (decimal).
 
Best regards,
Sonal
NVIDIA Customer Care