Does 175.16_geforce_winxp_32bit_english_whql.exe have problems withCRT TV output via composite?

Hello.

I finally decided to upgrade my installed v174.74 beta driver to v175.16
WHQL on my Windows XP Pro. SP2 system (IE6.0 SP2, all critical updates,
and optrional softwares excluding SP3 [will install later on when SP2 is
not supported anymore] this morning. I was expecting this upgrade to
work nicely and have no problems. Boy, was I wrong since I wasted about
an hour to figure out what's wrong and fix it.

The problem is that v175.16 WHQL driver broke my TV output (no picture).
I used to be able to have it either on as primary and secondary (mostly
for fullscreen videos and in clone setup). The driver didn't seem to
detect the TV either even if I set force deeper detection at Windows'
startup (kept detecting my 10+ years old 20" CRT TV as HDTV -- uh,
what?). I tried forcing "Composite - NTSC or PAL standard definitions
televisions" and picking USA, but I still didn't get anything on my TV
(blue screen -- not Windows' BSoD).

My old TV is connected to an old VCR that is connected to my EVGA
GeForce 7950 GT KO (512 MB; PCIE) video card with composite cables. I
thought it was a lose cable or something at first, but it wasn't because
I uninstalled NVIDIA driver, rebooted, reinstalled v174.74 beta, and had
TV output working nicely and perfectly like before. I believe the
problem is in this newest released driver and a bit concerned if future
versions will have this problem too.

Is anyone else having this problem too or just me? I didn't see anyone
else reporting issues like this. It must be a local issue. I also
tried uninstalling the beta driver, rebooting, and installing the WHQL
driver from scratch. It did not help.

I am getting fed up with NVIDIA's bad quality drivers and issues these
days (what happened to the good quality of v8x.xx and older drivers?). I
am going back to ATI/AMD video cards (even if they are slower) for my
next video card purchase (probably at the end of this year).

Thank you in advance.
--
"Many ants kill a camel." --Turkish
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
( ) or ANTant@zimage.com
Ant is currently not listening to any songs on his home computer.

Ant wrote:
> Hello.
>
> I finally decided to upgrade my installed v174.74 beta driver to v175.16
> WHQL on my Windows XP Pro. SP2 system (IE6.0 SP2, all critical updates,
> and optrional softwares excluding SP3 [will install later on when SP2 is
> not supported anymore] this morning. I was expecting this upgrade to
> work nicely and have no problems. Boy, was I wrong since I wasted about
> an hour to figure out what's wrong and fix it.
>
> The problem is that v175.16 WHQL driver broke my TV output (no picture).
> I used to be able to have it either on as primary and secondary (mostly
> for fullscreen videos and in clone setup). The driver didn't seem to
> detect the TV either even if I set force deeper detection at Windows'
> startup (kept detecting my 10+ years old 20" CRT TV as HDTV -- uh,
> what?). I tried forcing "Composite - NTSC or PAL standard definitions
> televisions" and picking USA, but I still didn't get anything on my TV
> (blue screen -- not Windows' BSoD).
>
> My old TV is connected to an old VCR that is connected to my EVGA
> GeForce 7950 GT KO (512 MB; PCIE) video card with composite cables. I
> thought it was a lose cable or something at first, but it wasn't because
> I uninstalled NVIDIA driver, rebooted, reinstalled v174.74 beta, and had
> TV output working nicely and perfectly like before. I believe the
> problem is in this newest released driver and a bit concerned if future
> versions will have this problem too.
>
> Is anyone else having this problem too or just me? I didn't see anyone
> else reporting issues like this. It must be a local issue. I also
> tried uninstalling the beta driver, rebooting, and installing the WHQL
> driver from scratch. It did not help.
>
> I am getting fed up with NVIDIA's bad quality drivers and issues these
> days (what happened to the good quality of v8x.xx and older drivers?). I
> am going back to ATI/AMD video cards (even if they are slower) for my
> next video card purchase (probably at the end of this year).
>
> Thank you in advance.

It's not you, there are a myriad of bizarre freshly hatched bugs with
this series of Forcewares due to the addition and rewrite of the video
engine, your specific method of use is affected.

It's called PureVideo HD or somesuch nonsense and television display is
part of that.

You can either fight with it, or revert back until the dust has settled,
which could be a while, a long while.

Mr.E Solved! wrote:
> Ant wrote:
>> Hello.
>>
>> I finally decided to upgrade my installed v174.74 beta driver to
>> v175.16 WHQL on my Windows XP Pro. SP2 system (IE6.0 SP2, all critical
>> updates, and optrional softwares excluding SP3 [will install later on
>> when SP2 is not supported anymore] this morning. I was expecting this
>> upgrade to work nicely and have no problems. Boy, was I wrong since I
>> wasted about an hour to figure out what's wrong and fix it.
>>
>> The problem is that v175.16 WHQL driver broke my TV output (no
>> picture). I used to be able to have it either on as primary and
>> secondary (mostly for fullscreen videos and in clone setup). The
>> driver didn't seem to detect the TV either even if I set force deeper
>> detection at Windows' startup (kept detecting my 10+ years old 20" CRT
>> TV as HDTV -- uh, what?). I tried forcing "Composite - NTSC or PAL
>> standard definitions televisions" and picking USA, but I still didn't
>> get anything on my TV (blue screen -- not Windows' BSoD).
>>
>> My old TV is connected to an old VCR that is connected to my EVGA
>> GeForce 7950 GT KO (512 MB; PCIE) video card with composite cables. I
>> thought it was a lose cable or something at first, but it wasn't
>> because I uninstalled NVIDIA driver, rebooted, reinstalled v174.74
>> beta, and had TV output working nicely and perfectly like before. I
>> believe the problem is in this newest released driver and a bit
>> concerned if future versions will have this problem too.
>>
>> Is anyone else having this problem too or just me? I didn't see anyone
>> else reporting issues like this. It must be a local issue. I also
>> tried uninstalling the beta driver, rebooting, and installing the WHQL
>> driver from scratch. It did not help.
>>
>> I am getting fed up with NVIDIA's bad quality drivers and issues these
>> days (what happened to the good quality of v8x.xx and older drivers?).
>> I am going back to ATI/AMD video cards (even if they are slower) for
>> my next video card purchase (probably at the end of this year).
>>
>> Thank you in advance.
>
> It's not you, there are a myriad of bizarre freshly hatched bugs with
> this series of Forcewares due to the addition and rewrite of the video
> engine, your specific method of use is affected.
>
> It's called PureVideo HD or somesuch nonsense and television display is
> part of that.
>
> You can either fight with it, or revert back until the dust has settled,
> which could be a while, a long while.

I've had to stick with the beta 174.74 as well. 175.16 has an odd bug
in BF2 and 2142 where it doesn't enumerate all available resolutions
(even standard ones) and thus causes it to CTD if you have anything
other than 800x600 or 1024x768 set beforehand. Reverting solves it, but
it's such an odd bug for what's been a very good driver series (17x.xx).

deimos wrote:

> I've had to stick with the beta 174.74 as well. 175.16 has an odd bug
> in BF2 and 2142 where it doesn't enumerate all available resolutions
> (even standard ones) and thus causes it to CTD if you have anything
> other than 800x600 or 1024x768 set beforehand. Reverting solves it, but
> it's such an odd bug for what's been a very good driver series (17x.xx).

I can't get BF2 to stay stable either, it quickly CTDs with no warning
or trace after a few minutes. The 175.16's are horrifying bad with
almost every game I've tried...nothing is stable.

Symptoms are looping audio with a freeze or a squeal and a freeze.
Creative even has new beta soundcard drivers to assist with this growing
problem.

I have no idea which driver to go back to, weren't there more than one
version of the 174.74 betas kicking around?

On 6/3/2008 2:49 PM PT, Mr.E Solved! typed:

>> I finally decided to upgrade my installed v174.74 beta driver to
>> v175.16 WHQL on my Windows XP Pro. SP2 system (IE6.0 SP2, all critical
>> updates, and optrional softwares excluding SP3 [will install later on
>> when SP2 is not supported anymore] this morning. I was expecting this
>> upgrade to work nicely and have no problems. Boy, was I wrong since I
>> wasted about an hour to figure out what's wrong and fix it.
>>
>> The problem is that v175.16 WHQL driver broke my TV output (no
>> picture). I used to be able to have it either on as primary and
>> secondary (mostly for fullscreen videos and in clone setup). The
>> driver didn't seem to detect the TV either even if I set force deeper
>> detection at Windows' startup (kept detecting my 10+ years old 20" CRT
>> TV as HDTV -- uh, what?). I tried forcing "Composite - NTSC or PAL
>> standard definitions televisions" and picking USA, but I still didn't
>> get anything on my TV (blue screen -- not Windows' BSoD).
>>
>> My old TV is connected to an old VCR that is connected to my EVGA
>> GeForce 7950 GT KO (512 MB; PCIE) video card with composite cables. I
>> thought it was a lose cable or something at first, but it wasn't
>> because I uninstalled NVIDIA driver, rebooted, reinstalled v174.74
>> beta, and had TV output working nicely and perfectly like before. I
>> believe the problem is in this newest released driver and a bit
>> concerned if future versions will have this problem too.
>>
>> Is anyone else having this problem too or just me? I didn't see anyone
>> else reporting issues like this. It must be a local issue. I also
>> tried uninstalling the beta driver, rebooting, and installing the WHQL
>> driver from scratch. It did not help.
>>
>> I am getting fed up with NVIDIA's bad quality drivers and issues these
>> days (what happened to the good quality of v8x.xx and older drivers?).
>> I am going back to ATI/AMD video cards (even if they are slower) for
>> my next video card purchase (probably at the end of this year).
>>
>> Thank you in advance.
>
> It's not you, there are a myriad of bizarre freshly hatched bugs with
> this series of Forcewares due to the addition and rewrite of the video
> engine, your specific method of use is affected.
>
> It's called PureVideo HD or somesuch nonsense and television display is
> part of that.
>
> You can either fight with it, or revert back until the dust has settled,
> which could be a while, a long while.

And that is going to suck since: 1) I need the latest drivers for the
newer games and fixes if any, and 2) I need to keep my **** TV out option!

NVIDIA, you suck now. From what I have read, ATI/AMD is looking good but
their gaming performances suck. Grr!
--
"The ants are back Ted!" --Dougal from Father Ted TV show.
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
( ) or ANTant@zimage.com
Ant is currently not listening to any songs on his home computer.

On 6/3/2008 5:31 PM PT, deimos typed:

> Mr.E Solved! wrote:
>> Ant wrote:
>>> Hello.
>>>
>>> I finally decided to upgrade my installed v174.74 beta driver to
>>> v175.16 WHQL on my Windows XP Pro. SP2 system (IE6.0 SP2, all
>>> critical updates, and optrional softwares excluding SP3 [will install
>>> later on when SP2 is not supported anymore] this morning. I was
>>> expecting this upgrade to work nicely and have no problems. Boy, was
>>> I wrong since I wasted about an hour to figure out what's wrong and
>>> fix it.
>>>
>>> The problem is that v175.16 WHQL driver broke my TV output (no
>>> picture). I used to be able to have it either on as primary and
>>> secondary (mostly for fullscreen videos and in clone setup). The
>>> driver didn't seem to detect the TV either even if I set force deeper
>>> detection at Windows' startup (kept detecting my 10+ years old 20"
>>> CRT TV as HDTV -- uh, what?). I tried forcing "Composite - NTSC or
>>> PAL standard definitions televisions" and picking USA, but I still
>>> didn't get anything on my TV (blue screen -- not Windows' BSoD).
>>>
>>> My old TV is connected to an old VCR that is connected to my EVGA
>>> GeForce 7950 GT KO (512 MB; PCIE) video card with composite cables. I
>>> thought it was a lose cable or something at first, but it wasn't
>>> because I uninstalled NVIDIA driver, rebooted, reinstalled v174.74
>>> beta, and had TV output working nicely and perfectly like before. I
>>> believe the problem is in this newest released driver and a bit
>>> concerned if future versions will have this problem too.
>>>
>>> Is anyone else having this problem too or just me? I didn't see
>>> anyone else reporting issues like this. It must be a local issue.
>>> I also tried uninstalling the beta driver, rebooting, and installing
>>> the WHQL driver from scratch. It did not help.
>>>
>>> I am getting fed up with NVIDIA's bad quality drivers and issues
>>> these days (what happened to the good quality of v8x.xx and older
>>> drivers?). I am going back to ATI/AMD video cards (even if they are
>>> slower) for my next video card purchase (probably at the end of this
>>> year).
>>>
>>> Thank you in advance.
>>
>> It's not you, there are a myriad of bizarre freshly hatched bugs with
>> this series of Forcewares due to the addition and rewrite of the video
>> engine, your specific method of use is affected.
>>
>> It's called PureVideo HD or somesuch nonsense and television display
>> is part of that.
>>
>> You can either fight with it, or revert back until the dust has
>> settled, which could be a while, a long while.
>
> I've had to stick with the beta 174.74 as well. 175.16 has an odd bug
> in BF2 and 2142 where it doesn't enumerate all available resolutions
> (even standard ones) and thus causes it to CTD if you have anything
> other than 800x600 or 1024x768 set beforehand. Reverting solves it, but
> it's such an odd bug for what's been a very good driver series (17x.xx).

I don't understand how NVIDIA certified this driver for release. Beta
was better than the certified!! I am scared to upgrade my NVIDIA drivers
now.
--
"If you're an ant, and you're walking along across the top of a cup of
pudding, you probably have no idea that the only thing between you and
disaster is the strength of that pudding skin." --Jack Handy from
Saturday Night Live
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
( ) or ANTant@zimage.com
Ant is currently not listening to any songs on his home computer.

On 6/3/2008 9:20 PM PT, Mr.E Solved! typed:

> I have no idea which driver to go back to, weren't there more than one
> version of the 174.74 betas kicking around?

Tip for you: Always keep the previous driver(s) that worked just in
case. I am glad I kept the working one before 175.16 even if it is a beta.
--
"If someone makes you angry, I think the thing to do is tie them down to
the ground, cover them in honey, and then release a swarm of killer ants
on them. That way, you can hit them over and over again and say, 'Hey!
I'm just trying to help!' and they can't really get mad at you." --R.M.
Weiner
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
( ) or ANTant@zimage.com
Ant is currently not listening to any songs on his home computer.

Ant wrote:
> On 6/3/2008 9:20 PM PT, Mr.E Solved! typed:
>
>> I have no idea which driver to go back to, weren't there more than one
>> version of the 174.74 betas kicking around?
>
> Tip for you: Always keep the previous driver(s) that worked just in
> case. I am glad I kept the working one before 175.16 even if it is a beta.

Aren't you cute thinking I don't have the entire library of versions to
pick and choose from. <pinches your cheek>

At issue is I don't know which version to use, since the past several
save been steadily degrading performance, also I use nhancer which makes
it problematic to deal with video driver uninstalling and reinstalling.

NVidia has purposely tried to lock out nhancer's meddling, and you have
to play the matching-version game or nothing works.

Not to mention ntune needs to be uninstalled and reinstalled in the
proper order in the driver update process, if you want to be sure of
getting the right settings as ntune and the new nvidia control panel are
now permanently entwined.

There is lots of dark pc-juju floating around these days, I don't like
it one bit.

On 6/3/2008 10:35 PM PT, Mr.E Solved! typed:

>>> I have no idea which driver to go back to, weren't there more than
>>> one version of the 174.74 betas kicking around?
>>
>> Tip for you: Always keep the previous driver(s) that worked just in
>> case. I am glad I kept the working one before 175.16 even if it is a
>> beta.
>
> Aren't you cute thinking I don't have the entire library of versions to
> pick and choose from. <pinches your cheek>

Heh, ants don't have cheeks. [grin] Too bad we can't use very old
drivers like 81.xx for the newer cards and newer games/software.


> At issue is I don't know which version to use, since the past several
> save been steadily degrading performance, also I use nhancer which makes
> it problematic to deal with video driver uninstalling and reinstalling.
>
> NVidia has purposely tried to lock out nhancer's meddling, and you have
> to play the matching-version game or nothing works.
>
> Not to mention ntune needs to be uninstalled and reinstalled in the
> proper order in the driver update process, if you want to be sure of
> getting the right settings as ntune and the new nvidia control panel are
> now permanently entwined.
>
> There is lots of dark pc-juju floating around these days, I don't like
> it one bit.

Yep, I hate it. I ask myself why I am in the IT industry as a software
quality assurance tester/analyst. :/
--
"An ant on the move does more than a dozing ox." --Mexican Proverb
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.home.dhs.org (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Remove ANT from e-mail address: philpi@earthlink.netANT
( ) or ANTant@zimage.com
Ant is currently not listening to any songs on his home computer.

>
> I don't understand how NVIDIA certified this driver for release. Beta
> was better than the certified!! I am scared to upgrade my NVIDIA drivers
> now.

WHQL = windows hardware quality labs. If this driver is certified it's a big mistake by microsoft. I don't think it is qualified for xp since 175.16 (beta) breaks remote desktop on the machine it's installed on. You can't remote desktop into the system. http://forums.nvidia.com/index.php?s...ic=67147&st=20