[MP1-4578] Crashes after standby. (4 Viewers)

[HTPCSourcer]

since I'm not anymore using worldweather, I don't have crashes after standby

Nothing to do with WorldWeather as discussed and explained in depth in this thread.

 

[Sebastiii]

Hi, i have try the whole day to figure out how to handle properly 'Main: OnDeviceLost()' but with no luck
In log i can clearly see that log line, i didn't have it on my side so maybe it's why i can't run into the issue

I can reproduce the lost device, if i set MP to start to my second GPU card and i disable it from windows (so i simulate a device lost) but i can't recover it correctly and most of the time it crash.

 

[HTPCSourcer]

Hi Seb,

Don't bother too much. It's not the software task to offset bad driver behavior. It is confirmed that my system resumes in a screen resolution other than what it should be in. The only thing that surprises me is that there are not more reports of this kind.obviously there aren't too many Intel systems with a similar hardware that run MediaPortal. Maybe it's the combination of this CPUCPU and the Asrock H87 mainboard, in which case there is anyway no solution.

The best behavior seems to be with V5 for me, V6 throws reproducible crashes of the d3derr type. I do not expect this to go into a regular build, however, the standard version crashes 100% of the time. How can we proceed from here with respect to potential inclusion into a branch?[DOUBLEPOST=1414261413][/DOUBLEPOST]One possible workaround would be to resume MP in window mode and then switch back to full screen. Not very elegant and a lot of screen flickering...

 

[andreas2]

Hallo,

in V6 generic-keyboard-remote-input-plugin not works

 

[killer8]

since I'm not anymore using worldweather, I don't have crashes after standby

Nothing to do with WorldWeather as discussed and explained in depth in this thread.

That's not correct. The initial crashes I created this forum thread for was caused by worldweather, which can be fixed by either disabling worldweather completely like @bribbon did or update to worldweather 1.6.2 test version given by @Micropolis earlier in this thread. After this it got mentioned there are other problems with mp after standby and that's what the thread is about now. But initially it was about the crashes regarding the worldweather plugin after standby.

Anyway, I didn't have any problems with V6 freeze fix today and yesterday. Mediaportal resumed fine multiple times. I also didn't see any of the mentioned D3D errors on my setup. It resumes nicely straight to mediaportal like it has to be No desktop is shown prior mediaportal and after the resume event.

 

[Micropolis]

Hello killer8,

...The initial crashes I created this forum thread for was caused by worldweather ...

Please prove your statement under reproduction with the original test conditions, otherwise I would ask you to keep your distance from this bold statement. It is really sad to hear that you do not want to accept the opinions of others. You should always be aware that our community use MediaPortal under various OS and driver conditions and hardware requirements.
The only change of test version posted here was the removal of the notification dialog, nothing more or less. Expect no more support, as long as I do not have your proof or it should be fully reproducible by other users. The previous version 1.6.1 can be found in the plugin repository.

Micropolis

 

[killer8]

Hello killer8,

...The initial crashes I created this forum thread for was caused by worldweather ...

Please prove your statement under reproduction with the original test conditions, otherwise I would ask you to keep your distance from this bold statement. It is really sad to hear that you do not want to accept the opinions of others. You should always be aware that our community use MediaPortal under various OS and driver conditions and hardware requirements.
The only change of test version posted here was the removal of the notification dialog, nothing more or less. Expect no more support, as long as I do not have the proof and it's completely reproduced by me.

Micropolis

Hi, I think I've proved this before in this thread:

So for the record:
mp 1.9 final + worldweather plugin 1.6.1 = crash
mp 1.9 + unfreeze fix = crash
mp 1.9 + worldweather plugin 1.6.2(without unfreeze fix) = working

Well, when i read your above post, i'm not so sure if the above is correct.
You state you downgraded your BIOS because that was giving you HDMI/Input Device issues, so maybe that was also the cause for the freezes after resume. HDMI (handshake) issues can definitely lead to that.

I'm really curious what happens when you install WorldWeather 1.6.1 on the 'fresh' system. I suspect it to work as it does now

It is correct, since the above conclusion isn't based on the "old" system(old bios) but tests are all made after the reinstall with the new bios(after downgrade).

1 downgraded the bios
2 reinstalled windows with mp 1.9 final and worldweather 1.6.1 = crash
3 installed freeze fix v5 = crash
4 removed freeze fix(restored original mediaportal.exe) and upgraded worldweather to 1.6.2 = working fine for last 24 hours.

Testing was done in above order, so I think this can exclude all other causes right?

Another thing I still don't get, how can this bios downgrade has fixed the hdmi audio problem with my external(not onboard) nvidia gtx 970 card(I had the same audio problem with my gt 520 which I replaced with the gtx 970 and has worked before I upgraded the bios months/a year ago)

I'm aware various users use different OS/Drivers/Hardware. I just mean for me the fix was to install worldweather 1.6.2 so maybe this will also make a difference for bribbon.

Since I installed 1.6.2 instead of 1.6.1 I didn't have the specific crash anymore(this is for more than a week now I think). For the last 2 days I'm also using V6 fix provided by seb and this also works fine, it just makes resume looking better(no desktop shows up etc).

I just meant by my comment it does make a difference for me. Even when just the dialog has been removed it is the difference which seems to be the fix for me. Maybe it doesn't make a difference for someone else but based on my testing mentioned in the above quite it does for me.

@Micropolis Is the 1.6.2 you released officially the same as you posted earlier in this thread?

 

[Sebastiii]

Hi

Something to test lol
Not sure about the result, like i can't reproduce it but maybe i can see something from log

 

[HTPCSourcer]

Hi, I think I've proved this before in this thread:

Not really. At some point you did a BIOS change that affected your HDMI device. HDMI behavior is vital to what your graphic driver is doing - and it's the driver that triggered your DirectX problems. Therefore just this BIOS change is making any comparison obsolete.

Anyway, the discussion is not aiming at proving you wrong or right, but to prevent others from believing that possible resume crashes were due to the plugin. I am glad that it's now working for you

 

[HTPCSourcer]

@Sebastiii ,

I ran your V7 - MePo crashes at resume, however, with thus far unseen error messages. I will return to V5, which is functioning for me.