Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
27th September 2009, 07:58 | #404 | Link |
Registered User
Join Date: Oct 2003
Posts: 435
|
so i tried a few things and so far my issues are pointing to these files: nvcuda.dll nvcuvid.dll
i get random crashes with drivers 190.62 so i installed drivers 186.38 which seem to be the last stable ones. ran lots of deint/resize stuff with no crashes. i then put the 190.62 nvcuda.dll nvcuvid.dll in the system32 folder with 186.38 drivers and got my system to crash like it did with all the 190.62 drivers installed. back to 186.38 nvcuda.dll nvcuvid.dll and everything is good again. dont know if this helps at all really but at least i know my system is ok hardware wise.... Last edited by woah!; 27th September 2009 at 08:05. |
27th September 2009, 09:13 | #405 | Link |
Registered User
Join Date: Aug 2008
Posts: 64
|
woah!
uninstall video drivers completly and install 190.62 |reboot, unpack DG NV tools and replace dgdecode.dll in avisynth plugin derictory. make sure that you run latest cuvidserver beta 10 work as usual.
__________________
message transgoogled :) |
27th September 2009, 09:37 | #406 | Link |
Registered User
Join Date: Oct 2003
Posts: 435
|
ahh i should have posted in this thread http://forum.doom9.org/showthread.php?t=149805
@Varies i have done all that, many times actually, i even bought a new gcard thinking my one was borked... winxp 32bit sp3, you name the bench test and i have run it, prime95/occt /linpack etc... all stable until i use cuda encoding with deinterlace and resizing options turned on in dgsource() with nvidia drivers after 186.38 i now have 2 different make gcards, one is the older 192 shader 260gtx , and now i have a msi 216 shader 260gtx which does the same crash... LoadPlugin("D:\NV10\DGDecodeNV.dll") DGSource("H:\1.dgm" ,deinterlace=2 ,resize_w=1024 ,resize_h=576) On Tue 9/22/2009 3:43:22 AM your computer crashed This was likely caused by the following module: nv4_disp.dll Bugcheck code: 0x100000EA (0x88B42890, 0x88DE39F0, 0xF78C6CBC, 0x1) Error: THREAD_STUCK_IN_DEVICE_DRIVER_M file path: H:\WINDOWS\system32\nv4_disp.dll product: NVIDIA Compatible Windows 2000 Display driver, Version 190.62 company: NVIDIA Corporation description: NVIDIA Compatible Windows 2000 Display driver, Version 190.62 |
27th September 2009, 10:40 | #407 | Link |
Registered User
Join Date: Aug 2008
Posts: 64
|
I think it's attached to your source or pc
my pc -> Code:
Processor: Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz (2745 МГц) Operation system: Microsoft Windows XP, 32-bit (Service Pack 3) DirectX: 9.0c Video processor: GeForce 9600 GT Driver version: 190.62 x264: x264 r1271 by x264.nl Code:
DGsource("D:\video\103.dgm",deinterlace=0) # tdeintted = TDeint(mode=2,type=3,mtnmode=3,slow=2,AP=128) tfm(order=-1,clip2=tdeintted, pp=7).tdecimate(mode=1,hybrid=0,nt=1,denoise=true) # BlackmanResize(960,720,181, 3, -182, -4,taps=8) # Code:
DGsource("D:\video\103.dgm",deinterlace=1) # tdecimate(mode=1,hybrid=0,nt=1,denoise=true) # BlackmanResize(960,720,181, 3, -182, -4,taps=8) # Code:
DGsource("D:\video\103.dgm",deinterlace=1, resize_w=960 ,resize_h=720) #crop in DGindex # tdecimate(mode=1,hybrid=0,nt=1,denoise=true) # Code:
DGsource("D:\video\103.dgm",deinterlace=2, resize_w=960 ,resize_h=720) #crop in DGindex # selecteven() tdecimate(mode=1,hybrid=0,nt=1,denoise=true) # fixed
__________________
message transgoogled :) Last edited by Varies; 27th September 2009 at 12:18. |
27th September 2009, 17:38 | #409 | Link | |
Registered User
Join Date: Aug 2008
Posts: 64
|
Quote:
I have same problem when i start virtual pc with adsl-lan connection.
__________________
message transgoogled :) |
|
28th September 2009, 22:36 | #413 | Link |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Fixed serious bug in CUVIDServer
I have refreshed NV beta 10 with a fix for a serious CUVIDServer bug. It could cause these horrible things:
1. Opening a new stream could return as the first frame a frame from the previous stream opened. 2. Random access could produce errored frames. I think some people learned to avoid this by killing and restarting CUVIDServer for each new stream/pass. This should no longer be necessary. http://neuron2.net/dgavcdecnv/NVbeta10.zip |
28th September 2009, 23:10 | #414 | Link | |
Aging Video Hobbyist
Join Date: Dec 2004
Location: Off the Map
Posts: 2,461
|
Quote:
I had found that with the newest vers of CUVIDServer, when I was in Vdub jumping to specific frames (for new chapters) that the previously-viewed frame was being retained i.e. Vdub was not refreshing to the GoTo'ed frame. On a hunch that CUVIDServer was to blame, I reverted-back to the one you published with the original beta9 (file modified Aug-29) before it would work again. But I am happy to report that the new CUVIDServer you published w/this post has fixed the problem! I wonder how you fixed this before I was able to report it--I haven't seen anyone mention this! No matter, very happy here! |
|
28th September 2009, 23:21 | #415 | Link | |
Guest
Join Date: Jan 2002
Posts: 21,901
|
Quote:
The funny thing is that the bug has been there all along. Fortuitous timing may have saved us before. Now with D3D-less operation timings have changed. |
|
29th September 2009, 15:08 | #416 | Link | |
Aging Video Hobbyist
Join Date: Dec 2004
Location: Off the Map
Posts: 2,461
|
Quote:
Thanks for fixing it so quickly, and saving me having to try to explain what the heck I was seeing! |
|
1st October 2009, 01:03 | #417 | Link |
Registered User
Join Date: Oct 2003
Posts: 435
|
well so far it seems this new release doesnt crash my system with 190.62 .dll's i have tried many of the prior source files that did crash my setup, but no issues and encodes run completely to end.
it looks like i have a 260gtx to SLI which i thought was borked... well done |
Thread Tools | Search this Thread |
Display Modes | |
|
|