Unity 6.x crashes entire Windows ARM laptop

Unity Engine
, ,
1

Hello,

I tried installing Unity on my surface pro 12 with the snapdragon plus chip.

Any time I create even a new project. It opens the editor, then hangs a little bit, then my entire system shuts down, and I have to boot to bios to be able to use my laptop again

I thought at first it was my fault installing the x64 version instead of the ARM version. So I reinstalled it and made sure to click on arm in unity hub, but it still shows up as x64. Here let me show an example. It’s so weird

20251118_173231
20251118_1732311920×1440 369 KB

Isn’t that odd? It clearly shows that it’s installing the arm version in the installation tab but in the installed editors section it shows x64. I tried multiple times deleting it and specifying directly that I want to install the ARM version but it doesn’t persist

I thought it was just a bug in Unity hub as well, but even installing specifically the ARM version directly without Unity Hub at all, the error persists

2

That’s currently a bug. I think that’s only displaying the wrong string but I only casually picked up on that in another thread a couple days ago.

The crash may not be related to that. Check the editor.log to check for details about the crash.

3

Yeah, I found out it’s an official bug and saw that the beta update I think 6.2.15 or something is supposed to solve it. So I updated and yeah it now shows that the correct architecture is represented so now it’s ARM finally…

But that didnt end up stopping unity from crashing my laptop when creating a new project. I would look up the error in the future thanks for the suggestion, but I just ended up resetting the laptop to return it before the return window closes. I hate macOS but I doubt I will deal with as many weird janky stuff on there.

I wish I could figure it out for future people with the same issue though :confused:

4

Same here, brand new Surface 12, Unity will hard reboot the system after launching in to a project (even a new one) also the hub is acting weird, I go to install the Arm version but it does not show as such.

5

I have a similar issue, a new Surface with Snapdragon(R) X 12-core X1E80100 and 32GB of RAM.
I tried 6000.2.7f2, 6000.3.0f1, 6000.0.63f1, 6000.0.33f1, all crashed the PC after using the editor for a few seconds.
It was working well before (I last tried it half a year ago).

6

I think I found the solution…

I tried disabling the new “AI Automatic super resolution” from Windows, and now it works for me.

In Windows Settings, go to System > Display > Graphics: there is a toggle for “Automatic super resolution”.

But, I tried Unity 6.3 and 6.0, and it only works for 6.0… not sure why. Maybe Unity should investigate this.

TL;DR: disable windows AI super resolution + use Unity 6000.0.63f1.

Hope this solves the issue for everybody :slight_smile:

7

Good find! :slight_smile:

I recall there’s another potentially problematic setting on that page, something about “optimizing”. Might even be the same, merely renamed - since today every “optimization” naturally implies “AI” as in “AI Overclocking” in BIOSes - it used to be “Automatic Overclocking” or similar for two decades but these days, of course it’s “AI” based. :roll_eyes:

8

Would it be possible to get the editor log from when it crashes? There may some information in there that would be helpful. Also, in case you haven’t already submitting a bug report would be greatly appreciated.

9

I’m sorry I can’t. I ended up returning my Surface Pro because of this issue alongside other technical hurdles for other applications and ended up getting myself a MacBook instead.

Would you still like me to create a bug report? Even though I would only be able to provide the same information I included in the discussion post?

10

I did also see that there was another person who created a discussion post a week earlier with the same problem

So I am not sure if they had already created a bug report, but I wouldn’t mind making one, I just haven’t done so before and any context would have to just be figured out since I don’t own the Surface laptop where the issue manifested in the first place anymore

I think most of the help from that thread and the beginning of this one was for fixing the visual bug of whether the editor is in fact using ARM install or x64, but it doesn’t resolve the issue with Unity editor itself still crashing. I think @JLPM did include somewhat of a workaround (?) but it doesn’t seem to fix the root issue. and especially only working for 6.0 is weird also

It’s a bit embarrassing but if Unity had worked on the Surface, I would have stuck with it since I use windows for work and gaming, so I would much rather use a windows’ laptop for game dev.

11

same here – thought i was crazy – where / what logs are needed to help diag this?

12

where would these be on disk?

13

@davidro_unity won’t let me upload the logs as I’m a “new user”

14

I have the same problem where my PC restarts. This is with version 6000.3.2f1 (ARM64).
I am using windows 11, on af Microsoft Surface Laptop Snapdragon(R) X 12-core X1E80100
When it is my own small project there is no problem, but when I try to follow the "Tanks"project in Unity Learn it restarts my PC.

15

That’s unfortunate, maybe put it on a google drive or something similar?

16

I had the same exact issue and for whatever reason this is really working. Guys that are working at Unity if there is a way of how I can help you to find and fix the issue and push the fixes into next LTS 6.x version I would really like to help you all

17

If you have repro steps that are different than anything else mentioned here then definitely let us know. Otherwise logs are always helpful. If you can’t post them here or don’t want to then feel free to DM them to me and pass them on to my teammates. (I don’t have a Windows ARM machine myself)