Twinmotion crashes PC when exporting and just general browsing around

LicenseAdmin · April 30, 2024, 2:56am

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.

LicenseAdmin · April 30, 2024, 3:58am

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 ***