<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - ESXi: Upgrading memory on host causes BSoD in windows VMs</title>
    <link>http://communities.vmware.com/community/vmtn/vi/esxi3.5?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Thu, 23 Oct 2008 13:59:41 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-10-23T13:59:41Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: ESXi: Upgrading memory on host causes BSoD in windows VMs</title>
      <link>http://communities.vmware.com/message/1082149?tstart=0#1082149</link>
      <description>&lt;br /&gt;
Hi&lt;br /&gt;
&lt;p /&gt;
Glad I could be of help!&lt;br /&gt;
&lt;br /&gt;
I have 2 ESXi servers at the moment, one with mixed memory DIMMS and I have not seen any issues as yet. &lt;br /&gt;
&lt;p /&gt;
Anytime I do have issues with any system running any OS, I start by simplifying the situation by removing complications such as mixed memory, addition adaptor cards, device drivers etc. By using this method you should be able to isolate the issue. &lt;img class="jive-emoticon" border="0" src="http://communities.vmware.com/images/emoticons/happy.gif" alt=":)" /&gt;&lt;br /&gt;
&lt;br /&gt;
Regards&lt;br /&gt;
Leafy911&lt;br /&gt;
&lt;br /&gt;
(Dont forget you recieve points when you award points)</description>
      <pubDate>Thu, 23 Oct 2008 13:59:41 GMT</pubDate>
      <author>Leafy911</author>
      <guid>http://communities.vmware.com/message/1082149?tstart=0#1082149</guid>
      <dc:date>2008-10-23T13:59:41Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: ESXi: Upgrading memory on host causes BSoD in windows VMs</title>
      <link>http://communities.vmware.com/message/1082075?tstart=0#1082075</link>
      <description>&lt;br /&gt;
Based on your suggestion and my planned activity to upgrade memory to 4x4GB=16GB, the problem has been fixed.&lt;br /&gt;
&lt;p /&gt;
2x2GB and 2x4GB together was causing the issue. Once I replaced the 2x2GB with 2x4GB, as i have planned, problem was gone. &lt;br /&gt;
&lt;p /&gt;
Conclusion:&lt;br /&gt;
&lt;p /&gt;
Even though the Memory was from the same vendor (OCZ) and same speed 800MHz, it (ESXi)  does not like different density (example: 2GB and 4GB) sticks put together&lt;br /&gt;
&lt;p /&gt;
 Hope, it will help other people as well.&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;</description>
      <pubDate>Thu, 23 Oct 2008 13:14:57 GMT</pubDate>
      <author>kuldipsingh</author>
      <guid>http://communities.vmware.com/message/1082075?tstart=0#1082075</guid>
      <dc:date>2008-10-23T13:14:57Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: ESXi: Upgrading memory on host causes BSoD in windows VMs</title>
      <link>http://communities.vmware.com/message/1081245?tstart=0#1081245</link>
      <description>&lt;br /&gt;
As far as I know ESX is very sensitive when it comes to memory and wil PSOD if there is an issue, so I find it strange to hear that on the VMs on top of it are affected. Have you tried using just the 2 x 4GB sticks to see what would happen?&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
Regards&lt;br /&gt;
Leafy911&lt;br /&gt;
&lt;br /&gt;
(Dont forget you recieve points when you award points)</description>
      <pubDate>Wed, 22 Oct 2008 15:35:07 GMT</pubDate>
      <author>Leafy911</author>
      <guid>http://communities.vmware.com/message/1081245?tstart=0#1081245</guid>
      <dc:date>2008-10-22T15:35:07Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>ESXi: Upgrading memory on host causes BSoD in windows VMs</title>
      <link>http://communities.vmware.com/message/1081130?tstart=0#1081130</link>
      <description>&lt;br /&gt;
I am facing a strange issue (at least to me) of Blue Screen of Death in Windows Server 2003 VMs.&lt;br /&gt;
&lt;p /&gt;
Description: My esxi host has 4x 2GB = 8GB memory and I decided to replace 2 x2GB sticks with 2x4GB sticks making total of (2x2GB + 2x $GB) = 12GB. However, this whole thing caused a grief for me.&lt;br /&gt;
&lt;p /&gt;
My esxi host booted up fine and it shows 12GB of memory and every thing was great. However, as soon as I started windows server 2003 and windows 2008 based VMs I see BSoD. See the picture attached.&lt;br /&gt;
&lt;p /&gt;
Few key points to note:&lt;br /&gt;
&lt;p /&gt;
1) I have 3 VMs. One windows 2003 and two windows 2008 based. &lt;br /&gt;
&lt;p /&gt;
2) VMs I have seen the issue are on the same DATA Store. &lt;br /&gt;
&lt;p /&gt;
3) If I only start any 1 VM out of 3, it boots up fine.&lt;br /&gt;
&lt;p /&gt;
4) As soon as I try to boot any of the remaining two, I see the BSoD on the VM which was already up and running. I have never seen BSoD if windows was up and running. I have always seen it during the booting of the windows but not if windows was up and running.&lt;br /&gt;
&lt;p /&gt;
5) Please find the screen shot of BDoD.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
Please help!</description>
      <pubDate>Wed, 22 Oct 2008 14:11:08 GMT</pubDate>
      <author>kuldipsingh</author>
      <guid>http://communities.vmware.com/message/1081130?tstart=0#1081130</guid>
      <dc:date>2008-10-22T14:11:08Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
  </channel>
</rss>

