nVidia newer drivers degrading??

[ZimZum]

Originally posted by: Keysplayr
Things have pretty much been explained to you. If it was the driver, EVERYONE would be BSOD with them, wouldn't they?

Keys you know enough about computers to understand thats not how it works. Unless you can replicate his exact hardware and software specs you cant say he doesn't have an issue. All you can say is on your system you haven't had any issues. But your not even running the same graphics hardware he is, let alone the rest of his setup.

 

[Keysplayr]

Originally posted by: Phynaz

Originally posted by: Keysplayr
Things have pretty much been explained to you. If it was the driver, EVERYONE would be BSOD with them, wouldn't they?

Not necessarily, many driver bugs affect just a particular configuration, such as a particular bios version, interactions with other drivers, etc.

EXACTLY!!!!! I was actually counting on Yusux disagreeing with me and saying this very thing, but I guess you beat him to it.

 

[Keysplayr]

Originally posted by: ZimZum

Originally posted by: Keysplayr
Things have pretty much been explained to you. If it was the driver, EVERYONE would be BSOD with them, wouldn't they?

Keys you know enough about computers to understand thats not how it works. Unless you can replicate his exact hardware and software specs you cant say he doesn't have an issue. All you can say is on your system you haven't had any issues. But your not even running the same graphics hardware he is, let alone the rest of his setup.

See my above post to Phynaz.

 

[n7]

Originally posted by: pcslookout

Originally posted by: cmdrdredd
Lots of ppl over at guru3d forums have trouble with anything past 186.18 driverset. I can't touch the 190.xx or I have a lot of various issues.

Same here but strangely people say the 190.62 work great in windows xp but not vista or 7 ?

How strange is that?

The other thing is all drivers after 182.50 or all 190. drivers, for some strange reason, make your tv out screen if you use this a lot smaller on the left and right. I have never found a fix to this and need to sense I use a projector. I don't want my 92" screen to be smaller than it needs to be. Sucks. I was reading with the newest nvidia drivers and wdm 1.1 there was going to be some horrible changes. Looks like that is one.

I have the same issue with my GTX 260 + projector :frown:

I tried everything to fix it, but nothing works other than downgrading the drivers to much older sets.

I know this isn't a popular opinion, but i simply have not found nV's drivers to be decent in Vista pretty much ever.
When Vista first came out, it took forever for them to be even stable (no BSODs, especially when alt-tabbing).

They finally got that figured out, but then new problems cropped up, like no matter what some of us nV users tried, L4D would lock up or stutter randomly.

I swear there is something new (or old) with most of the drivers, that effs up with pretty much every nV card (8800 GTX/GTX 260/GTX 280) i've had in Vista.

I had no idea how smooth life could be until i switched my main rig over to an HD 4890.

Obviously, not everyone has such issues w/ nV & lack of with AMD, but wow, it's made a world of difference for me.

 

[Keysplayr]

Originally posted by: n7

Originally posted by: pcslookout

Originally posted by: cmdrdredd
Lots of ppl over at guru3d forums have trouble with anything past 186.18 driverset. I can't touch the 190.xx or I have a lot of various issues.

Same here but strangely people say the 190.62 work great in windows xp but not vista or 7 ?

How strange is that?

The other thing is all drivers after 182.50 or all 190. drivers, for some strange reason, make your tv out screen if you use this a lot smaller on the left and right. I have never found a fix to this and need to sense I use a projector. I don't want my 92" screen to be smaller than it needs to be. Sucks. I was reading with the newest nvidia drivers and wdm 1.1 there was going to be some horrible changes. Looks like that is one.

I have the same issue with my GTX 260 + projector :frown:

I tried everything to fix it, but nothing works other than downgrading the drivers to much older sets.

I know this isn't a popular opinion, but i simply have not found nV's drivers to be decent in Vista pretty much ever.
When Vista first came out, it took forever for them to be even stable (no BSODs, especially when alt-tabbing).

They finally got that figured out, but then new problems cropped up, like no matter what some of us nV users tried, L4D would lock up or stutter randomly.

I swear there is something new (or old) with most of the drivers, that effs up with pretty much every nV card (8800 GTX/GTX 260/GTX 280) i've had in Vista.

I had no idea how smooth life could be until i switched my main rig over to an HD 4890.

Obviously, not everyone has such issues w/ nV & lack of with AMD, but wow, it's made a world of difference for me.

You have definitely had a train wreck of bad luck with NV. So I can sympathize, because I had the very same, with ATI. I guess our experiences form our preferences one way or the other. Natural I guess.

 

[nOOky]

