Issues in Win7 browsers (video color range, stutter in games)

[Dixel]

On 5/19/2024 at 1:56 AM, D.Draker said:

Sounds very much like your monitor is over-contrast to begin with. Try lower your contrast first, as full RGB looks amazing and shouldn't put strain on eyes.

Yes. and some people are sensitive to LED lights, thus using LED back-lit monitors isn't recommended. I still use an old CCFL, and full RGB looks good.

[test5362]

On 5/29/2024 at 3:11 AM, superleiw said:

In your first post you mentionned that you were using Webrender, is this still true? Did you manually enable it?

Because most of these settings only work on W10+.

 

In about:config those two options are for W10+ so maybe you can try setting them to False :

gfx.webrender.all -> true (Windows 10/11 only)
gfx.webrender.software -> true (Uses CPU instead of GPU but requires Windows 10+)

The following options might also need to be reset to their default values :

gfx.webrender.enabled
gfx.webrender.compositor
gfx.webrender.compositor.force-enabled

Yes, I'm indeed using Webrender, I may have possibly set it at one point because scrolling exhibited tearing otherwise. At least that was the case in the old days where it was just hardware acceleration on/off the in the regular options. But it's been so long that I don't know for sure.

I'm aware that the browser disables certain functions on Win7, specifically WEBRENDER_DCOMP_PRESENT/WEBRENDER_COMPOSITOR (FEATURE_FAILURE_DCOMP_NOT_WIN10). Also ACCELERATED_CANVAS2D shows as "Disabled by default" due to "FEATURE_FAILURE_DISABLED", not sure if that stems from the aforementioned one. And WebGPU is also blocked ("WebGPU cannot be enabled in release or beta", WEBGPU_DISABLE_RELEASE_OR_BETA). In any case, of the flags you mentioned only gfx.webrender.compositor was actually true, but it's blocked anyway as I just said. I did try to set it to false anyway which expectedly changed nothing for the video issue.

The flag that enables Webrender in my case is probably one of these:

gfx.webrender.software.d3d11=true
gfx.webrender.enabled-no-gpu-process-with-angle-win=true

Edited June 5 by test5362

[test5362]

I finally got around to check the browser flags in a comparison with the laptop, and deleted a whole bunch of those that didn't exist on the laptop and looked like they could be related to the issue, but unfortunately no success. I simply can't get hardware accelerated video to not look washed out in Firefox, using the GTX 1060. It could still be some very obscurely named flag that I missed, but at this point I rather think that video acceleration might have not been tested with this newer card under Win7, or that it's a driver issue (I have a problem with blank selection menus in the multi-monitor driver tab that I could never fix with driver updates so far).

Comparing about:support doesn't yield anything interesting either, only thing that stands out to me is that the pixel ratio on the 1060 is listed as 1,1,1,1 while on the laptop it says 1, which I don't really understand. The only other thing is that a couple of the browser flags were shader related or device ID related and showed newer versions on the 1060 setup, but I didn't really feel like changing those to what is shown on the laptop, the hardware is different after all.

At this point I'm probably done with this unless someone else with a Pascal card and Win7 is willing to test this issue. Here is the list of flags that I changed:

sanity-test.advanced-layers false -> true

All deleted:

layers.m true
layers.mlgpu.sanity-test-failed false
gfx.crash-guard.d3d11layers.appVersion	55.0
gfx.crash-guard.d3d11layers.deviceID	0x1c03
gfx.crash-guard.d3d11layers.driverVersion	22.21.13.8233
gfx.crash-guard.d3d11layers.feature-d2d	true
gfx.crash-guard.d3d11layers.feature-d3d11	true
gfx.crash-guard.glcontext.appVersion	45.0.2
gfx.crash-guard.glcontext.deviceID	0x11c0
gfx.crash-guard.glcontext.driverVersion	10.18.13.6472
gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle	true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle	true
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11	false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp	false
gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11	true
gfx.crash-guard.status.d3d11layers	2
gfx.crash-guard.status.d3d9video	2
gfx.crash-guard.status.glcontext	2
gfx.webrender.force-disabled	false

 

Edited June 19 by test5362

