View Issue Details

IDProjectCategoryView StatusLast Update
0000494madVRbugpublic2018-01-14 11:52
ReporterEde_123 Assigned Tomadshi  
PriorityurgentSeveritycrashReproducibilityalways
Status closedResolutionunable to reproduce 
OSWindowsOS Version10 
Summary0000494: madVR crashes with Intel HD Graphics 520 with driver version 21.20.16.4718
DescriptionUsing madVR with MPC-HC and Intel HD Graphics Driver 21.20.16.4590 on a Notebook with Intel HD Graphics 520 works fine.

After updating to Intel HD Graphics Driver 21.20.16.4718 running any video seems to causes critical graphics issues (severe system-wide graphic errors, system lockups and complete system failure (i.e. automatic reboot or completely unresponsive requiring a hard switch).

Going back to the previous driver version solved the issue again.
TagsNo tags attached.
madVR Version0.91.11
Media Player (with version info)MPC-HC 1.7.13
Splitter (with version info)LAV Splitter 0.70.2.1-git
Decoder (with version info)LAV Video Decoder 0.70.2.1-git
DecodingDXVA2 Native
Deinterlacingnone (progressive)
DXVA2 Scaling Activeyes
Aero / Desktop CompositionOn
Problem occurs with modewindowed mode
GPU ManufacturerIntel
GPU ModelHD Graphics 520
GPU Driver Version21.20.16.4718

Activities

madshi

2017-07-31 21:49

administrator   ~0001754

So why are you reporting this to me and not to Intel? ;-)

Ede_123

2017-07-31 22:05

reporter   ~0001755

Because you might know what's wrong and how/where to report it...

If you think it's an Intel issue I'd be happy to report it there (some pointers where to turn would be welcome), but I'm not sure if they'll even be willing to support me (as I'm basically forced to use Lenovo's OEM driver on my system and the official Intel driver can only be installed via workarounds).

madshi

2017-07-31 22:10

administrator   ~0001756

I've contacts to some Intel guys, but those only interested in HDR related stuff. Also, I don't really know where even "normal" users can report bugs. There isn't really much I can do at all. Since the problem doesn't appear to occur with Nvidia or AMD GPUs, or even other Intel drivers, everything points to the new Intel driver version you've installed.

Of course you could try to work around the issue, e.g. by trying to turn on/off some madVR options like "use D3D11 for presentation", or "automatic fullscreen exclusive mode", or by trying to reduce the number of pre-presented frames. But I don't know if any of that will help.

Ede_123

2017-10-24 01:00

reporter   ~0001875

Ughh, after Microsoft force-updated my driver twice now (one after the falls creators update and once just for the fun of it afterward) I tried to deal with this again and it's still messed up...

Some new observations on hte issue:
- it's independent of exclusive mode (happens with MPC-HC windowed
- it's not happening always
- when it's happening
  * playback mostly fails to start,
  * madVR reports "resetting Direct3D device failed" and/or "creating dxva decoding surface failed"
  * my secondary screen (which is the Notebook display) but not my primary screen (which is an external monitor) gets completely garbled(graphics memory corrupted?) and sometimes one even sees how it becomes black from the top line-by-line; usually most of the display is black but a few distorted lines at the top which show something that is porbably supposed to be the desktop...
  * audio playback is influenced, too, and starts to crack like an old LP.

Life saver in these scenarios: Win+Ctrl+Shift+B (I think this restarts the graphics driver) which lets one resume working with the system...

I tried some things (enable/disable D3D11 for presentation, disable pre-presentation, change number of pre-presented frames, use separate device for presentation/DXVA) but nothing seems to help so far :-(

madshi

2018-01-14 11:52

administrator   ~0002007

I'm really sorry that you have these problems, but since they all seem to be GPU driver problems, I don't have the slightest idea what I could do, so I'll have to close this bug report.

Hint: You can disable forced driver updates somewhere (don't remember where, Google should help).

Issue History

Date Modified Username Field Change
2017-07-31 21:36 Ede_123 New Issue
2017-07-31 21:49 madshi Note Added: 0001754
2017-07-31 22:05 Ede_123 Note Added: 0001755
2017-07-31 22:10 madshi Note Added: 0001756
2017-10-24 01:00 Ede_123 Note Added: 0001875
2018-01-14 11:52 madshi Note Added: 0002007
2018-01-14 11:52 madshi Status new => closed
2018-01-14 11:52 madshi Assigned To => madshi
2018-01-14 11:52 madshi Resolution open => unable to reproduce