Answers (N/A if not applicable)
Provide a detailed description of the issue AND 'does it fail every single time, or only sometimes?' If you can offer a % rate please do.
When "Conservative Morphological Anti-Alising" is set to "Override Application Settings", display driver would crash when you run one of the Passmark’s PerformanceTest 8.0 3D DirectX 9 tests (either one of the two)
Brand and Model of the system.
Sony VAIO Tap 11
Hybrid or switchable graphics system? ie Does it have AMD or NV graphics too?
Intel HD Graphics 4200
Make and model of any Displays that are used to see the issue (see note2 below).
LFP = Local Flat Panel (Laptop panel)
EFP = External Flat Panel (Monitor you plug in)
Built in notebook monitor - LFP
How much memory [RAM] in the system (see note2 below).
Provide any other hardware needed to replicate the issue.
ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc
Hardware Stepping (see note1 below).
Operating System version (see note2 below).
Windows 10 HOME
VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.
Graphics Output Protocol (GOP) Version: 5.0.1036
Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).
SW/Apps version used to replicate the issue.
Passmark’s PerformanceTest 8.0
Single display, clone, or extended (see note2 below).
Display resolution & refresh rate setting of each display (see note2 below).
1920 x 1080
AC or DC mode, i.e. is power cable plugged in or not?
AC (or DC, doesn't matter)
How to repro
Please provide steps to replicate the issue. These steps are very crucial to finding the root cause and fix.
A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.
I have received same error message "Display driver Intel® HD Graphics for Windows 8(R) stopped responding and has successfully recovered." I followed step by step instructions and I got same issue. I am forwarding this information to our engineering team.
This issue is resolved with our latest internal driver build. Checking our release schedule, I don't believe it will make our upcoming Q2'16 driver to DownloadCenter, but it will be in the Q3'16 release [July-Sept] or a prior one if an interim release is completed. Thanks for helping us to improve Intel products.
Wow... phenomenal - one entire year after this was initially reported (this message was actually re-posted by Bryce@intel after about 6 months of back-and-forth replies in another thread) and acknowledged but the issue STILL exists.
I have lost my patience. But what else can I do when Intel decides to totally ignore rants from customers like me?