GeForce 6150 issues

[asthepenguinfly]

I've installed them on my MSI 6150, and vmr9 appears to be working now. HOORAY. Also, some of the flicker seems to be resolved, but I'm gonna change some settings regarding noise reduction as per the stuff above and see what happens.

I'm at a unique position because I'm unsure whether all of my flicker comes from purevideo/drivers or if it comes during capture from my dualtv. Dualtv and xp home don't get along in terms of customizing.

There is a little instabillity in the drivers though evertime I click on the control panel the screen does a little flash.

[BruenerXII]

I also just installed these new 93.71 drivers and they seem to have fixed my ASUS M2NPV-VM 6150 VMR corruption problem.. See here: http://forums.sagetv.com/forums/showthread.php?p=187226

IncredibleHat, try them out man.. I'm almost sure they will work for you!

[IncredibleHat]

I yam I yam! I already installed them on my Gaming rig... and Pirates of the Caribbean didn't barf on them like it has on all prior 9x.xx drivers, so thats a good sign

I need to pull myself away from the game long enough to go mess with the HTPC now

EDIT:
Yeah, my discussions on the issue too:
http://forums.freytechnologies.com/f...ad.php?t=20329
http://forums.freytechnologies.com/f...9&postcount=26

Image: http://swankyplace.com/forumimgs/fuggenvidia.jpg

[emok]

After uninstalling and reinstalling the drivers, the problem hasn't returned. My corruption issues on a K8NGM2-FID seem to be resolved as well with the latest drivers.

The only random issue I have is with the Nvidia Control Panel giving inconsistent behavior. I had to switch to classic control panel and reboot to change some of the settings (overscan compensation). Then I switched back to the new control panel and now there were new selections. Kind of strange.

But so far, I'm happy.

E

[kricker]

-IncredibleHat
let me know how it goes, I am tempted to try them from the others reports, but we have been down this road before so I am still warry. The wife is not happy when I screw with things.

-everyone else
Are any of you using the DVI? and if so have you adjusted it per the release notes for color space:

Video color-space range for DVI-only* outputs is erroneously set to
standard mode (16-235) instead of extended mode (0-255).
A new detection feature to apply Standard CSC mode to TV outputs
(including NTSC, PAL, 480i, and 576i), included DVI-only outputs by
mistake.
Note: The driver correctly applies extended mode to analog outputs, and
standard mode to TV outputs (including NTSC, PAL, 480i, and 576i).
A future driver release will correct this and apply the extended-mode color
space to DVI-only outputs.
You can work around this issue by forcing either standard or extended mode
as follows:
* “DVI-only” means only one display is connected, and it is to the DVI output.

1 Launch regedit and determine the current primary display card by
looking in
HKey_Local_Machine\Hardware\DeviceMap\Video
and note the GUID (global unique identifier assigned by Windows),
which is the long string in brackets { } at the end of the entry
ʺ\device\video0ʺ.
2 Look in
HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\Video\
{GUID}\0000
where {GUID} is the number derived from the previous step.
3 Open the ʺ0000ʺ directory and create a new DWORD called
VMRCCCSStatus and give it a value of
0x3 - to force use of the standard YUV range of 16-235
0x1 - to force use of the extended YUV range of 0-255

-BruenerXII
you have the same board as me, are you using an x2 processor? If so did you have to do any of the following:

There may be intermittent application compatibility issues with dual
core CPUs.
If you experience this issue, first make sure you have downloaded and
installed the dual core patches from your CPU manufacturer and from
Microsoft. The Microsoft knowledge base article is available at:http://
support.microsoft.com/?id=896256.
If you still experience problems you can attempt to work around these by
toggling off NVIDIA’s multithread optimizations using the following
instructions:
1 Launch regedit and determine the current primary display card by
looking in
HKey_Local_Machine\Hardware\DeviceMap\Video
and note the GUID (global unique identifier assigned by Windows),
which is the long string in brackets { } at the end of the entry
ʺ\device\video0ʺ.
2 Look in
HKey_Local_Machine\SYSTEM\CurrentControlSet\Control\Video\
{GUID}\0000
where {GUID} is the number derived from the previous step.
3 Open the ʺ0000ʺ directory and create a new DWORD called
OGL_ThreadControl and give it a value of 2.
This will disable multithreading in the driver for all OpenGL applications.
4 If you want to disable driver multithreading for all Direct3D applications–
In the same ʺ0000ʺ directory, create a new DWORD called
WTD_EXECMODEL and give it a value of 0.

[kricker]

Originally Posted by emok

Issues Resolved in Version 93.71:

