- Thread starter
- Moderator
- #1,031
It can some of something weird that madVR send to API GPU level maybe but it is strange and maybe here something can persist at OS level.
if madVR crash on startup (the first video playing) it is weird, on a second one, it it more possible because we need to destroy the instance first (so here something can be wrong).
About the deadlock, madshi need to lock some stuff but in between we lock also on our filter and then thread A wait the thread B to finish but thread B wait A to finish so it will never unfreeze lol.
Maybe it's can be a faulty GPU drivers, for ex on dev i have an HD4000 and AMD card 5770, with the ATI, my PC freeze and the only way to get it back it's to reset, so i don't use madVR with this card.
And all my test is done with HD4000.
On HTPC i have and Nvidia GTX750TI but i can't trigger the deadlock too, so no clue