Nvidia 301.24 BETA -500 series comment and support thread-

Change Page: < 123456 > | Showing page 2 of 6, messages 31 to 60 of 174
Author Message
ryu4000

  • Total Posts : 374
  • Joined: 1/25/2009
  • Location: Picayune MS
  • Status: offline
  • Folding: 611
Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 12:49 AM (permalink)
Loving these drivers tested the witcher 2 on 296.10 drivers and only got 44fps with surround gaming and when updated to these drivers jump to 58fps.
Case Haf X
Mobo ASUS Rampage IV Formula   
Cpu Core i7 3820 4.75ghz @ 1.296volts        
HDD Samsung SpinPoint 3 1TB
SDD Samsung 830 256gb    
GPU 3x EVGA FTW GTX 670 
PSU emerson 1250watt   
Monitor ASUS PB278Q 2560x1440
Ram 16GB
HDTV PN51D8000
 
#31
    KopyKat007

    • Total Posts : 133
    • Joined: 11/13/2011
    • Location: Canada
    • Status: offline
    Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 1:13 AM (permalink)
    How does using the adaptive vsync compare with using 3Doverrider for vsync and triple buffering?  Are they similar, whats the main difference?
     
    I use 3Doverrider and have very smooth frames but when i installed this driver i can't use 3Doverrider due to very choppy performance (which was stated in the install of these new drivers, i know) but when i turn 3Doverrider off, then everything runs good.
     
    Also when i installed these on XP 32 bit i had the nvidia control panel option for the FXAA (which i usually use for all or most of my in game settings, so i left this off) but i had no options for adaptive vsync, just on or off or application controlled.
     
    Im sure i maybe didn't install it properly, but im just wondering what others have experienced with these new drivers with a 550Ti or other 500 series cards.
     
    #32
      normality

      • Total Posts : 4
      • Joined: 4/19/2010
      • Location: Brisbane, Australia
      • Status: offline
      Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 1:52 AM (permalink)
      Still having consistant 'Driver has crashed and recovered' issues with this driver and a 560Ti FPB.
       
      Used driversweeper to remove old 27x.xx driver and only installed the driver and pysx componants of this new update. Have already flashed card to latest bios revision, running out of things to try. Time to warranty, or wait for another driver?
       
      Edit: Ignore below specs, currently working on my girl's pc.
      CPU - i5 750 || Cooler - Cool It ALC Vantage || MB - EVGA P55 SLI || RAM - 8GB G.Skil 1600MHz CL8 || VGA - EVGA GTX465 1GB || Primary Drive - Western Digital 500GB RE4 || Case - Coolermaster Storm Scout || PSU - PC Power and Cooling Silencer 750W
       
      #33
        jimmycricket

        • Total Posts : 1566
        • Joined: 11/26/2011
        • Status: offline
        Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 8:00 AM (permalink)
        These drivers are crap for me
        Can't play any games in SLI without the screen going black on stock speeds
         
        #34
          =DCM=Fionn

          • Total Posts : 721
          • Joined: 12/29/2010
          • Location: Cork, Ireland
          • Status: offline
          • Ribbons: 1
          • Folding: 1,950,004
          Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 8:09 AM (permalink)
          I'm very happy with these drivers, I've finally managed to pass my 13k goal on 3DMark 11 that I set almost a year ago using the exact same Overclocks on CPU and GPU's.
           

           
          I should be ashamed of myself that I never ran Unigine Heaven before on this build but I'm glad I did.
           

           
          I can't really say I notice much improvements in Battlefield 3 as maniacvvv said but there were no notes on it so I didn't expect any. I can't say much on any improvements on Skyrim because I run a whole bunch of graphics mods and they are changing all the time. I wish there was some sort of definite benchmarking tool for these games to get a proper knowing of how drivers/settings work rather then running around a map.
           
          This is how I feel with these drivers so far:
           

          First time I played Skyrim I followed a rabbit into a woddy area on a snowy mountain and punched the poor thing to death and got lost.

           
          #35
            Porpoise Hork

            • Total Posts : 5085
            • Joined: 3/17/2009
            • Status: offline
            • Ribbons: 17
            Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 8:30 AM (permalink)
            All I have noticed in comparison to the 301.10 is my 580 so far doesnt want to clock down to its low power state (51hz).  Now for me at least this has been very common since Nvidia made it so their driver installer does not require a reboot after install.  To correct this I just do another clean install of the driver and reboot usually fixes it.
             
            As far as any boost in performance can't really say since all I played last night was The Witcher (enhanced Steam version) and that game even in 3d does not really push the system all that hard.
            The Second Amendment.

            A well regulated Militia, being necessary to the security of a free State, the right of the people to keep and bear Arms, shall not be infringed.

            The answer to 1984 is 1776!  -Alex Jones-
            Veni et capient eam!
             
             
            #36
              Baasha

              • Total Posts : 385
              • Joined: 2/5/2011
              • Location: USA
              • Status: offline
              • Ribbons: 1
              Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 12:35 PM (permalink)
              maniacvvv


              Baasha


              I downloaded and installed this Beta driver today and all seemed to go well.

              Once I tried to launch Cinema 4D, it launched but within a few seconds "stopped responding" and I had to kill it. The same thing happened with Photoshop. When I tried to open Vegas, the loading screen was stuck and it too "stopped responding" and crashed. **** is going on?

              I noticed that on the Photoshop crash, it said something about nvsmartmax64.dll as being the 'fault' module.

              This refers to the window sizing they fixed with the 300+ drivers where in Surround you don't have to click and drag your windows; it will automatically scale to the size of one monitor. In addition to this, the task bar is now centered as well.

              However, I think it has something to do with the window resizing as my design work is across the three monitors and that is what Surround is most useful for.

              Please HELP! I can't figure out how to fix this and I really want to use this driver as it has adaptive v-sync etc.


              That is very odd, it must have something to do with your monitor setup or a install problem.

              I just checked my CS5 (PH,IL and AE) working correctly and import/render output tested.
              C4D (11.5) also working fine (project started with previous driver) and rendered out fine
              Ran my last project file out of Vegas... no issues.

              Head on over to the CS and C4D sites and see if anyone with a setup like yours is reporting issues.



               
              Maniac,
               
              Please help me out bro! This problem is really weird. Here's what I've tried so far.
               
              I uninstalled the beta driver (301.24) using this guide: http://www.overclock.net/...our-nvidia-gpu-drivers
               
              I tried going back to 296.10 but the SAME problem occurs in those drivers too! I can't open Premier Pro or Vegas (both crash on launch at the splash screen). Cinema 4D and Photoshop crash soon after opening. Now, iTunes works but when I close the program, it crashes and says "iTunes has stopped working".
               
              I narrowed it down to some setting in Surround. I reverted back to "Maximize 3D Performance" for single screen display and it first (for a couple of times) only showed 3-Way SLI (I'm running 4-Way). But now, it works 4-Way SLI in one screen and all programs open/close/work fine. The moment I turn Surround on, even though it's still 4-Way SLI, the problem comes back! I can't open those programs! I tried searching on Sony Vegas forums and Adobe but found nothing.
               
              Something is seriously screwed up with the install and/or drivers! The 296.10 was working PERFECTLY and now this POS driver has ruined that as well! ARRRGH! I'm so freakin annoyed right now.
               
              I looked at your procedure and uninstalled Precision X and MSI Afterburner Beta 15 and THEN installed the new beta no to avail. The problem still occurs. Since everything works in Single display mode, it can't be the installation procedure right?
               
              HELP!
               
              PS: I forgot to mention that my cards (EVGA GTX-580 Classified 3GB in 4-Way SLI) are in OC mode (RED LED on). I uninstalled 296.10 with OC mode on. Installed the beta with OC mode on. And the OC mode is still on. Could this be the issue? Since OC mode is a different BIOS would that be causing this? However, since everything works in Single display it has to be something with Surround.
              <message edited by Baasha on Tuesday, April 10, 2012 12:40 PM>
              Gaming on 3 30" monitors - ThirtyIR
              Exotic Car Madness: UberExotica
              -------------------------------------------------------- 
              Please check out my FOR SALE thread!
               
              #37
                mcj008

                • Total Posts : 32
                • Joined: 7/10/2009
                • Status: offline
                Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 1:42 PM (permalink)
                exellent drivers for me, adaptive V-sync really works well on all games I got no tearing when ingame v-sync is disabled, especially in STALKER SoC I notice this, on low settings I reached temps of 85C with v-sync on wich I found strange, now on max settings I see max temp of 65C big difference! On BF3 I had big spikes on my gpu performance (looking at the in-game performance graphic) , adaptive v-sync fixed this so my CPU and GPU are pretty equal now. good job nVidia!
                CPU Intel i7 980x 4.275Ghz  CPU Cooler Thermalright Ultra 120 Extreme Board Asus Rampage II RAM Corsair Dominator 12GB Ram Cooler Corsair Airflow 2 Video 3x EVGA GTX570 SLI Disk Corsair p128 SSD, Raid-0 2x Intel 320's 300GB for games, PSU Corsair AX1200W Case Corsair 800D Audio  Steinberg MR816x Headphones Logitech G930 Speakers KRK Rokit_5 Monitor Dell U3011
                 
                #38
                  KopyKat007

                  • Total Posts : 133
                  • Joined: 11/13/2011
                  • Location: Canada
                  • Status: offline
                  Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 2:57 PM (permalink)
                  mcj008


                  exellent drivers for me, adaptive V-sync really works well on all games I got no tearing when ingame v-sync is disabled, especially in STALKER SoC I notice this, on low settings I reached temps of 85C with v-sync on wich I found strange, now on max settings I see max temp of 65C big difference! On BF3 I had big spikes on my gpu performance (looking at the in-game performance graphic) , adaptive v-sync fixed this so my CPU and GPU are pretty equal now. good job nVidia!

                   
                  Im really excited about trying adaptive vsync but for some reason i didn't get that option when i installed it, i did get the FXAA option, weird, i really haven't had much time to screw around with different installs though and i just did the usual recommended install.  I rolled back to 295.73 drivers and those for me work flawlessly as always lol.
                   
                  I also notice that 3Doverrider does not work with the 301.24 drivers either, using the vsync and the triple buffering, but i notice it does say to uninstalled all third party software before installing these 3xx drivers.  Arg, i hate uninstalled and reinstalling stuff and then not knowing if the outcome will even be worth it.
                   
                  #39
                    QuickShow

                    • Total Posts : 18
                    • Joined: 12/4/2011
                    • Status: offline
                    Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 9:40 PM (permalink)
                    FXAA is awesome! I have it enabled globally and have no issue so far.
                    <message edited by QuickShow on Tuesday, April 10, 2012 9:44 PM>
                    Attachment(s)Attachments are not available: Download requirements not met
                    CPU: Intel i7-980 (EK - Supreme HF - EN)
                    Motherboard: Asus Rampage III Formula
                    RAM: Corsair Vengeance 4GB * 3 1600 MHz
                    GPU: eVGA GTX 570 HD SC * 3-way SLI (EK - FC570 GTX SE rev. 1.1 - EN) (900 MHz @ 1.075v, Tmax = 60 °C @ Burning)
                    SSD: OCZ Vertex 3 120 GB 
                    HDD: Hitachi 1+2 TB 7200 rpm 
                    PSU: Thermaltake Toughpower 1200W
                    Display: Asus VG236H
                    Rads: Alphacool NexXxoS UT60
                    Fans: Scythe Gentle Typhoon AP-15 (4 Fan * 2 Array, P & P)
                    Speaker: Altec Lansing FX3022 2.2 Channel (Excellent performance with THX Enabled)
                    [font
                     
                    #40
                      007vsMagua

                      • Total Posts : 1109
                      • Joined: 9/10/2008
                      • Location: Land of 10,000 Lakes
                      • Status: offline
                      • Ribbons: 1
                      Re:Nvidia 301.24 BETA Tuesday, April 10, 2012 11:03 PM (permalink)
                      I seem to be unable to run the 3DMark11 or the Heaven 3.0 benchmark without getting extremly low fps. P460, or something like that, in 3DMark11 and only about 2fps in Heaven. I'm not sure what the deal is. I did a very clean install of this driver using the time tested method of doing driver installs, and have never run into this problem before. Is anyone else having this problem?
                      EVGA ___ GTX 570 --- P55 SLI
                      INTEL ___ i5-750 @ 3.2GHz
                      CORSAIR ___ 4 x 2GB @ 1600MHz --- TX750W --- M90
                      WD ___ 640GB Black --- 500GB x 2
                      XIGMATEK ___ HDT-S1283
                      LG ___ x16 BD-R Burner 
                      ASUS ___ x24 DVD --- 27" 1080
                      AVERMEDIA ___ AVer TV Combo G2
                      CREATIVE ___ SB Recon3D PCIe
                      ANTEC ___ Nine Hundred Two
                      WINDOWS 7 ___ HP  64-bit
                       
                       
                      #41
                        XrayMan

                        • Total Posts : 31167
                        • Joined: 12/14/2006
                        • Location: Santa Clarita, Ca.
                        • Status: offline
                        • Ribbons: 72
                        Re:Nvidia 301.24 BETA -500 series comment and support thread- Tuesday, April 10, 2012 11:12 PM (permalink)
                         
                         Great job on this Maniacvvv.      
                        //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////      
                          
                                                                                     My Affiliate Code: 8WEQVXMCJL
                          
                         
                        #42
                          maniacvvv

                          • Total Posts : 7847
                          • Joined: 9/10/2009
                          • Location: Spokane WA
                          • Status: offline
                          • Ribbons: 122
                          Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 12:56 AM (permalink)
                          007vsMagua


                          I seem to be unable to run the 3DMark11 or the Heaven 3.0 benchmark without getting extremly low fps. P460, or something like that, in 3DMark11 and only about 2fps in Heaven. I'm not sure what the deal is. I did a very clean install of this driver using the time tested method of doing driver installs, and have never run into this problem before. Is anyone else having this problem?


                          Havent heard that before...
                           
                          What software are you using to monitor the videocard?
                          Check your temps and clocks... sounds like throttle
                          Try shuting it down, then completely uninstall it.... reboot and run the test again.
                           
                          You didnt do your Win7 patches... and then try to run the tests?
                          That would explain it, as the optimizers suck up CPU cycles after the patches for awhile.
                           
                          MANIAC-VVV-'s 2013 Ultimate Nvidia Guide  -CLICK HERE-
                          MANIAC-VVV-'s Ultimate Battlefield 3 Guide  -CLICK HERE- 
                          MANIAC-VVV-'s Ultimate BFBC2 Settings Guide  -CLICK HERE-              

                           
                          #43
                            KopyKat007

                            • Total Posts : 133
                            • Joined: 11/13/2011
                            • Location: Canada
                            • Status: offline
                            Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 1:18 AM (permalink)
                            One little thing i notice is that when using a slightly lower resolution in Windows XP and maybe other Windows too, it doesn't let me use the options menu in this new version of Precision X because its cut off at the top where i can move the window, the old version of Precision does fine with lower resolutions in windows, just letting the staff know.
                             
                            #44
                              maniacvvv

                              • Total Posts : 7847
                              • Joined: 9/10/2009
                              • Location: Spokane WA
                              • Status: offline
                              • Ribbons: 122
                              Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 1:30 AM (permalink)
                              KopyKat007


                              One little thing i notice is that when using a slightly lower resolution in Windows XP and maybe other Windows too, it doesn't let me use the options menu in this new version of Precision X because its cut off at the top where i can move the window, the old version of Precision does fine with lower resolutions in windows, just letting the staff know.
                               
                              You should run Afterburner 2.2.0 BETA15, it will fit much better running at 1280x1024
                              *Precision and Afterburner are really basicly the same programs (RivaTuner Overlays), both coded by Unwinder
                               
                              MANIAC-VVV-'s 2013 Ultimate Nvidia Guide  -CLICK HERE-
                              MANIAC-VVV-'s Ultimate Battlefield 3 Guide  -CLICK HERE- 
                              MANIAC-VVV-'s Ultimate BFBC2 Settings Guide  -CLICK HERE-              

                               
                              #45
                                KopyKat007

                                • Total Posts : 133
                                • Joined: 11/13/2011
                                • Location: Canada
                                • Status: offline
                                Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 2:20 AM (permalink)
                                maniacvvv


                                KopyKat007


                                One little thing i notice is that when using a slightly lower resolution in Windows XP and maybe other Windows too, it doesn't let me use the options menu in this new version of Precision X because its cut off at the top where i can move the window, the old version of Precision does fine with lower resolutions in windows, just letting the staff know.
                                 
                                You should run Afterburner 2.2.0 BETA15, it will fit much better running at 1280x1024
                                *Precision and Afterburner are really basicly the same programs (RivaTuner Overlays), both coded by Unwinder

                                 
                                Oh sorry for the lack of detail, i have recently upgraded to a 20 inch wide screen 16x9 monitor and i use 1600x900 for gaming now (native resolution for this monitor and im loving it) but i use 1280x720 in Windows XP desktop. 
                                 
                                The newest version of the old Precision works fine with this lower resolution for the top menu options.  So im just trying to find a way to use this 1280x720 resolution and still be able to see the top of the options window or to manually move it lower within this res to use the full options lol.
                                 
                                Thanks for the quick response as usual!  Any tips would be awesome!
                                 
                                #46
                                  maniacvvv

                                  • Total Posts : 7847
                                  • Joined: 9/10/2009
                                  • Location: Spokane WA
                                  • Status: offline
                                  • Ribbons: 122
                                  Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 10:14 AM (permalink)
                                  Baasha


                                  maniacvvv


                                  Baasha


                                  I downloaded and installed this Beta driver today and all seemed to go well.

                                  Once I tried to launch Cinema 4D, it launched but within a few seconds "stopped responding" and I had to kill it. The same thing happened with Photoshop. When I tried to open Vegas, the loading screen was stuck and it too "stopped responding" and crashed. **** is going on?

                                  I noticed that on the Photoshop crash, it said something about nvsmartmax64.dll as being the 'fault' module.

                                  This refers to the window sizing they fixed with the 300+ drivers where in Surround you don't have to click and drag your windows; it will automatically scale to the size of one monitor. In addition to this, the task bar is now centered as well.

                                  However, I think it has something to do with the window resizing as my design work is across the three monitors and that is what Surround is most useful for.

                                  Please HELP! I can't figure out how to fix this and I really want to use this driver as it has adaptive v-sync etc.


                                  That is very odd, it must have something to do with your monitor setup or a install problem.

                                  I just checked my CS5 (PH,IL and AE) working correctly and import/render output tested.
                                  C4D (11.5) also working fine (project started with previous driver) and rendered out fine
                                  Ran my last project file out of Vegas... no issues.

                                  Head on over to the CS and C4D sites and see if anyone with a setup like yours is reporting issues.




                                  Maniac,

                                  Please help me out bro! This problem is really weird. Here's what I've tried so far.

                                  I uninstalled the beta driver (301.24) using this guide: http://www.overclock.net/...our-nvidia-gpu-drivers

                                  I tried going back to 296.10 but the SAME problem occurs in those drivers too! I can't open Premier Pro or Vegas (both crash on launch at the splash screen). Cinema 4D and Photoshop crash soon after opening. Now, iTunes works but when I close the program, it crashes and says "iTunes has stopped working".

                                  I narrowed it down to some setting in Surround. I reverted back to "Maximize 3D Performance" for single screen display and it first (for a couple of times) only showed 3-Way SLI (I'm running 4-Way). But now, it works 4-Way SLI in one screen and all programs open/close/work fine. The moment I turn Surround on, even though it's still 4-Way SLI, the problem comes back! I can't open those programs! I tried searching on Sony Vegas forums and Adobe but found nothing.

                                  Something is seriously screwed up with the install and/or drivers! The 296.10 was working PERFECTLY and now this POS driver has ruined that as well! ARRRGH! I'm so freakin annoyed right now.

                                  I looked at your procedure and uninstalled Precision X and MSI Afterburner Beta 15 and THEN installed the new beta no to avail. The problem still occurs. Since everything works in Single display mode, it can't be the installation procedure right?

                                  HELP!

                                  PS: I forgot to mention that my cards (EVGA GTX-580 Classified 3GB in 4-Way SLI) are in OC mode (RED LED on). I uninstalled 296.10 with OC mode on. Installed the beta with OC mode on. And the OC mode is still on. Could this be the issue? Since OC mode is a different BIOS would that be causing this? However, since everything works in Single display it has to be something with Surround.


                                  Any updates or luck to report on this bro?
                                  Since I only run a single monitor, I really cant be as helpful as I would like on this matter
                                   
                                  MANIAC-VVV-'s 2013 Ultimate Nvidia Guide  -CLICK HERE-
                                  MANIAC-VVV-'s Ultimate Battlefield 3 Guide  -CLICK HERE- 
                                  MANIAC-VVV-'s Ultimate BFBC2 Settings Guide  -CLICK HERE-              

                                   
                                  #47
                                    bong47406

                                    • Total Posts : 24
                                    • Joined: 9/27/2011
                                    • Status: offline
                                    Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 11:25 AM (permalink)
                                    I posted this on geforce.com, but they seemed not to care for it.  Anyway...
                                     
                                    Adaptive VSync actually caused micro-stuttering or tearing in Skyrim.  I never experienced such things  before, so I'm not sure which one can describe the issue better.  Anyway, it's like a horizontal divider appears (not actually a solid line, but I can see the screen is divided) very frequently.  Turning the adaptive VSync off solved the problem.  I wonder what kind of setup nVidia engineers used for testing, but my system is not quite an outlier:
                                    i5 2400
                                    MSI H67 ( latest BIOS / IGP disabled)
                                    Samsung F3 500GB
                                    Corsair XMS3 8GB @stock 1333 MHz
                                    EVGA GTX 560 Ti 448 Classified 838  MHz / 2000MHz / Stock 1.025v
                                    Windows 7 Ultimate 64 bit SP1
                                    Antec HCG-620
                                    Antec Three Hundred
                                    HP 2211 1920 x 1080 via DVI
                                    When playing with the built-in Vsync @Ultra preset, I have mostly 60 FPS and no stuttering or tearing on 1920 x 1080.  With the adaptive VSync, the display is almost unbearable to my eyes, although playable.  
                                     
                                     
                                    #48
                                      007vsMagua

                                      • Total Posts : 1109
                                      • Joined: 9/10/2008
                                      • Location: Land of 10,000 Lakes
                                      • Status: offline
                                      • Ribbons: 1
                                      Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 11:56 AM (permalink)
                                      maniacvvv


                                      007vsMagua


                                      I seem to be unable to run the 3DMark11 or the Heaven 3.0 benchmark without getting extremly low fps. P460, or something like that, in 3DMark11 and only about 2fps in Heaven. I'm not sure what the deal is. I did a very clean install of this driver using the time tested method of doing driver installs, and have never run into this problem before. Is anyone else having this problem?


                                      Havent heard that before...

                                      What software are you using to monitor the videocard?
                                      Check your temps and clocks... sounds like throttle
                                      Try shuting it down, then completely uninstall it.... reboot and run the test again.

                                      You didnt do your Win7 patches... and then try to run the tests?
                                      That would explain it, as the optimizers suck up CPU cycles after the patches for awhile.


                                      After I installed 301.24 I installed PrecisionX to monitor my card and set the overclock...800MHz @ stock voltage. I set the fan speed in Precision to 80% and closed Precision. I also installed the latest Win7 updates (patches?) and ran 3DMark11 again with better results but still not right.
                                       
                                      I've gone gone back to 295.73 and reinstalled Precision v2.1.1 and all is well again. I really like the live graphs in the older Precision and hope that the newer versions of Precision will have something like that in the future. Will wait for the WHQL and try again. Thanks...
                                      EVGA ___ GTX 570 --- P55 SLI
                                      INTEL ___ i5-750 @ 3.2GHz
                                      CORSAIR ___ 4 x 2GB @ 1600MHz --- TX750W --- M90
                                      WD ___ 640GB Black --- 500GB x 2
                                      XIGMATEK ___ HDT-S1283
                                      LG ___ x16 BD-R Burner 
                                      ASUS ___ x24 DVD --- 27" 1080
                                      AVERMEDIA ___ AVer TV Combo G2
                                      CREATIVE ___ SB Recon3D PCIe
                                      ANTEC ___ Nine Hundred Two
                                      WINDOWS 7 ___ HP  64-bit
                                       
                                       
                                      #49
                                        mblystone

                                        • Total Posts : 618
                                        • Joined: 8/21/2008
                                        • Status: offline
                                        Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 12:25 PM (permalink)
                                        maniacvvv


                                        sputnik7913


                                        So, how does adaptive VSYNC works with 500 series? Good thread man!


                                        Yes it does 

                                        But only users who are trying to keep FPS/temps down or who's monitor quality is lacking will have any interest in using it at all.

                                        With the high frametrates -above- refresh rates and high quality responce time/low input lag monitors.
                                        Tearing is a thing of the past with modern game engines, and Vsync is not needed.

                                        Users who's configs cant keep above their refresh rates consistantly, or who use monitors with high processing input lag (shown below) will love this feature.
                                        *Although it may take some serious tinkering to get it to work correctly and across game engines.

                                        Examples of processing input lag on some of todays monitors (lower is better)




                                        Good thread, I'm loving these drivers, but you are a little bit confused on vsync and it's relationship to input lag.
                                         
                                        Input lag on a modern LCD is typically a function of the internal scaler on the monitor itself, and measures the time difference(lag) between a control input and display output, it does not directly influence screen tearing, nor does it have anything at all to do with ghosting, which is what a monitor's rated pixel response time represents.
                                         
                                        The quality of an LCD does not directly determine it's refresh rate, there are plenty of quality 120hz panels, and plenty of quality 60hz panels as well.  A 60hz panel will physically only update the picture you see 60 times a second, regardless of framerate, however, vsync keeps these frames consistent, so you get an entire frame at a time, rather than partial frames (this is what causes tearing, a combination of two or more partially drawn frames being sent to the monitor)
                                         
                                        To combat this, vsync waits until a full frame can be delievered to the display device, that causes a form of input lag itself, and is one of the reasons triple buffering has become so ubiquitous, despite it's additional framebuffer requirements, and added input lag, because the performance penalty for double-buffered vsyncing is so extreme, that tossing an already finished back buffer frame to the display is much faster.
                                         
                                        On 60hz monitors, tearing is most certainly not a thing of the past, and will occur any time the framerate exceeds the input polling rate and what the device is physically capable of displaying, this is why adaptive vsync is such a blessing, and these drivers are so great!
                                         
                                        This hardforum post does a really good job of explaining vsync http://hardforum.com/showthread.php?t=928593
                                        <message edited by mblystone on Wednesday, April 11, 2012 12:39 PM>
                                         
                                        #50
                                          maniacvvv

                                          • Total Posts : 7847
                                          • Joined: 9/10/2009
                                          • Location: Spokane WA
                                          • Status: offline
                                          • Ribbons: 122
                                          Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 1:09 PM (permalink)
                                          mblystone


                                          maniacvvv


                                          sputnik7913


                                          So, how does adaptive VSYNC works with 500 series? Good thread man!


                                          Yes it does 

                                          But only users who are trying to keep FPS/temps down or who's monitor quality is lacking will have any interest in using it at all.

                                          With the high frametrates -above- refresh rates and high quality responce time/low input lag monitors.
                                          Tearing is a thing of the past with modern game engines, and Vsync is not needed.

                                          Users who's configs cant keep above their refresh rates consistantly, or who use monitors with high processing input lag (shown below) will love this feature.
                                          *Although it may take some serious tinkering to get it to work correctly and across game engines.

                                          Examples of processing input lag on some of todays monitors (lower is better)




                                          Good thread, I'm loving these drivers, but you are a little bit confused on vsync and it's relationship to input lag.

                                          Input lag on a modern LCD is typically a function of the internal scaler on the monitor itself, and measures the time difference(lag) between a control input and display output, it does not directly influence screen tearing, nor does it have anything at all to do with ghosting, which is what a monitor's rated pixel response time represents.

                                          The quality of an LCD does not directly determine it's refresh rate, there are plenty of quality 120hz panels, and plenty of quality 60hz panels as well.  A 60hz panel will physically only update the picture you see 60 times a second, regardless of framerate, however, vsync keeps these frames consistent, so you get an entire frame at a time, rather than partial frames (this is what causes tearing, a combination of two or more partially drawn frames being sent to the monitor)

                                          To combat this, vsync waits until a full frame can be delievered to the display device, that causes a form of input lag itself, and is one of the reasons triple buffering has become so ubiquitous, despite it's additional framebuffer requirements, and added input lag, because the performance penalty for double-buffered vsyncing is so extreme, that tossing an already finished back buffer frame to the display is much faster.

                                          On 60hz monitors, tearing is most certainly not a thing of the past, and will occur any time the framerate exceeds the input polling rate and what the device is physically capable of displaying, this is why adaptive vsync is such a blessing, and these drivers are so great!

                                          This hardforum post does a really good job of explaining vsync http://hardforum.com/showthread.php?t=928593


                                          I have been using displays for over 40 years, I know what tearing is and what it looks like.
                                          I also happen to know exactly what the causes are based on hardware, game engines and drivers.
                                           
                                          My current config does not suffer from it (with the games I currently run) and Vsync is unneeded, even at framerates approaching 200fps on a 60hz monitor.
                                           
                                          According to you this is impossible.....
                                          I assure you it is quite possible with the correct hardware and game engines.
                                           
                                          If you suffer from screen tearing, its NOT something you will miss as its quite distracting and looks awful.....
                                          --->For those users, different Vsync methods can be quite helpful.
                                          (of course at a serious cost in FPS and input lag, that is unacceptable for competitive FPS gameplay)
                                          *The best way to avoid screen tearing is not using Vsync, but spending alot more money on graphics horsepower, buying the correct monitor (and setting it up correctly) and then paying alot more attention to how USB polling works and what the effects are when using todays higher polling rate mouse devices.....  
                                           
                                          Users should work with their system, games and drivers to find what works best for them.
                                           
                                           
                                           
                                           
                                           
                                          <message edited by maniacvvv on Wednesday, April 11, 2012 1:29 PM>
                                           
                                          MANIAC-VVV-'s 2013 Ultimate Nvidia Guide  -CLICK HERE-
                                          MANIAC-VVV-'s Ultimate Battlefield 3 Guide  -CLICK HERE- 
                                          MANIAC-VVV-'s Ultimate BFBC2 Settings Guide  -CLICK HERE-              

                                           
                                          #51
                                            killabee98

                                            • Total Posts : 8
                                            • Joined: 4/26/2011
                                            • Status: offline
                                            Re:Nvidia 301.24 BETA -500 series comment and support thread- Wednesday, April 11, 2012 1:30 PM (permalink)
                                            hey guys im new to this whole forum deal so ill say sorry if i brake any rules right out the gate. but im curious about the new beta drivers for the nvidia 500 cards. i just literaly tore apart my old alienware area 51 x58 desk top down to just a case and upgraded to the evga x58 sli board, core i7 920 oc to 3.8, 12 gigs corsair vengence 1600, silverstone st1000 pos, 4 seagate baracudas in raid 0-1 4k gigs total, duel blueray burners, 12 in one media card reader with bluetoth, and duel evga gtx 560 ti's in sli 2gig, and a gt 9800 dedicated to physx 1gig. this is a week old system now and runs like a champ pushing 185 plus frames top end in bf3 ultra settings no lower than 89 fps. so all in all under the 296 drivers there doing well. so what is new with the new 300 beta drivers? will it be in my interest to update to that new driver?
                                            Attachment(s)Attachments are not available: Download requirements not met
                                             
                                            #52
                                              mblystone

                                              • Total Posts : 618
                                              • Joined: 8/21/2008
                                              • Status: offline
                                              Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 1:54 PM (permalink)
                                              maniacvvv


                                              mblystone


                                              maniacvvv


                                              sputnik7913


                                              So, how does adaptive VSYNC works with 500 series? Good thread man!


                                              Yes it does 

                                              But only users who are trying to keep FPS/temps down or who's monitor quality is lacking will have any interest in using it at all.

                                              With the high frametrates -above- refresh rates and high quality responce time/low input lag monitors.
                                              Tearing is a thing of the past with modern game engines, and Vsync is not needed.

                                              Users who's configs cant keep above their refresh rates consistantly, or who use monitors with high processing input lag (shown below) will love this feature.
                                              *Although it may take some serious tinkering to get it to work correctly and across game engines.

                                              Examples of processing input lag on some of todays monitors (lower is better)




                                              Good thread, I'm loving these drivers, but you are a little bit confused on vsync and it's relationship to input lag.

                                              Input lag on a modern LCD is typically a function of the internal scaler on the monitor itself, and measures the time difference(lag) between a control input and display output, it does not directly influence screen tearing, nor does it have anything at all to do with ghosting, which is what a monitor's rated pixel response time represents.

                                              The quality of an LCD does not directly determine it's refresh rate, there are plenty of quality 120hz panels, and plenty of quality 60hz panels as well.  A 60hz panel will physically only update the picture you see 60 times a second, regardless of framerate, however, vsync keeps these frames consistent, so you get an entire frame at a time, rather than partial frames (this is what causes tearing, a combination of two or more partially drawn frames being sent to the monitor)

                                              To combat this, vsync waits until a full frame can be delievered to the display device, that causes a form of input lag itself, and is one of the reasons triple buffering has become so ubiquitous, despite it's additional framebuffer requirements, and added input lag, because the performance penalty for double-buffered vsyncing is so extreme, that tossing an already finished back buffer frame to the display is much faster.

                                              On 60hz monitors, tearing is most certainly not a thing of the past, and will occur any time the framerate exceeds the input polling rate and what the device is physically capable of displaying, this is why adaptive vsync is such a blessing, and these drivers are so great!

                                              This hardforum post does a really good job of explaining vsync http://hardforum.com/showthread.php?t=928593


                                              I have been using displays for over 40 years, I know what tearing is and what it looks like.
                                              I also happen to know exactly what the causes are based on hardware, game engines and drivers.

                                              My current config does not suffer from it (with the games I currently run) and Vsync is unneeded, even at framerates approaching 200fps on a 60hz monitor.

                                              According to you this is impossible.....
                                              I assure you it is quite possible with the correct hardware and game engines.

                                              If you suffer from screen tearing, its NOT something you will miss as its quite distracting and looks awful.....
                                              --->For those users, different Vsync methods can be quite helpful.
                                              (of course at a serious cost in FPS and input lag, that is unacceptable for competitive FPS gameplay)
                                              *The best way to avoid screen tearing is not using Vsync, but spending alot more money on graphics horsepower, buying the correct monitor (and setting it up correctly) and then paying alot more attention to how USB polling works and what the effects are when using todays higher polling rate mouse devices.....  

                                              Users should work with their system, games and drivers to find what works best for them.







                                              Unfortunately, it doesn't matter how old you are, you are engaging in magical thinking regarding vsync, magical thinking is bad in the realm of computer science, and you should probobly not only read that link I posted, but google "how does vsync work" and educate yourself.
                                               
                                              If you aren't employing some form of throttling to prevent buffer thrash, and you are actually tossing 200 frames through the link cable to your display as you claim, you are most likely going to experience the visual tearing vsync seeks to combat.  It's basic computer science 101 stuff.  It's science, not theory. 
                                               
                                              Magical thinking is disastrous both to our hobby, and my occupation.  I spend literally my entire day dispelling magical thinking, don't think because you are old you are immune, in fact, older people are much more likely to engage in magical thinking to justify thier beliefs. 
                                               
                                              That you would link USB polling rates and screen refresh based tearing is completely indicitive that you have leapt fully into the realm of magical thinking, and no longer even care how the monitor and video card interact.  Physical input has absolutely nothing to do with screen tearing.  This can be demonstrated by setting up a script to pan a camera at a set interval in a 3d scene, and removing vsync.  Provided rendering is occuring at a set, non variable, over 60, not divisible by 60 rate, the scene will always tear.
                                              <message edited by mblystone on Wednesday, April 11, 2012 1:59 PM>
                                               
                                              #53
                                                PanzerMensch

                                                • Total Posts : 1650
                                                • Joined: 6/22/2009
                                                • Location: Canada
                                                • Status: offline
                                                • Ribbons: 4
                                                Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 2:09 PM (permalink)
                                                Installed this beta for my GTX590, and it makes my voltages jump all over the place, all the way up to .963 volts. I had the same problem with the previous 301 driver.
                                                Conspiracy Theorist:
                                                Nothing more than a derogatory title
                                                used to dismiss a critical thinker.
                                                **NOTE** I'm still crazy though
                                                 
                                                #54
                                                  maniacvvv

                                                  • Total Posts : 7847
                                                  • Joined: 9/10/2009
                                                  • Location: Spokane WA
                                                  • Status: offline
                                                  • Ribbons: 122
                                                  Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 4:06 PM (permalink)
                                                  mblystone


                                                  maniacvvv


                                                  mblystone


                                                  maniacvvv


                                                  sputnik7913


                                                  So, how does adaptive VSYNC works with 500 series? Good thread man!


                                                  Yes it does 

                                                  But only users who are trying to keep FPS/temps down or who's monitor quality is lacking will have any interest in using it at all.

                                                  With the high frametrates -above- refresh rates and high quality responce time/low input lag monitors.
                                                  Tearing is a thing of the past with modern game engines, and Vsync is not needed.

                                                  Users who's configs cant keep above their refresh rates consistantly, or who use monitors with high processing input lag (shown below) will love this feature.
                                                  *Although it may take some serious tinkering to get it to work correctly and across game engines.

                                                  Examples of processing input lag on some of todays monitors (lower is better)




                                                  Good thread, I'm loving these drivers, but you are a little bit confused on vsync and it's relationship to input lag.

                                                  Input lag on a modern LCD is typically a function of the internal scaler on the monitor itself, and measures the time difference(lag) between a control input and display output, it does not directly influence screen tearing, nor does it have anything at all to do with ghosting, which is what a monitor's rated pixel response time represents.

                                                  The quality of an LCD does not directly determine it's refresh rate, there are plenty of quality 120hz panels, and plenty of quality 60hz panels as well.  A 60hz panel will physically only update the picture you see 60 times a second, regardless of framerate, however, vsync keeps these frames consistent, so you get an entire frame at a time, rather than partial frames (this is what causes tearing, a combination of two or more partially drawn frames being sent to the monitor)

                                                  To combat this, vsync waits until a full frame can be delievered to the display device, that causes a form of input lag itself, and is one of the reasons triple buffering has become so ubiquitous, despite it's additional framebuffer requirements, and added input lag, because the performance penalty for double-buffered vsyncing is so extreme, that tossing an already finished back buffer frame to the display is much faster.

                                                  On 60hz monitors, tearing is most certainly not a thing of the past, and will occur any time the framerate exceeds the input polling rate and what the device is physically capable of displaying, this is why adaptive vsync is such a blessing, and these drivers are so great!

                                                  This hardforum post does a really good job of explaining vsync http://hardforum.com/showthread.php?t=928593


                                                  I have been using displays for over 40 years, I know what tearing is and what it looks like.
                                                  I also happen to know exactly what the causes are based on hardware, game engines and drivers.

                                                  My current config does not suffer from it (with the games I currently run) and Vsync is unneeded, even at framerates approaching 200fps on a 60hz monitor.

                                                  According to you this is impossible.....
                                                  I assure you it is quite possible with the correct hardware and game engines.

                                                  If you suffer from screen tearing, its NOT something you will miss as its quite distracting and looks awful.....
                                                  --->For those users, different Vsync methods can be quite helpful.
                                                  (of course at a serious cost in FPS and input lag, that is unacceptable for competitive FPS gameplay)
                                                  *The best way to avoid screen tearing is not using Vsync, but spending alot more money on graphics horsepower, buying the correct monitor (and setting it up correctly) and then paying alot more attention to how USB polling works and what the effects are when using todays higher polling rate mouse devices.....  

                                                  Users should work with their system, games and drivers to find what works best for them.







                                                  Unfortunately, it doesn't matter how old you are, you are engaging in magical thinking regarding vsync, magical thinking is bad in the realm of computer science, and you should probobly not only read that link I posted, but google "how does vsync work" and educate yourself.

                                                  If you aren't employing some form of throttling to prevent buffer thrash, and you are actually tossing 200 frames through the link cable to your display as you claim, you are most likely going to experience the visual tearing vsync seeks to combat.  It's basic computer science 101 stuff.  It's science, not theory. 

                                                  Magical thinking is disastrous both to our hobby, and my occupation.  I spend literally my entire day dispelling magical thinking, don't think because you are old you are immune, in fact, older people are much more likely to engage in magical thinking to justify thier beliefs. 

                                                  That you would link USB polling rates and screen refresh based tearing is completely indicitive that you have leapt fully into the realm of magical thinking, and no longer even care how the monitor and video card interact.  Physical input has absolutely nothing to do with screen tearing.  This can be demonstrated by setting up a script to pan a camera at a set interval in a 3d scene, and removing vsync.  Provided rendering is occuring at a set, non variable, over 60, not divisible by 60 rate, the scene will always tear.

                                                   
                                                  I am glad your such an expert, please feel free to do whatever you want with your hardware
                                                   
                                                  You are a novice, sprouting what you have read on the internet.
                                                  I suppose you think the eye can only see 30 fps too.....
                                                   
                                                  Its a free country, say whatever you want bro...
                                                   Good day to you sir
                                                   
                                                  My experience levels and track record on these fourms speaks for itself.
                                                  I know what I am talking about, I live for this stuff bro.  
                                                    
                                                   
                                                  <message edited by maniacvvv on Wednesday, April 11, 2012 4:09 PM>
                                                   
                                                  MANIAC-VVV-'s 2013 Ultimate Nvidia Guide  -CLICK HERE-
                                                  MANIAC-VVV-'s Ultimate Battlefield 3 Guide  -CLICK HERE- 
                                                  MANIAC-VVV-'s Ultimate BFBC2 Settings Guide  -CLICK HERE-              

                                                   
                                                  #55
                                                    mblystone

                                                    • Total Posts : 618
                                                    • Joined: 8/21/2008
                                                    • Status: offline
                                                    Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 6:36 PM (permalink)
                                                    maniacvvv

                                                     
                                                     I am glad your such an expert, please feel free to do whatever you want with your hardware

                                                    You are a novice, sprouting what you have read on the internet.

                                                    I suppose you think the eye can only see 30 fps too.....

                                                    Its a free country, say whatever you want bro...
                                                    Good day to you sir

                                                    My experience levels and track record on these fourms speaks for itself.
                                                    I know what I am talking about, I live for this stuff bro.  
                                                     


                                                     
                                                    Dude, it's ok to not know how some things work.  We all learn a little something every day, but you are grasping now, and it's obvious.  I doubt you actually work in your hobbyist field, and that is ok, but you need to do some actual reading on how exactly the devices in your computer individually interact, if you honestly think, in any sense, usb polling rates, or anything else connected to that bus even, have any type of effect on monitor refresh artifacting, aside from data on a hard drive enforcing a vsync setting.
                                                     
                                                      Bottom line, vsync exists to resolve artifacts which are a direct result of an inability for the monitor to update more than 60 times a second.  That is what a 60hz refresh rate represents.  60 updates a second.  What your eye, and what my eye can percieve, are completely inconsequential with regard to the ability of your video output device to represent more than 60 discreet updates a second.  One hundred and twenty HZ monitors represent another thing.  A different thing, something with double the fidelity, a display which updates at one hundred and twenty times a second, which also polls the video card for input, you guessed it, one hundred and twenty times a second. 
                                                     
                                                    Vsync exists, because in certain circumstances, two different frames, with wildly different components, show a disparate image, and an artifact, or tear, separates the two displayed frames.  This is, indeed, unpleasing to the eye.  This effect can be mitigated by SYNCHRONIZING the output of the framebuffer and video card with the display device.  Again, this is not theory, this is actually how the process works.
                                                     
                                                    You remind me of my father, who was a radio technician, and to this day, insists that a microwave oven contains fissionable material or "is NUCLEAR!".  Please, trouble yourself to do some reading, not just online.  Here is what wikipedia has to say on the subject:
                                                     
                                                    http://en.wikipedia.org/w...rtical_synchronization
                                                     
                                                    ***********************************************
                                                    Vertical synchronization

                                                    Vertical synchronization (Also vertical sync or VSYNC) separates the video fields. In PAL and NTSC, the vertical sync pulse occurs within the vertical blanking interval. The vertical sync pulses are made by prolonging the length of HSYNC pulses through almost the entire length of the scan line.

                                                    The vertical sync signal is a series of much longer pulses, indicating the start of a new field. The sync pulses occupy the whole of line interval of a number of lines at the beginning and end of a scan; no picture information is transmitted during vertical retrace. The pulse sequence is designed to allow horizontal sync to continue during vertical retrace; it also indicates whether each field represents even or odd lines in interlaced systems (depending on whether it begins at the start of a horizontal line, or mid-way through).

                                                    The format of such a signal in 525-line NTSC is:
                                                    pre-equalizing pulses (6 to start scanning odd lines, 5 to start scanning even lines)
                                                    long-sync pulses (5 pulses)
                                                    post-equalizing pulses (5 to start scanning odd lines, 4 to start scanning even lines)

                                                    Each pre- or post- equalizing pulse consists in half a scan line of black signal: 2 µs at 0 V, followed by 30 µs at 0.3 V.

                                                    Each long sync pulse consists in an equalizing pulse with timings inverted: 30 µs at 0 V, followed by 2 µs at 0.3 V.

                                                    In video production and computer graphics, changes to the image are often kept in step with the vertical synchronization pulse to avoid visible discontinuity of the image. Since the frame buffer of a computer graphics display imitates the dynamics of a cathode-ray display, if it is updated with a new image while the image is being transmitted to the display, the display shows a mishmash of both frames, producing a page tearing artifact partway down the image.

                                                    Vertical synchronization eliminates this by timing frame buffer fills to coincide with the vertical blanking interval, thus ensuring that only whole frames are seen on-screen. Software such as video games and computer aided design (CAD) packages often allow vertical synchronization as an option, because it delays the image update until the vertical blanking interval. This produces a small penalty in latency, because the program has to wait until the video controller has finished transmitting the image to the display before continuing. Triple buffering reduces this latency significantly.

                                                    Two timing intervals are defined - the front porch between the end of displayed video and the start of the sync pulse, and the back porch after the sync pulse and before displayed video. These and the sync pulse itself are called the horizontal blanking (or retrace) interval and represent the time that the electron beam in the CRT is returning to the start of the next display line.
                                                    *******************************
                                                     
                                                    Now thats enough oldylocks.  Get Read.
                                                    <message edited by mblystone on Wednesday, April 11, 2012 6:39 PM>
                                                     
                                                    #56
                                                      tiddl3ywinks

                                                      • Total Posts : 10
                                                      • Joined: 8/28/2009
                                                      • Status: offline
                                                      Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 8:24 PM (permalink)
                                                      so im using a 590 and under the driver info it says it adds support for a 4th display but i cant seem to get it to work... this still for 600 and up cards? kinda confused :(
                                                       
                                                      #57
                                                        maniacvvv

                                                        • Total Posts : 7847
                                                        • Joined: 9/10/2009
                                                        • Location: Spokane WA
                                                        • Status: offline
                                                        • Ribbons: 122
                                                        Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 8:45 PM (permalink)
                                                        tiddl3ywinks


                                                        so im using a 590 and under the driver info it says it adds support for a 4th display but i cant seem to get it to work... this still for 600 and up cards? kinda confused :(


                                                        I'm not really sure if it will work using a dual GPU card like a 590
                                                         
                                                        Perhaps someone else with more 590 experience and surround knowledge will comment
                                                         
                                                        MANIAC-VVV-'s 2013 Ultimate Nvidia Guide  -CLICK HERE-
                                                        MANIAC-VVV-'s Ultimate Battlefield 3 Guide  -CLICK HERE- 
                                                        MANIAC-VVV-'s Ultimate BFBC2 Settings Guide  -CLICK HERE-              

                                                         
                                                        #58
                                                          tiddl3ywinks

                                                          • Total Posts : 10
                                                          • Joined: 8/28/2009
                                                          • Status: offline
                                                          Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 8:52 PM (permalink)
                                                          maniacvvv


                                                          tiddl3ywinks


                                                          so im using a 590 and under the driver info it says it adds support for a 4th display but i cant seem to get it to work... this still for 600 and up cards? kinda confused :(


                                                          I'm not really sure if it will work using a dual GPU card like a 590

                                                          Perhaps someone else with more 590 experience and surround knowledge will comment


                                                          hope so.. though with the drivers bein beta they might just have not removed the wording from the driver details part but who knows
                                                           
                                                          #59
                                                            catnlew

                                                            • Total Posts : 17
                                                            • Joined: 1/13/2012
                                                            • Status: offline
                                                            Re:Nvidia 301.24 BETA Wednesday, April 11, 2012 9:11 PM (permalink)
                                                            Just got a second 560 ti and installed in SLI today.  Did a clean install of the new beta drivers up from 280.62.  After a quick reboot, things appear to be working beautifully...  BF3 runs smoothly w/o problem.  Skyrim without a hint of micro stutter.
                                                             
                                                            I've had such bad luck with any of the drivers past 280.62 that I had given up-- but am feeling happy and lucky.
                                                             
                                                            Also, GPU temps appear to be much lower than before:  Previously, single GPU was running about 63 degrees during intense BF3 sessions, now both GPUs are running maybe 54-55 degrees max (top at 55, bottom at 53-54).  I have my original GPU over clocked by about 14%, but I think tomorrow I will probably reset to stock speeds until I run into something that gives it trouble.    (Of course, I am currently running games on a single monitor setup until I can save the scratch for a third)
                                                             
                                                            Gotta say, I'm happy!  Hope things work out well for those having problems... Will test more after work tomorrow.
                                                            Coolermaster Storm Enforcer (4 fans: front 240, top 240, back 140, side 140{ G.skill memory fan)  
                                                            I5-2500K (4.5 gHz)
                                                            GIGABYTE GA-Z68MA-D2H-B3 board
                                                            Thermalright Macho cooler
                                                            G.SKILL Ripjaws X Series 8GB SDRAM DDR3 1600 with G.Skill memory cooler
                                                            eVGA 560GTX Ti 2GB (stock)) x 2
                                                            Corsair Force 3 SSD 120gb boot
                                                            Seagate Barracuda ST500DM002 500GB 7200 RPM
                                                            Western Digital Caviar Blue 750 GB
                                                            Seasonic Platinum 1000 PSU 
                                                            Dell U2410 (photos)
                                                            Samsung Syncmaster 24 TN (games)
                                                            Windows 7 64bit
                                                             
                                                            #60
                                                              Change Page: < 123456 > | Showing page 2 of 6, messages 31 to 60 of 174

                                                              Jump to:

                                                              Current active users

                                                              There are 0 members and 1 guests.

                                                              Icon Legend and Permission

                                                              • New Messages
                                                              • No New Messages
                                                              • Hot Topic w/ New Messages
                                                              • Hot Topic w/o New Messages
                                                              • Locked w/ New Messages
                                                              • Locked w/o New Messages
                                                              • Read Message
                                                              • Post New Thread
                                                              • Reply to message
                                                              • Post New Poll
                                                              • Submit Vote
                                                              • Post reward post
                                                              • Delete my own posts
                                                              • Delete my own threads
                                                              • Rate post

                                                              2000-2013 ASPPlayground.NET Forum Version 3.8