SmoothVideo Project — SVPmanager won't start on Windows 10 14251

Re: SVPmanager won't start on Windows 10 14251

null@example.com (radragon23) — Thu, 04 Feb 2016 13:11:58 +0000

Indeed it is. Thanks for the support Chainik.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (river) — Thu, 04 Feb 2016 02:37:33 +0000

It's fixed in 14257

Re: SVPmanager won't start on Windows 10 14251

null@example.com (radragon23) — Mon, 01 Feb 2016 10:39:11 +0000

I'm not too worried about it. Will probably be fixed with the next windows build. If not then ehh.. Slight annoyance I can't watch anime in 60fps for a while but oh well lol. Will try some other things and post if I find a fix.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (Chainik) — Mon, 01 Feb 2016 10:33:26 +0000

if this's a Qt's issue it's probably not too late to post a bug report before 5.6.0 release...

Re: SVPmanager won't start on Windows 10 14251

null@example.com (radragon23) — Mon, 01 Feb 2016 10:26:36 +0000

Yeah, I figured. And those do not work. Same error as stated above.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (Chainik) — Mon, 01 Feb 2016 10:24:04 +0000

here they are

5.2 is not an option cause we really need HighDPI screens support

Re: SVPmanager won't start on Windows 10 14251

null@example.com (radragon23) — Mon, 01 Feb 2016 10:21:41 +0000

Same error with 5.6.0 beta files. 5.2 will probably work if rebuilt but who knows. It will probably be fixed in the next insiders build but that could be a while.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (radragon23) — Mon, 01 Feb 2016 10:01:48 +0000

Upload them and I will. I tried using 5.2 libs but it seems incompatible without rebuilding from source.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (Chainik) — Mon, 01 Feb 2016 09:58:21 +0000

BTW you can try to replace Qt libs with the latest 5.6.0 beta build...

Re: SVPmanager won't start on Windows 10 14251

null@example.com (radragon23) — Mon, 01 Feb 2016 06:51:00 +0000

I should mention, it will probably be fine once they fix the memory bug in this build.(probably?) So I shouldn't really say it's an issue with Qt5.5.. just that it conflicts with the latest build for whatever reason.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (river) — Mon, 01 Feb 2016 06:48:52 +0000

Thanks. I almost reset my Windows.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (radragon23) — Mon, 01 Feb 2016 05:04:34 +0000

I am also encountering this error on the latest build. It is indeed an issue with Qt5.5. Apparently if the program is compiled with Qt5.2 it will then work.(At least that is what occurred with another program that uses Qt) Restarting does not fix the error.

Re: SVPmanager won't start on Windows 10 14251

null@example.com (river) — Mon, 01 Feb 2016 04:51:50 +0000

Faulting application name: SVPManager.exe, version: 4.0.0.60, time stamp: 0x00000000
Faulting module name: Qt5Core.dll, version: 5.5.1.0, time stamp: 0x777a675f
Exception code: 0xc0000005
Fault offset: 0x0024b7f7
Faulting process id: 0x16e4
Faulting application start time: 0x01d15ca9bf80abd2
Faulting application path: C:\Program Files (x86)\SVP 4 Dev\SVPManager.exe
Faulting module path: C:\Program Files (x86)\SVP 4 Dev\Qt5Core.dll
Report Id: 9fe7e011-b201-4445-9566-2eb449777305
Faulting package full name:
Faulting package-relative application ID:

I found the error, it looks like something's wrong with Qt

Re: SVPmanager won't start on Windows 10 14251

null@example.com (Chainik) — Thu, 28 Jan 2016 08:50:23 +0000

as Google tells us, 0xc0000142 error is usually about some system dlls mess or broken user account data after upgrade

> 14251

Known issues
...
Due to a recent memory management change, you may see periodic app crashes or other memory related app errors. The workaround is to reboot your PC.

that's great!

SVPmanager won't start on Windows 10 14251

null@example.com (river) — Thu, 28 Jan 2016 08:34:09 +0000

I got a 0xc0000142 error when starting the SVPmanager.
Then I tried reinstalling the SVP, video card driver and VS redistribute 2013, but nothing helped.

Now I roll back to the 11102, everything back to normal again.