Installation problem with 186.18 in fresh windows 7
Hello,

As I posted in others topics I tested the new 186.18 and they were ok. Unhappily the silly update system of MS has overwritten my drivers with an old 181.xx driver without asking (I forgot to desactivate automatic updates, and the windows update has no mercy...). So my happy installation became garbage in few seconds thanks to some happy idea from some people developing OS... :rolleyes:

After uninstalling all nvidia drivers, clean them, etc, I installed nforce 15.35 (just as before) but when I try to install forceware 186.18 it doesn't allow me to install them: the installation finish telling "Your system has not been modified. Bla bla". And the forceware drivers not installed.

After looking on inet for solution, it seems that it is a problem/bug of MS, that after upgrading drivers through windows update iit blocks some permissions (?) in registry or close some services that are needed (?), so the best (and only?) thing to do is a complete format and reinstall (!!). Please take note of my experience and desactivate the automatic updates: better to select "notify me only" or similar.

So I have done that, just after a fresh install of Windows 7 RC 7100 x64, the first thing I do is to install nforce 15.35, and the 3D vision CD 1.09. Now the OS allows me to install the forceware 186.18. Ok. But to my surprise after reboot, and during the installation of stereo drivers (before the wizard starts), when it installs the NVIDIA bus controller, windows tell me (through a notification icon in taskar) that the driver for that device (nvidia bus) couldn't be installed correctly.

The installation finishes and the wizard works ok, but after that no 3D stereo application works except the test application from the control panel, even the wizard if I try to relaunch it, doesn't work, neither the screenshots that should be shown at the end of the wizard or by the shorcut in Start menu. I thought that I have done something bad, and still, once time more I reinstalled all the OS (after another HD formatting), but the problem persists.

That problem is SO stupid (because all is clean and new) that it is quite irritating. The only thing I could think on is that maybe these drivers are buggy, and they only work if I had installed previously the 185.85 set? Maybe both are buggy? Drivers and Windows7? Maybe drivers are not buggy but a bit too special for a buggy Windows7 ? etc

Now it is too late here, I'll have to wait until tomorrow evening to try...Meanwhile, do you found the same problem? or do you have some advice?

Excuse me for the rant, please.

Tx
Hello,



As I posted in others topics I tested the new 186.18 and they were ok. Unhappily the silly update system of MS has overwritten my drivers with an old 181.xx driver without asking (I forgot to desactivate automatic updates, and the windows update has no mercy...). So my happy installation became garbage in few seconds thanks to some happy idea from some people developing OS... :rolleyes:



After uninstalling all nvidia drivers, clean them, etc, I installed nforce 15.35 (just as before) but when I try to install forceware 186.18 it doesn't allow me to install them: the installation finish telling "Your system has not been modified. Bla bla". And the forceware drivers not installed.



After looking on inet for solution, it seems that it is a problem/bug of MS, that after upgrading drivers through windows update iit blocks some permissions (?) in registry or close some services that are needed (?), so the best (and only?) thing to do is a complete format and reinstall (!!). Please take note of my experience and desactivate the automatic updates: better to select "notify me only" or similar.



So I have done that, just after a fresh install of Windows 7 RC 7100 x64, the first thing I do is to install nforce 15.35, and the 3D vision CD 1.09. Now the OS allows me to install the forceware 186.18. Ok. But to my surprise after reboot, and during the installation of stereo drivers (before the wizard starts), when it installs the NVIDIA bus controller, windows tell me (through a notification icon in taskar) that the driver for that device (nvidia bus) couldn't be installed correctly.



The installation finishes and the wizard works ok, but after that no 3D stereo application works except the test application from the control panel, even the wizard if I try to relaunch it, doesn't work, neither the screenshots that should be shown at the end of the wizard or by the shorcut in Start menu. I thought that I have done something bad, and still, once time more I reinstalled all the OS (after another HD formatting), but the problem persists.



That problem is SO stupid (because all is clean and new) that it is quite irritating. The only thing I could think on is that maybe these drivers are buggy, and they only work if I had installed previously the 185.85 set? Maybe both are buggy? Drivers and Windows7? Maybe drivers are not buggy but a bit too special for a buggy Windows7 ? etc



Now it is too late here, I'll have to wait until tomorrow evening to try...Meanwhile, do you found the same problem? or do you have some advice?



Excuse me for the rant, please.



Tx

