<?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:BSOD with eGPU on Lunar Lake in Mobile and Desktop Processors</title>
    <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1715396#M85730</link>
    <description>&lt;P&gt;Hey Jed:&lt;/P&gt;&lt;P&gt;Apologies, I just moved to a new residence. I've been pretty busy and haven't had a chance to unpack my setup yet, I will provide you with event logs, etc. when I have the chance.&lt;/P&gt;&lt;P&gt;I can confirm that the system works without the eGPU connected, and while Lenovo isn't in the business of certifying individual eGPU enclosures, the general use case of eGPUs is supported.&lt;/P&gt;</description>
    <pubDate>Fri, 05 Sep 2025 19:23:31 GMT</pubDate>
    <dc:creator>rcyyz</dc:creator>
    <dc:date>2025-09-05T19:23:31Z</dc:date>
    <item>
      <title>BSOD with eGPU on Lunar Lake</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1712413#M85598</link>
      <description>&lt;P&gt;I am on a ThinkPad X1 Carbon 13th gen. I have an eGPU (Radeon 6700XT) connected via an enclosure and Thunderbolt 4 (Intel certified cable). When booting with the eGPU connected, it runs for a while before BSODing, especially when handling intensive graphics workloads like games.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After an investigation of the event viewer, it seems that a WHEA_UNCORRECTABLE_ERROR causes the BSOD, which is preceded by a flurry of WHEA code 17, indicating corrected errors, all stemming from the eGPU.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A Reddit search indicated that running&amp;nbsp;&lt;SPAN&gt;bcdedit /set {current} pciexpress forcedisable as administrator fixes the issue, and it worked for me, but this disables the integrated Intel GPU, so it's a shoddy workaround at best.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The eGPU works fine on my old laptop. These people seem to have had similar issues to mine on the same architecture, which is why I suspect this may be an Intel problem:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.intel.com/t5/Thunderbolt-Share/Lunar-lake-PCIE-Crash-while-connecting-EGPU/m-p/1687702#M145" target="_blank" rel="noopener"&gt;Lunar lake PCIE Crash while connecting EGPU - Intel Community&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.reddit.com/r/eGPU/comments/1jyewob/a_fix_for_whea_log_17_errors/" target="_blank" rel="noopener"&gt;A fix for WHEA log 17 errors! : eGPU&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am available to provide any dump files, event logs etc on request.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can also confirm that I've installed all relevant driver/OS updates from Microsoft, Intel, Lenovo, AMD, etc.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Aug 2025 04:11:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1712413#M85598</guid>
      <dc:creator>rcyyz</dc:creator>
      <dc:date>2025-08-29T04:11:50Z</dc:date>
    </item>
    <item>
      <title>Re:BSOD with eGPU on Lunar Lake</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1714353#M85664</link>
      <description>&lt;P&gt;Hello rcyyz,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for posting on Intel Community Forum.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To address your concern properly, please share the information below.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Have you contacted Lenovo to see if your current set up is supported?&lt;/P&gt;&lt;P&gt;2. Do the system work when the eGPU is not connected?&lt;/P&gt;&lt;P&gt;3. Kindly share the Event Logs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Additionally, to have a better understanding of your system configuration and components please generate System Support Utility (SSU) report. Please follow instructions here and send the report -&amp;nbsp;&lt;A href="https://www.intel.com/content/www/us/en/support/articles/000057926/memory-and-storage.html" rel="noopener noreferrer" target="_blank"&gt;&lt;EM&gt;How to get the Intel® System Support Utility Logs on Windows*&lt;/EM&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I look forward to your response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Jed G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 01 Sep 2025 05:56:16 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1714353#M85664</guid>
      <dc:creator>JedG_Intel</dc:creator>
      <dc:date>2025-09-01T05:56:16Z</dc:date>
    </item>
    <item>
      <title>Re:BSOD with eGPU on Lunar Lake</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1715044#M85704</link>
      <description>&lt;P&gt;Hello rcyyz,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I wanted to check if you had the chance to review the questions I posted. Please let me know at your earliest convenience so that we can determine the best course of action to resolve this matter.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Jed G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 04 Sep 2025 05:14:19 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1715044#M85704</guid>
      <dc:creator>JedG_Intel</dc:creator>
      <dc:date>2025-09-04T05:14:19Z</dc:date>
    </item>
    <item>
      <title>Re: Re:BSOD with eGPU on Lunar Lake</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1715396#M85730</link>
      <description>&lt;P&gt;Hey Jed:&lt;/P&gt;&lt;P&gt;Apologies, I just moved to a new residence. I've been pretty busy and haven't had a chance to unpack my setup yet, I will provide you with event logs, etc. when I have the chance.&lt;/P&gt;&lt;P&gt;I can confirm that the system works without the eGPU connected, and while Lenovo isn't in the business of certifying individual eGPU enclosures, the general use case of eGPUs is supported.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Sep 2025 19:23:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1715396#M85730</guid>
      <dc:creator>rcyyz</dc:creator>
      <dc:date>2025-09-05T19:23:31Z</dc:date>
    </item>
    <item>
      <title>Re:BSOD with eGPU on Lunar Lake</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1715645#M85742</link>
      <description>&lt;P&gt;Hello rcyyz,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for the update. We would appreciate it if you could share the reports at your earliest convenience, as this will enable us to proceed with a thorough investigation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I look forward to your response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Jed G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Sep 2025 05:46:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1715645#M85742</guid>
      <dc:creator>JedG_Intel</dc:creator>
      <dc:date>2025-09-08T05:46:41Z</dc:date>
    </item>
    <item>
      <title>Re:BSOD with eGPU on Lunar Lake</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1716303#M85778</link>
      <description>&lt;P&gt;Hi rcyyz,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I'm checking to see if there are any updates on the reports? Kindly provide it at your earliest convenience so we can investigate the matter.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Jed G.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 11 Sep 2025 03:39:43 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1716303#M85778</guid>
      <dc:creator>JedG_Intel</dc:creator>
      <dc:date>2025-09-11T03:39:43Z</dc:date>
    </item>
    <item>
      <title>Re:BSOD with eGPU on Lunar Lake</title>
      <link>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1717015#M85836</link>
      <description>&lt;P&gt;Hi &lt;STRONG&gt;rcyyz&lt;/STRONG&gt;,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;As we have not received a response from you, we will now proceed to close this inquiry. Please note that this thread will no longer be monitored.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;If you still require assistance or have any further questions, we kindly ask that you submit a new inquiry through our support channels or community forum, and we will be happy to assist you.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thank you for contacting Intel Customer Support, and we appreciate your understanding.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt; &amp;nbsp;&lt;/P&gt;&lt;P&gt;Patrick V.&lt;/P&gt;&lt;P&gt;Intel Customer Support Technician&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 15 Sep 2025 09:16:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Mobile-and-Desktop-Processors/BSOD-with-eGPU-on-Lunar-Lake/m-p/1717015#M85836</guid>
      <dc:creator>PatrickV_Intel</dc:creator>
      <dc:date>2025-09-15T09:16:02Z</dc:date>
    </item>
  </channel>
</rss>