• GeForce 6150/6100: Video gets corrupted if attempted to be played using any media player and any driver past 82.05. Problem not present when user does not try to play videos. =)

I don't see that anywhere in the release notes either.

[blade]

Works for me. I just installed on top of my old drivers, which were the latest release that did have the grid problem. I know I'm lazy, but it works with VMR9 so I'm happy.

[BruenerXII]

Originally Posted by kricker

-BruenerXII
you have the same board as me, are you using an x2 processor? If so did you have to do any of the following:

No I dont have an x2 processor. Just a Athlon 64 3200+.
If you are worried about trying these drivers, just create a system restore point first. Then you can always fall back to where you are now.

[kricker]

Originally Posted by BruenerXII

No I dont have an x2 processor. Just a Athlon 64 3200+.
If you are worried about trying these drivers, just create a system restore point first. Then you can always fall back to where you are now.

yeah yeah I know...but you know how it goes...think it's easy to go back, but then something else happens....good ole Murphy's law.

[emok]

Originally Posted by kricker

I don't see that anywhere in the release notes either.

"nvidia recommends playing videos of pigs flying to avoid the problem"...

Just havin' a little fun. In any case, since it looks like the issue may be resolved, maybe they should add that to the release notes.

[emok]

Originally Posted by kricker

-IncredibleHat
let me know how it goes, I am tempted to try them from the others reports, but we have been down this road before so I am still warry. The wife is not happy when I screw with things.

-everyone else
Are any of you using the DVI? and if so have you adjusted it per the release notes for color space:

-BruenerXII
you have the same board as me, are you using an x2 processor? If so did you have to do any of the following:

I'm using DVI and have not tried the color space adjustments.

I'm using an X2 and did install the microsoft patch and the AMD driver. I've also tried the nvidia registry hack. For me, NO combination of the three was able to get around the video corruption problem.

[kricker]

-emok
I am a bit confused. A few posts up you say your problem has been fixed, but this last post reads as if you still have VMR9 playback issues. Can you clarify?

[emok]

Originally Posted by kricker

-emok
I am a bit confused. A few posts up you say your problem has been fixed, but this last post reads as if you still have VMR9 playback issues. Can you clarify?

Sorry, I meant that previously, no combintation of the three would help me get around the problem. The only thing that fixed the corruption issue for me was using the 82.05 drivers from the MSI website.

BUT with the new drivers, everything seems to be working fine, with the exception of some random nvidia control panel issues I'm seeing. But the video corruption problem seems to be resolved.

I STILL have the microsoft hotfix and the AMD drivers installed, but I did not implement the nvidia registry hack.

E

[kricker]

Ok. Thank You.

[IncredibleHat]

OK! My results in:

Initial tests of all the possible times it occurred before, returned perfectly fine and fluid playback! No more freaky boxies!

SageTV -> Going to LiveTV after UI Launch used to cause the boxies. NO MORE!
Zoomplayer -> Setting to VMR9 Renderless used to make all movies into boxies. NO MORE!

Yay.

I still notice a random occurrance where when I dive right into LiveTV, the screen kinda flickers a gross mess on the far right of the screen (about a split seconds worth), but never returns. And totally random, but its done this before long long time, so its prolly a Sage thing or Hauppauge thing.

These drivers didnt fix ALL the issues I had, one unrelated issue is Zoomplayer no longer could 'zoom out' beyond the screen edge centered ever since 9x.xx was introduced. Blight (Lead developer of Zoomplayer) claims its an nvidia issue that he has been trying to get nvidia to fix ever since 9x.xx started. I say he will have to try harder to convince them, as nvidia ignored my bug repot on that (yet responded to the 6150 boxies bug).

On my game machine, these drivers appear to run decent enough so far. But I have not run through the myraid of games I have on that machine yet. Initial tests result in decency (again, totally unrelated hardware to the 6150).

[IncredibleHat]

Oh... yeah:

DVI Output to HDMonitor at 720p resolution (I havnt really tried pushing my 6150 up to 1080p yet).

[kricker]

Did you make the DVI color space correction in the registry?

[IncredibleHat]

Did I do what? No... not unless its automatic. I don't like messin with the registry unless I absolutly have too.

[kricker]

...well most likely then your color output from the DVI connector is wrong. It is using the 16-235 color space instead of the 0-255.

[IncredibleHat]

Uh... ok. But I thought for output to a TV, you COULDNT do 0-255 as they only understand 16-235 (I mean, its why you have to calibrate your capture cards so they stop clipping the blastid whites and blacks). Right?

What is this registry hack thou speakeths of?