Unity 6000.2.5f1 - frequent crashes when using the editor (Windows 11 Pro)

Unity Engine
1

Hello there,

I have been experiencing frequent crashes while working on my Unity project so I am posting this message here in case some of you had had the same experiences or some guidance for me.

  • Unity version: Unity 6000.2.5f1
  • System Information:
      Time of this report: 11/24/2025, 10:45:39
             Machine name: CREATOR07
               Machine Id: {8B1E3A46-5531-4E6E-ACF9-685904239A11}
         Operating System: Windows 11 Pro 64-bit (10.0, Build 26200) (26100.ge_release.240331-1435)
                 Language: English (Regional Setting: English)
      System Manufacturer: ASUS
             System Model: System Product Name
                     BIOS: 3002 (type: UEFI)
                Processor: Intel(R) Core(TM) i9-14900K (32 CPUs), ~3.2GHz
                   Memory: 196608MB RAM
      Available OS Memory: 196292MB RAM
                Page File: 11188MB used, 197390MB available
              Windows Dir: C:\WINDOWS
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: 96 DPI (100 percent)
       System DPI Setting: 144 DPI (150 percent)
          DWM DPI Scaling: UnKnown
                 Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
 DirectX Database Version: 1.7.6
   Auto Super Res Version: Unknown
       System Mux Support: Mux Support Inactive - Ok
           Mux Target GPU: dGPU
    Mux Incompatible List: 
           DxDiag Version: 10.00.26100.7019 64bit Unicode

I have identified the crashes can happen at 3 different contexts

  • At launch of the editor
  • After loading/unloading heavy scenes
  • Or just randomly while working

I’ve attached some Editor.log files and crash dump files.
CrashReport2025-11-17_111431521.txt (238.6 KB)
CrashReport2025-11-06_164600751.txt (646.7 KB)
CrashReport2025-11-06_135317648.txt (721.5 KB)
CrashReport2025-11-06_133328399.txt (732.3 KB)
CrashReport2025-11-06_131826853.txt (635.6 KB)
CrashReport2025-11-20_102520707.txt (811.6 KB)
CrashReport2025-11-18_132117310.txt (739.4 KB)
Editor.log 18-11-2025-14-21-00.txt (2.0 MB)
Editor.log 18-11-2025-12-01-00.txt (65.6 KB)
CrashReport2025-11-17_111431506.txt (238.6 KB)

Thanks for the help.

2

Are you a) aware of the issues surrounding this line of CPUs and b) have you applied the necessary fixes available to you?
(BIOS update, otherwise ensure BIOS settings do not overclock CPU beyond Intel’s specs).

I was affected myself and it led to infrequent crashes, some less random than others. BIOS update fixed it, and did so for other users. And yes, those crashes mostly occured in Unity for some reason, probably because no other app is so taxing on the system.

3

Yes, we are aware of all the issues regarding this CPU.
It is running the latest BIOS by the motherboard manufacturer.
It has been reset to BIOS defaults after the latest flash.
Processor setting is to ‘intel Performance’ (the alternative is ‘intel Extreme’
There isnt a single extra functionality or OC profile enabled.
System is specced with an RTX 5090 to ensure maximum compatibility with a heavy unity project.
System has run prime95 + Furmark 4k test at the same time for 2 hours, no crash.
System has run a seperate prime95 2 hour memory stress test as well, no crash.
Systels runs after office hours as render node in Houdini farm, hasnt crashed or had a memory segmentation fault in any of these tasks

1 Like
4

I see you did your homework! :+1: :smiling_face_with_sunglasses:

Unlikely given your tests, but worth noting: my system was also stable with long Prime/Furmark runs, and the crashes didn’t occur until half a year in. It was really odd but I guess this is how the degradation shows. The problem of course is that it’s not repairable, once it’s there it doesn’t go away and can occur even under conservative settings.

Intel has this diagnostics tool. Not sure if reliable, but I’ll run it myself later cause my system has been mucking recently.

  at <unknown> <0xffffffff>
  at Unity.Properties.Internal.PropertyBagStore:AddPropertyBag <0x00032>
  at Unity.Properties.PropertyBag:Register <0x0001a>
  at UnityEngine.UIElements.UIElementsInitialization:RegisterBuiltInPropertyBags <0x00d2a>
  at InitializeUIElementsJob:Execute <0x0001a>
  at JobStruct`1:Execute <0x0001a>
  at ExecuteJobFunction:invoke_void_T&_intptr_intptr_JobRanges&_int <0x000b9>
  at <Module>:runtime_invoke_void__this___intptr&_intptr_intptr_intptr&_int <0x000b5>

I’ve definitely seen this stacktrace before (property bags). Try updating to the latest 6.2, my suspicion is that this may be an actual bug that’s been fixed.