| | | Junior Member
       
Group: Forum Members Last Login: 8/12/2009 1:16:49 PM Posts: 12, Visits: 18 |
| | Everytime I load up stereoscopic software (including software included with the VR920) my computer crashes. This occurs all the time with the 3D visualizer when entering full screen mode (windowed mode seems to be fine). I read a post earlier about the system appearing crashed and that I should disconnect the USB cable and then reconnect it, but the computer is completely locked. Ctrl+Alt+Del, Esc, Windows Key all have no effect and only seems recoverable by manually turning off the power to my computer. |
| | | | 
Technical Support
       
Group: Administrators Last Login: Yesterday @ 12:36:09 PM Posts: 62, Visits: 133 |
| TempestX,
Could you provide some more information about your configuration (basic hardware information and how your display settings are configured)? Could you tell me what driver and firmware versions you are using? Specifically what other software, aside from the 3D Visualizer, are you experiencing crashes with? Is there any other software that you have been able to successfully run using the VR920?
Brian J. Degus
Technical Support
brian_degus@vuzix.com
585-359-5909
|
| | | | Junior Member
       
Group: Forum Members Last Login: 8/12/2009 1:16:49 PM Posts: 12, Visits: 18 |
| | Hello, I am running a Vista 64 laptop with the latest firmware and version 2.4 of the iwear software. The free demos that were included on the installation CD and Unreal Tournament 2004 all crash when transitioning into full screen mode. I am able to use the stereoscopic movie player with no problems. |
| | | | Junior Member
       
Group: Forum Members Last Login: 8/12/2009 1:16:49 PM Posts: 12, Visits: 18 |
| | Well, I still have no idea why my computer keeps crashing with those games, but I have decided to use the VR920 on my Windows XP desktop instead of my Vista 64 laptop. |
| | | | Forum Newbie
       
Group: Forum Members Last Login: 7/2/2009 10:46:07 PM Posts: 2, Visits: 5 |
| | Fwiw, I'm having the same issue in Seven RC x64 which is essentially, I'm led to believe, Vista in this case. Pretty much anything using the 920 causes a lock-up or crash. The 3D viewer, the 3D viusaulizer (haven't tried not-full screened). I've had a couple BSODs from MS FSX. If I remember correctly, the Crysis demo works ok, but that's about the only thing so far. Running: Windows Seven RC, Build7100 - Intel i7 quad on EVGA x58 mobo - Radeon 4890 with current drivers - 6GB DDR3 Triple channel RAM. |
| | | | 
Technical Support
       
Group: Administrators Last Login: Yesterday @ 12:36:09 PM Posts: 62, Visits: 133 |
| How do you have your displays settings configured? (is the VR920 set as the primary display? are you cloning your display?)
When you say entering full screen mode, do you mean when changing from window mode to full screen and applying that setting, or when a game is loading?
Is the crash or lock always the same? Does it crash to desktop, give you a BSOD or just lock up?
Brian J. Degus
Technical Support
brian_degus@vuzix.com
585-359-5909
|
| | | | Forum Newbie
       
Group: Forum Members Last Login: 7/2/2009 10:46:07 PM Posts: 2, Visits: 5 |
| | I may have jumped on the bandwagon a little quickly, Brian. The issue seems to be when FSX is directed to the 4890's "Display1" (as opposed to Display0) ie. ANY configuration of the video card that results in FSX's display coming out the 4890's "Display1" port causes a BSOD when "pause" is pressed in game. The BSOD appears on "Display0", but only for a second or so, before rebooting. All I had time to see is something about "Driver IRQL" and "not less than or equal" something. In any case, doesn't sound so much like a VR920 issue now. When the visualizer locked up, it was in full screen mode and had been running ok for a minute or two. Then it just stopped in its tracks. ie. the display froze, the music kept playing. The only way to get out was to kill the process from Task Manager. The Visualizer was also running on "Display1" - The card was configured as: Display1 Primary, extend to Display0. Having said all that, I can't get it to lock up again, now. ??? Probably more info than you wanted. At this point, I'll just play with it for a few days and see what happens. |
| |
|
|