3d Vision Discover freezes/crashes
Hello there. I wonder if you can help me, I've googled around - quite a lot - but haven't been able to find an answer to my problem.

I'm running 3d Vision Discover with a GeForce GTX 550Ti, on a 4GB RAM Intel Core i4-2400 CPU 3.10GHz, OS Windows 7 x64. I'm using the 280 drivers.

The trouble is that playing for any amount of time with the games I've tried seems to invarably lead to a crash/freeze. It's preceeded by a moment when the screen is slightly garbled - little white squares appear on random points of the screen, and then the whole thing freezes (sometimes sound stops as well; sometimes it goes on). Ctrl-Alt-Del doesn't work, nor Alt-F4, nor any key combination, forcing me to do a hard reset.

Granted, I haven't tested it with high-end newer games, or even games-that-were-new-until-a-while-ago, like Portal or BioShock. Rather, I've tested it with Fahrenheit (a.k.a. Indigo Prophecy, which, by browsing around, I gather other people have sucessfully run without errors in 3d Vision) and Beyond Good and Evil. BG&E I had to do a bit of registry hack in order to even get the stereoscoping to work (just set a configuration to turn an "FX" option off), so I assumed that was the problem. Fahrenheit worked great straight out of the box, but just as I thought I was safe - at a certain point the game invariably crashes.

Well, I say invariably - it crashed two times in a row at the exact same spot. I have no desire to try it again.

I'm also understandably wary of trying out any newer games until I find out what's going on. It doesn't help that I can find no mention of it anywhere, like no one else is having this problem...

Can anyone help me at all?

EDIT - Oh, I also dabbled a bit in Simon the Sorcerer 5. It didn't crash, but it wasn't open long enough for it to have the chance, either.

EDIT 2 - Scary developments, which have made me forget all about 3d vision.

(incidently, I forgot to mention that prior to all the aforementioned crashes, I did get a "The NVIDIA kernel crashed and sucessfully restored" message after quitting a 3d-vision-enabled game)

I load up Fahrenheit, ready for a last try. While I'm adjusting depth and convergence, my girlfriend calls on Trillian, so I alt-tab to her. Almost immediately, the screen gets garbled like it did just before a crash. In panic I tried to deactivate 3d vision, but it isn't long before the whole computer becomes frozen and unresponsive. Anyway, I could move the mouse around for a bit, but even while I could, no key or mouse-click triggered a reaction.

I had to reset the computer. And as soon as I do, before Windows even boots, I see a garbled monitor. It's displaying the same things it displays every time I boot up, but it's garbled.

I reset again. I turn off the monitor. I turn it back on. It's still garbled. I assume I've damaged the monitor, and start getting freaky. I enter safe mode - garbled - and look at the Device Manager. The NVIDIA Graphic Card has a yellow triangle next to it.

Fortunately, I have the CD with the original drivers, but better yet, I'd downloaded the 280 drivers. I restarted in normal Windows mode. This time my monitor is clear, and I breathe a sigh of relief. I reinstall the drivers. All is well.

I have no idea what happened - I would imagine my monitor maybe doesn't support something that needs to be supported, but that doesn't really explain why it would crash the *graphic card* kernel, then the computer, then practically destroy the video card's drivers.

I shan't be trying 3d vision again. But I would still like to know, if anyone has an inkling...

WTF just happened over here?

EDIT - And it happened with iZ3D (anaglyph) as well, though not until after I quit Fahrenheit - and I managed to stop it before it actually crashed (so I only got the garbage). So it's definitely not a 3d vision problem, it's something with my hardware.

I would still appreciate any theories about what's happening, though.
Hello there. I wonder if you can help me, I've googled around - quite a lot - but haven't been able to find an answer to my problem.



I'm running 3d Vision Discover with a GeForce GTX 550Ti, on a 4GB RAM Intel Core i4-2400 CPU 3.10GHz, OS Windows 7 x64. I'm using the 280 drivers.



