<?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 Re: Re:Access Violation on glReadPixels() with Intel UHD Graphics in Graphics</title>
    <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407536#M109151</link>
    <description>&lt;P&gt;Hello Steven,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Yes, it's a custom application created by me, the only purpose is to reproduce the issue.&lt;/LI&gt;
&lt;LI&gt;I attached a ready-to-use VisualStudio sample in my first post, just open it and run the application to reproduce the exception.&lt;/LI&gt;
&lt;LI&gt;I don't have 11th or 12th generation graphics to test it, sorry.&lt;/LI&gt;
&lt;LI&gt;The expected behavior is just not to crash.&lt;/LI&gt;
&lt;LI class="sub_section_element_selectors"&gt;I don't know, most of our client uses a&amp;nbsp;&lt;SPAN&gt;different type of graphics adapters that don't have the issue.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Simone&lt;/P&gt;</description>
    <pubDate>Thu, 11 Aug 2022 07:19:52 GMT</pubDate>
    <dc:creator>simonem</dc:creator>
    <dc:date>2022-08-11T07:19:52Z</dc:date>
    <item>
      <title>Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1405972#M109038</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With the attached simple applications, I get an Access Violation exception on the&amp;nbsp;glReadPixels. Here is the relevant code:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="cpp"&gt;glfwWindowHint(GLFW_SAMPLES, 4);

short* pxData = new short[SCR_WIDTH * SCR_HEIGHT];

//glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);

glReadPixels(0, 0, SCR_WIDTH, SCR_HEIGHT, GL_DEPTH_COMPONENT, GL_SHORT, pxData);&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I don't call glfwWindowHint the exception doesn't occur.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If I call a glClear before the glReadPixels the exception doesn't occur.&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;&lt;SPAN class="sub_section_element_selectors"&gt;Controller and driver:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;&lt;SPAN class="sub_section_element_selectors"&gt;Intel UHD Graphics&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;&lt;SPAN class="sub_section_element_selectors"&gt;Driver Version: 31.0.101.2111&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The code executes without violation exception&amp;nbsp;when using the NVIDIA GeForce GTX 1650 Ti on the same machine, or on machines with different graphics adapters.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Aug 2022 12:36:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1405972#M109038</guid>
      <dc:creator>simonem</dc:creator>
      <dc:date>2022-08-04T12:36:53Z</dc:date>
    </item>
    <item>
      <title>Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1406431#M109075</link>
      <description>&lt;P&gt;Hello simonem,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you for posting on the Intel® communities.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;In order to better assist you, please provide the following information:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;When did the issue start? Was there any change before the issue started?&lt;/LI&gt;&lt;LI&gt;Download the Intel® SSU &lt;A href="https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-" target="_blank"&gt;https://downloadcenter.intel.com/download/25293/Intel-System-Support-Utility-for-Windows-&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Open the application and select "Everything", click on "Scan" to see the system and device information. By default, Intel® SSU will take you to the "Summary View". Click on the menu where it says "Summary" to change to "Detailed View". To save your scan, click on "Next", then "Save".&amp;nbsp;Please attach the file to your reply.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Steven G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 05 Aug 2022 21:46:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1406431#M109075</guid>
      <dc:creator>Steven_Intel</dc:creator>
      <dc:date>2022-08-05T21:46:04Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1406697#M109091</link>
      <description>&lt;P&gt;Hello Steven,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I don't know when the issue started. I received reports of sporadic exception from my clients about 1 year ago but this is the first time I managed to systematically reproduce it in a small sample.&lt;/P&gt;
