<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Intel Communities: Message List</title>
    <link>http://communities.intel.com/index.jspa?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Tue, 01 May 2012 00:25:19 GMT</pubDate>
    <generator>Jive SBS 5.0.2.0  (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2012-05-01T00:25:19Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Monitor sleep leads to constant "device connect" / "device disconnect" sounds (and other very annoying issues)</title>
      <link>http://communities.intel.com/message/155250?tstart=0#155250</link>
      <description>&lt;!-- [DocumentBodyStart:1fb82641-29db-4a8c-8661-47ee6f24a70c] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;I am having the exact same issue.&amp;nbsp; If I forget to turn my primary HP monitor off before the dual monitors go to sleep, the graphics subsystem disconnects and reconnects the device over and over.&amp;nbsp; After hours of this, eventually system usually blue screens.&amp;nbsp; So, it's effectively impossible to have a stable, always-on system without excessive power consumption.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The primary monitor has been used with several other Windows 7 systems, with Nvidia and Radion drivers, with no problem.&amp;nbsp; I'm using Core i5-2500K CPU.&amp;nbsp; Have tried many different versions of HD 3000 Graphics drivers.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;span style="color: #ff0000; font-size: 14pt;"&gt;&lt;strong&gt;How hard would it be for Intel to add a driver option to disable automatic monitor detection?&amp;nbsp; This seems to be the standard practice, and it would not require Intel to test the driver with many different monitor models.&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;I am extremely discouraged about Intel as a result of the lack of support or any attention to this issue.&amp;nbsp;&amp;nbsp; &lt;/strong&gt;&lt;img height="16px" src="http://communities.intel.com/5.0.2/images/emoticons/sad.gif" width="16px"/&gt;&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:1fb82641-29db-4a8c-8661-47ee6f24a70c] --&gt;</description>
      <pubDate>Tue, 01 May 2012 00:25:19 GMT</pubDate>
      <author>webadmin@intel.com</author>
      <guid>http://communities.intel.com/message/155250?tstart=0#155250</guid>
      <dc:date>2012-05-01T00:25:19Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
  </channel>
</rss>

