MP 1.4 Not starting up. D3D: Could not create device error. Since last Windows update. (1 Viewer)

[markus_g]

MP 1.4 has been working a dream for me until the latest windows updates.
I have a HTPC that automatically boots up each day and starts up Media Portal. When the computer boots up the HDMI TV screen is normally turned off.
Since the last windows updates when I turn the TV on at a latter stage the MP startup screen is there stuck with initializing directx and a box with D3D: Could not create device error. I then run MP configuration to shutdown MP. I then can restart MP normally. Any ideas, or should I choose to manually start MP from now.
Could the patch (Resuming from Standby not working) help or if this only for the TV server problem.
Regards,
Markus

 

[markus_g]

No ideas. That's ok. Not a issue any more. I upgraded to 1.5 Pre release and it is now working correctly.

 

[markus_g]

Problem came back and was happening about 1 in 4 start-ups. I tried the suggestion from another thread to run Mediaportal using task scheduler on start-up and disabling the auto start in MP configuration. This has fixed my problem.

 

[Golf4]

Hi,
Thanks for the information.
I have the same problem.
I've been using for the autostart of MP this tool:
http://www.r2.com.au/page/products/show/startup-delayer/
I use to wake up the server (as Win-Task):
http://www.depicus.com/wake-on-lan/wake-on-lan-cmd.aspx
See also here:
https://forum.team-mediaportal.com/...rmanager-deutscher-thread.93746/#post-1030040

Greetings from cold Germany

 

[Sebastiii]

I have supply a bin to test against 1.6.0 Pre-Release
https://forum.team-mediaportal.com/...eated-after-resume.119910/page-6#post-1049791

I can't trigger the issue on my side but if someone with the issue can try the files and let me know if we are in the good direction
Thanks

 

[markus_g]

I have supply a bin to test against 1.6.0 Pre-Release
https://forum.team-mediaportal.com/...eated-after-resume.119910/page-6#post-1049791

I can't trigger the issue on my side but if someone with the issue can try the files and let me know if we are in the good direction
Thanks

Hi,
Thanks for the new bin. Unfortunately I have tested the bin and it hasn't fixed the issue.
Now back to running MP using windows task scheduler.

Regards,

Markus.

 

[Sebastiii]

Thank you for the test
I can't reproduce it, MP always start correctly here.

Can you retry without my patch and post log to compare ?
In my patch i have fixed detection of null value and then we can see now :

[2013-12-29 23:31:27,678] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)
[2013-12-29 23:31:27,928] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)
[2013-12-29 23:31:28,178] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)
[2013-12-29 23:31:28,428] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)
[2013-12-29 23:31:28,678] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)
[2013-12-29 23:31:28,928] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)
[2013-12-29 23:31:29,178] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)
[2013-12-29 23:31:29,428] [Log    ] [MPMain  ] [WARN ] - Main: Failed to get capabilities for adapter #0: Intel(R) HD Graphics 3000 (retry in 250ms)

I don't think it was the case before but even with that 20 retry (it's an hardcoded value), it failed .

So it seems :
First check : 23:31:27,678 and MP will be ready at : 23:32:38,986 so in fact 1 min 11 seconds but the retry is only for 250 ms for 20.

Maybe we can higher this number, because it seems that my previous check (when init() method involved) is not the culprit

 

[markus_g]

Here are the logs without your patch.

Just for your info with and without the patch, the message on the MP start up screen is initializing directx. When I click on the box the direct3d error message comes to the foreground.

Off to bed now.

Regards,
Markus[DOUBLEPOST=1388327416][/DOUBLEPOST]Here are the logs when starting using windows task scheduler.
Regards,
Markus

 

[Sebastiii]

New bin for testing
The change add more time to test GetCapabilities();

 

[FreakyJ]

I think there is nothing that helps except the task shedular:
See also here:
https://forum.team-mediaportal.com/...ease-the-build-to-release.118963/#post-993718
and here:
forum.team-mediaportal.com/threads/freeze-initializing-directx.119031/

Somewhere I also posted logs where I increased the retrys etc. maybe that helps you
But I'm lucky and the error just disappeared somehow without any interaction of me^^