Intel HD 630 Driver Hang

[Madarasz__graham]

We've seen hundreds of instances of the attached driver hang. On Intel HD 530/630 as far as we know, we consistently end up with one thread doing a DwmFlush deadlocked with the driver thread itself (or so the stacks seem to imply).

This reproduces with every driver version up to 6444, but does not occur with rev 6025 when rolled back.

It appears to be exclusive to the Win 10 64-bit driver stack.

[Madarasz__graham]

There's system support utility dump included in the attached zip.

[Madarasz__graham]

The end result is that all swaps cease after a certain point and the app continues running as if all is well, except there's nothing ever hitting the screen again.

[Michael_C_Intel2]

Can you fill in the template below? We need the info to properly investigate the issue. Thanks

System Setup Information:
-----------------------------------------

System Used: (Manufacturer/Model)
CPU SKU: (i3, i5, Pentium, Celeron, etc.)
GPU SKU: (HD4400, HD5100, etc.)
Processor Line: (Y-Series, U-Series, etc.)
System BIOS Version:
CMOS settings:
Graphics Driver Version:
GOP/VBIOS Version:
Operating System:
OS Version:
API:
Occurs on non-Intel GPUs?:

Steps to Reproduce:
-------------------------------
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Expected Results:
-------------------------------

Actual Results:
-------------------------------

Additional Information:
-------------------------------

[Madarasz__graham]

This turned out to be issues with occlusion queries hanging in specific affected driver versions...

[Madarasz__graham]

Even with occlusion queries eliminated from use, there's still a very broken swap bug in the 6861 and 6890 revisions.

OpenGL gives no errors. SwapBuffers gives no errors.

But the window backbuffer stays stuck on a prev frame's contents forever despite rendering and swapping still happening without error.

The requested information was already provided in the .zip attachment above...

[Madarasz__graham]

We've narrowed down this hang to only occurring when we use glReadPixels for readback while we are also issuing occlusion queries.

If we avoid the readback, the occlusion queries work as expected. If we don't, the GL_QUERY_RESULT_AVAILABLE request hangs forever.

[Madarasz__graham]

This happens even if we only read back a single pixel.

It's pretty clearly a threading issue within the driver...