Every tie i try to open a level that i downloaded from LAB or even if i try to import on editor from that content any meshes it always crashes i even tried to make an project default level to be the level of content i dovloaded but still keeps crashing , i do have 2 different PC’s both are with 4080 Super one has i9 9900K and the other one which im having this problem has 14900K , on that older PC i do not have any problem , but with this one i cant work at all it keeps crashing everytime i try to open a different level or if i try to add meshes on editor from that content i got on FAB
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 783]
Array index out of bounds: 5260 into an array of size 0
if these issues are on similar installs of UE (if this is not the case would it be possible to try a clean Engine install without plugins as it may be a plugin causing this though I am doubtful)
what follows is if the problem persists after verifying it is not immediately engine plugins:
where the issue is with a system running a 14900K how long has it been running, before and/or after the micro-code/BIOS update?
if the processor has been running in a “higher” power state with the older micro-code/BIOS then it may have degraded, and one of the most common parts effected was the PCIE interlink showing as a “GPU issue”
to rule out an actual GPU issue is it possible for you to swap the GPUs between the systems? (at the very least try the GPU from the working system in the one having the problem)
if the RAM is compatible maybe try taking the RAM from the working system and try it in the system having the issue.
the “Good” news if the problem is the CPU is that Intel was at least promising comprehensive almost no questions asked replacements though you may need to get in touch with the retailer you got the CPU from (I have not tried this my self as I did not have one Intel’s processors of the affected generations)
you may need to contact a PC repair shop to see if they can help you do A-B testing for your CPU and RAM (the motherboard being the culprit is very rare unless it is 12-VO then it can be of greater concern)
Hey there @TheThrillogy1! I agree with Gard here in that you may need to do some A/B testing with parts to rule out hardware (once we exhaust all software possibilities). There have been some known issues with the 13x-14x series of Intel CPUs as mentioned, that aren’t always so pronounced or even indicated as CPU issues and can sometimes cause issues in other areas muddying the waters.
Reading the call stack indicates that Nanite’s vertex buffer is having issues getting the correct (or any) vertex array. Does disabling Nanite or dropping the RHI to DX11 stop this error from occurring?
I tired the DX11 and two scenes worked without problem ,but when i try to open some blue prints it crashes and also it keeps crashing in one other level from other content , disabling nanite it makes file project unable to open at all it crashes at launch … yeah idk i may try to check CPU cause GPU is new on both systems Pro art 4080 Super , i try to update bios and see what it happens
All its fixed, i just had to do a BIOS update, and DDU the graphic Drivers (this part i don’t understand why it helped cause i had same version of graphic drivers) and is worth mention that i also disabled some default Windows APP-s i don’t know if they were necessary to be disabled but in the end it worked perfect, thankyou so much guys you are wonderful
to the best of my knowledge the BIOS update prevents further damage by limiting the voltage curve it does not reverse the damage done.
The damage that has been caused is already done, and you shouldn’t be surprised if similar issues appear in the future requiring either further voltage limits or replacing the CPU. I would still suggest looking into the Intel warranty replacement for the 14900K where these are signs that would align with what triggered them finally offering the warranty and BIOS things in the first place.