Archicad 28 Direct3D Runtime Error

[ETSaum]

Archicad 28 is constantly freezing or crashing, diving a Direct3D / graphics card error.

Archicad 27 and Archicad 26 do not have the same problem.

I've updated graphics drivers, and uninstalled / reinstalled Archicad to no avail.

I get the same error every time; sometimes, it's within seconds of opening the program. Other times, it can take several minutes. But it happens multiple times a day.

'Direct3D Runtime received a Device Removed Message  DXGI_ERROR_DEVICE_HUNG'

That's typically an issue with either the graphics card itself or the graphics card's connection the rest of the machine. However, this is the *only* program experiencing the problem, which is usually indicative of a glitch in the program or an incompatibility between the program and the graphics drivers.

These are two of the smallest projects I've ever done in Archicad, and the only two on 28 so far. Archicad 28 appears to be sending conflicting instructions to the GPU, which causes it to hang. No other programs are effected when it happens; in some instances, when it happens in one Archicad 28 file, it doesn't even impact the *other* Archicad 28 file I've got open.

Dell XPS 15 9530 with NVIDIA GeForce RTX 4060 Laptop GPU.

Archicad 28.0.2 (3110)

Operating system used: Windows

[Laszlo Nagy]

I asked Grok about these two Registry values because this starts to seem to me like some deep-level system tinkering. Here is what it says:

"Note: Microsoft documentation emphasizes these are primarily for driver developers during testing/debugging, not routine end-user tweaks. Increasing the values can mask underlying driver/hardware issues (e.g., actual hangs, overheating, or bugs) and may reduce system stability in some cases. It's safer to address root causes like updating drivers, checking hardware temperatures, or optimizing applications first."

[Harvey Fontanilla]

Good day,

We are currently experiencing issues with Archicad 28 on our workstations equipped with Intel Arc graphics cards. The error occurs consistently across 4 workstations with identical specifications:

Workstation Specs:
Processor: AMD Ryzen 7 9700X
RAM: 32 GB
GPU: Intel Arc B580 12GB
OS: Windows 11

Issue:

This error shows up even if the GPU Driver has been updated to the latest version

Could you please confirm if Archicad 28 officially supports Intel Arc B580 GPUs? If not, are there any recommended workarounds, driver versions, or settings we can apply to avoid this issue?We appreciate your assistance and look forward to your recommendations. Thank you.

Regards,
Harvey

Operating system used: Windows 11 25H2

Moderator edit.

This post merged with similar topic

[Barry Kelly]

@Harvey Fontanilla 

I merged you post with another on the same topic.

It is a known issue and there is a lot to read through.

In particular look at this post ... https://community.graphisoft.com/t5/Installation-update/Archicad-28-Direct3D-Runtime-Error/m-p/66678...

Barry.

[jamesMorris]

Your Intel GPU is officially supported, since the system requirements only states: 

"DirectX 11 compatible graphics card"

Still think that a Intel GPU is a bold choice for ArchiCAD. 

Just to give you a feeling for it: when we switched to AMD 1900X CPUs back in 2019, support basically told us that we are using exotic hardware and attributed some issues to that. 

[Dani11]

Hello everyone,

I am experiencing a serious issue with Archicad 28. The program runs normally for about 2 minutes, but then the following error appears and the application freezes (stops responding), becoming unusable:

“The Direct3D runtime received a device removed message. Reason given was: DXGI_ERROR_DEVICE_HUNG”

My system specs are:

• GPU: AMD Radeon RX 6600M
• Operating System: Windows 11

This happens consistently, making it impossible for me to work.

I have already tried lowering the graphical settings within the software and also updating my graphics card drivers, but the error still occurs.

Has anyone experienced this issue or knows how to fix it?
Any help or suggestions would be greatly appreciated.

Thank you in advance.

Moderator edit.

This post merged with similar topic

[runxel]

There has been an ongoing issue with sloppy nVidia drivers, but I cannot remember anybody reporting similar issues with AMD.

