oZone wrote:Problem with Nvidia is on Windows 7 (on Windows 10 no, same PC multiboot) and on Windows 10 (other PC with different card). Intel only Windows 10 (other PC, thanks to friends I can test it with different configuration ). All drivers are latest from Intel or Nvidia, or from Windows update.
I have spent a couple of hours scratching my head on this issue. I could reproduce it on my laptop with the same intel integrated chip. We did find a fix for this, but it is not something we were happy with as it included a pretty massive hit to the cpu usage.
oZone, I beg of you... We need to get clear and specific about what is going on.
We need to know very clearly and unambiguously what hardware and OS you are on when you see and don't see the issue in question. We need to know when you last updated the drivers for the graphics hardware.
We are currently under the impression that this ONLY happens on a system that has a CPU with Intel Integrated Graphics built in. It doesn't matter if the OS is Win7 or Win10. This NEVER happens when using discrete graphics that are not using shared memory and integrated into the CPU.
jsmorley wrote:oZone, I beg of you... We need to get clear and specific about what is going on.
We need to know very clearly and unambiguously what hardware and OS you are on when you see and don't see the issue in question. We need to know when you last updated the drivers for the graphics hardware.
We are currently under the impression that this ONLY happens on a system that has a CPU with Intel Integrated Graphics built in. It doesn't matter if the OS is Win7 or Win10. This NEVER happens when using discrete graphics that are not using shared memory and integrated into the CPU.
Another friend is traveling, so I can't check it, but he is using only Windows 10 and he said that it appears only when he use Nvidia card, I think it's 500m series.
I use Windows 10 and have Intel HD 630 with Nvidia GeForce GTX 1050 Ti. The issue appears only with Intel card.
theAzack9 wrote:
I have spent a couple of hours scratching my head on this issue. I could reproduce it on my laptop with the same intel integrated chip. We did find a fix for this, but it is not something we were happy with as it included a pretty massive hit to the cpu usage.