The trouble is that playing for any amount of time with the games I've tried seems to invarably lead to a crash/freeze. It's preceeded by a moment when the screen is slightly garbled - little white squares appear on random points of the screen, and then the whole thing freezes (sometimes sound stops as well; sometimes it goes on). Ctrl-Alt-Del doesn't work, nor Alt-F4, nor any key combination, forcing me to do a hard reset.



Granted, I haven't tested it with high-end newer games, or even games-that-were-new-until-a-while-ago, like Portal or BioShock. Rather, I've tested it with Fahrenheit (a.k.a. Indigo Prophecy, which, by browsing around, I gather other people have sucessfully run without errors in 3d Vision) and Beyond Good and Evil. BG&E I had to do a bit of registry hack in order to even get the stereoscoping to work (just set a configuration to turn an "FX" option off), so I assumed that was the problem. Fahrenheit worked great straight out of the box, but just as I thought I was safe - at a certain point the game invariably crashes.



Well, I say invariably - it crashed two times in a row at the exact same spot. I have no desire to try it again.



I'm also understandably wary of trying out any newer games until I find out what's going on. It doesn't help that I can find no mention of it anywhere, like no one else is having this problem...



Can anyone help me at all?



EDIT - Oh, I also dabbled a bit in Simon the Sorcerer 5. It didn't crash, but it wasn't open long enough for it to have the chance, either.



EDIT 2 - Scary developments, which have made me forget all about 3d vision.



(incidently, I forgot to mention that prior to all the aforementioned crashes, I did get a "The NVIDIA kernel crashed and sucessfully restored" message after quitting a 3d-vision-enabled game)



I load up Fahrenheit, ready for a last try. While I'm adjusting depth and convergence, my girlfriend calls on Trillian, so I alt-tab to her. Almost immediately, the screen gets garbled like it did just before a crash. In panic I tried to deactivate 3d vision, but it isn't long before the whole computer becomes frozen and unresponsive. Anyway, I could move the mouse around for a bit, but even while I could, no key or mouse-click triggered a reaction.



I had to reset the computer. And as soon as I do, before Windows even boots, I see a garbled monitor. It's displaying the same things it displays every time I boot up, but it's garbled.



I reset again. I turn off the monitor. I turn it back on. It's still garbled. I assume I've damaged the monitor, and start getting freaky. I enter safe mode - garbled - and look at the Device Manager. The NVIDIA Graphic Card has a yellow triangle next to it.



Fortunately, I have the CD with the original drivers, but better yet, I'd downloaded the 280 drivers. I restarted in normal Windows mode. This time my monitor is clear, and I breathe a sigh of relief. I reinstall the drivers. All is well.



I have no idea what happened - I would imagine my monitor maybe doesn't support something that needs to be supported, but that doesn't really explain why it would crash the *graphic card* kernel, then the computer, then practically destroy the video card's drivers.



I shan't be trying 3d vision again. But I would still like to know, if anyone has an inkling...



WTF just happened over here?



EDIT - And it happened with iZ3D (anaglyph) as well, though not until after I quit Fahrenheit - and I managed to stop it before it actually crashed (so I only got the garbage). So it's definitely not a 3d vision problem, it's something with my hardware.



I would still appreciate any theories about what's happening, though.

#1
Posted 10/02/2011 04:18 PM   
I just noticed that my resolution and frequency, which is was 1400x900 75Hz(on a Samsung Syncmaster 943nw), was NOT the optimum res and frequency (I thought it was).

So I just changed to the optimal settings: 1440x900 60Hz.

I'm very wary of retrying anything 3d, but I have to know, could this small difference affect my display? If 1440x900 is the optimum resolution, then what I was using, 1400x900, was a rather odd setting, and at elevated frequency, no less - could this have negatively affected my experience with Anaglyph 3d, and led to the garbage and freezes and even the incapacitation of the NVIDIA video drivers?

Incidently, I presume that the 120Hz minimum I keep hearing about don't apply to 3d Vision Discover, but exclusively to the other modes.

