<?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 ProLiant Gen8 stuck at post (code 0114) in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-gen8-stuck-at-post-code-0114/m-p/7204672#M184941</link>
    <description>&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;ProLiant Gen8 stuck at post (code 0114)&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;I bought a secondhand Proliant Gen8 microserver which cannot seem to boot and stays stuck at 90% post with message "Memory and QPI Link Initialization Start" and status code&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;0114&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After I replaced the CPU G1610T with E3-1220L V2, it would not boot, but it was working fine before.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I read this must be related to the DIMMS so I have tried removing one of the two dimms, swaping them, tried all slots and combinations with no luck.&lt;/P&gt;&lt;P&gt;&lt;FONT&gt;&lt;SPAN&gt;I also read that the system does not support registered dimms. However, my dimms (which look like they are the default certified hp) have this reference: 4&lt;/SPAN&gt;&lt;STRONG&gt;GB 1RX8 PC3L-12800E-11-13-D1&lt;/STRONG&gt;&lt;SPAN&gt;. If I read this correctly, this means the dimms&amp;nbsp;&lt;/SPAN&gt;&lt;U&gt;are&lt;/U&gt;&lt;SPAN&gt;&amp;nbsp;udimm memory and thus compatible with the system.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;I have checked the CPU for a bent pin but everything looked fin. Also cleaned it just in case.&lt;/P&gt;&lt;P&gt;I also have access to the ILO.&lt;/P&gt;&lt;P&gt;Anyone would have a clue about my issue? Is there a chance I bought the wrong rams? Can the problem come from somewhere else?&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Thu, 18 Jan 2024 10:33:31 GMT</pubDate>
    <dc:creator>nmonarcha</dc:creator>
    <dc:date>2024-01-18T10:33:31Z</dc:date>
    <item>
      <title>ProLiant Gen8 stuck at post (code 0114)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-gen8-stuck-at-post-code-0114/m-p/7204672#M184941</link>
      <description>&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;ProLiant Gen8 stuck at post (code 0114)&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;I bought a secondhand Proliant Gen8 microserver which cannot seem to boot and stays stuck at 90% post with message "Memory and QPI Link Initialization Start" and status code&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;0114&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After I replaced the CPU G1610T with E3-1220L V2, it would not boot, but it was working fine before.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I read this must be related to the DIMMS so I have tried removing one of the two dimms, swaping them, tried all slots and combinations with no luck.&lt;/P&gt;&lt;P&gt;&lt;FONT&gt;&lt;SPAN&gt;I also read that the system does not support registered dimms. However, my dimms (which look like they are the default certified hp) have this reference: 4&lt;/SPAN&gt;&lt;STRONG&gt;GB 1RX8 PC3L-12800E-11-13-D1&lt;/STRONG&gt;&lt;SPAN&gt;. If I read this correctly, this means the dimms&amp;nbsp;&lt;/SPAN&gt;&lt;U&gt;are&lt;/U&gt;&lt;SPAN&gt;&amp;nbsp;udimm memory and thus compatible with the system.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;I have checked the CPU for a bent pin but everything looked fin. Also cleaned it just in case.&lt;/P&gt;&lt;P&gt;I also have access to the ILO.&lt;/P&gt;&lt;P&gt;Anyone would have a clue about my issue? Is there a chance I bought the wrong rams? Can the problem come from somewhere else?&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 18 Jan 2024 10:33:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-gen8-stuck-at-post-code-0114/m-p/7204672#M184941</guid>
      <dc:creator>nmonarcha</dc:creator>
      <dc:date>2024-01-18T10:33:31Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant Gen8 stuck at post (code 0114)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-gen8-stuck-at-post-code-0114/m-p/7204769#M184962</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;You may refer to knowledge base article "&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=kc0112440en_us" target="_blank" rel="noopener"&gt;HPE ProLiant SL270s Gen8 Server - Server May Halt on Pre POST Screen with No Display After Updating BIOS to 09/08/2013&lt;/A&gt;". Though this talks about a BIOS update to HPE ProLiant SL270s Gen8 Server, the solution involves performing a cold boot. Hence, please review this article and perform the recommendation and see if it helps.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 06:11:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-gen8-stuck-at-post-code-0114/m-p/7204769#M184962</guid>
      <dc:creator>TVVJ</dc:creator>
      <dc:date>2024-01-18T06:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: ProLiant Gen8 stuck at post (code 0114)</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-gen8-stuck-at-post-code-0114/m-p/7204967#M185021</link>
      <description>&lt;P&gt;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1272627"&gt;@TVVJ&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I try it,but it can't work.4010 0128 0114 POST codes shown repeatedly on iLO4 status bar.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2024 07:10:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-gen8-stuck-at-post-code-0114/m-p/7204967#M185021</guid>
      <dc:creator>nmonarcha</dc:creator>
      <dc:date>2024-01-22T07:10:37Z</dc:date>
    </item>
  </channel>
</rss>

