16.1.1 Update Visual Glitch

Hello. Since the 16.1.0 I'm having a visual glitch I uninstalled it and installed it again, even the 16.1.1 but it didn't solve anything.

To be more explicit, the problem is that I get some visual "noise" around subtitles and around any "text" showing on my MPC-HC. Here are some examples:

The last image is when I click the skip frames command.




Everything else is working fine but my OCD doesn't let me focus on what I'm reading with that visual glitch.

Thanks in advance.

Weird. This is the first time I see this issue.

Please copy this log here:
Codec Tweak Tool > Generate Log

I am experiencing the same issue as "Trombe" with visual "noise" around subtitles and around any "text" showing on my MPC-HC, since the upgrade.

I have installed the latest updates: klcp_update_1614_20210422, but problem still persist..

Is there any solution to this issue?

Thank you in advance for your assistance

Codec Tweak Tool | Log file | Generated at 2021-04-28 23:01:46

#####  System Information  #####

OS:           Windows 10 Home (10.00.19041) (x64)
CPU name:     11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
CPU details:  2803 MHz | 8 core(s) | Family 6 Model 140 Stepping 1
Memory:       16160 MB
Screen size:  1920x1080 (32bits) (60Hz) (125%)
GPU:          Intel(R) Iris(R) Xe Graphics
              VendorID: 8086, DeviceID: 9a49, SubSys: 87cb103c
GPU memory:   1024 MB
GPU driver:   igdumdim64.dll (Version 27.20.100.8935) (10-28-2020)
Audio device: Intel Smart Sound Technology for Digital Microphones
              VendorID: 8086, DeviceID: ae20
Audio driver: IntcDMic.sys (Version 10.29.0.4911) (12-10-2020)

#####  K-Lite Codec Pack  #####

KLCP version: 16.1.4 (base 16.1.0)
KLCP type:    standard

Speaker conf: 2.0

MPC renderer: MPC VR
MPC subs:     ISR
MPC audio:    Internal Audio Renderer
MPC decoder:  h264=DXVA2N hevc=DXVA2N vp9=DXVA2N vc1=0 mpeg2=0

#####  Decoder Settings #####

LAV Video:
H264=DXVA2CB HEVC=DXVA2CB VP9=DXVA2CB VC1=0 MPEG2=1 MPEG4=1 WMV3=0

LAV Audio:
MP3=1 AC3=1 DTS=1 DTSHD=1 EAC3=1 TRUEHD=1 AAC=1 Vorbis=1 LPCM=1 WMA=0

#####  DirectShow Filters (32-bit)  #####

(A total of 69 filters, 0 shown, 69 hidden)

#####  DirectShow Filters (64-bit)  #####

(A total of 69 filters, 0 shown, 69 hidden)

#####  ICM Class Manager (32-bit)  #####

(A total of 2 filters, 0 shown, 2 hidden)

#####  ICM Class Manager (64-bit)  #####

(A total of 2 filters, 0 shown, 2 hidden)

#####  Default source filters (32-bit)  #####

(A total of 56 default source filters, 0 shown, 56 hidden)

#####  Default source filters (64-bit)  #####

(A total of 56 default source filters, 0 shown, 56 hidden)

#####  ACM and VFW Codecs (32-bit)  #####

(A total of 14 codecs, 0 shown, 14 hidden)

#####  ACM and VFW Codecs (64-bit)  #####

(A total of 13 codecs, 0 shown, 13 hidden)

First try with latest Intel graphics driver, as this is likely a bug in your current driver:
https://downloadcenter.intel.com/download/30381/Intel-Graphics-Windows-10-DCH-Drivers

If that does not solve it, then press Ctrl+J to show the video renderer debug overlay and make a screenshot. Then I can check if that shows anything unusual.

As a workaround you can try a different video renderer:
MPC-HC options > Playback > Output
Use EVR-CP or madVR

For DirectShow Video - changed from "MPC Video Renderer" to "Enhanced Video Renderer (custom presenter)"

This workaround fix my issue.

Thank you very much for your assistance

I almost forgot about it and was using it with that visual glitch until today that I got the update haha.

jtranla solution of changing the video render worked for me as well. Thank you!!

Can you also test if the newer driver fixes the problem with MPC Video Renderer?

This problem only occurs on Intel Xe Graphics. So it is likely a driver bug.

Admin wrote:Can you also test if the newer driver fixes the problem with MPC Video Renderer?

This problem only occurs on Intel Xe Graphics. So it is likely a driver bug.

I didn't fix it.

Press Ctrl+J to display the debug information of the video renderer.

Please make a screenshot of that for me. That information should help the developers of the renderer to figure out what might be wrong. Thanks.