EDIT - Nope. I still get the garbage - those white squares that appear and start flickering in random parts of the screen. As soon as I see them, I'm out of the game like a flash, turning off 3d vision, before my PC has a chance to lock up. What *is* happening?
I just noticed that my resolution and frequency, which is was 1400x900 75Hz(on a Samsung Syncmaster 943nw), was NOT the optimum res and frequency (I thought it was).



So I just changed to the optimal settings: 1440x900 60Hz.



I'm very wary of retrying anything 3d, but I have to know, could this small difference affect my display? If 1440x900 is the optimum resolution, then what I was using, 1400x900, was a rather odd setting, and at elevated frequency, no less - could this have negatively affected my experience with Anaglyph 3d, and led to the garbage and freezes and even the incapacitation of the NVIDIA video drivers?



Incidently, I presume that the 120Hz minimum I keep hearing about don't apply to 3d Vision Discover, but exclusively to the other modes.



EDIT - Nope. I still get the garbage - those white squares that appear and start flickering in random parts of the screen. As soon as I see them, I'm out of the game like a flash, turning off 3d vision, before my PC has a chance to lock up. What *is* happening?

#2
Posted 10/03/2011 11:27 AM   
*bump*

A reply would be nice.
*bump*



A reply would be nice.

#3
Posted 10/05/2011 11:11 AM   
I'm not sure what the problem is. What drivers are you using? Fahrenheit works perfect for me in 3D Vision or 3D Vision Discover. I also hacked the .exe to get widescreen (which is only applicable in game and not the menus). To get it at your desired widescreen resolution go here: http://widescreengamingforum.com/dr/indigo-prophecy
I'm not sure what the problem is. What drivers are you using? Fahrenheit works perfect for me in 3D Vision or 3D Vision Discover. I also hacked the .exe to get widescreen (which is only applicable in game and not the menus). To get it at your desired widescreen resolution go here: http://widescreengamingforum.com/dr/indigo-prophecy

#4
Posted 10/05/2011 04:16 PM   
[quote name='photios' date='05 October 2011 - 04:16 PM' timestamp='1317831392' post='1303756']
I'm not sure what the problem is. What drivers are you using? Fahrenheit works perfect for me in 3D Vision or 3D Vision Discover. I also hacked the .exe to get widescreen (which is only applicable in game and not the menus). To get it at your desired widescreen resolution go here: http://widescreengamingforum.com/dr/indigo-prophecy
[/quote]

Actually, I'm just now - just this very moment - struggling with something else. It turns out that 3d vision was not the issue, though it seems to have coincided with when I first enabled it. I'm getting the problem in 3d games (i.e. "Wanted - A Wild Western Adventure") now even without 3d vision. I've rolled back to the drivers this computer came with (266), and am getting a kernel crash which I'm investigating.

My troubles aren't over, but they certainly belong to another part of this forum now, I guess. Thanks for your reply - I was going to post this here soon, anyway.
[quote name='photios' date='05 October 2011 - 04:16 PM' timestamp='1317831392' post='1303756']

I'm not sure what the problem is. What drivers are you using? Fahrenheit works perfect for me in 3D Vision or 3D Vision Discover. I also hacked the .exe to get widescreen (which is only applicable in game and not the menus). To get it at your desired widescreen resolution go here: http://widescreengamingforum.com/dr/indigo-prophecy





Actually, I'm just now - just this very moment - struggling with something else. It turns out that 3d vision was not the issue, though it seems to have coincided with when I first enabled it. I'm getting the problem in 3d games (i.e. "Wanted - A Wild Western Adventure") now even without 3d vision. I've rolled back to the drivers this computer came with (266), and am getting a kernel crash which I'm investigating.



My troubles aren't over, but they certainly belong to another part of this forum now, I guess. Thanks for your reply - I was going to post this here soon, anyway.

#5
Posted 10/05/2011 04:19 PM   
I was going to just edit my previous post, but I figured it would be best to let you know of the developments. The issue was not with 3d vision at all, apparently. It was simply - it seems - a matter of overheating. At least I hope that's what it was. Never having been that much of a hardcore gamer, I never overclocked, but neither did I ever bother much with the fan or the temperature.

