Videocards - NVIDIA Drivers Section In this section you can discuss everything ForceWare driver related. ForceWare (Detonator) drivers are for NVIDIA TNT, Quadro and all GeForce based videocards.
|
|
|
|
Newbie
Videocard: 2x EVGA SC SE Titan
Processor: AMD 8 core @ 5ghz
Mainboard:
Memory:
Soundcard:
PSU: Corsair 1200
|

05-22-2013, 01:01
| posts: 4
Quote:
Originally Posted by Mraz
Ok, you can see my rig on the left here.
Before the Titan I had MSI Lightning GTX 680, and I have never experienced any slowdowns.
Now I have Titan and I can pretty much say the same, I have no problems whatsoever, after reading through this thread a bit I started fraps and turned on the FPS monitor thing, I've never go under 70 FPS with Titan, and I capped it in the video options at 120.
Anyway my point is that sometimes the slowdowns can occur if you OC your CPU or GPU too much that the OC is not stable.
Example of that at GPU is that the card doesnt ''crash'' because GDDR5 is correcting itself, but instead you get lower FPS or poor performance instead of what you could be getting. I have been pointed out at this numerous times by various users here, and after removing my OC on memory clock, and just by further OC'ing the core clock, I got higher and stable performance out of my GPU. Example was on BF3 I couldnt break 140 FPS no matter how much I pushed memory clock, but after setting it back to default, and as said above, pushing only core clock without memory, I got higher FPS then ever, and it is rock solid.
Same goes for CPU, after reaching 4.7 Ghz which does work 24/7 I got sometimes weird hiccups or even slow posting in W7, also some app's were behaving weird or were just slower then usual, and then by accident and advice from user --TK-- I was messing up with my OC settings, only to end up lowering it at 4.6 Ghz and give it a go. Result was, that my PC immediately felt snappier and started responding normally, and my theory on that is, that its vcore was barely enough to keep it running at 4.7 but it never crashed, resulting in poorer performance, as funny as it sounds.
So please guys as much problems as you have, please be 100% sure that what you're playing on is also 100% stable and rock solid, otherwise something like this is possible.
I would go for that one saying, its not always ''The more the better!''.
|
I understand what your saying but when I run Crisis 3, far cry and even witcher 2 with ubersampling without any issues whatsoever but borderlands keeps dropping FPS left and right then it is definitely a game specific issue.
Also if you google borderlands 2 and physx issue you will see a myriad of threads regarding the issue.
|
|
|
|
|
|
|
|
Newbie
Videocard: Asus GTX Titan + GTX680
Processor: Core I7-2700K @ 4.8Ghz
Mainboard: Asus Sabertooth Z77
Memory: 32GB TridentX 2400C10
Soundcard: Logitech Z4
PSU: Corsair AX1200W
|

05-22-2013, 07:24
| posts: 29 | Location: Slovenia
Back when the game was released, i play it with a 680 and a 560ti as a physx card and i had no issues. After the first DLC got released i got bored of the game and stopped playing.
When i bought the TITAN i wanted to see how the game performs and got the same issues as you guys had. Even with physx set to low, the game ran like crap. Well, guess what. After i threw in the 560ti as a dedicated physx card everything went back to normal.
So all of you who have 2 cards, do you still experience this issue if you dedicate one card for physx (select card and check "dedicate for physx" in NvCP)?
|
|
|
|
|
|
|
|
Master Guru
Videocard: Geforce GTX 680
Processor: Intel Core i7 2600k @4.6
Mainboard: GA-P67A-UD4B3
Memory: 16GB DDR3 1600 RipJaws
Soundcard: HT Omega Claro+ 7.1
PSU: Corsair 750w
|

05-22-2013, 13:24
| posts: 281
I tried running with a 680+460GTX as a dedicated PhysX card, and the performance was worse than just the single 680. The game is utterly broken for me.
|
|
|
|
|
|
|
|
Newbie
Videocard: Asus GTX Titan + GTX680
Processor: Core I7-2700K @ 4.8Ghz
Mainboard: Asus Sabertooth Z77
Memory: 32GB TridentX 2400C10
Soundcard: Logitech Z4
PSU: Corsair AX1200W
|

Yesterday, 00:09
| posts: 29 | Location: Slovenia
Hmmm thats strange, because we had pretty much a identical setup. Were you running the 460 in the second pci-e (x8) or the last one(x4)?
|
|
|
|
|
|
|
|
Ancient Guru
Videocard: 680 Classified 1306 /7200
Processor: 3570k @4.7Ghz
Mainboard: z77x UP4 TH
Memory: Dominator GT 2.4GHz 8gb
Soundcard: Asus Xonar dx
PSU: xfx 850w
|

Yesterday, 07:32
| posts: 3,138 | Location: Sunny Scotland
perhaps the 460 wasn't 'snappy' enough for bl2 (i'm not talking horse power) whereas the 560 was, there's another user with good results with a dedicated 650 in the PhysX section.
|
|
|
|
|
|
|
|
Newbie
Videocard: Asus GTX Titan + GTX680
Processor: Core I7-2700K @ 4.8Ghz
Mainboard: Asus Sabertooth Z77
Memory: 32GB TridentX 2400C10
Soundcard: Logitech Z4
PSU: Corsair AX1200W
|

Today, 13:16
| posts: 29 | Location: Slovenia
Maybe, but i highly doubt a 460 would not be snappy enough. Its just calculating Physx, nothing more. My 560`s usage in heavy physx scenes never goes above 20% (usually around 5-10%, so i dont think a 460 could not handle it. But then again, i am not an expert.
One thing got me thinking though. It is very, very weird that some have these issues, and some not, even with almost identical setups. Then i read the reaply from Gearbox to the user who sent him his "error logs". Gearbox said, that information was not "moving" fast enough through the PCI-E slots as it should-or something like that. Did anyone even try to manually set his primary PCI-E slot in the bios to Gen2 or Gen3 or in general tried to play with those settings. Most motherboard manufacturers leave it at auto, especially with the z77 series which support CPUs with gen2 and gen3 PCI-E lanes, and maybe the conflict could be the auto settings. Just wondering and trying to help if anyone still got the nerves to try to get to the bottom of this.
This should at least help those with dedicated physx cards. If you have one, put it in the x4 slot, and choose to run it in x4 mode instead of x1(?).
Single card users, if any of you remembers this post next time he boots up his system, and have a look at the PCI-E mode setting in the bios and report back i`d appreciate it.
Really sucks to have such issues on top end hardware in a year(?) old game which is otherwise great, but not being able to play it and having no concrete answer as to what the culprint is. Not to mention a fix/patch that would correct.
If this was already tried to no avail, then sorry for wasting your time.
Regards
BuBBle.D
Last edited by BuBBle.D; Today at 14:06.
|
|
|
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
Powered by vBulletin® Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
vBulletin Skin developed by: vBStyles.com
Copyright (c) 1995-2012, All Rights Reserved. The Guru of 3D, the Hardware Guru, and 3D Guru are trademarks owned by Hilbert Hagedoorn.
|