Crashing on medium detail

Development Asset Creation
,
1

Hello been getting many crashes always in the same spot during reconstruction at medium detail. It doesn’t matter if i have 60 images or 200+ images. preview mesh runs fine.
I have reinstalled RC happens on most of my scans, but not all of them which is strange. Image size does seem to make it work, but not always. Caches are all cleaned out. Drivers all updated. default settings. It doesn’t matter if the images are JPGs or Raw.

everything worked properly before with no issues but in the last few weeks, this has been a major problem, I’m not sure if it has something to do with the newer version of 1.3 or even perhaps a hardware issue?

PC specs are:
CPU: 13th Gen Intel(R) Core™ i9-13900K, 3000 Mhz, 24 Core(s), 32 Logical
GPU: NVIDIA Geforce RTX4090

Screenshot 2024-03-31 124200
Screenshot 2024-03-31 124200963×662 141 KB

Screenshot 2024-03-31 132923
Screenshot 2024-03-31 132923781×686 322 KB

RealityCaptureCrash_8884_69514-667_1_3_2_117357_RC.dmp (871.8 KB)
RealityCaptureCrash_8867_21825-667_1_3_2_117357_RC.dmp (716.2 KB)

Help would be appreciated!

2

Could be multiple issues.
I’d suggest going down the list and checking.

  • First off I would try to check if all drivers are up to date.
  • Second would do a check of windows files (from command line try the command sfc /scannow)
  • Third do scan for malware (try something llke Malwarebytes)
  • Do an antivirus scan
  • Check if you are missing any critical windows updates
1 Like
3

Thank you for a quick reply, I will give this a try

4

Hello again,

I went through checklist a couple times.

  • Drivers, all up to date.
  • Windows Resource Protection did not find any integrity violations.
  • No virus or threats.
  • No needed windows updates or any missing.

just tried again with completely different images. Same thing happened at the exact same spot during reconstruction.
From what I’ve noticed, if i try roughly about 5 times and get this crash, then after around the 5th attempt my computer will Bluescreen.

Screenshot 2024-03-31 145043
Screenshot 2024-03-31 1450431697×930 245 KB

RealityCaptureCrash_8884_78461-667_1_3_2_117357_RC.dmp (721.6 KB)
RealityCaptureCrash_8884_78459-667_1_3_2_117357_RC.dmp (820.3 KB)
RealityCaptureCrash_8884_78453-667_1_3_2_117357_RC.dmp (771.3 KB)
RealityCaptureCrash_8884_78446-667_1_3_2_117357_RC.dmp (705.9 KB)
RealityCaptureCrash_8884_78447-667_1_3_2_117357_RC.dmp (454.2 KB)

I appreciate the help :slight_smile:

5

In one of the dumps I found
FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_RealityCapture.exe!Unknown

This can be caused by reading invalid memory.
It could be a memory problem.
Try running Windows Memory Diagnostic.

If you have overclocked memory then maybe try reducing the speed to the base memory speed (no OC or XMP) and see if it’s more stable.

second file seems to follow a similar error
WARNING: Teb 122 pointer is NULL - defaulting to 000000007ffde000
WARNING: 000000007ffde000 does not appear to be a TEB This dump file has an exception of interest stored in it. The stored exception information can be accessed via .ecxr. (5a54.3f84): Access violation - code c0000005 (first/second chance not available)

1 Like
6

This seamed to do the trick! Thank you :slight_smile:

I didn’t realize my ram was overclocked by default.

g.skill trident z5 rgb 64gb (2x32gb) ddr5 6400mhz
now is set to base of 4800mhz.
GIGABYTE Z790 AORUS ELITE AX motherboard
I will have to tinker with the settings to see what works best.

The windows memory Diagnostic did give me an error, saying there is hardware problem which freaked me out a little considering this is a brand new PC.

I definitely learned somethings about memory. So thank you very much for that also.

lastly thanks again for responding so quickly

  • Eric
1 Like