[ContextCapture] Windows timeout detection and recovery (TDR) error

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Oto — Mon, 22 Oct 2018 08:07:01 GMT

On Windows server 2012 there is one more setting to increase DPC_WATCHDOG_VIOLATION timeout :

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Kernel\
DpcWatchdogPeriod=REG_DWORD 0003a980 (hexidecimal)
DpcTimeout=REG_DWORD 00000000

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Oto — Thu, 13 Oct 2016 06:37:47 GMT

Do you have latest CC version v4.3.0.507?

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Florent Poux — Tue, 11 Oct 2016 12:16:37 GMT

Hi Oto,

yes I have similar observations using Z-GPU and the windows processus manager list of CPU use...

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Florent Poux — Tue, 11 Oct 2016 12:15:18 GMT

Hi Pierre,

I had to stop the project it was stuck at 94% for 2 days... Yest I relaunched from 70% because before it was taking too long so I stopped.
Even relaunching I get the same problem. I also try upgrading to the newest version of CC but nothing changes unfortunately...

Best regards

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Oto — Tue, 11 Oct 2016 08:58:15 GMT

What are maximums frequencies and GPU load you observe? Also what is most frequent limiting factor for GPU shown in PerfCap?

What I see from my observations is that GPU load is jumping from 0 to 100% while production is calculating, then when progress is at 18% GPU load drops to 0% but CPU load is 100%. Afterwards it again switches to GPU calculations and GPU load fluctuates from 0 to 100% till production finishes. Average GPU load for productions is 25%

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Pierre Diebolt — Fri, 07 Oct 2016 12:39:04 GMT

Hi Florent,

Thanks for the share.
It looks like the latest project has not the same amount of faces than the older one so we can't compare them together.
Here are the differences:
- 1M faces for the one generated some months ago and 10M faces for your latest project
- 2 textures extracted vs 9 textures for the latest one

Also we have noticed the latest project is not computing the reconstruction from scratch but is starting at the <Exporting mesh> steps.
The best here should to reset the reconstruction then restart it so to make sure you are computing the whole process.

Best regards,
Pierre

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Florent Poux — Thu, 06 Oct 2016 18:16:07 GMT

Here you will find the two logs at this adress: https://we.tl/2iuH8ECcWz

the okay one is te one with correct processing times (launch some months before)

The not ok is the one still processing

Kind regards

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Pierre Diebolt — Thu, 06 Oct 2016 16:19:43 GMT

Can you attach the log for this project in particular ?

The best should to attach the log of the previous version and the log from the latest (even if it still computing) so to be able to compare them and see what's wrong here.

Here's a screenshot that explain how to export a log file from Contextcapture:

Click on the reconstructed production then click on General tab

Now click on <More details> button then Right-click on the tile and choose "Export log file for technical support" option.

Thanks

Pierre

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Florent Poux — Thu, 06 Oct 2016 15:39:41 GMT

Hum, it seems I have the same value as you stated :

What do you think ?

Kind regards,

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Pierre Diebolt — Thu, 06 Oct 2016 15:34:54 GMT

Ok let's check another thing :)

We suspect the Timeout Detection and Recovery key is not set properly and could impact the performance of the GPU card.

- Could you open regedit then go to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

- Can you tell me if you have a TdrLevel or any other Tdr registry keys that are listed here ?

For example I only have the <TdrLevel> key that is set to (0) which is the value you should have by default.

Best regards,

Pierre

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Florent Poux — Thu, 06 Oct 2016 15:02:55 GMT

Hello Pierre,

Here is the corresponding screenshot :

As you can see, the score is close to yours (117.1).

Concerning the project, I tested on many different blocks that I already processed let say 2 months ago. The blocks varies including photos (24 Mpixels in RAW from Canon 5D Mark III) from 20 to 300 photos per block. Right now for a concrete example, I am running a project (AT done) with 74 photos used for reconstruction, and it is still calculating the 3D reconstruction after more than 12 hours (started yersteday at 8 pm). As a benchmark, I ran the same project on my colleague computer which has a 1080 GTX and 64 Gb of RAM, and it took less than 3h to complete.

I do not split the model before reconstruction nor use for theses blocks the Ultra option.

Any possible leads toward a solution :) ?

Thanks !

Kind regards,

Florent

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Pierre Diebolt — Thu, 06 Oct 2016 14:50:43 GMT

Hi Florent,

In order to make sure this card (GTX 980) is well used by ContextCapture could you check the following :

- Run CCSettings.exe from C:\Program Files\Bentley\ContextCapture\bin folder
- Click on System information tab
- Can you send a screenshot of the Display adapters ? if you have 2 adapters there is chance contextcapture is not pointing to the NVidia card but another one (intel chispet for example)
- Also can you click on "start benchmark" and note the score you obtain ? For information I have the same GTX 980 and same drivers version (and updated with latest windows 10 update too) and my score is 119.8/100

If your card is OK, can you tell me more about the project you are running ?
- How many photos and their resolution if possible (Gigapixel value should be fine too).
- Do you have blocks or do you split the model before you submit the reconstruction ?

Also please note - in case you changed it - that there is great difference of performance between the geometric precision options:
- <Ultra> option is taking much longer than <Highest> and <Highest> much longer than <High> etc...

Best regards,
Pierre

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Florent Poux — Thu, 06 Oct 2016 13:02:52 GMT

Theses are my results. Semms strange that so few memory of my GPU is used, or ?

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Oto — Thu, 06 Oct 2016 09:47:21 GMT

What is GPU load while processig if using GPU-Z tool?

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Florent Poux — Thu, 06 Oct 2016 08:52:09 GMT

I have a similar hardware configuration (OS:Win10 Pro with last update, RAM:32GB, GPU: GTX 980 (driver 372.90)) and after reinstalling CC, all the drivers, the error doesn't show at start-up. However, processing takes much too long, 7 to 10 times longer than usual....
I still investigate, but if you have a solution I would be eager to know about it...

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Gregory Moreno — Tue, 04 Oct 2016 05:01:34 GMT

I tried that but with no luck. Please let me know if you had success. I found processing to take 2 even 3 times longer after the update.
I was having other problems with Windows also though. Search not working, default app problems, blank start menu etc.

I'm going to wait for a while before I upgrade windows again, hopefully some of the problems will be sorted by then.

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Oto — Mon, 03 Oct 2016 10:52:02 GMT

Yes seems to be after so called anniversary update to Version 1607 (14393 build).

Will try to reinstall GPU drivers and ContextCapture.

RE: [ContextCapture] Windows timeout detection and recovery (TDR) error

Gregory Moreno — Mon, 03 Oct 2016 10:22:31 GMT

Is this after the Windows 10 Anniversary update?
I had a few problems after updating and this was one of them. Programs loaded very slowly, they would hang for a few minutes or just not load at all. I have rolled back the update and have no problems with context capture or others