madshi bug tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000528madVRbugpublic2017-12-30 12:152018-01-21 14:38
Assigned Tomadshi 
StatusclosedResolutionno change required 
PlatformWindows 64-bitOSWindows 10 ProOS Version1709
Summary0000528: madVR 0.92.10 crashes every 6 ... 8 times when a specific file is played
DescriptionmadVR 0.92.10 crashes sometimes when a specific file is played.

I already disabled LAV Filters, and the issue still appears.
I couldn't reproduce it when using EVR custom presenter in MPC-BE x64, so I tend to think it is a madVR issue. I have only a message that MPC-BE x64 stopped working and I close this, then in Eventviewer I only see:
Name der fehlerhaften Anwendung: mpc-be64.exe, Version:, Zeitstempel: 0x5a4465fb
Name des fehlerhaften Moduls: unknown, Version:, Zeitstempel: 0x00000000
Ausnahmecode: 0xc00000fd
Fehleroffset: 0x00000265caa20017
ID des fehlerhaften Prozesses: 0x216c
Startzeit der fehlerhaften Anwendung: 0x01d3815d614b8118
Pfad der fehlerhaften Anwendung: C:\Program Files\MPC-BE x64\mpc-be64.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: d8b0364c-ae50-4236-b41a-998f5267d6ea
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

MiniDump is also not created by MPC-BE
Steps To ReproducePlay a file like this sample: [^]
Additional InformationI have hundred if not thousands of videos but it looks that only this video is affected. Only a small music video ;)
I already downloaded for test purposes the latest encoded version of youtube
(YouTube creates newer and smaller files for videos after some time) and I muxed it with the newer MKVToolNix 19.0.0 but I get the same issue.
My old file with the same issue was created with MKVToolNix v12.0.0 or so an was 2 MB bigger.
I think it has to to with data, that MediaInfo reports on this file:
colour_range : Limited
colour_primaries : BT.601 NTSC
transfer_characteristics : BT.709
matrix_coefficients : BT.601

I don't have any other file with this specific info, if this info is available in the file, I only get three times BT.709.
TagsNo tags attached.
madVR Version0.92.10
Media Player (with version info)MPC-BE 1.5.2 beta 3238
Splitter (with version info)MPC Matroska Source
Decoder (with version info)LAV Video Decoder
Deinterlacingnone (progressive)
DXVA2 Scaling Activeno
Aero / Desktop CompositionOff
Problem occurs with modefullscreen exclusive mode
GPU Manufacturer<select>
GPU ModelRX480 8 GB
GPU Driver Version17.12.1
Attached Files

- Relationships

-  Notes
madshi (administrator)
2017-12-30 12:42

Can you please double check with another video player, just to be safe? Normally, when madVR crashes, there's a madVR crash box. Since this doesn't seem to be the case here, it could just as well be a media player bug.
Klaus1189 (reporter)
2017-12-30 12:47

Which one should I use?
Klaus1189 (reporter)
2017-12-30 12:53

I try MPC-HC, although the two players are very similar
madshi (administrator)
2017-12-30 12:54

MPC-HC would be fine. Maybe you can also try 32bit media player instead of 64bit (or vice versa).
Klaus1189 (reporter)
2017-12-30 12:55

Klaus1189 (reporter)
2017-12-30 15:33

It only happened one time anymore in 2,5 hours of playing various files.
I can't reproduce it. I don't know what to think about it now ...
madshi (administrator)
2017-12-30 17:29

Well, sometimes things are weird. Without it being reliably reproducable, and without a madVR crash report, there's really not much I can do.
Klaus1189 (reporter)
2018-01-13 12:53

I tested MPC-BE x86 build and two weeks of testing, no crash.

x64 build sometimes and I found a new file which causes the same issue [^]

But I think it doesn't help to identy the problem, isn't it?
madshi (administrator)
2018-01-13 13:19

It would help only if the crash were either reproducable, or if you got a madVR crash report. As long as the crash only happens rarely and there's no indication that this is actually a bug in madVR, there's not much I can do.

