Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1197279" data-attributes="member: 82144">Hi RobThanks for the updated log files. I've had a look, and I confess I'm currently a bit puzzled on two fronts:<ol>
<li data-xf-list-type="ol">What the cause could be.</li>
<li data-xf-list-type="ol">How this problem could have arisen since MP 1.14.</li>
</ol>Are you certain that the problem appeared immediately after updating to MP 1.15?If not, aside from updating to MP 1.15, have you made any other significant changes - installed new software or hardware, updated to Windows 10, updated drivers, connected a new TV or AV receiver etc. - that might be responsible for the problem?Would it be possible to try [temporarily] going back to MP 1.14 to check if the problem goes away?If this would be possible, this would be my next recommendation... and I'd be very keen to see log files showing MP 1.14 resuming without problem.Best regards,mm</blockquote>

[QUOTE="mm1352000, post: 1197279, member: 82144"] Hi Rob Thanks for the updated log files. I've had a look, and I confess I'm currently a bit puzzled on two fronts: [LIST=1] [*]What the cause could be. [*]How this problem could have arisen since MP 1.14. [/LIST] Are you certain that the problem appeared immediately after updating to MP 1.15? If not, aside from updating to MP 1.15, have you made any other significant changes - installed new software or hardware, updated to Windows 10, updated drivers, connected a new TV or AV receiver etc. - that might be responsible for the problem? Would it be possible to try [temporarily] going back to MP 1.14 to check if the problem goes away? If this would be possible, this would be my next recommendation... and I'd be very keen to see log files showing MP 1.14 resuming without problem. Best regards, mm [/QUOTE]

Verification