Topic: “Unable to initiate GPU-based renderer…” Nothing fixes it

This problem is in Whirligig. MPC is fine. Your suggestion of using Driver Display Uninstaller doesn’t resolve the issue. After reinstalling Nvidia the same “Unable to initiate GPU-based renderer…” error appears. CCleaner didn’t fix it, neither did reinstalling SVP nor updating Whirligig.

So is it possible to make this damn problem go away?

  • MAG79
  • SVP developer
  • Offline

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

What the error you get now?
We need full text of the error with error number.
Or you can send us SVP logs, it will be better: SVP menu - Information - Send problem report....

  • Thanks: 97

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

Legion wrote:

CCleaner didn’t fix it

Mistake 101. CCleaner doesn't fix anything. Registry cleaners don't fix even if they say so. At best they clean without no harm... at best.

4 Reply by Legion (edited by Legion 13-04-2019 13:56:57)

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

MAG79 wrote:

What the error you get now?
We need full text of the error with error number.
Or you can send us SVP logs, it will be better: SVP menu - Information - Send problem report....

I'd been using SVP in Whirligig for a couple of years without this problem.

Log attached.

Post's attachments

log.txt 27.5 kb, 366 downloads since 2019-04-13 

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

> I'd been using SVP in Whirligig for a couple of years without this problem.

so, what changed?

> initialization completed in 131810 ms

2 mins for the initialization hmm this's not normal

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

I don't know what changed. It doesn't happen every time I open Whirligig, about 80% of the time.

What takes two minutes for initialisation?

What is the actual problem? Is it a problem with Nvidia, Avisynth, SVP?

  • MAG79
  • SVP developer
  • Offline

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

> What takes two minutes for initialisation?
It is information from your log:

Main: initialization completed in 131810 ms, but still waiting for the screens measurement...

Some issues with screens detection.

Error in your log is:
unable to init GPU-based renderer - code 262138
unable to init GPU-based renderer - code 262139
It is OpenCL error. for example

code 262139 is error of clCreateContext()
CL_OUT_OF_RESOURCES: if there is a failure to allocate resources required by the OpenCL implementation on the device

OpenCL is a part of GPU drivers. So, firstly you need to reinstall NVIDIA drivers. With clean install options.

> Nvidia, Avisynth, SVP?
NVIDIA. 99,9%

8 Reply by Legion (edited by Legion 14-04-2019 12:04:49)

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

MAG79 wrote:

So, firstly you need to reinstall NVIDIA drivers. With clean install options.

I already mentioned that I used DDU - several times in the process of reinstalling the current Nvidia driver and then the latest version – clean installs every time.


Having updated/reinstalled everything without success I turned my attention to Whirligig, as I never have this problem with MPC-BE. I installed an older version of Whirligig, played around with it, constantly opening the programme and loading videos for the last 24 hours, and there hasn’t been a single instance of this so-called Nvidia problem to date. To make sure, I reinstalled later versions of Whirligig and the “Unable to init…” was back. Went through the same process of installing the older version and the issue disappears, hopefully for good.

So as far as I’m concerned it’s a Whirligig problem. I’ll drop a line to the developer.

Re: “Unable to initiate GPU-based renderer…” Nothing fixes it

Never seen such a problem before (with gtx 1070 + rift), also re-checked now with the latest Whirligig (version 4.731) and gtx 2070 - works just fine 10 of 10 attempts.