BUG: Samsung DLP's Setup Backdated Error Specific error for Samsung DLP's
I have an issue with my Samsung TV that is different than going round of my Samsung DLP’s is not detected and If this does not get fixed I will no longer be able to use my glasses with my 3D DLP.

I was one of the first users to ever post here and used the 3D Vision all the time. During a period of the year I got a new 52" LCD which is not 3D but I wanted to use this for my machine instead plus no new games were coming out.

So I decided that the Advatar 3D Demo and my COD MW2 addiction was good reason to dive back in. Little did I know the trouble I was about to run into. I spent over 8 hours reformatting different OS's while using certain conditions and have found when this went wrong for me but not exactly what went wrong but I do have a good idea.

Since my break with 3D gaming I missed a few month of drivers, so this is were my problem begins. I have a freshly formatted system 2 weeks old I downloaded the newest 1.17 Full Driver CD. Updated the stuff as I normally do and went to set up the 3D portion. I Installed the Geforce drivers, rebooted, it auto installed 3D drivers and when I hit finish..

Wham! This get thrown in my face:
[code]StereoCPLAPI returned invalid video mode (1920x2160) from StereoLauncher-> getDefaultModeInfo[/code]

What an odd resolution error but what more odd is that this error only comes up when its attached to my 3D Samsung DLP (HL-T6184SAX) with any driver CD after 1.09 only. Again I can install any following version 1.10, 1.11, 1.13, 1.15, 1.17 and it will install correctly but the second it starts the 3D wizard I get this error. Now if I have 1.10, 1.11, 1.13, 1.15, 1.17 installed and move the DVI connection to any other monitor I can run the set up with no error but after version 1.15 I will not detect my 3D DLP as many other users of the forum.

This prevents me from using my 3D glasses with any driver improvement after June 22nd. On July 16th they released 1.10 that has one sole fix that looks like it almost black listed my model from even setting up the 3D with the wizard.

[size=4][b]This fix was: "Fixed multiple monitor crash on Windows7/Vista 64 bit"[/b][/size]

I have isolated the 1.10 driver as the start of the issue as with my 8 hours I have reformatted making sure I didn’t install anything else that could trip this and eventually got down to reformatting Windows 7 64bit, then reformatting with Vista 64bit with EVERY DRIVER RELEASE!!!

Both Windows 7/Vista 64 bit showed the same results.

[b][size=4]1) Can NOT run the set up wizard ONLY when its connected to my Samsung HL-T6184SAX 3D DLP starting at version 1.10(Yeah you read that right)[/size][/b]

2) Full Version 1.16 and up will not recognize ANY 3D Samsung DLP at the end of wizard

3) Version 1.09 and below will run the set up wizard and detect my TV as expected.

Well this explains why I had to go through so many drivers releases because when I took my break I think Nvidia was at 1.07. I really started walking backwards with each driver as I did not expect this to happen to each driver.

I have not been able to use ANY update after June. I am pushed out of 6 months of support and am late telling Nvidia about this because of my break. I have spent enough time to at least have someone from Nvidia officially respond to me somehow as I am a paying customer and it is like my TV somehow got blacklisted.

I can hook up any monitor with version any run the set up with but crashes with my 3D DLP and won’t even allow to try an force it. If I run the setup wizard or turn it on anyhow I get the same error.

Please Nvidia / Andrew if you read this you need to get in contact me. It is one thing that Samsung have been disabled in the last 2 released but my TV has been giving a major error since July 16th and I just could not report it to you until now.

With all the hard work I spent tracking this down as I am not the only users this has been happening to please fix this. If I sent this into Nvidia Quality Driver team it would make their head explode and mine as well.

Signed,

A paying customer
I have an issue with my Samsung TV that is different than going round of my Samsung DLP’s is not detected and If this does not get fixed I will no longer be able to use my glasses with my 3D DLP.