ASUS Maximus XI Hero (Wi-Fi) // Intel 9700K CPU // 32Gb Corsair Vengeance RGB Pro DDR4 RAM // Asus GTX1060 6Gb Strix GPU // NVIDIA Quadro K620 GPU // Asus My Cinema ES2-750 Capture Card // Orico 7 USB 3.0 PCIe Expansion card // Corsair AX860i PSU // Phanteks Evolv X case // Logitech G903 mouse // Logitech PowerPlay charging mouse pad // Logitech Illuminated keyboard // Wacom Intuos 4 tablet // Creative GigaWorks T20 II speakers // Razer Tiamat 7.1 Headphones // Dell U2413 LCD // 3D Ready Samsung 2233RZ LCD // Nvidia 3D Vision glasses 1 & 2 // 3D compatible Sharp XR-10X DLP Projector // Da-Lite 100" HighPower Gain 2.8 Projection screen // XRite i1Display Pro // MadCatz Cyborg Gaming Lights // NZXT HUE 2 // Corsair Commander Pro // Corsair Lighting Node Pro // IcyBox External HDD // Naturalpoint TrackIR 5 Pro // Microsoft Sidewinder ForceFeedback 2 Red // Thrustmaster Hotas Cougar // Saitek Pro Flight Rudder Pedals // Windows 10 x64

#1
Posted 06/23/2009 09:48 PM   
Update: What I found during the wizard (so after the error) is that with the 185.85 set, when I plug the emitter and the wizard configure it, the red light was there during 10-15 seconds before becoming green, but now, with the 186.18, it stays red only 1 second before turning green! That seems to me that the driver or configuration of emitter is not well done (probably because of the nvidia bus controller fails to install in the previous step), and thus there are problems later...

Has somebody installed the 186.18 set from scracth, on a clean W7 RC 7100 64 bits installation? If so, went it ok?
Update: What I found during the wizard (so after the error) is that with the 185.85 set, when I plug the emitter and the wizard configure it, the red light was there during 10-15 seconds before becoming green, but now, with the 186.18, it stays red only 1 second before turning green! That seems to me that the driver or configuration of emitter is not well done (probably because of the nvidia bus controller fails to install in the previous step), and thus there are problems later...



Has somebody installed the 186.18 set from scracth, on a clean W7 RC 7100 64 bits installation? If so, went it ok?

ASUS Maximus XI Hero (Wi-Fi) // Intel 9700K CPU // 32Gb Corsair Vengeance RGB Pro DDR4 RAM // Asus GTX1060 6Gb Strix GPU // NVIDIA Quadro K620 GPU // Asus My Cinema ES2-750 Capture Card // Orico 7 USB 3.0 PCIe Expansion card // Corsair AX860i PSU // Phanteks Evolv X case // Logitech G903 mouse // Logitech PowerPlay charging mouse pad // Logitech Illuminated keyboard // Wacom Intuos 4 tablet // Creative GigaWorks T20 II speakers // Razer Tiamat 7.1 Headphones // Dell U2413 LCD // 3D Ready Samsung 2233RZ LCD // Nvidia 3D Vision glasses 1 & 2 // 3D compatible Sharp XR-10X DLP Projector // Da-Lite 100" HighPower Gain 2.8 Projection screen // XRite i1Display Pro // MadCatz Cyborg Gaming Lights // NZXT HUE 2 // Corsair Commander Pro // Corsair Lighting Node Pro // IcyBox External HDD // Naturalpoint TrackIR 5 Pro // Microsoft Sidewinder ForceFeedback 2 Red // Thrustmaster Hotas Cougar // Saitek Pro Flight Rudder Pedals // Windows 10 x64

