<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Even with occlusion queries in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169961#M87839</link>
    <description>&lt;P&gt;Even with occlusion queries eliminated from use, there's still a very broken swap bug in the 6861 and 6890 revisions.&lt;/P&gt;&lt;P&gt;OpenGL gives no errors.&amp;nbsp;SwapBuffers gives no errors.&lt;/P&gt;&lt;P&gt;But the window backbuffer stays stuck on a prev frame's contents forever despite rendering and swapping still happening without error.&lt;/P&gt;&lt;P&gt;The requested information was already provided in the .zip attachment above...&lt;/P&gt;</description>
    <pubDate>Thu, 20 Jun 2019 20:37:10 GMT</pubDate>
    <dc:creator>Madarasz__graham</dc:creator>
    <dc:date>2019-06-20T20:37:10Z</dc:date>
    <item>
      <title>Intel HD 630 Driver Hang</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169956#M87834</link>
      <description>&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;This reproduces with every driver version up to 6444, but does not occur with rev 6025 when rolled back.&lt;/P&gt;&lt;P&gt;It appears to be exclusive to the Win 10 64-bit driver stack.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 03 Dec 2018 20:04:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169956#M87834</guid>
      <dc:creator>Madarasz__graham</dc:creator>
      <dc:date>2018-12-03T20:04:40Z</dc:date>
    </item>
    <item>
      <title>There's system support</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169957#M87835</link>
      <description>&lt;P&gt;There's system support utility dump included in the attached zip.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Dec 2018 20:06:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169957#M87835</guid>
      <dc:creator>Madarasz__graham</dc:creator>
      <dc:date>2018-12-03T20:06:15Z</dc:date>
    </item>
    <item>
      <title>The end result is that all</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169958#M87836</link>
      <description>&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Dec 2018 20:07:36 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169958#M87836</guid>
      <dc:creator>Madarasz__graham</dc:creator>
      <dc:date>2018-12-03T20:07:36Z</dc:date>
    </item>
    <item>
      <title>Can you fill in the template</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169959#M87837</link>
      <description>&lt;P&gt;Can you fill in the template below? We need the info to properly investigate the issue. Thanks&lt;/P&gt;&lt;P&gt;System Setup Information:&lt;BR /&gt;-----------------------------------------&lt;/P&gt;&lt;P&gt;System Used: (Manufacturer/Model)&lt;BR /&gt;CPU SKU: (i3, i5, Pentium, Celeron, etc.)&lt;BR /&gt;GPU SKU: (HD4400, HD5100, etc.)&lt;BR /&gt;Processor Line: (Y-Series, U-Series, etc.)&lt;BR /&gt;System BIOS Version:&lt;BR /&gt;CMOS settings:&lt;BR /&gt;Graphics Driver Version:&lt;BR /&gt;GOP/VBIOS Version:&lt;BR /&gt;Operating System:&lt;BR /&gt;OS Version:&lt;BR /&gt;API:&lt;BR /&gt;Occurs on non-Intel GPUs?:&lt;/P&gt;&lt;P&gt;Steps to Reproduce:&lt;BR /&gt;-------------------------------&lt;BR /&gt;1.&lt;BR /&gt;2.&lt;BR /&gt;3.&lt;BR /&gt;4.&lt;BR /&gt;5.&lt;BR /&gt;6.&lt;BR /&gt;7.&lt;BR /&gt;8.&lt;BR /&gt;9.&lt;BR /&gt;10.&lt;/P&gt;&lt;P&gt;Expected Results:&lt;BR /&gt;-------------------------------&lt;/P&gt;&lt;P&gt;Actual Results:&lt;BR /&gt;-------------------------------&lt;/P&gt;&lt;P&gt;Additional Information:&lt;BR /&gt;-------------------------------&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2019 14:27:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169959#M87837</guid>
      <dc:creator>Michael_C_Intel2</dc:creator>
      <dc:date>2019-04-04T14:27:16Z</dc:date>
    </item>
    <item>
      <title>This turned out to be issues</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169960#M87838</link>
      <description>&lt;P&gt;This turned out to be issues with occlusion queries hanging in specific affected driver versions...&lt;/P&gt;</description>
      <pubDate>Wed, 29 May 2019 16:29:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169960#M87838</guid>
      <dc:creator>Madarasz__graham</dc:creator>
      <dc:date>2019-05-29T16:29:13Z</dc:date>
    </item>
    <item>
      <title>Even with occlusion queries</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169961#M87839</link>
      <description>&lt;P&gt;Even with occlusion queries eliminated from use, there's still a very broken swap bug in the 6861 and 6890 revisions.&lt;/P&gt;&lt;P&gt;OpenGL gives no errors.&amp;nbsp;SwapBuffers gives no errors.&lt;/P&gt;&lt;P&gt;But the window backbuffer stays stuck on a prev frame's contents forever despite rendering and swapping still happening without error.&lt;/P&gt;&lt;P&gt;The requested information was already provided in the .zip attachment above...&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2019 20:37:10 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169961#M87839</guid>
      <dc:creator>Madarasz__graham</dc:creator>
      <dc:date>2019-06-20T20:37:10Z</dc:date>
    </item>
    <item>
      <title>We've narrowed down this hang</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169962#M87840</link>
      <description>&lt;P&gt;We've narrowed down this hang to only occurring when we use glReadPixels for readback while we are also issuing occlusion queries.&lt;/P&gt;&lt;P&gt;If we avoid the readback, the occlusion queries work as expected. If we don't, the GL_QUERY_RESULT_AVAILABLE request hangs forever.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2019 18:42:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169962#M87840</guid>
      <dc:creator>Madarasz__graham</dc:creator>
      <dc:date>2019-07-11T18:42:15Z</dc:date>
    </item>
    <item>
      <title>This happens even if we only</title>
      <link>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169963#M87841</link>
      <description>&lt;P&gt;This happens even if we only read back a single pixel.&lt;/P&gt;&lt;P&gt;It's pretty clearly a threading issue within the driver...&lt;/P&gt;</description>
      <pubDate>Thu, 11 Jul 2019 19:16:46 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Intel-HD-630-Driver-Hang/m-p/1169963#M87841</guid>
      <dc:creator>Madarasz__graham</dc:creator>
      <dc:date>2019-07-11T19:16:46Z</dc:date>
    </item>
  </channel>
</rss>