I was one of the first users to ever post here and used the 3D Vision all the time. During a period of the year I got a new 52" LCD which is not 3D but I wanted to use this for my machine instead plus no new games were coming out.



So I decided that the Advatar 3D Demo and my COD MW2 addiction was good reason to dive back in. Little did I know the trouble I was about to run into. I spent over 8 hours reformatting different OS's while using certain conditions and have found when this went wrong for me but not exactly what went wrong but I do have a good idea.



Since my break with 3D gaming I missed a few month of drivers, so this is were my problem begins. I have a freshly formatted system 2 weeks old I downloaded the newest 1.17 Full Driver CD. Updated the stuff as I normally do and went to set up the 3D portion. I Installed the Geforce drivers, rebooted, it auto installed 3D drivers and when I hit finish..



Wham! This get thrown in my face:

StereoCPLAPI returned invalid video mode (1920x2160) from StereoLauncher-> getDefaultModeInfo




What an odd resolution error but what more odd is that this error only comes up when its attached to my 3D Samsung DLP (HL-T6184SAX) with any driver CD after 1.09 only. Again I can install any following version 1.10, 1.11, 1.13, 1.15, 1.17 and it will install correctly but the second it starts the 3D wizard I get this error. Now if I have 1.10, 1.11, 1.13, 1.15, 1.17 installed and move the DVI connection to any other monitor I can run the set up with no error but after version 1.15 I will not detect my 3D DLP as many other users of the forum.



This prevents me from using my 3D glasses with any driver improvement after June 22nd. On July 16th they released 1.10 that has one sole fix that looks like it almost black listed my model from even setting up the 3D with the wizard.



This fix was: "Fixed multiple monitor crash on Windows7/Vista 64 bit"



I have isolated the 1.10 driver as the start of the issue as with my 8 hours I have reformatted making sure I didn’t install anything else that could trip this and eventually got down to reformatting Windows 7 64bit, then reformatting with Vista 64bit with EVERY DRIVER RELEASE!!!



Both Windows 7/Vista 64 bit showed the same results.



1) Can NOT run the set up wizard ONLY when its connected to my Samsung HL-T6184SAX 3D DLP starting at version 1.10(Yeah you read that right)



2) Full Version 1.16 and up will not recognize ANY 3D Samsung DLP at the end of wizard



3) Version 1.09 and below will run the set up wizard and detect my TV as expected.



Well this explains why I had to go through so many drivers releases because when I took my break I think Nvidia was at 1.07. I really started walking backwards with each driver as I did not expect this to happen to each driver.



I have not been able to use ANY update after June. I am pushed out of 6 months of support and am late telling Nvidia about this because of my break. I have spent enough time to at least have someone from Nvidia officially respond to me somehow as I am a paying customer and it is like my TV somehow got blacklisted.



I can hook up any monitor with version any run the set up with but crashes with my 3D DLP and won’t even allow to try an force it. If I run the setup wizard or turn it on anyhow I get the same error.



Please Nvidia / Andrew if you read this you need to get in contact me. It is one thing that Samsung have been disabled in the last 2 released but my TV has been giving a major error since July 16th and I just could not report it to you until now.



With all the hard work I spent tracking this down as I am not the only users this has been happening to please fix this. If I sent this into Nvidia Quality Driver team it would make their head explode and mine as well.



Signed,



A paying customer

#1
Posted 11/30/2009 03:12 PM   
Make there heads explode /teehee.gif' class='bbc_emoticon' alt=':teehee:' />

send it in but andrew suggested in a recent thread that a mod should create a bug list we update every week for nvidia to work on

i dont know if they will work on it but andrew actually posted it and he actually works for nvidia so there is a chance

i think one of the mods will be creating it soon , dont worry man there is hope , but that is a weird weird problem ..
Make there heads explode /teehee.gif' class='bbc_emoticon' alt=':teehee:' />



send it in but andrew suggested in a recent thread that a mod should create a bug list we update every week for nvidia to work on



i dont know if they will work on it but andrew actually posted it and he actually works for nvidia so there is a chance



i think one of the mods will be creating it soon , dont worry man there is hope , but that is a weird weird problem ..

intel i5 2500k @ 4.6 30C Stable

EVGA gtx 470 SLI

windows vista 64 bit

8 gig Corsair Vengeance RAM

#2
Posted 11/30/2009 04:03 PM   
[quote name='nhoj333' post='957678' date='Nov 30 2009, 09:03 AM']Make there heads explode /teehee.gif' class='bbc_emoticon' alt=':teehee:' />

send it in but andrew suggested in a recent thread that a mod should create a bug list we update every week for nvidia to work on

i dont know if they will work on it but andrew actually posted it and he actually works for nvidia so there is a chance

i think one of the mods will be creating it soon , dont worry man there is hope , but that is a weird weird problem ..[/quote]


Can you link the post in which Andrew has said it please?
[quote name='nhoj333' post='957678' date='Nov 30 2009, 09:03 AM']Make there heads explode /teehee.gif' class='bbc_emoticon' alt=':teehee:' />



send it in but andrew suggested in a recent thread that a mod should create a bug list we update every week for nvidia to work on



i dont know if they will work on it but andrew actually posted it and he actually works for nvidia so there is a chance



i think one of the mods will be creating it soon , dont worry man there is hope , but that is a weird weird problem ..





Can you link the post in which Andrew has said it please?

#3
Posted 11/30/2009 05:27 PM   
[quote name='pappmasta' post='957727' date='Nov 30 2009, 12:27 PM']Can you link the post in which Andrew has said it please?[/quote]


[url="http://forums.nvidia.com/index.php?s=&showtopic=151015&view=findpost&p=957659"]http://forums.nvidia.com/index.php?s=&...st&p=957659[/url]
[quote name='pappmasta' post='957727' date='Nov 30 2009, 12:27 PM']Can you link the post in which Andrew has said it please?





http://forums.nvidia.com/index.php?s=&...st&p=957659

#4
Posted 11/30/2009 07:29 PM   
Bump

I believe Andrew missed this as thinking my DLP is not detected...
Bump



I believe Andrew missed this as thinking my DLP is not detected...

#5
Posted 12/15/2009 08:31 PM   
[quote name='1WayJonny' post='965254' date='Dec 15 2009, 03:31 PM']Bump

I believe Andrew missed this as thinking my DLP is not detected...[/quote]

Hi

Please read the recent posts that I said the 195.81 driver will fix this.
[quote name='1WayJonny' post='965254' date='Dec 15 2009, 03:31 PM']Bump



I believe Andrew missed this as thinking my DLP is not detected...



Hi



Please read the recent posts that I said the 195.81 driver will fix this.

#6
Posted 12/15/2009 09:42 PM   
[quote name='andrewf@nvidia' post='965298' date='Dec 15 2009, 02:42 PM']Hi

Please read the recent posts that I said the 195.81 driver will fix this.[/quote]


Thanks will get back to you! =)
[quote name='andrewf@nvidia' post='965298' date='Dec 15 2009, 02:42 PM']Hi



Please read the recent posts that I said the 195.81 driver will fix this.





Thanks will get back to you! =)

#7
Posted 12/15/2009 09:59 PM   
[quote name='1WayJonny' post='965313' date='Dec 15 2009, 04:59 PM']Thanks will get back to you! =)[/quote]

Hi All