#2
Posted 06/24/2009 06:17 AM   
Confirmed that the problem is with the USB controller: "NVIDIA Stereoscopic 3D USB controller", the emitter installs too fast, and then I found a "Unknown device" with a yellow mark in device manager, and if I try to install it manually (looking for the inf file in folder "USB driver" from the folder of 1.09 CD, windows tells me that (aprox translation) "windows found controller software for the device but and error was found when trying to install it" and it adds "This device can't be started"

So it seems to me some problem with the new driver structure that Andrew announced in the 186.18 topic.

I have reinstalled/reformatted HD the OS this afternoon 5 times, checking and trying different combinations, with no success.

Could somebody try it and see if it has the same problem?

Please could somebody help me?

Andrew?
Confirmed that the problem is with the USB controller: "NVIDIA Stereoscopic 3D USB controller", the emitter installs too fast, and then I found a "Unknown device" with a yellow mark in device manager, and if I try to install it manually (looking for the inf file in folder "USB driver" from the folder of 1.09 CD, windows tells me that (aprox translation) "windows found controller software for the device but and error was found when trying to install it" and it adds "This device can't be started"



So it seems to me some problem with the new driver structure that Andrew announced in the 186.18 topic.



I have reinstalled/reformatted HD the OS this afternoon 5 times, checking and trying different combinations, with no success.



Could somebody try it and see if it has the same problem?



Please could somebody help me?



Andrew?

ASUS Maximus XI Hero (Wi-Fi) // Intel 9700K CPU // 32Gb Corsair Vengeance RGB Pro DDR4 RAM // Asus GTX1060 6Gb Strix GPU // NVIDIA Quadro K620 GPU // Asus My Cinema ES2-750 Capture Card // Orico 7 USB 3.0 PCIe Expansion card // Corsair AX860i PSU // Phanteks Evolv X case // Logitech G903 mouse // Logitech PowerPlay charging mouse pad // Logitech Illuminated keyboard // Wacom Intuos 4 tablet // Creative GigaWorks T20 II speakers // Razer Tiamat 7.1 Headphones // Dell U2413 LCD // 3D Ready Samsung 2233RZ LCD // Nvidia 3D Vision glasses 1 & 2 // 3D compatible Sharp XR-10X DLP Projector // Da-Lite 100" HighPower Gain 2.8 Projection screen // XRite i1Display Pro // MadCatz Cyborg Gaming Lights // NZXT HUE 2 // Corsair Commander Pro // Corsair Lighting Node Pro // IcyBox External HDD // Naturalpoint TrackIR 5 Pro // Microsoft Sidewinder ForceFeedback 2 Red // Thrustmaster Hotas Cougar // Saitek Pro Flight Rudder Pedals // Windows 10 x64

#3
Posted 06/24/2009 08:31 PM   
Well, I give to myself the solution ^_^ . Finally I SOLVED THE PROBLEM!! :magic:

After countless reformatting and reinstalls of Win7, I tried to take out the second gfx card (7900gtx) and leave only the GTX285, try to disconnect the network cable (just in case), etc but nothing seemed to solve the problem.

Then I concentrate in the "unknown device" that appeared in devices manager (as explained in my last post), and I was mistaken, it was not the Nvidia emitter.

I started to install other drivers to see which one was it, and after some drivers installation I found the device: it was Silverstone MFP51 Front LCD and IR remote addon (build by Soundgraph). This device needs to install two USB controller devices (Soundgraph Universal Serial controller and TG Universal Serial Controller), and apparently, because its driver was not installed, it interacted/blocked or corrupted the installation of NVIDIA Universal Serial controller (I guess Windows thought that the NVIDIA Universal serial controller was for the LCD/remote instead of NVIDIA emitter, or something similar...IMO).

After installing Silverstone/Soundgraph LCD, then NVIDIA's stereo is installed flawlessly!

So, conclusions:

[b]1.[/b] [b]DON'T ALLOW NEVER Microsoft Windows Update to make updates automatically[/b]. Or at least be sure that you don't allow to download and install [b]drivers [/b](I think in Win7 there is a specific option for that). Personally I highly recommend to configure updates as "Notify me but don't download neither install them" (I usually do, but this time I forgot it :"> )

[b]2.[/b] The time taken for the emitter to go from red light to green light when installing it, has nothing to do.

[b]3.[/b] It is highly [b]recommended installing the 3D Vision CD (or at least the stereo driver) the last of all your hardware[/b]. First nforce (if applies) or mobo, nvidia ESA (if applies), sound card, [u]AND any other device you could have[/u]. After that, go with 3D Vision/Stereo. I think you can install Forceware after mobo, (no need to wait to install it with the 3D Vision CD), but it doesn't hurt to install it together with stereo. Alternatively you can take out the hardware that interacts, or *maybe* disable it in device manager (if you think you know which is it) - BUT I HAVE NOT TESTED THAT. I still recommend to install stereo drivers the last thing.

Note: I thought that this driver interaction only arised with the new 186.18, but it is there also for the 185.85. I have not tested older driver sets though. Probably it is not a problem of nvidia drivers, maybe Win7. But I don't know, I'm not even programmer.

Just in case somebody needs help...

Now, finally coming back to "testing" :rolleyes: new drivers... /clap.gif' class='bbc_emoticon' alt=':clap:' />
Well, I give to myself the solution ^_^ . Finally I SOLVED THE PROBLEM!! :magic:



After countless reformatting and reinstalls of Win7, I tried to take out the second gfx card (7900gtx) and leave only the GTX285, try to disconnect the network cable (just in case), etc but nothing seemed to solve the problem.



Then I concentrate in the "unknown device" that appeared in devices manager (as explained in my last post), and I was mistaken, it was not the Nvidia emitter.



I started to install other drivers to see which one was it, and after some drivers installation I found the device: it was Silverstone MFP51 Front LCD and IR remote addon (build by Soundgraph). This device needs to install two USB controller devices (Soundgraph Universal Serial controller and TG Universal Serial Controller), and apparently, because its driver was not installed, it interacted/blocked or corrupted the installation of NVIDIA Universal Serial controller (I guess Windows thought that the NVIDIA Universal serial controller was for the LCD/remote instead of NVIDIA emitter, or something similar...IMO).



After installing Silverstone/Soundgraph LCD, then NVIDIA's stereo is installed flawlessly!



So, conclusions:



1. DON'T ALLOW NEVER Microsoft Windows Update to make updates automatically. Or at least be sure that you don't allow to download and install drivers (I think in Win7 there is a specific option for that). Personally I highly recommend to configure updates as "Notify me but don't download neither install them" (I usually do, but this time I forgot it :"> )



2. The time taken for the emitter to go from red light to green light when installing it, has nothing to do.



3. It is highly recommended installing the 3D Vision CD (or at least the stereo driver) the last of all your hardware. First nforce (if applies) or mobo, nvidia ESA (if applies), sound card, AND any other device you could have. After that, go with 3D Vision/Stereo. I think you can install Forceware after mobo, (no need to wait to install it with the 3D Vision CD), but it doesn't hurt to install it together with stereo. Alternatively you can take out the hardware that interacts, or *maybe* disable it in device manager (if you think you know which is it) - BUT I HAVE NOT TESTED THAT. I still recommend to install stereo drivers the last thing.



Note: I thought that this driver interaction only arised with the new 186.18, but it is there also for the 185.85. I have not tested older driver sets though. Probably it is not a problem of nvidia drivers, maybe Win7. But I don't know, I'm not even programmer.



Just in case somebody needs help...



Now, finally coming back to "testing" :rolleyes: new drivers... /clap.gif' class='bbc_emoticon' alt=':clap:' />

ASUS Maximus XI Hero (Wi-Fi) // Intel 9700K CPU // 32Gb Corsair Vengeance RGB Pro DDR4 RAM // Asus GTX1060 6Gb Strix GPU // NVIDIA Quadro K620 GPU // Asus My Cinema ES2-750 Capture Card // Orico 7 USB 3.0 PCIe Expansion card // Corsair AX860i PSU // Phanteks Evolv X case // Logitech G903 mouse // Logitech PowerPlay charging mouse pad // Logitech Illuminated keyboard // Wacom Intuos 4 tablet // Creative GigaWorks T20 II speakers // Razer Tiamat 7.1 Headphones // Dell U2413 LCD // 3D Ready Samsung 2233RZ LCD // Nvidia 3D Vision glasses 1 & 2 // 3D compatible Sharp XR-10X DLP Projector // Da-Lite 100" HighPower Gain 2.8 Projection screen // XRite i1Display Pro // MadCatz Cyborg Gaming Lights // NZXT HUE 2 // Corsair Commander Pro // Corsair Lighting Node Pro // IcyBox External HDD // Naturalpoint TrackIR 5 Pro // Microsoft Sidewinder ForceFeedback 2 Red // Thrustmaster Hotas Cougar // Saitek Pro Flight Rudder Pedals // Windows 10 x64

#4
Posted 06/25/2009 12:07 PM   
When I installed the Windows 7 RC (build 7100), it autodetected and installed versions of the drivers for both the graphics card (NVidia 8800GT) and the chipset (NForce 780i) just fine and it was working out of the box. It had an update for the video card, that updated the video drivers to version 185.xx (I can't remember the step-revision). Later on I downloaded and installed the Windows 7 specific driver from NVidia that was the 186.xx (once again, I can't remember the step revision, but I can look at it again tonight) which was in beta at the time (non WHQL). It came with the video driver, PhysX, 3Dvision, and the Nvidia control panel. No issues on the installation, whatsoever. The only thing that it gave a stink about was that it wasn't a WHQL qualified driver, and I just told it to continue anyways. I did not download and install the seperate NForce chipset drivers, as they were detected and stock drivers were installed and they all worked. I can try doing a clean install and then test with installing the nForce drivers and then try to install the video driver and see if I run into the problem, but otherwise, my system installed the drivers just fine.
When I installed the Windows 7 RC (build 7100), it autodetected and installed versions of the drivers for both the graphics card (NVidia 8800GT) and the chipset (NForce 780i) just fine and it was working out of the box. It had an update for the video card, that updated the video drivers to version 185.xx (I can't remember the step-revision). Later on I downloaded and installed the Windows 7 specific driver from NVidia that was the 186.xx (once again, I can't remember the step revision, but I can look at it again tonight) which was in beta at the time (non WHQL). It came with the video driver, PhysX, 3Dvision, and the Nvidia control panel. No issues on the installation, whatsoever. The only thing that it gave a stink about was that it wasn't a WHQL qualified driver, and I just told it to continue anyways. I did not download and install the seperate NForce chipset drivers, as they were detected and stock drivers were installed and they all worked. I can try doing a clean install and then test with installing the nForce drivers and then try to install the video driver and see if I run into the problem, but otherwise, my system installed the drivers just fine.

#5
Posted 06/30/2009 11:42 PM   
Thank you for your interest!!, although the problem is solved, happily.

In fact I do not recommend to let Windows update the drivers except if you like the surprise to see downgraded your gfx drivers (and, eventually, loss stereo functionality) without previous announcement, thats all. Another thing is the first drivers that windows will install the first time you install/boot it, that's different.

It does surprise me that the 3DVision driver came with the forceware driver (except the 3DVision CD of course). Andrew told that a part of 3D Vision comes with forceware, but you still need the stand-alone 3D Vision one, but I have not tested any 186.xx driver in beta stage, so I can't be sure.

On the other hand, as I explained depending on the hardware you have, you will eventually need to install some drivers before others, talking in a general way. And that is what was shown once time more with my problem (silly me, I didn't recall that basic aspect of drivers installation :"> !!)

IMO, choosing which drivers and when to install them, doing a clean uninstall before if possible, is a known way to avoid eventual problems. Not following these precautions sometimes works ok, but other times it only seems to be ok only to find problems/glitches later and wondering why of that graphic glitch in a certain game...(by experience)

In any case is proven that cleaning drivers DO solve some problems and is a good practice, imo.

That said, it is wonderful to hear that other people don't have to pass through the crazyness I passed, I don't wish these baffling situations to anyone ;) !!
Thank you for your interest!!, although the problem is solved, happily.



In fact I do not recommend to let Windows update the drivers except if you like the surprise to see downgraded your gfx drivers (and, eventually, loss stereo functionality) without previous announcement, thats all. Another thing is the first drivers that windows will install the first time you install/boot it, that's different.



It does surprise me that the 3DVision driver came with the forceware driver (except the 3DVision CD of course). Andrew told that a part of 3D Vision comes with forceware, but you still need the stand-alone 3D Vision one, but I have not tested any 186.xx driver in beta stage, so I can't be sure.



On the other hand, as I explained depending on the hardware you have, you will eventually need to install some drivers before others, talking in a general way. And that is what was shown once time more with my problem (silly me, I didn't recall that basic aspect of drivers installation :"> !!)



IMO, choosing which drivers and when to install them, doing a clean uninstall before if possible, is a known way to avoid eventual problems. Not following these precautions sometimes works ok, but other times it only seems to be ok only to find problems/glitches later and wondering why of that graphic glitch in a certain game...(by experience)



In any case is proven that cleaning drivers DO solve some problems and is a good practice, imo.



That said, it is wonderful to hear that other people don't have to pass through the crazyness I passed, I don't wish these baffling situations to anyone ;) !!

ASUS Maximus XI Hero (Wi-Fi) // Intel 9700K CPU // 32Gb Corsair Vengeance RGB Pro DDR4 RAM // Asus GTX1060 6Gb Strix GPU // NVIDIA Quadro K620 GPU // Asus My Cinema ES2-750 Capture Card // Orico 7 USB 3.0 PCIe Expansion card // Corsair AX860i PSU // Phanteks Evolv X case // Logitech G903 mouse // Logitech PowerPlay charging mouse pad // Logitech Illuminated keyboard // Wacom Intuos 4 tablet // Creative GigaWorks T20 II speakers // Razer Tiamat 7.1 Headphones // Dell U2413 LCD // 3D Ready Samsung 2233RZ LCD // Nvidia 3D Vision glasses 1 & 2 // 3D compatible Sharp XR-10X DLP Projector // Da-Lite 100" HighPower Gain 2.8 Projection screen // XRite i1Display Pro // MadCatz Cyborg Gaming Lights // NZXT HUE 2 // Corsair Commander Pro // Corsair Lighting Node Pro // IcyBox External HDD // Naturalpoint TrackIR 5 Pro // Microsoft Sidewinder ForceFeedback 2 Red // Thrustmaster Hotas Cougar // Saitek Pro Flight Rudder Pedals // Windows 10 x64

#6
Posted 07/01/2009 02:49 PM   
Scroll To Top