I just reinstalled my operating system and of course, Unity. When I am trying to open it, at the splash screen the program crashes. I was using the same OS before and Unity was working properly.
I have already tried the following: - adding -force-d3d11 to the target. - running as administrator. - running with graphics processor: High-performance NVIDIA processor. - reinstalling Unity3D in the default location. - reinstalling Unity3D in a different location.
Note: I looked for the Editor.log file at “C:\Users\Alin\AppData\Local\Unity\Editor” but the folder is empty.
Could you please post a crash dump if you can find it?
If you see the built in Windows Error Reporting dialog then there’s a crash dump we can possibly just fetch. It’s located in your C:\Users<your user profile here>\AppData\Local\CrashDumps (this may be a hidden directory, so you need to show hidden items/files accordingly in your Explorer view)
Very odd. I’m assuming this was grabbed with some dialog open, but there is no “crash” in this case. It’s waiting on loading a library during the case of checking computer information for license checking. Its stalling on checking on the win32_bios version via WMI.
My curiosity would be, can you run powershell, and run “get-wmiobject win32_bios” ? (We’re effectively doing this call via code)
Something is interfering there. I’m not having much googling much of folk having such issue, but did come across some folk having issue with Asus PCProbe? Really not sure how that may or may not interfere.
Okay so I ran powershell and pasted in there what you told me to. Here’s the result:
SMBIOSBIOSVersion : X550JK.303
Manufacturer : American Megatrends Inc.
Name : BIOS Date: 10/08/14 09:51:55 Ver: 04.06.05
SerialNumber : EBN0CV46778247E
Version : ACRSYS - 1072009
Also, I installed 5.0.3 to be able to continue working on my project. If you guys have no idea how this can be fixed then I can just use 0.3 instead (hoping there are no big differences between those two versions).
One last question - does the 32 bit build work instead for 5.1 ?
The dump doesn’t have a clear smoking gun of something for us to fix.
Could you also confirm you took the Unity.exe dump with the crash dialog open? Otherwise, perhaps we’re just looking at a perfectly valid state before it heads off to crash…
I have the same crash as Alineshh. I’ve just installed a totally new computer (see dxdiag), and Unity 5.0.4f1 and 5.1.2f1.
5.0.4f1 works fine, but 5.1.2f1 isn’t working at all.
I have the graphic drivers, directx, and windows up to date.
Unity dump file :
get-wmiobject win32_bios result :
SMBIOSBIOSVersion : F3
Manufacturer : American Megatrends Inc.
Name : BIOS Date: 01/29/15 17:06:54 Ver: 05.06.05
SerialNumber : To be filled by O.E.M.
Version : ALASKA - 1072009
Dxdiag attached to this post
It’s kinda problematic for me as I bought a new computer to work on the Oculus version of our game, and we need to switch to the native integration. I’ve tried with 5.2.0b6, and it’s crashing too.