3D Vision 195.81 and CD 1.19 (includes 3D Vision & GeForce 195.81 drivers) are now relesaed. This should address your CRT and Samsung DLP issues:
[list]
[*][url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_CD_1.19.html"]CD 1.17[/url]
[*][url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_195.81.html"]3D Vision 195.81[/url]
[/list]

Please let us know if your issues are now resolved.
[quote name='1WayJonny' post='965313' date='Dec 15 2009, 04:59 PM']Thanks will get back to you! =)



Hi All



3D Vision 195.81 and CD 1.19 (includes 3D Vision & GeForce 195.81 drivers) are now relesaed. This should address your CRT and Samsung DLP issues:





Please let us know if your issues are now resolved.

#8
Posted 12/16/2009 04:44 PM   
=(

This is still happening, I installed Driver CD 1.19 and when you tick "Turn 3D on or Run Setup Wizard" the Setup Wizard crashes and gives the same error as above, there is a new message after the error.
[code]StereoCPLAPI returned invalid video mode (1920x2160) from StereoLauncher-> getDefaultModeInfo[/code]
[code]"The previous background texture was released"[/code]

So I can still not use my product because it has to run through the Setup Wizard which will not even start much less trying to make it to the end of the Setup Wizard!

I really need some attention on the problem please... Can not use my product since July
=(



This is still happening, I installed Driver CD 1.19 and when you tick "Turn 3D on or Run Setup Wizard" the Setup Wizard crashes and gives the same error as above, there is a new message after the error.

StereoCPLAPI returned invalid video mode (1920x2160) from StereoLauncher-> getDefaultModeInfo


"The previous background texture was released"




So I can still not use my product because it has to run through the Setup Wizard which will not even start much less trying to make it to the end of the Setup Wizard!



I really need some attention on the problem please... Can not use my product since July

#9
Posted 12/20/2009 12:30 PM   
Andrew,

Just thinking something logical here... Could you have the driver team put in a option for DEBUG in the next driver release where it will dump a log of what happens while running setup wizard? Then we can all post our small log files to the forum here...

I bet this would provide a lot of technical data to your driver team to as of why I cant run the setup wizard at all and two why is is not detect generic 3d DLP's anymore...

This feature would not interfere with the drivers and since everyone is having trouble with the new release I am sure many people would not mind handing in logs.

Not full logs for playing 3D games but for the Setup Wizard only...
Andrew,



Just thinking something logical here... Could you have the driver team put in a option for DEBUG in the next driver release where it will dump a log of what happens while running setup wizard? Then we can all post our small log files to the forum here...



I bet this would provide a lot of technical data to your driver team to as of why I cant run the setup wizard at all and two why is is not detect generic 3d DLP's anymore...



This feature would not interfere with the drivers and since everyone is having trouble with the new release I am sure many people would not mind handing in logs.



Not full logs for playing 3D games but for the Setup Wizard only...

#10
Posted 12/20/2009 12:50 PM   
Excellent suggestion. I'm surprised that 3DVision hasn't a logging feature builtin already.

[quote name='1WayJonny' post='967838' date='Dec 20 2009, 04:50 AM']Andrew,

Just thinking something logical here... Could you have the driver team put in a option for DEBUG in the next driver release where it will dump a log of what happens while running setup wizard? Then we can all post our small log files to the forum here...

I bet this would provide a lot of technical data to your driver team to as of why I cant run the setup wizard at all and two why is is not detect generic 3d DLP's anymore...

This feature would not interfere with the drivers and since everyone is having trouble with the new release I am sure many people would not mind handing in logs.

Not full logs for playing 3D games but for the Setup Wizard only...[/quote]
Excellent suggestion. I'm surprised that 3DVision hasn't a logging feature builtin already.



[quote name='1WayJonny' post='967838' date='Dec 20 2009, 04:50 AM']Andrew,



Just thinking something logical here... Could you have the driver team put in a option for DEBUG in the next driver release where it will dump a log of what happens while running setup wizard? Then we can all post our small log files to the forum here...



I bet this would provide a lot of technical data to your driver team to as of why I cant run the setup wizard at all and two why is is not detect generic 3d DLP's anymore...



This feature would not interfere with the drivers and since everyone is having trouble with the new release I am sure many people would not mind handing in logs.



Not full logs for playing 3D games but for the Setup Wizard only...

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#11
Posted 12/20/2009 03:52 PM   
Scroll To Top