&lt;P&gt;Attached is the System Information.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Simone&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2022 07:49:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1406697#M109091</guid>
      <dc:creator>simonem</dc:creator>
      <dc:date>2022-08-08T07:49:31Z</dc:date>
    </item>
    <item>
      <title>Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407132#M109124</link>
      <description>&lt;P&gt;Thank you for your response.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are going to work on this issue based on the given information. As soon as I have an update, I will let you know.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Steven G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Aug 2022 15:59:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407132#M109124</guid>
      <dc:creator>Steven_Intel</dc:creator>
      <dc:date>2022-08-09T15:59:47Z</dc:date>
    </item>
    <item>
      <title>Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407426#M109143</link>
      <description>&lt;P&gt;Hello simonem,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;In order to continue, please provide the following information:&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is this a custom application created by you? What is the purpose of this application?&lt;/LI&gt;&lt;LI&gt;Could you please provide a step by step to reproduce the issue?&lt;/LI&gt;&lt;LI&gt;Is this happening only with 10th generation graphics? By any chance have you tested with newer graphics such as 11th and 12th generation?&lt;/LI&gt;&lt;LI&gt;What is the expected behavior we should see if the code runs normally?&lt;/LI&gt;&lt;LI&gt;How many systems/clients are affected by the issue?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;As well, could you please provide a video showing the issue or how to run the app/codes?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Steven G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 10 Aug 2022 18:18:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407426#M109143</guid>
      <dc:creator>Steven_Intel</dc:creator>
      <dc:date>2022-08-10T18:18:18Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407536#M109151</link>
      <description>&lt;P&gt;Hello Steven,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Yes, it's a custom application created by me, the only purpose is to reproduce the issue.&lt;/LI&gt;
&lt;LI&gt;I attached a ready-to-use VisualStudio sample in my first post, just open it and run the application to reproduce the exception.&lt;/LI&gt;
&lt;LI&gt;I don't have 11th or 12th generation graphics to test it, sorry.&lt;/LI&gt;
&lt;LI&gt;The expected behavior is just not to crash.&lt;/LI&gt;
&lt;LI class="sub_section_element_selectors"&gt;I don't know, most of our client uses a&amp;nbsp;&lt;SPAN&gt;different type of graphics adapters that don't have the issue.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Simone&lt;/P&gt;</description>
      <pubDate>Thu, 11 Aug 2022 07:19:52 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407536#M109151</guid>
      <dc:creator>simonem</dc:creator>
      <dc:date>2022-08-11T07:19:52Z</dc:date>
    </item>
    <item>
      <title>Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407961#M109177</link>
      <description>&lt;P&gt;Thank you for the information.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are going to keep working on this issue. As soon as I have an update, I will let you know.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Steven G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 12 Aug 2022 18:08:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1407961#M109177</guid>
      <dc:creator>Steven_Intel</dc:creator>
      <dc:date>2022-08-12T18:08:01Z</dc:date>
    </item>
    <item>
      <title>Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1408318#M109214</link>
      <description>&lt;P&gt;Hello simonem,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;So we can continue and replicate the issue, could you please provide the step by step? We need to know how and where should we run the command.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Steven G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Aug 2022 20:24:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1408318#M109214</guid>
      <dc:creator>Steven_Intel</dc:creator>
      <dc:date>2022-08-15T20:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1408481#M109221</link>
      <description>&lt;P&gt;As I said&amp;nbsp;&lt;SPAN&gt;just open and start the application attached in my first post, have you tried it?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I attached a small video showing the issue.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 16 Aug 2022 07:29:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1408481#M109221</guid>
      <dc:creator>simonem</dc:creator>
      <dc:date>2022-08-16T07:29:54Z</dc:date>
    </item>
    <item>
      <title>Re:Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1408912#M109251</link>
      <description>&lt;P&gt;Thank you for your response.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are going to work on this issue. As soon as I have an update, I will let you know.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Steven G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 17 Aug 2022 17:51:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1408912#M109251</guid>
      <dc:creator>Steven_Intel</dc:creator>
      <dc:date>2022-08-17T17:51:32Z</dc:date>
    </item>
    <item>
      <title>Re: Access Violation on glReadPixels() with Intel UHD Graphics</title>
      <link>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1413478#M109645</link>
      <description>&lt;P&gt;&lt;STRIKE&gt;Is there any news? Did you replicate the exception?&lt;/STRIKE&gt;&lt;/P&gt;
&lt;P&gt;Sorry, I saw now that you have emailed me but the message ended up in SPAM folder.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;Best Regards,&lt;/P&gt;
&lt;P class="sub_section_element_selectors"&gt;Simone&lt;/P&gt;</description>
      <pubDate>Thu, 08 Sep 2022 10:06:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Graphics/Access-Violation-on-glReadPixels-with-Intel-UHD-Graphics/m-p/1413478#M109645</guid>
      <dc:creator>simonem</dc:creator>
      <dc:date>2022-09-08T10:06:34Z</dc:date>
    </item>
  </channel>
</rss>

