Support forum for DG Tools

Hi, I just rebuilt a PC which broke a couple of weeks ago. Fresh Win7 Home Premium 64bit, nvidia driver 296.10, inserted a lower model card (MSI VNGT220GT-MD1G). It's stable.

Obtained a new DGdecNV key for this PC. When I open a .mpg file in DGdecNV it gives me the blue screen of death and crashes the PC. It works on another PC with an 8800GT.

Any assistance appreciated.

Does it happen with 2041 and 2042RC1?

Does it happen with other CUVID enabled applications?

Can you open DGIndexNV, don't open a file, but just open the Options/List GPU Devices, and then give me a screenshot of it? Thanks.

OK attached. FWIW, the 2042RC1 works without problem. Happy to try other applications if you indicate which one(s) to try.

edit: confirmed 2041 opening same .mpg file leads to BSOD within 10 secs.

You say 2042RC1 works fine? I would suggest using that version, then.

Hi! Then I am not the only one with this problem: Gigabyte GT220 + Nvidia 296.10 or 295.78. I get BSOD all the time with any of these drivers + DGDecNV 2041 or 2042. I reinstalled the old nvidia 266.xx driver and 2041 works fine again, 2042 doesn't even start, new driver would be needed for 2042.

photo of the BSOD message:

Can you try 301.24 + 2042?

Yes, I will give you a feedback after trying!

neuron2 wrote:Can you try 301.24 + 2042?

Groucho2004 wrote:

invictus wrote:Hi! Then I am not the only one with this problem: Gigabyte GT220 + Nvidia 296.10 or 295.78. I get BSOD all the time with any of these drivers + DGDecNV 2041 or 2042. I reinstalled the old nvidia 266.xx driver and 2041 works fine again, 2042 doesn't even start, new driver would be needed for 2042.

Google "nvlddmkm.sys" and check the remarkable number of BSOD reports. DGDecNV may not be the source of your problems.

Only with GT 220, with DGDecNV... and not a DGDecNV problem... quite impossible.

neuron2 wrote:Can you try 301.24 + 2042?

So, here's what happened with 301 and 2042: DGDecNV starts, I add the .264 file and then the app is not responding, but at least no BSOD. 2041 is fine again with 301 driver. Anything else I can do?

You can try the latest dev driver:

http://developer.nvidia.com/cuda-downloads

CUDA for Windows, Step 2. Grab the appropriate driver and try it.

Also, are you running the 32-bit or 64-bit DGDecNV stuff? Is it DGIndexNV that becomes nonresponsive? With 2042, are you using the cubin's that ship with it?

This is interesting, but now 2042 works fine with 301 beta driver...

Maybe we are discovering that the CUDA 4.2 cubins I ship with 2042 require the latest 3xx series driver. I haven't had any problem using them with 2xx series drivers, however, but your experience suggests that may not be universal. We are in a transition period to Kepler/CUDA 4, and your experience/feedback is valuable for helping us to navigate those waters. Thanks for your assistance and patience in helping us to sort this out.

You're welcome and thanks for the help!