Up Studio Crashing

[Ramatu]

Hey, I've installed the latest version of Up Studio on one of my PCs without issue. On the other one, it crashed the first time I opened it. Now, every time I try and open it, nothing happens. Have you encountered this before?

I've tried uninstalling it and reinstalling it multiple times as well as reverting to an older version. Nothing seems to change the result.

The software works on my Surface Pro 3 but not on my Alienware. Both are x64 and both have Windows 10. Any ideas?

[Marauderz]

I'm now getting this issue on my Surface Pro 3 which was fine about 2 weeks ago, just runs and crashes, this is the crash info in evevnt viewer.

Faulting application name: UPStudio.exe, version: 1.1.2.0, time stamp: 0x57982cdc
Faulting module name: ntdll.dll, version: 10.0.14393.0, time stamp: 0x578997b2
Exception code: 0xc0000374
Fault offset: 0x00000000000f73e3
Faulting process id: 0x1e74
Faulting application start time: 0x01d1f84a3b2c6fd6
Faulting application path: C:\Program Files\UP Studio\X64\UPStudio.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 5432572a-e83b-4422-90ac-eb1b95c6a2d2
Faulting package full name:
Faulting package-relative application ID:

[Solice]

I'm having this exact issue at the moment. I've attempted to run the application with every permutation of with or without Administrator rights, compatibility modes for Windows Vista, 7, and 8. At best, it shows the splash screen and crashes on that. At worst, it creates two processes (viewable in Task Manager), then immediately quits out without displaying anything or creating a task button on the task bar.

Windows 10 Professional 64-bit, all current updates installed.

Faulting application name: UPStudio.exe, version: 1.1.2.0, time stamp: 0x57982cdc
Faulting module name: ntdll.dll, version: 10.0.14393.0, time stamp: 0x578997b2
Exception code: 0xc0000374
Fault offset: 0x00000000000f73e3
Faulting process id: 0x20a8
Faulting application start time: 0x01d1f99477cea756
Faulting application path: C:\Program Files\UP Studio\X64\UPStudio.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: e2dc6782-6e7b-431e-88f2-906197f4f07f
Faulting package full name:
Faulting package-relative application ID:

[Solice]

I'm not sure what the exact issue is, but I think a recent update to Windows 10 (maybe the Anniversary Update?) seems to break it. I tried it on a computer that has not applied that batch of updates yet, and v 1.1.2.0 of Up Studio at least starts on it.

[HarryArmytage]

I am now having this exact issue on a Mac. Are you still having problems on Windows or was a fix found for it? I'm guessing that it again is linked to me updating my Mac operating software....

[ideas108]

Gang

I have a fully updated IMac in ithe ideas space I will test in the next day or so and report back

Kind regards

John

[Barry]

I got the same problem here. After the latest update UP studio crashes after a while of use. But my brother doesn't has any problems using the program with the newest version. I'm using a lenovo ideapad y 50-70 with the newest windows 10 version on it. Are there any solution's yet?

[thehumancnc]

UPStudio crashes for me to. After I was prompted for an update, the program does not work anymore even though i reinstalled an older version

[redbear]

I have the same problem. Is there a solution to this issue ?

I have tried the latest version 2.2.61.62, the 2.2.58 Beta, the earliest version on UP website 1.9.2.2, with full uninstall and %appdata% folder removal between each one.

I have installed ntdll.dll file from pan.baidu.com/s/1gfMi3uF into executable directory with no different result.

I have sfc'ed my system looking for an altered ntdll.dll file.

EventViewer returns this error information :
------------------------------------------------------------------------------------------------------------
Faulting application name: UPStudio.exe, version: 2.2.58.62, time stamp: 0x5a52ece2
Faulting module name: ntdll.dll, version: 6.1.7601.24009, time stamp: 0x5a524044
Exception code: 0xc0000005
Fault offset: 0x000000000004008d
Faulting process id: 0x108c
Faulting application start time: 0x01d3a14446a64bfa
Faulting application path: C:\Program Files\UP Studio\win64\UPStudio.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 9101aa5a-0d37-11e8-aa02-1866da424c4d
------------------------------------------------------------------------------------------------------------

Luckily the old Up2.18 software works, but why doesn't this software work ???

Any ideas, solutions for this.

My system spec is :

Intel i7-6700 @ 3.4GHz, 16Gb RAM Win7 Enterprise SP1 with AMD R5 340X and onboard Intel530 graphics cards.


Any advice would be appreciated. It seems that a lot of people have this issue, but not enough people to warrant a timely solution from UP.

[Tiertime-Elaine]

Hi Guys,

We are looking into this problem.

Please be aware that UP Studio does not compatible with operating system prior to Windows 7 SP1.

Cheers,

Elaine

[GOD]

Hi Everyone.

I have a fresh install of Win10, and after installing UP Installer_x64_2.4.22.351 it crashes on startup EVERY time and says "Crashed. Upload error messages?" the two choice boxes never get text and it just sits there for the rest of time. This is the same type of problem raised in 2018 and still no solution posted in this forum. I have this software running on a PC of same hardware and Win10 with no problems. Is there some driver / library / reliance on existing software issue going on here ?

What information do you need me to provide you to find a solution ?
Could anyone tell me if they have ever got this error message ? I can't find any other reference on forum specific to it.


I have tried the BETA and earlier versions with no luck ..

Cheers,

[GOD]

Hi everyone. my last comment hasn't yet been approved but I have found a solution that is worth a try.


Install Microsoft Visual C++ 2015 Redistributable (x64) and it works. The file is 14.5MB
and obviously the UP Studio installation is requiring files that are not standard with a fresh install. So perhaps TierTime could try running their software on a fresh PC and seeing what the issue is.

Software works for now.

Hope you publish this one as it has a solution which might help people in the same situation.