Twinmotion crashes PC when exporting and just general browsing around

I’ve run all the Windows 10 Updates, ASUS motherboard updates, GeForce updates and other driver updates along with running both the most recent version of Twin Motion and the preview release. That hasn’t resolved the issue of the the computer blue screening whenever they do exporting of photos and other general tasks in the app.

Is there a recommended and tested hardware OEM configuration for ArchiCAD and Twinmotion? The computer we’re running on currently has a NVIDIA GeForce RTX 3080 GPU, Asus ROG Crosshair VIII Dark Hero motherboard with an AMD 5950X CPU, 128GB RAM and Samsung 980 Pro 1TB SSD.

It doesn't matter whether I'm using the current preview version of Twinmotion or the most recent stable version. We've also tried different files. It doesn't make a difference.

Here's the WinDbg analysis:

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 19041 MP (32 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff806`60800000 PsLoadedModuleList = 0xfffff806`6142a210

Debug session time: Wed Feb 15 17:40:49.419 2023 (UTC - 8:00)

System Uptime: 0 days 1:07:43.040

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..................

Loading User Symbols

Loading unloaded module list

..........

For analysis of this file, run !analyze -v

14: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. Parameter 1 identifies the type of error

source that reported the error. Parameter 2 holds the address of the

nt!_WHEA_ERROR_RECORD structure that describes the error condition. Try !errrec Address of the nt!_WHEA_ERROR_RECORD structure to get more details.

Arguments:

Arg1: 0000000000000000, Machine Check Exception

Arg2: ffffc10f33d52028, Address of the nt!_WHEA_ERROR_RECORD structure.

Arg3: 00000000bc000800, High order 32-bits of the MCi_STATUS value.

Arg4: 0000000001010135, Low order 32-bits of the MCi_STATUS value.

Debugging Details:

------------------

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

*** ***

*************************************************************************

*************************************************************************

*** ***

*** ***

*** Either you specified an unqualified symbol, or your debugger ***

*** doesn't have full symbol information. Unqualified symbol ***

*** resolution is turned off by default. Please either specify a ***

*** fully qualified symbol module!symbolname, or enable resolution ***

*** of unqualified symbols by typing ".symopt- 100". Note that ***

*** enabling unqualified symbol resolution with network symbol ***

*** server shares in the symbol path may cause the debugger to ***

*** appear to hang for long periods of time when an incorrect ***

*** symbol name is typed or the network symbol server is down. ***

*** ***

*** For some commands to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: hal!_WHEA_PROCESSOR_GENERIC_ERROR_SECTION ***

*** ***

*************************************************************************

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec

Value: 3764

Key : Analysis.DebugAnalysisManager

Value: Create

Key : Analysis.Elapsed.mSec

Value: 9599

Key : Analysis.Init.CPU.mSec

Value: 4499

Key : Analysis.Init.Elapsed.mSec

Value: 78048

Key : Analysis.Memory.CommitPeak.Mb

Value: 94

Key : WER.OS.Branch

Value: vb_release

Key : WER.OS.Timestamp

Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version

Value: 10.0.19041.1

FILE_IN_CAB: 021523-12125-01.dmp

BUGCHECK_CODE: 124

BUGCHECK_P1: 0

BUGCHECK_P2: ffffc10f33d52028

BUGCHECK_P3: bc000800

BUGCHECK_P4: 1010135

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Twinmotion-Win64-Shipping.exe

STACK_TEXT:

ffffd481`f73db938 fffff806`60cb688a : 00000000`00000124 00000000`00000000 ffffc10f`33d52028 00000000`bc000800 : nt!KeBugCheckEx

ffffd481`f73db940 fffff806`5ea915b0 : 00000000`00000000 ffffc10f`33d52028 ffffc10f`2f7f3670 ffffc10f`33d52028 : nt!HalBugCheckSystem+0xca

ffffd481`f73db980 fffff806`60db8a9e : 00000000`00000000 ffffd481`f73dba29 ffffc10f`33d52028 ffffc10f`2f7f3670 : PSHED!PshedBugCheckSystem+0x10

ffffd481`f73db9b0 fffff806`60cb81b1 : ffffc10f`3d379900 ffffc10f`3d379900 ffffc10f`2f7f36c0 ffffc10f`2f7f3670 : nt!WheaReportHwError+0x46e

ffffd481`f73dba90 fffff806`60cb8523 : 00000000`0000000e ffffc10f`2f7f36c0 ffffc10f`2f7f3670 00000000`0000000e : nt!HalpMcaReportError+0xb1

ffffd481`f73dbc00 fffff806`60cb8400 : ffffc10f`2f726a10 00000000`00000000 ffffd481`f73dbe00 00000000`00000000 : nt!HalpMceHandlerCore+0xef

ffffd481`f73dbc50 fffff806`60cb7945 : ffffc10f`2f726a10 ffffd481`f73dbef0 00000000`00000000 00000000`00000000 : nt!HalpMceHandler+0xe0

ffffd481`f73dbc90 fffff806`60cba105 : ffffc10f`2f726a10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpHandleMachineCheck+0xe9

ffffd481`f73dbcc0 fffff806`60d0fb99 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalHandleMcheck+0x35

ffffd481`f73dbcf0 fffff806`60c0acba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiHandleMcheck+0x9

ffffd481`f73dbd20 fffff806`60c0a977 : 00000000`00000000 00000000`00000000 0000015d`33b3a0e0 00000000`00000000 : nt!KxMcheckAbort+0x7a

ffffd481`f73dbe60 00007ff6`31bf9b59 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x277

0000002b`44aff770 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff6`31bf9b59

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x124_0_AuthenticAMD_PROCESSOR__UNKNOWN_IMAGE_AuthenticAMD.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {035dcc87-485b-74b3-1c1b-ee50cb0c2865}

Followup: MachineOwner

---------

Hello there,

Thanks for posting in the community.

That hardware configuration should be more than enough to run Twinmotion smoothly. Something else is certainly going on with your system that we'd have to investigate if you're crashing on blank projects during general browsing/rendering.

If you could please generate a bug report here, we'd be happy to dig into this further with you:

  • https://twinmotionhelp.epicgames.com/s/case-community-page

Also, if Twinmotion crashes again without going to the BSOD, please hit Send Report. If it does send you to a blue screen, please send us the generated crash log on your bug report, which can be found here:

  • Win: C:\Users\...\AppData\Local\Twinmotion\Saved\Crashes

We'll look for your ticket and will reach out soon.