Archicad 27 BIMCloud - The Project on the server has been damaged problem -

[Sefa Yakut]

Hello everyone,

I have been having a problem for a long time and this issue affects our workflow as an office.

When another user tries to join the project I shared via BIMCloud Basic, he/she gets this error. The interesting thing is that this problem is present on some computers but not on others and this situation is not stable. The computer that has the problem can work the next day without any problem. This issue has become quite annoying. We have 9 licenses in the office and we cannot work teamwork efficiently.
We have tried many methods. We have changed the file name, re-shared the file, removed and re-added linked libraries, cleaned up local data, but this solution has been nothing more than temporary. After a certain period of time, we continue to have the same problem.

 

 

[Gil Magno]

We've encountered the same issue. While we can open the BIM model with older generation Intel processors, we are unable to do so with the latest 14th Gen Intel processors

[Laszlo Nagy]

Here is what Grok answered me about Intel's 13th and 14th Gen CPU issues:

"Intel’s 13th and 14th generation CPUs, part of the Raptor Lake and Raptor Lake Refresh lineup, have faced significant stability issues that have caused quite a stir among users. The main problem stems from something called "Vmin Shift Instability," where a glitch in the CPU’s microcode causes it to request incorrect voltage levels—often too high. Over time, this excessive voltage can degrade the processor, leading to crashes, system instability, and, in some cases, permanent damage. This isn’t just a minor hiccup; it’s been a headache for gamers, professionals, and even data centers running these chips.
The issue primarily affects desktop processors with a base power of 65W or higher, including high-end models like the Core i9-13900K and i9-14900K, but also potentially mid-range ones like the i5-13600K. Reports of crashes started popping up in mid-2023, especially in demanding scenarios like gaming—think Unreal Engine titles where shader compilation would tank the system. Early on, some game developers even suggested workarounds like underclocking, but that was just a Band-Aid.
Intel’s response has been a slow burn. They first acknowledged the problem in early 2024 and pinned it on motherboard makers pushing power limits beyond spec. By July, they identified the microcode flaw as the root cause and rolled out a series of updates—culminating in the 0x12B microcode patch—to correct the voltage requests. This fix, delivered via BIOS updates, started hitting systems in late 2024. Good news for new chips: if you apply the update early, it should prevent the issue entirely. Bad news for older ones: if your CPU’s already showing instability, the damage might be baked in. Think of it like overcooking a steak—once it’s charred, no amount of seasoning fixes it.
There’s more to the story, though. Some early 13th-gen chips also had a separate manufacturing defect tied to via oxidation, which Intel says they fixed in 2023. They insist it’s not related to the voltage mess, but it’s added fuel to the trust fire. Affected users can RMA their chips, and Intel’s extended the warranty on these processors to five years, which is a nod to the severity. Still, there’s no recall, and no clear way to check if your chip’s silently degrading before it starts crashing.
The fallout? High return rates—reports suggest 13th-gen chips were sent back four times more often than 12th-gen, and 14th-gen three times more. Gamers and builders are wary, and some are jumping ship to AMD’s Ryzen 7000 series, which haven’t had these headaches. Intel claims the latest patches put the issue to bed as of October 2024, but skepticism lingers—especially for those with chips that ran hot and hard before the fix. If you’ve got one, update your BIOS ASAP. If it’s already acting up, contact Intel support. Otherwise, you might be rolling the dice on how long it lasts."

So, it seems that solution could be to update your system's BIOS. but it may or may not fix the issue entirely. 

If you have guarantee for the CPU, returning it may also be an option (and getting a new one that is fixed, I guess?)