I have tried/uninstalled every new driver since the 190's, but the older drivers still work flawlessly so I use them. Of course I have an older card now, so I don't expect too much support. Same with ATI, certain releases suck, some work better than others.

 

[pcslookout]

Originally posted by: n7

Originally posted by: pcslookout

Originally posted by: cmdrdredd
Lots of ppl over at guru3d forums have trouble with anything past 186.18 driverset. I can't touch the 190.xx or I have a lot of various issues.

Same here but strangely people say the 190.62 work great in windows xp but not vista or 7 ?

How strange is that?


found a fix to this and need to sense I use a projector. I don't want my 92" screen to be smaller than it needs to be. Sucks. I was reading with the newest nvidia drivers and wdm 1.1 there was going to be some horrible changes. Looks like that is one.

I have the same issue with my GTX 260 + projector :frown:

I tried everything to fix it, but nothing works other than downgrading the drivers to much older sets.

I know this isn't a popular opinion, but i simply have not found nV's drivers to be decent in Vista pretty much ever.
When Vista first came out, it took forever for them to be even stable (no BSODs, especially when alt-tabbing).

They finally got that figured out, but then new problems cropped up, like no matter what some of us nV users tried, L4D would lock up or stutter randomly.

I swear there is something new (or old) with most of the drivers, that effs up with pretty much every nV card (8800 GTX/GTX 260/GTX 280) i've had in Vista.

I had no idea how smooth life could be until i switched my main rig over to an HD 4890.

Obviously, not everyone has such issues w/ nV & lack of with AMD, but wow, it's made a world of difference for me.

That sucks. My next video card I think will be a ATI if my Geforce 8800 GTS 320 ever dies or I feel like upgrading. It won't be purely ATI because of nvidia drivers but based on price too.

The only thing I am worried about is the stupid CCC I think with ATI drivers that you must have installed. Think you need .net and java as well. I know it is one or the other can't remember.

 

[yusux]

Originally posted by: Keysplayr
Things have pretty much been explained to you. If it was the driver, EVERYONE would be BSOD with them, wouldn't they? So cover your ears and scream LaLaLaLa like this and you won't get very far. Got another hard drive to spare? If so, you know what to do.

It is the driver's fault, my 182 and 185 didn't lock the cards clock @ 400/800 like the new 190, who said anything about BSOD? DID I SAY ANYTHING ABOUT BSOD? NO.

You are being a sarcastic little ass prick, but it is standard for most dramafags.

nVidia fires rollo and hires Keysplayr :roll:

 

[yusux]

Originally posted by: Keysplayr

Originally posted by: Phynaz

Originally posted by: Keysplayr
Things have pretty much been explained to you. If it was the driver, EVERYONE would be BSOD with them, wouldn't they?

Not necessarily, many driver bugs affect just a particular configuration, such as a particular bios version, interactions with other drivers, etc.

EXACTLY!!!!! I was actually counting on Yusux disagreeing with me and saying this very thing, but I guess you beat him to it.

You're the one whose disagreeing with me on the fact that nvidia released latest piece of shit win7 drivers for my 285.

 

[Keysplayr]

Originally posted by: yusux

Originally posted by: Keysplayr
Things have pretty much been explained to you. If it was the driver, EVERYONE would be BSOD with them, wouldn't they? So cover your ears and scream LaLaLaLa like this and you won't get very far. Got another hard drive to spare? If so, you know what to do.

It is the driver's fault, my 182 and 185 didn't lock the cards clock @ 400/800 like the new 190, who said anything about BSOD? DID I SAY ANYTHING ABOUT BSOD? NO.

You are being a sarcastic little ass prick, but it is standard for most dramafags.

nVidia fires rollo and hires Keysplayr :roll:

Like I said, it's your system configuration. If it were the driver, I'd be having the same problems you are. I started with a fresh system install of Win7 64 bit, all latest drivers, and it's working very nicely. The BSOD reference was taken from geoffry, who was posting right alongside you in this thread.

As for your comment above? That is a "gotcha" moment. This type of response is usually when someone is angry when something is suggested to them that they might be wrong and cannot handle it.

"You're the one whose disagreeing with me on the fact that nvidia released latest piece of shit win7 drivers for my 285."

Indeed I am. You've been shown otherwise by not only myself, but a few others in this thread that the new driver presents no problems for them. Ignored it. It's you, and your rig, and it's current configuration. If I were having your problems, I'd agree with you. But I am not, so I can't. Get yourself a spare hard drive and do a fresh install. Yes, ignore this to. :roll:

You've got problems with your rig. At least make a half hearted attempt to solving it.