- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello!
After upgrading to win 10 1709 version, AmiDuos android emulator shows a black screen and does nothing. Same result after upgrading to latest Intel Graphics driver.
Some users report that driver 10/2016 version runs fine on win 10 1709 version. Looks like it's a graphics driver problem.
https://amiduos.com/support/topic/black-screen-after-upgrade-to-latest-win10-1709-version https://amiduos.com/support/topic/black-screen-after-upgrade-to-latest-win10-1709-version
Thank you.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi uraken: Thank you very much for contacting the Intel® Graphics communities. We are sorry to hear the Emulator is now not working properly.
Based on the link you gave us, it seems to be that in order to try to fix this problem they recommend to install an older driver version, so that will be a good option to do. Also we recommend to install the drivers provided by the manufacturer of the computer.
What is the model of the processor?
What is the model of the board?
If this is a laptop, what is the model of the laptop?
Since the platform works with Intel® HD Graphics 520, we can also try to install driver 4849:
https://downloadcenter.intel.com/download/27266/Graphics-Intel-Graphics-Driver-for-Windows-15-60-?product=88355 https://downloadcenter.intel.com/download/27266/Graphics-Intel-Graphics-Driver-for-Windows-15-60-?product=88355
Any further questions, please let me know.
Regards,
Alberto R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello.
The latest driver also shows black screen. It happens with all driver versions following the one installed with W10 Fall Creators Update.
The " laptop": https://www.amazon.com/Kingdel-SKYLAKE-Desktop-Computer-4096x2304/dp/B01NAW90U8/ref=sr_1_6?s=electronics&ie=UTF8&qid=1512491513&sr=1-6&keywords=kingdel&refinements=p_n_feature_four_browse-bin:2289792011 Amazon.com: Kingdel Intel i7 6th Gen. SKYLAKE CPU Mini Desktop Computer, 4K HTPC with 16GB RAM, 256GB SSD, 4096x2304, HD… https://www.amazon.com/Kingdel-SKYLAKE-Desktop-Computer-4096x2304/dp/B01NAW90U8/ref=sr_1_6?s=electronics&ie=UTF8&qid=1512491513&sr=1-6&keywords=kingdel&refinements=p_n_feature_four_browse-bin:2289792011 https://www.amazon.com/Kingdel-SKYLAKE-Desktop-Computer-4096x2304/dp/B01NAW90U8/ref=sr_1_6?s=electronics&ie=UTF8&qid=1512491513&sr=1-6&keywords=kingdel&refinements=p_n_feature_four_browse-bin:2289792011
I think it's a laptop in a mini desktop case.
CPU: Intel i7 6600U @ 2.60GHz
Board: INTEL Corporation SKYBAY (U3E1)
I'll try an older driver, but I think that Windows will update it.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello again.
I can confirm that driver version 15.45.19.4678, date 05/30/2017, runs fine. All newer versions have the black screen issue.
Best regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I'm seeing this issue on a new Surface Pro i7 with the 640 Iris HD graphics. I don't have the ability to
Rollback the drivers from within windows 10 pro. Are there drivers I could download from here that support the graphics in my Surface Pro?
Thanks for any guidance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
After installing the working version 4678, Windows has updated automatically (as expected) to version 4749, 07/24/2017, and it doesn't work.
I will install the latest version 4849 and wait for a solution.
Best regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
uraken: Thank you very much for letting us know those updates. Sure, no problem, test driver 4849 and when you get the chance please let us know the results.
Any questions, please let me know.
Regards,
Alberto R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
uraken: Thank you for providing those results. We will do further research on this matter, as soon as I get any updates I will post all the details on this thread.
Any questions, please let me know.
Regards,
Alberto R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
uraken: I just received an update on this matter, and actually there is a new driver available in our web site, it is driver version 4877, please install it to try to fix this problem:
https://downloadcenter.intel.com/download/27355/Graphics-Intel-Graphics-Driver-for-Windows-15-60-?product=88355 https://downloadcenter.intel.com/download/27355/Graphics-Intel-Graphics-Driver-for-Windows-15-60-?product=88355
Any questions, please let me know.
Regards,
Alberto R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Driver version 4877 doesn't work. Same black screen issue.
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi uraken: Thank you very much for letting us know those results. We will continue with our research on this matter in order to try to find a possible solution. As soon as I get any updates, I will post all the details on this thread.
Any questions, please let me know.
Regards,
Alberto R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also tried version 15.60.01.4877 on my Surface Pro I5 with Intel HD Graphics 620. The screen is still black.
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
HeinrichB: Please submit your inquiry on a new thread, the reason for this is that every scenario is different even if the same product is being used, so for us to better assist you and in order to try to fix the problem, please submit a new thread:
/community/tech https://communities.intel.com/community/tech
Let me apologize for any inconvenience.
Regards,
Alberto R
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello uraken,
I would like to confirm that I have been able to replicate this issue in our test lab. Internal bug ID 1406738941 has been filed.
As previously observed, with driver https://downloadcenter.intel.com/download/26836 15.45.4678 it appears to be working as expected, thus I suggest continuing with that driver until this gets sorted out.
I'll update this thread once I have news or updates.
I appreciate your patience, and also I'm thankful for your feedback.
Best Regards,
Ronald M.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have this problem too
I hope you'll update this thread once you have news or updates and you will not forget it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello everyone,
I got an update from our debugging team regarding this issue.
Our debugging showed a heap corruption because of double free pointing to the application's exe.
The reason why older drivers do not show this issue is complex. In a nutshell, this application uses OpenGL* and our most recent and latest drivers (e.g.https://downloadcenter.intel.com/download/27847 24.20.100.6136) introduced a new rule coming straight from the GLSL 4.4 official specification (https://www.khronos.org/registry/OpenGL/specs/gl/GLSLangSpec.4.40.pdf https://www.khronos.org/registry/OpenGL/specs/gl/GLSLangSpec.4.40.pdf) and the application appears to be handling this rule differently.
We'll be trying to reach the AMIDUOS dev team in order to pass along our debugging results, but for now this concludes our investigation on this issue.
Best Regards,
Ronald M.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the support!
If you want you can contact Amiduos Team here:
https://ami.com/en/contact-us/ American Megatrends Inc. - Contact Us
Thanks again and best regards
![](/skins/images/C4F7392A5C68ACA60290C9576F107044/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page