Are you by any chance on a laptop? If so you can try to disable the internal GPU. One common error is that Windows wants to "smartly" manage energy consumption by switching graphics on the fly. Your description on that it works for the first minutes is remarkably close to that. The switch then goes wrong and Archicad is left with no device to speak to.

[Barry Kelly]

@Dani11 

I merged you post with another on the same topic.

It is a known issue and there is a lot to read through.

In particular look at this post ... https://community.graphisoft.com/t5/Installation-update/Archicad-28-Direct3D-Runtime-Error/m-p/66678...

Barry.

[Kevin Bald]

[Moderator: Translated from German to English]

Hi Guys,

So maybe I found a way to fix this Problem, i created an advice which options to change:

A. NVIDIA App:

Disable the NVIDIA overlay and the automatic improvement of detected programs.

Install the Studio driver or the legacy driver and test the result.

B. Registry:

In regedit.exe, navigate to --> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers

Create three 32-bit DWORD entries directly in this directory:

- TdrLevel 0 (Decimal)

- TdrDdiDelay 3c (Hexadecimal)

- TdrDelay 3c (Hexadecimal)

C. NVIDIA Control Panel:

Disable anti-aliasing:

NVIDIA Control Panel --> Manage 3D Settings --> Program Settings --> Select the problematic Archicad (27 in our case)

Disable Antialiasing FXAA, Antialiasing Gamma Correction, Antialiasing Transparency, and Antialiasing Mode.

If its still not solved, you can further investigate dxdiag.exe, and make sure to restart after a, b and c.

Greetings,

Kevin Bald from Germany Munich

[Laszlo Nagy]

I asked my AI chatbot (Perplexity) about whether it is safe to create and change these values and this is what it said:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

Short answer: changing these keys is technically possible but not “safe” in the sense of recommended default behavior, especially setting TdrLevel = 0 (disabling GPU timeout detection). It’s something you only do as a targeted workaround when you fully understand the risks and are willing to accept them.

What these settings do

In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers:

• TdrLevel

  • Controls whether Timeout Detection and Recovery (TDR) is active.

  • Default is 3 (“recover on timeout”), which means Windows will reset the GPU driver if it hangs longer than the delay.

  • Setting it to 0 disables detection and recovery completely (“TdrLevelOff”), so the OS will not try to reset a hung GPU.

• TdrDelay

  • Number of seconds the GPU can block before Windows decides it has timed out.

  • Default effective value is 2 seconds when the key is absent.

  • Increasing it (e.g. to 10, 20, 60) gives long-running GPU workloads more time before a reset.

• TdrDdiDelay

  • Extra grace period (in seconds) the OS waits for the driver to return control after a timeout condition.

  • Default is 5 seconds when the key is absent.

  • Raising it (e.g. to 60) can help if the driver needs more time to clean up.

The proposed values:

• TdrLevel = 0 (decimal) – disables TDR detection/recovery.

• TdrDelay = 0x3c (hex) = 60 seconds.

• TdrDdiDelay = 0x3c (hex) = 60 seconds

Microsoft’s stance and “safety”

Microsoft explicitly documents these keys for driver developers and advanced testing; they state that end users and applications should not generally manipulate them outside of targeted testing or troubleshooting.

Concrete recommendation

1. If your question is literally “is this safe in the general sense?” – No: disabling TDR (TdrLevel = 0) is not what I’d call safe for a general-purpose workstation. It is an aggressive, high-risk workaround that you should only use if you accept possible system freezes.

2. If you want to reduce TDR errors for GPU-heavy apps, the broadly recommended path is:

   • Keep TdrLevel at default (3).

   • Set TdrDelay and TdrDdiDelay to a higher but reasonable value (e.g. 20–60 seconds, in decimal).

3. Always document what you changed and how to revert: removing those keys, or restoring TdrDelay = 2, TdrDdiDelay = 5, returns default behavior.

[jamesMorris]

ai nonsense. 

IMHO disrespecting the valuable time of other forum members.

Even worse, it is coming from a mod. 

If you can't help yourself posting AI slop, please at least follow basic AI etiquette.