Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1175323" data-attributes="member: 82144">Hmmm, same error in the log files. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" />No, not really.Did you actually get to the point where your system partition c: ran out of space? I mean, I can see your recording partition has run out of space so none of your new recordings will be playable. However if the system partition also ran out of space that may have caused file corruption which in turn could be causing what you're seeing. In that case a full and clean LAV, MP or even Windows reinstallation may be required to resolve. I say reinstallation because it may be prohibitively difficult to identify and fix/replace all the files that have corrupted.On the other hand, I note the entries in the Windows system event log:&quot;12/02/2016 00:32:48&quot;;&quot;amdkmdag&quot;;&quot;DVD_OV&quot;;&quot;Information&quot;;&quot;UVD Information&quot;;&quot;1073804288&quot;...which people have previously suggested may point to GPU driver problems. For example:<a href="https://forum.team-mediaportal.com/threads/mp-crash-while-switching-to-hd-channel.53343/" target="_blank">https://forum.team-mediaportal.com/threads/mp-crash-while-switching-to-hd-channel.53343/</a>However, that's quite an old thread, so I'm not exactly confident in the advice. Especially considering that MPC-HC can play the file.Is it possible that the problem started when you updated the LAV codecs to v0.66?...or have you changed the LAV configuration recently?...or have you updated drivers (particularly the GPU driver) recently?Ultimately the underlying assumption I make is that problems don't just start for no reason. Something must have changed for the problem to start. Whether it was an unexpected power loss, HDD running out of space, driver update, configuration change, LAV update, Windows update... I don't know. You know better than us when the problem started, what your PC might have been doing at/around that date/time etc. etc. etc. Therefore I would hope you're in a better position than us to recognise the cause of the problem. I can only try and point out things which I think are somewhat suspicious...</blockquote>

[QUOTE="mm1352000, post: 1175323, member: 82144"] Hmmm, same error in the log files. :( No, not really. Did you actually get to the point where your system partition c: ran out of space? I mean, I can see your recording partition has run out of space so none of your new recordings will be playable. However if the [I]system [/I]partition also ran out of space that may have caused file corruption which in turn could be causing what you're seeing. In that case a full and clean LAV, MP or even Windows reinstallation may be required to resolve. I say reinstallation because it may be prohibitively difficult to identify and fix/replace all the files that have corrupted. On the other hand, I note the entries in the Windows system event log: "12/02/2016 00:32:48";"amdkmdag";"DVD_OV";"Information";"UVD Information";"1073804288" ...which people have previously suggested may point to GPU driver problems. For example: [URL]https://forum.team-mediaportal.com/threads/mp-crash-while-switching-to-hd-channel.53343/[/URL] However, that's quite an old thread, so I'm not exactly confident in the advice. Especially considering that MPC-HC can play the file. Is it possible that the problem started when you updated the LAV codecs to v0.66? ...or have you changed the LAV configuration recently? ...or have you updated drivers (particularly the GPU driver) recently? Ultimately the underlying assumption I make is that problems don't just start for no reason. [I]Something[/I] must have changed for the problem to start. Whether it was an unexpected power loss, HDD running out of space, driver update, configuration change, LAV update, Windows update... I don't know. You know better than us when the problem started, what your PC might have been doing at/around that date/time etc. etc. etc. Therefore I would hope you're in a better position than us to recognise the cause of the problem. I can only try and point out things which I think are somewhat suspicious... [/QUOTE]

Verification