From what I can see right now, it doesn't seem to be a bug in madVR, but somewhere else.
Klaus1189 (reporter)
2018-01-15 19:35

just got a crash with madvr 32 bit

Name der fehlerhaften Anwendung: mpc-be.exe, Version:, Zeitstempel: 0x5a5c1cae
Name des fehlerhaften Moduls: MADHCNET32.DLL, Version:, Zeitstempel: 0x59b94d81
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000ac1e
ID des fehlerhaften Prozesses: 0x7a8
Startzeit der fehlerhaften Anwendung: 0x01d38e2f5362f7ba
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\MPC-BE\mpc-be.exe
Pfad des fehlerhaften Moduls: C:\Users\Klaus Luppert\Documents\Programme\madVR\MADHCNET32.DLL
Berichtskennung: f2b7861d-c370-4c04-ba72-5502c47464a5
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
madshi (administrator)
2018-01-15 19:44

Still no madVR crash box, though? Looks something like this: [^]
Klaus1189 (reporter)
2018-01-15 20:14

I can olny close the window and look up in Eventviewer/Ereignisanzeige what happened. But 10000+ files are fine, only two are affected, and not always. This is what makes me headache ...
madshi (administrator)
2018-01-15 21:39

And how often do those 2 affected files crash now? BTW, I just released v0.92.11. But I don't expect it to help with this problem.
Klaus1189 (reporter)
2018-01-21 12:23

I always use your latest version, the crash I reported in post 0002127 on 2018-01-15 19:35, I was already using 0.92.11.

I have very good news! I know what setting I have to disable, so no crash appeared the hole week I tested on both x86 and x64.

I disabled the following setting in madVR:
rendering → general settings → delay playback start until render queue is full

It is diabled by default, but it was needed to get fewer dropped/skipped frames and presentation glitches in the past with my settings and configuration.
Since I switched to the built in refresh rate changer in madVR, which works very nice, I don't need the setting anymore.

I am very happy I found that :D
madshi (administrator)
2018-01-21 13:56

Strange, I don't think anybody reported this option to cause crashes yet.

So I guess I can close this bug report?
Klaus1189 (reporter)
2018-01-21 14:36


- Issue History
Date Modified Username Field Change
2017-12-30 12:15 Klaus1189 New Issue
2017-12-30 12:42 madshi Note Added: 0001968
2017-12-30 12:47 Klaus1189 Note Added: 0001969
2017-12-30 12:53 Klaus1189 Note Added: 0001970
2017-12-30 12:54 madshi Note Added: 0001971
2017-12-30 12:55 Klaus1189 Note Added: 0001972
2017-12-30 15:33 Klaus1189 Note Added: 0001973
2017-12-30 17:29 madshi Note Added: 0001974
2018-01-13 12:53 Klaus1189 Note Added: 0001987
2018-01-13 13:19 madshi Note Added: 0001989
2018-01-14 11:30 madshi Assigned To => madshi
2018-01-14 11:30 madshi Status new => feedback
2018-01-15 19:35 Klaus1189 Note Added: 0002127
2018-01-15 19:35 Klaus1189 Status feedback => assigned
2018-01-15 19:44 madshi Note Added: 0002130
2018-01-15 19:44 madshi Status assigned => feedback
2018-01-15 20:14 Klaus1189 Note Added: 0002131
2018-01-15 20:14 Klaus1189 Status feedback => assigned
2018-01-15 21:39 madshi Note Added: 0002132
2018-01-15 21:40 madshi Status assigned => feedback
2018-01-21 12:23 Klaus1189 Note Added: 0002160
2018-01-21 12:23 Klaus1189 Status feedback => assigned
2018-01-21 13:56 madshi Note Added: 0002163
2018-01-21 13:56 madshi Status assigned => feedback
2018-01-21 14:36 Klaus1189 Note Added: 0002164
2018-01-21 14:36 Klaus1189 Status feedback => assigned
2018-01-21 14:38 madshi Status assigned => closed
2018-01-21 14:38 madshi Resolution open => no change required

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker