<?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 370 in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902015#M15206</link>
    <description>I have a ML-370 that has just started rebooting for no apparent reason. It has NT 4 and SP6 plus the latest patches and hot fixes. When it does re-boot it shows nothing obvious in the event log. Seems that every time it does happen I get the following error, and I hope someone can help me on this one.&lt;BR /&gt;&lt;BR /&gt;Event ID: 4188&lt;BR /&gt;&lt;BR /&gt;The Compaq System Management Driver has detected that the system&lt;BR /&gt;encountered an NT bugcheck prior to this boot.  The&lt;BR /&gt;bugcheck data was: STOP: 0x000000DE (0x00000002, 0xE1619594, 0xFFFFFFFF, 0xE224CA48).&lt;BR /&gt;</description>
    <pubDate>Tue, 11 Feb 2003 18:25:26 GMT</pubDate>
    <dc:creator>Dan DeVEcka</dc:creator>
    <dc:date>2003-02-11T18:25:26Z</dc:date>
    <item>
      <title>Proliant 370</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902015#M15206</link>
      <description>I have a ML-370 that has just started rebooting for no apparent reason. It has NT 4 and SP6 plus the latest patches and hot fixes. When it does re-boot it shows nothing obvious in the event log. Seems that every time it does happen I get the following error, and I hope someone can help me on this one.&lt;BR /&gt;&lt;BR /&gt;Event ID: 4188&lt;BR /&gt;&lt;BR /&gt;The Compaq System Management Driver has detected that the system&lt;BR /&gt;encountered an NT bugcheck prior to this boot.  The&lt;BR /&gt;bugcheck data was: STOP: 0x000000DE (0x00000002, 0xE1619594, 0xFFFFFFFF, 0xE224CA48).&lt;BR /&gt;</description>
      <pubDate>Tue, 11 Feb 2003 18:25:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902015#M15206</guid>
      <dc:creator>Dan DeVEcka</dc:creator>
      <dc:date>2003-02-11T18:25:26Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant 370</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902016#M15207</link>
      <description>Does it occur at any specific time, say when starting a backup?  How often does it occur?  Any changes to the system?</description>
      <pubDate>Tue, 11 Feb 2003 18:30:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902016#M15207</guid>
      <dc:creator>Theo Hill_1</dc:creator>
      <dc:date>2003-02-11T18:30:27Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant 370</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902017#M15208</link>
      <description>It has not had any rime or reason to when it happens, and no changes have been made.&lt;BR /&gt;&lt;BR /&gt;It started 1/15/03 then 1/30/30 and 2/11/03&lt;BR /&gt;</description>
      <pubDate>Tue, 11 Feb 2003 18:34:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902017#M15208</guid>
      <dc:creator>Dan DeVEcka</dc:creator>
      <dc:date>2003-02-11T18:34:10Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant 370</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902018#M15209</link>
      <description>Do you remember adding any patches or anything around the time it first happened?&lt;BR /&gt;&lt;BR /&gt;If you don't want to call Microsoft on this one, you could always try to anaylze the memory dump (if one was created).  The easiest way would be to use DUMPCHK.EXE and PSTAT.EXE.  Those will give you the module that initiated the bugcheck, and then you can take it from there.&lt;BR /&gt;&lt;BR /&gt;You can find info on these pretty much anythere on the web.</description>
      <pubDate>Tue, 11 Feb 2003 20:47:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902018#M15209</guid>
      <dc:creator>Tom Mucha_1</dc:creator>
      <dc:date>2003-02-11T20:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant 370</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902019#M15210</link>
      <description>Same error here with brandnew&lt;BR /&gt;ML370 G3, NT4 SP6, Smart Array 532. First Reboot appeared 14 days after isntallation.</description>
      <pubDate>Thu, 27 Feb 2003 21:30:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902019#M15210</guid>
      <dc:creator>thomas strienz</dc:creator>
      <dc:date>2003-02-27T21:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant 370</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902020#M15211</link>
      <description>Thomas,&lt;BR /&gt;&lt;BR /&gt;Is you server patched via Microsoft? I will get back to you on what patch may be the problem. I just don't remember the exact numer at this time.</description>
      <pubDate>Thu, 27 Feb 2003 21:50:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902020#M15211</guid>
      <dc:creator>Dan DeVEcka</dc:creator>
      <dc:date>2003-02-27T21:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant 370</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902021#M15212</link>
      <description>Only fix installed&lt;BR /&gt; is Q328970 for IE 5.5 SP2</description>
      <pubDate>Sat, 08 Mar 2003 19:20:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/proliant-370/m-p/2902021#M15212</guid>
      <dc:creator>thomas strienz</dc:creator>
      <dc:date>2003-03-08T19:20:03Z</dc:date>
    </item>
  </channel>
</rss>