[lll888]

I think you're just looking in the wrong direction.
The fact is that hard telemetry was built into the Nvidia driver, which is watching you and this is the cause of all the troubles.
The latest normal driver version is 446.14.
If you want to install a new driver, then use the NVSlimmer utility, plus the rest needs to be modified manually so that this does not happen in your system, then everything will work well.
 

[D.Draker]

5 hours ago, lll888 said:

The fact is that hard telemetry was built into the Nvidia driver, which is watching you and this is the cause of all the troubles.
The latest normal driver version is 446.14.

The last driver without telemetry was 372.73 and 372.95

[lll888]

Perhaps I won’t argue, but I meant hard telemetry, which leads to freezing. This can be said in online mode, they monitor what you are doing there ))

[Dixel]

On 7/2/2024 at 8:32 AM, D.Draker said:

The last driver without telemetry was 372.73 and 372.95

I second this, telemetry was introduced in 373.19. It even had a restoration file "recovery.bat" file (in case someone was clever enough to delete it).

[lll888]

I don’t even know what you’re talking about, but I cut out all the telemetry from the system a long time ago.

Telemetry interferes with work, eats up resources, plus I don’t like to be followed, and those who like it installed win 10, so the users are divided and only those who are on win 7 are close to me

[Dixel]

8 hours ago, lll888 said:

I don’t even know what you’re talking about, but I cut out all the telemetry from the system a long time ago.

Most likely, you didn't notice (that's the idea!), Nvidia installer puts the file "recovery.bat" into Windows folder. 

It's not enough to simply delete the files you wrote about, read in the comments on that link.

"Disable the service, restart computer, remove the registry entries, restart computer and then remove the telemetry folders and telemetry recovery.bat in the Windows folder."

https://www.ghacks.net/2018/01/20/how-to-block-the-chrome-software-reporter-tool-software_reporter_tool-exe/

Or use the tool NVSlimmer (driver slimmer).

 

Edited July 4 by Dixel

[test5362]

You guys are seriously thinking that Nvidia telemetry causes washed out video in Firefox? Because I don't think these issues are related at all and Nvidia telemetry discussion would be really better off in a seperate thread.

But fine, I'll bite, I haven't actually seen the telemetry container process or any services in years, and certainly don't have any recovery.bat in my Windows folder. I think all of that is outdated information for current drivers and if telemetry is in there it's not visible by these factors anymore.

[lll888]

I don’t think that video blurring in Firefox is caused by telemetry, I can’t say, I’ve never had this happen, but you need to install the drivers correctly from the very beginning so as not to blame them later.
After processing nvslimmer, go to the Display.Driver folder, open the files via notepad2 and erase everything that is there by preserving
DisplayDriverRAS.dll
NvProfileUpdaterPlugin.dll
NvTelemetry64.dll
nvtopps.db3
nvtopps.dll

and then just install the driver
after installing the driver, go to drive C and insert the names of these files into the search in the upper right corner and delete everything using unlocker
This is how to install this driver correctly ))

That is, first erase everything that is there in these files and after installation, then delete them.

After my online game began to freeze, I spent a couple of days to understand how to install this driver correctly and there were no more problems

and I have Firefox 127 version installed on win 7 and it works fine

Edited July 5 by lll888

[D.Draker]

I once had a weird colour problems, it was caused by a worn out, old HDMI cable, once I replaced it with a good shielded cable, all came back to normal. Don't buy China cables, they lack good copper.

The best ones are still left on the market are Dutch or maybe Japan.

[lll888]

8 часов назад, Д.Дрейкер сказал:

 

We don’t take the cable into account, as we hope that this was taken into account when purchasing, do not buy a fake cable ))

[D.Draker]

On 7/6/2024 at 5:02 PM, lll888 said:

We don’t take the cable into account, as we hope that this was taken into account when purchasing, do not buy a fake cable ))

On my spare setup, which I keep in the storage room (video surveillance), I had an odd issue with the contrast, It was changing during the day. I thought it was browser and/or surveillance software related, unless I realised it was linked to the dried out capacitors in one of the monitors. But it glitched out ALL monitors connected to the card!