Support forum for DG Tools

---------------------------
Warning
---------------------------
ERROR: Failed to create CUDA context on device 0

Hit Yes to continue notifying this specific error type; hit No to disable it.
Hit Cancel to suppress all further errors.
---------------------------

Occasionally happens. The only thing you need to do is to try again.

I'm calling from command line using "dgindexnv -i 20.m2ts -o 20.dgi -h -e", etc.

Any chance for an auto reattempt?

I have such issues some versions back. With newest version I had no problem. I think Don could make for you debug build to see in what stage it is happened.

@MeteorRain

We could try something like that but obviously I am averse to band-aid fixes. First, let me ask you some things.

Do you have multiple cards installed? If not, why are you forcing the device number in the INI file?

What are the cards you have installed? What nVidia driver version? Latest DGIndexNV being used (fresh downloaded)?

Is anything else going on in the background? Playing videos? Running any other scripts?

Will answer your other questions later. Hold on for a second.

You answered a question I didn't ask and none of the ones I did ask. I waited many seconds.

Sorry I was on my way to office, so post my local config first just in case you need it later -- You know, TeamViewer got hacked and I dare not to leave it running for long.

Following are the answers to your questions.

Yes I have multiple cards, one discrete GTX 950 one integrated from 4th gen i7.

nVidia driver I need to go home to get the number.

I'm using the version (fresh downloaded) about a month ago.

I have tons of programs running and I haven't reboot my computer for 3 months. Windows 10 stable channel.

No video playing at the moment.

Let me clarify: It only happens every couple days, randomly, no matter if I'm using the computer or I'm sleeping, no matter day or night, etc. Almost impossible to reproduce. Run the command again and it works perfectly.

You have "tons of programs running"?

Can you not reboot and try it with nothing else running?

And how do you run this when you are sleeping? A batch file or something?

So basically I have bunch of windows explorer running, sometimes M$ Office running, FTP client running, Sublime Text, couple consoles, etc.

It happens every couple days, and it's not that possible to have nothing else running for couple days.

Yes I'm doing batch encoding using bash and rakefile.

Since I found it stuck in the morning I now always pre-create index beforehand -- and still occasionally hit the issue when creating index in a batch.

Are you running anything else that consumes GPU memory?

I'll make a test build for you tomorrow that tries several times.

Not as I'm aware of, except the desktop itself.
nVidia, afaik, is on 358.91. (If I'm reading the correct version number.)

Just notice that dgindexnv.exe has the last modified date of 1/12.
Should I just update to the latest version first and see how it works?

Yes, please do a fresh download and test it. I will await your results before making a test build for you.

Do you have any further test results for us, MeteorRain? One of the recent updates fixed a race condition that could cause problems like yours.

admin wrote:Do you have any further test results for us, MeteorRain? One of the recent updates fixed a race condition that could cause problems like yours.

So far so good, tried encoding like 30 files and haven't hit the issue yet.

OK, thanks. Let me know if anything untoward occurs, please.

Not too bad one time per month but still happens.



Was playing a video when the task started.

One more hit right now. Almost doing nothing just have about 40 windows on the desktop.

Ctrl-C and retry worked.

Maybe you ran out of memory.

admin wrote:Maybe you ran out of memory.

I don't think so, as it sometimes happens right after an encode, so at least 3-4GB of memory is freed right before running dgnv.

And I do have 16GB of memory, not that much but not easy to be used up as well