Crash and autoreboot

It seems, there can be also problem with number of your cores. 8 cores * 2 hyperthreading * 4 gb of ram per thread = 64gb ram for a good performance in high compute calculation. Otherwise it is swapped on C disc.
Also, could you test disabling 4 cores/ 8 threads or disabling hyperthreading in your BIOS? and turn the reconstruction test again?
One more thing I would try is to manually set windows swap to 150% of your current RAM so you would have 32GB+ 150% on windows swap (keep in mind to use an SSD disk for that when you will all the time have at least 50 GB of storage left)
How To Manage Virtual Memory (Pagefile) In Windows 10 | Tom’s Hardware
The minimum and maximum size of the Pagefile can be up to 1.5 times and 4 times of the physical memory that your computer has, respectively. For example, if your computer has 1GB of RAM, the minimum Pagefile size can be 1.5GB, and the maximum size of the file can be 4GB.
By default, Windows 10 automatically manages the Pagefile according to your computer’s configuration and the RAM present in it. However, if you ever face lagging while working on Windows 10, or you start getting the PAGE_FAULT_IN_NONPAGED_AREA or KERNEL_DATA_INPAGE_ERROR Blue Screen of Death (BSOD), managing the size of the Pagefile manually is the first thing you should look for.
And one more thing, there is new [pre-release](Redirecting... tn =-UK-R&c%5B0%5D=AT2bxJOa48xog5do4fQfWTChoBbkFmVhZmSlg7E-3rVepvfcxjxIGZFo5Mf_ZUkHTesdeqZzA_Ifo1HOptIrsnn_zS5l-jMMYJkKkbxpawX5QjRkw0bAPueQkZRLLpoptTxn5ngjSFdXKVJSURVXdXi7jV_EsmmWt-o), which has different way, how to compute model. You can try it, but it is just pre-release.

Regarding to the video, can you upload it on Wetransfer and send me a link to it?

I try with disabling Hyperthreading with 4 and 6 and all active processor cores, and with Hypertheading enabled with 4 and all active processor cores.

Same results unfortunately.

I will follow along your indication about the Pagefile and let you know asap.

Then, just in case, will test the new pre-release.

The video of the crash has been taken with Hyperthreading ON and all cores active. For your information, this setting keeped the sistem running for more than 1 min before crashing, while the other settings trials failed in few seconds. Here’s the link

https://we.tl/t-oEcN2EfR7z

Just test it out after the change of min and max size of Pagefile according to the size of my 32768 MB RAM (min 49152 max 131072).

Kept 2:23 min, then chashed. Here the link:

on OS ssd (C:), same of Pagefile, I still have 180GB of space

Sorry, but I get this message after instal.

I don’t understand why your new pre-release link drive me to download a version, RealityCapture-1.2.0.16575-Tarasque.msi, which is already outdated since 1.2.0.17385 has been officially released.

Hi, that crashes seem strange. Can you share your dataset with us? Are you able to test that dataset on another machine? 

Regarding that link, it is older one, to download the actual release you can do it here: https://www.capturingreality.com/DownloadNow

 

We have 1 machine with such good performance, and it’s the one I’m using to test your software.

This issue happens with not just my dataset but with others as well, for exemple this free dataset I found on your website.

This seems like a HW issue, probably with GPU, as it is in reconstruction step.

Can you try something of this: https://www.dell.com/support/kbdoc/sk-sk/000178112/alienware-systems-random-blue-screen-with-no-error-code

Also, can you try older GPU driver version?

 

Hi Ondrej,

thank to your support and help I found out it was a hardware issue:

My Nvidia Geforce 2080Ti in a Normal details mesh building faces peaks of consumption which were too high for the standard power supply of 500W. I replaced it with a 700W one and it works fine.

Hope this could help you improving your sw as well as anybuddy facing this same issue

Bye!

Hi,

thank you so much for letting us and other users know the solution.