Workarounds for "Warning: attempt to run stereoscopic..." error msg.
I've had to find two independent workarounds for the dreaded persistent "Warning: attempt to stereoscopic 3D.." error msg in 3D vision.

When I first installed the 3D vision kit last January I was using a GTX260 hooked up to an Acer H5360 projector and could not get rid of this msg when running 3D. What solved the problem then was to install the older 197.45 drivers after a thorough cleaning my newer Nvidia drivers (safe mode / Drivesweeper). Curiously, I could subsequently load newer drivers after this, and the problem did not reappear.

I recently upgraded to a GTX560Ti and the problem returned. In this case the glasses shutters were reversed and the error msg displayed whenever in 3D mode. I could not use my original workaround because the 197.45 drivers will not load with a GTX560Ti installed. (The galling thing is that I could live w/ having to wear the glasses upside down but the persistent error msg was intolerable.....thx Nvidia!) After trying everything under sun, what finally worked this time was to slap an adapter on the cable and use the VGA port instead of the HDMI port on the projector.

Hope one of these two workarounds are helpful to others plagued by this problem.
I've had to find two independent workarounds for the dreaded persistent "Warning: attempt to stereoscopic 3D.." error msg in 3D vision.



When I first installed the 3D vision kit last January I was using a GTX260 hooked up to an Acer H5360 projector and could not get rid of this msg when running 3D. What solved the problem then was to install the older 197.45 drivers after a thorough cleaning my newer Nvidia drivers (safe mode / Drivesweeper). Curiously, I could subsequently load newer drivers after this, and the problem did not reappear.



I recently upgraded to a GTX560Ti and the problem returned. In this case the glasses shutters were reversed and the error msg displayed whenever in 3D mode. I could not use my original workaround because the 197.45 drivers will not load with a GTX560Ti installed. (The galling thing is that I could live w/ having to wear the glasses upside down but the persistent error msg was intolerable.....thx Nvidia!) After trying everything under sun, what finally worked this time was to slap an adapter on the cable and use the VGA port instead of the HDMI port on the projector.



Hope one of these two workarounds are helpful to others plagued by this problem.

#1
Posted 06/29/2011 04:24 PM   
Did you try replacing the .inf?
Did you try replacing the .inf?

Ed

Creator

www.3Dizzy.com

Home of 3D Videos

#2
Posted 06/29/2011 05:58 PM   
If you're referring to the H5360.inf, yes I did that from the get go. I don't know if it's critical to either work around though, as it's been there from the start and did not solve the problem alone.
If you're referring to the H5360.inf, yes I did that from the get go. I don't know if it's critical to either work around though, as it's been there from the start and did not solve the problem alone.

#3
Posted 06/29/2011 06:45 PM   
I'm sick of it. I'm trying to run my PC thru my Onkyo amp to my speakers and H5360 projector and I'm so fed up trying to work arounds to stop this flipping message.
I'm seriously thinking of selling my 3D setup and going to a 2D only system.
I'm sick of it. I'm trying to run my PC thru my Onkyo amp to my speakers and H5360 projector and I'm so fed up trying to work arounds to stop this flipping message.

I'm seriously thinking of selling my 3D setup and going to a 2D only system.

#4
Posted 06/29/2011 07:58 PM   
Edgarin: you got this errormessage even with 720p/120Hz?
Interesting. I only get with custom 100Hz mode.
Yes, with vga cable it work, but i don't want to use it because of the distance (about 10m).
Would be good to use 100Hz with hdmi also.
Edgarin: you got this errormessage even with 720p/120Hz?

Interesting. I only get with custom 100Hz mode.

Yes, with vga cable it work, but i don't want to use it because of the distance (about 10m).

Would be good to use 100Hz with hdmi also.

#5
Posted 06/30/2011 05:21 AM   
If you have a SLI system like me, if this annoying red message appears, just disable and enable SLI again, and the problem will go away. That's how it works for me.
It's the only thing I figured out that solves this issue and it's better than restarting PC which also works.
Now, if you have this problem and don't use SLI, I'm not sure what workaround you can try out...

I think SLI, as it blinks the screen and changes screen display, GPU's used, somehow it clears this problem. This problem happens to me occasionaly, not rarely, but hopefully, not all the time.
Usually, I have my Plasma 3D Ready TV connected to my VGA which is also connected to my Alienware 120hz display. If I turn my TV off while I'm using my PC and 120hz display, I get this issue, but I have my SLI workaround to solve the problem. I think because my TV is connected to my VGA and when it's turned off, I hear a disconnection noise and my 120hz display blinks, and this causes some conflicts that can generate the red message issue. I hate my guts that red message, very annoying I agree...
If you have a SLI system like me, if this annoying red message appears, just disable and enable SLI again, and the problem will go away. That's how it works for me.

It's the only thing I figured out that solves this issue and it's better than restarting PC which also works.

Now, if you have this problem and don't use SLI, I'm not sure what workaround you can try out...



I think SLI, as it blinks the screen and changes screen display, GPU's used, somehow it clears this problem. This problem happens to me occasionaly, not rarely, but hopefully, not all the time.

Usually, I have my Plasma 3D Ready TV connected to my VGA which is also connected to my Alienware 120hz display. If I turn my TV off while I'm using my PC and 120hz display, I get this issue, but I have my SLI workaround to solve the problem. I think because my TV is connected to my VGA and when it's turned off, I hear a disconnection noise and my 120hz display blinks, and this causes some conflicts that can generate the red message issue. I hate my guts that red message, very annoying I agree...

Windows 7 Home Premium 64 Bits - Core i7 2600K @ 4.5ghz - Asus Maximus IV Extreme Z68 - Geforce EVGA GTX 690 - 8GB Corsair Vengeance DDR3 1600 9-9-9-24 (2T) - Thermaltake Armor+ - SSD Intel 510 Series Sata3 256GB - HD WD Caviar Black Sata3 64mb 2TB - HD WD Caviar Black 1TB Sata3 64mb - Bose Sound System - LG H20L GGW Blu Ray/DVD/CD RW - LG GH20 DVD RAM - PSU Thermaltake Toughpower 1000W - Samsung S27A950D 3D Vision Ready + 3D HDTV SAMSUNG PL63C7000 3DTVPLAY + ROLLERMOD CHECKERBOARD

#6
Posted 06/30/2011 03:39 PM   
Yesterday I found the red warning message for the first time after updating to latest drivers. After +2 hours of wasted time and frustration, my conclusion is that when it happens, it's because 3d vision wants to use the resolution that it's marked as "native". With my acer h5360, at 720 I had the warning, but at 1024x768, the resolution that is marked as native in the resolutions list at the nvidia control panel, the warning is gone. I tried several monitor inf's but the resolution marked as native is always 1024x768. I'm pretty sure that if there is a way to move that tag from 1024x768 to 1280x720 the problem would be fixed.
Yesterday I found the red warning message for the first time after updating to latest drivers. After +2 hours of wasted time and frustration, my conclusion is that when it happens, it's because 3d vision wants to use the resolution that it's marked as "native". With my acer h5360, at 720 I had the warning, but at 1024x768, the resolution that is marked as native in the resolutions list at the nvidia control panel, the warning is gone. I tried several monitor inf's but the resolution marked as native is always 1024x768. I'm pretty sure that if there is a way to move that tag from 1024x768 to 1280x720 the problem would be fixed.

#7
Posted 07/06/2011 08:12 AM   
Scroll To Top