I've cleaned the back of my case (which had a horrible layer of dust right where the air from the GPU's fan is supposed to blow out - nice going) and readjusted my fans in the BIOS and with my ASUS Suite. Also, I've installed - and kept running - EVGA Precision. I've turned on the fan's automatic controls, and monitor them on my SysTray to ensure that everything's Jake.

My guess is that when I started using 3d Vision, my GPU started working a lot more than it had worked before (makes sense, huh?), and I simply hadn't equipped my system for it. Funny how those tiny things like "fan power" never occur to one, huh?

I *hope* my problems are solved. I'm sorry to have disturbed you. Cheers.
I was going to just edit my previous post, but I figured it would be best to let you know of the developments. The issue was not with 3d vision at all, apparently. It was simply - it seems - a matter of overheating. At least I hope that's what it was. Never having been that much of a hardcore gamer, I never overclocked, but neither did I ever bother much with the fan or the temperature.



I've cleaned the back of my case (which had a horrible layer of dust right where the air from the GPU's fan is supposed to blow out - nice going) and readjusted my fans in the BIOS and with my ASUS Suite. Also, I've installed - and kept running - EVGA Precision. I've turned on the fan's automatic controls, and monitor them on my SysTray to ensure that everything's Jake.



My guess is that when I started using 3d Vision, my GPU started working a lot more than it had worked before (makes sense, huh?), and I simply hadn't equipped my system for it. Funny how those tiny things like "fan power" never occur to one, huh?



I *hope* my problems are solved. I'm sorry to have disturbed you. Cheers.

#6
Posted 10/05/2011 06:22 PM   
Ok. I really should have left it at that.

But no. I had to go and start using 3d vision again, secure in the knowledge that my computer was dust free and my GPU's temperature was being monitored. Indeed, in these past few days it never got above 60ºC. Heck, it hardly ever GOT TO 60º.

So while I was playing Fahrenheit - again, the garbage, the freeze, the non-responsive system. Again the reset.

Again the freaky screen garbage. But this time it doesn't go away. Safe mode, normal mode, newest drivers, drivers that came with the CD. Nothing works. EVGA Precision, which I'd set to autoboot with Windows, informs me it can't detect the proper hardware.

Device manager gives me Code 43.

Googling around it's pretty obvious that Code 43 means my card is dead. AFAIK, 3D vision killed it - more fool me for going back to it. I don't see WHY or HOW it could have - it wasn't overheating, my system could take it (in discover mode, at least), but it did.

I can only be thankful that my entire system was bought fresh four months ago, and so the card is still under warranty. I'm going there tomorrow, hoping to get back to normal state, hoping to get a computer which recognises a graphic card again, and hoping never to hear about 3d vision ever again.
Ok. I really should have left it at that.



But no. I had to go and start using 3d vision again, secure in the knowledge that my computer was dust free and my GPU's temperature was being monitored. Indeed, in these past few days it never got above 60ºC. Heck, it hardly ever GOT TO 60º.



So while I was playing Fahrenheit - again, the garbage, the freeze, the non-responsive system. Again the reset.



Again the freaky screen garbage. But this time it doesn't go away. Safe mode, normal mode, newest drivers, drivers that came with the CD. Nothing works. EVGA Precision, which I'd set to autoboot with Windows, informs me it can't detect the proper hardware.



Device manager gives me Code 43.



Googling around it's pretty obvious that Code 43 means my card is dead. AFAIK, 3D vision killed it - more fool me for going back to it. I don't see WHY or HOW it could have - it wasn't overheating, my system could take it (in discover mode, at least), but it did.



I can only be thankful that my entire system was bought fresh four months ago, and so the card is still under warranty. I'm going there tomorrow, hoping to get back to normal state, hoping to get a computer which recognises a graphic card again, and hoping never to hear about 3d vision ever again.

#7
Posted 10/07/2011 08:18 PM   
Scroll To Top